# Who should approve utilities and energy invoices? > Utility invoices need two approvers, not one: facilities checks usage, procurement or AP checks the rate against contract. Here is how to split it. Source: https://valuexpa.com/insights/who-should-approve-utilities-and-energy-invoices Publisher: ValueXPA (https://valuexpa.com) Updated: 2026-09-07 --- Margin drift is the gap between what a vendor contract says and what the invoice actually charges. On a utilities and energy bill, that gap hides inside a meter read, a rate tier, a demand charge or a surcharge line that nobody on the approval chain is positioned to check. Utility invoices usually get one approver: whoever in AP has authority to release the payment. That person can confirm the bill arrived and the amount looks like last month's. They cannot confirm the rate schedule applied is the one in the contract, or that the demand charge reflects an actual load event rather than a meter error. ## Executive Summary Utilities and energy invoices get routed to accounts payable and approved on receipt because the amount looks stable month to month. That stability is the problem. A meter read, a rate schedule, a demand charge and a power factor penalty can each move independently, and none of them show up on a purchase order the way a shipment or a service ticket does. AP has no PO to match against and no engineering context to judge a demand spike, so the invoice clears on pattern recognition rather than verification. The fix is not moving approval to one person. It is splitting the approval into two questions answered by two different roles: does the usage make sense, and does the rate applied match the contract or tariff on file. A facilities or operations owner who knows the plant's actual load answers the first. Someone with the utility contract or the tariff schedule in hand, whether that is AP, procurement or a controller, answers the second. Neither role alone can catch what the other misses. What changes outcomes is putting both signatures on the same invoice before it pays, not after a variance shows up in the monthly close. A stated basis for every check, not a rubber stamp based on last month's total, is what turns approval into an actual control. ## 1. Who is actually approving utilities invoices today? **In most AP workflows, a single approver with payment authority signs off on utility invoices, the same person who approves any recurring vendor bill. They check that the invoice exists, that the vendor is on file and that the amount is within a normal range of prior months. They are not given the rate schedule, the tariff class or the facility's metered load, so a rate error or a misapplied demand charge passes through looking exactly like a normal bill.** This single-approver pattern exists because utility bills are treated as fixed cost rather than variable spend. A freight invoice gets checked against a rate card because freight teams expect variance. A utility bill gets treated like rent: a number that repeats until it doesn't. That assumption breaks down for a few reasons. Rate schedules change when a utility revises tariffs. Demand charges depend on a 15- or 30-minute peak that can be driven by a single equipment startup. Power factor penalties depend on load characteristics the AP approver never sees. None of these show up as a variance flag in a standard AP workflow, because the total invoice amount can still land close to a prior period even when a component of it is wrong. The result is an approval that verifies the bill was received and paid on time, not that the charge was correct. The pattern repeats across other indirect categories too, each with its own version of a check that never happens. ## 2. Why doesn't a single AP approver catch rate errors? **An AP approver checks an invoice against a payment schedule and a vendor master file. Neither document contains the tariff class, the rate tier boundaries, or the contract's demand charge formula. Without that reference, a rate error looks identical to a correct invoice: both are a number that resembles last month's. The approver has no independent basis to challenge the figure and no reason to, because nothing in their view of the transaction flags a discrepancy.** AP's job in most organizations is matching, not interpreting. A three-way match confirms an invoice against a purchase order and a receipt. Utility invoices rarely route through that process at all, because there is no purchase order for electricity delivered to a meter. The invoice arrives, gets coded to a utilities expense account and gets paid. That gap is structural, not a training issue. Even a diligent AP approver reading the invoice line by line cannot tell whether a demand charge of a given size reflects the contract's rate structure without the tariff document open next to it. Nobody hands them that document as part of the standard workflow. This is one of the six categories where invoice-to-contract drift accumulates, covered in full in [indirect spend audit categories](/guides/indirect-spend-audit-categories). ## 3. Who should approve the usage side of the invoice? **The usage side of a utility invoice, meaning whether the kWh consumed, the peak demand recorded or the therms billed match what the facility actually ran, belongs with facilities, operations or plant engineering. They know when a line was down, when a new piece of equipment started up, or when a shift schedule changed. That context is what turns a demand spike from an unexplained number into an explainable one, or flags it as a meter or billing error worth.** A facilities lead who reviews the invoice against a maintenance log or a production schedule can answer a question AP cannot: did the plant actually draw that much power in that window. If a demand charge jumps and nothing in the plant's operation explains it, that is a signal to request the utility's interval data before paying, not after. This role does not need to own the payment decision. It needs a defined checkpoint: a sign-off field on the invoice or a routing step that asks a facilities contact to confirm usage looks consistent with plant activity before the invoice moves to payment approval. ## 4. Who should approve the rate and contract side? **The rate and contract side, meaning whether the tariff class, rate tier, demand charge formula and any surcharges match the utility contract or the applicable tariff schedule on file, belongs with whoever holds that contract: procurement, a controller, or an AP lead who has been given the tariff document. This check does not require engineering knowledge. It requires the contract in hand and a line-by-line comparison against the invoice's rate section.** Utility contracts and tariffs specify a rate structure: a base charge, a per-unit energy rate, a demand charge formula and sometimes a power factor penalty threshold. Each of these can be checked against the invoice without knowing anything about the plant's operations. The person who does this does not need to be senior. They need the document and a recurring reason to open it. A rate schedule that was correct at contract signing can go stale if the utility revises tariffs or the account gets reclassified into a different rate tier, and nothing in the invoice itself announces that change. 2% year over year, which is the kind of underlying cost movement a stale contract reference can miss entirely. ### A. What the rate reviewer checks The rate reviewer confirms the tariff class matches the contract, the per-unit rate matches the current schedule, the demand charge formula is applied correctly against the metered peak, and any surcharge or adjustment line has a stated basis rather than appearing as a flat add-on. ### B. What the rate reviewer does not need This review does not require site access, equipment knowledge or production data. It is a document comparison: contract terms against invoice terms, which is why it can sit with procurement or AP once they are given the reference document facilities already has no reason to hold. ## 5. Can one person hold both approvals? **One person can hold both approvals only if they have both the plant's operational context and the utility contract in hand at the time of review, which is uncommon outside small single-site operations. At most manufacturers, usage knowledge sits with facilities and contract knowledge sits with procurement or finance. Splitting the check across two roles costs one additional sign-off step and closes the gap that a single generalist approver leaves open.** Combining both checks in one role is not wrong in principle. It fails in practice because the two checks draw on different information sources that live in different departments, and keeping both current for every metered account across multiple sites is a maintenance burden that tends to fall to whichever check is easier: the AP approver's glance at the total. A two-signature approval does not need to be slow. Facilities confirms usage looks consistent with operations, procurement or AP confirms the rate matches contract, and the invoice pays once both are on record. The added step is a checkbox and a name, not a committee. ## 6. How should this approval be documented? **Each utility invoice should carry two recorded sign-offs before payment: a usage confirmation naming who reviewed it and against what reference (a production log, a maintenance record), and a rate confirmation naming who reviewed it and against which contract or tariff version. Recording the basis, not just a name, is what makes the approval auditable later and what lets a controller spot which invoices were rubber-stamped versus actually checked.** A sign-off without a stated basis is indistinguishable from no review at all when someone asks about it six months later. Recording that facilities checked usage against the maintenance log for that period, and that AP checked the rate against the current tariff schedule on file, turns the approval into evidence rather than a formality. This documentation also does the work of catching contract drift over time. If the rate reviewer's note starts citing an outdated tariff version, that is visible in the record, not buried in an invoice PDF nobody reopens. - **Usage sign-off:** Facilities or operations confirms metered usage against a production or maintenance record for the billing period. - **Rate sign-off:** Procurement, AP or a controller confirms the tariff class and rate structure against the current contract or tariff schedule. - **Basis recorded:** Each sign-off names the document it was checked against, not just the approver's name. - **Escalation trigger:** A demand charge or surcharge with no operational explanation routes to a dispute review before payment, not after. ## 7. What does this look like across multiple sites? **At a multi-site manufacturer, the same two-role split applies at each site, but the rate side benefits from centralizing at least the contract and tariff library so one reviewer isn't reconstructing which schedule applies to which account from memory. Usage review has to stay local, because only the site's facilities team knows what that plant ran. Centralizing only the document reference, not the judgment, is what scales the check without slowing it down.** A company running several plants typically holds several separate utility accounts, each potentially on a different tariff class depending on load size and local rate structure. A rate reviewer covering all sites needs quick access to which contract or tariff applies to which account, otherwise the review becomes a research project every cycle and gets skipped under time pressure. A shared reference, whether a spreadsheet or a contract repository, that maps each account to its current rate schedule removes that friction. It does not replace the local usage check, which still depends on someone at the plant knowing what ran that month. For the full breakdown of what an audit of this category covers end to end, see how do you audit utilities and energy invoices, and for where utilities sits among the other categories worth checking, see indirect spend audit categories. The same two-role logic applies in adjacent categories: [telecom and connectivity invoices](/answers/how-do-you-audit-telecom-and-connectivity-invoices) carry a similar split between usage and contract review, as do [calibration and safety compliance invoices](/answers/how-do-you-audit-calibration-and-safety-compliance-invoices). For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. ## 8. Frequently Asked Questions (People Also Ask) ### Should AP or facilities approve the electric bill? Neither alone. AP or procurement should confirm the rate and tariff match the contract, while facilities or operations confirms the metered usage matches what the plant actually ran. Splitting the check across both roles catches errors a single approver, working from either the invoice total or a production log alone, would miss. ### Does a utility invoice need a purchase order to be approved properly? No. Utility invoices rarely have a purchase order because they bill against a meter, not an order. The substitute for a PO match is a documented comparison against the contract or tariff schedule on file, done by whoever holds that document, alongside a usage check by whoever knows the plant's operations. ### What should a facilities lead actually check on a utility invoice? Whether the metered usage, kWh, peak demand, or therms billed, is consistent with the facility's actual operations for that period: production schedule, equipment startups, or known downtime. This check does not require reading the rate schedule; it requires knowing what the plant ran. ### Who is responsible for catching a stale rate schedule? Whoever reviews the rate side of the invoice against the current contract or tariff, typically procurement, AP or a controller. This requires having the current tariff version on hand, since a rate that was correct at signing can go stale if the utility revises its schedule. ### Can a small company combine both utility approval roles into one person? Yes, if that person has both the plant's operational context and the current contract or tariff in hand at review time. This is more feasible at a single-site operation than at a multi-site manufacturer, where usage knowledge and contract knowledge typically sit in different departments. ### What happens if a demand charge spikes with no explanation? It should route to a dispute review before payment rather than being approved on the assumption that the total still looks close to prior months. Requesting the utility's interval data for that billing window is the standard way to confirm whether the spike reflects actual load or a meter or billing error. ### Does this two-approval process slow down payment? It adds one additional sign-off step, not a committee. A checkbox and a name from facilities on usage, and a checkbox and a name from procurement or AP on rate, can both be captured within a normal payment cycle if the tariff reference document is already on hand. ### Why doesn't the current AP approval already catch these errors? AP's approval checks that the invoice exists, the vendor is valid and the total resembles prior periods. It does not include the tariff schedule or the plant's usage data, so a rate error or an unexplained demand spike appears identical to a normal, correct invoice. ### Is contract complexity quietly draining your operating margin? A small systematic drift between your negotiated contracts and your actual vendor billing compounds quietly across a year of invoices. Stop guessing at your exposure and run a targeted audit. **[Take the Free Screener → https://valuexpa.com/margin-drift-screener](https://valuexpa.com/margin-drift-screener)** ## Executive Summary Utilities and energy invoices get routed to accounts payable and approved on receipt because the amount looks stable month to month. That stability is the problem. A meter read, a rate schedule, a demand charge and a power factor penalty can each move independently, and none of them show up on a purchase order the way a shipment or a service ticket does. AP has no PO to match against and no engineering context to judge a demand spike, so the invoice clears on pattern recognition rather than verification. The fix is not moving approval to one person. It is splitting the approval into two questions answered by two different roles: does the usage make sense, and does the rate applied match the contract or tariff on file. A facilities or operations owner who knows the plant's actual load answers the first. Someone with the utility contract or the tariff schedule in hand, whether that is AP, procurement or a controller, answers the second. Neither role alone can catch what the other misses. What changes outcomes is putting both signatures on the same invoice before it pays, not after a variance shows up in the monthly close. A stated basis for every check, not a rubber stamp based on last month's total, is what turns approval into an actual control. ## 1. Who is actually approving utilities invoices today? In most AP workflows, a single approver with payment authority signs off on utility invoices, the same person who approves any recurring vendor bill. They check that the invoice exists, that the vendor is on file and that the amount is within a normal range of prior months. They are not given the rate schedule, the tariff class or the facility's metered load, so a rate error or a misapplied demand charge passes through looking exactly like a normal bill. This single-approver pattern exists because utility bills are treated as fixed cost rather than variable spend. A freight invoice gets checked against a rate card because freight teams expect variance. A utility bill gets treated like rent: a number that repeats until it doesn't. That assumption breaks down for a few reasons. Rate schedules change when a utility revises tariffs. Demand charges depend on a 15- or 30-minute peak that can be driven by a single equipment startup. Power factor penalties depend on load characteristics the AP approver never sees. None of these show up as a variance flag in a standard AP workflow, because the total invoice amount can still land close to a prior period even when a component of it is wrong. The result is an approval that verifies the bill was received and paid on time, not that the charge was correct. The pattern repeats across other indirect categories too, each with its own version of a check that never happens. ## 2. Why doesn't a single AP approver catch rate errors? An AP approver checks an invoice against a payment schedule and a vendor master file. Neither document contains the tariff class, the rate tier boundaries, or the contract's demand charge formula. Without that reference, a rate error looks identical to a correct invoice: both are a number that resembles last month's. The approver has no independent basis to challenge the figure and no reason to, because nothing in their view of the transaction flags a discrepancy. AP's job in most organizations is matching, not interpreting. A three-way match confirms an invoice against a purchase order and a receipt. Utility invoices rarely route through that process at all, because there is no purchase order for electricity delivered to a meter. The invoice arrives, gets coded to a utilities expense account and gets paid. That gap is structural, not a training issue. Even a diligent AP approver reading the invoice line by line cannot tell whether a demand charge of a given size reflects the contract's rate structure without the tariff document open next to it. Nobody hands them that document as part of the standard workflow. This is one of the six categories where invoice-to-contract drift accumulates, covered in full in [indirect spend audit categories](/guides/indirect-spend-audit-categories). ## 3. Who should approve the usage side of the invoice? The usage side of a utility invoice, meaning whether the kWh consumed, the peak demand recorded or the therms billed match what the facility actually ran, belongs with facilities, operations or plant engineering. They know when a line was down, when a new piece of equipment started up, or when a shift schedule changed. That context is what turns a demand spike from an unexplained number into an explainable one, or flags it as a meter or billing error worth. A facilities lead who reviews the invoice against a maintenance log or a production schedule can answer a question AP cannot: did the plant actually draw that much power in that window. If a demand charge jumps and nothing in the plant's operation explains it, that is a signal to request the utility's interval data before paying, not after. This role does not need to own the payment decision. It needs a defined checkpoint: a sign-off field on the invoice or a routing step that asks a facilities contact to confirm usage looks consistent with plant activity before the invoice moves to payment approval. ## 4. Who should approve the rate and contract side? The rate and contract side, meaning whether the tariff class, rate tier, demand charge formula and any surcharges match the utility contract or the applicable tariff schedule on file, belongs with whoever holds that contract: procurement, a controller, or an AP lead who has been given the tariff document. This check does not require engineering knowledge. It requires the contract in hand and a line-by-line comparison against the invoice's rate section. Utility contracts and tariffs specify a rate structure: a base charge, a per-unit energy rate, a demand charge formula and sometimes a power factor penalty threshold. Each of these can be checked against the invoice without knowing anything about the plant's operations. The person who does this does not need to be senior. They need the document and a recurring reason to open it. A rate schedule that was correct at contract signing can go stale if the utility revises tariffs or the account gets reclassified into a different rate tier, and nothing in the invoice itself announces that change. 2% year over year, which is the kind of underlying cost movement a stale contract reference can miss entirely. ### A. What the rate reviewer checks The rate reviewer confirms the tariff class matches the contract, the per-unit rate matches the current schedule, the demand charge formula is applied correctly against the metered peak, and any surcharge or adjustment line has a stated basis rather than appearing as a flat add-on. ### B. What the rate reviewer does not need This review does not require site access, equipment knowledge or production data. It is a document comparison: contract terms against invoice terms, which is why it can sit with procurement or AP once they are given the reference document facilities already has no reason to hold. ## 5. Can one person hold both approvals? One person can hold both approvals only if they have both the plant's operational context and the utility contract in hand at the time of review, which is uncommon outside small single-site operations. At most manufacturers, usage knowledge sits with facilities and contract knowledge sits with procurement or finance. Splitting the check across two roles costs one additional sign-off step and closes the gap that a single generalist approver leaves open. Combining both checks in one role is not wrong in principle. It fails in practice because the two checks draw on different information sources that live in different departments, and keeping both current for every metered account across multiple sites is a maintenance burden that tends to fall to whichever check is easier: the AP approver's glance at the total. A two-signature approval does not need to be slow. Facilities confirms usage looks consistent with operations, procurement or AP confirms the rate matches contract, and the invoice pays once both are on record. The added step is a checkbox and a name, not a committee. ## 6. How should this approval be documented? Each utility invoice should carry two recorded sign-offs before payment: a usage confirmation naming who reviewed it and against what reference (a production log, a maintenance record), and a rate confirmation naming who reviewed it and against which contract or tariff version. Recording the basis, not just a name, is what makes the approval auditable later and what lets a controller spot which invoices were rubber-stamped versus actually checked. A sign-off without a stated basis is indistinguishable from no review at all when someone asks about it six months later. Recording that facilities checked usage against the maintenance log for that period, and that AP checked the rate against the current tariff schedule on file, turns the approval into evidence rather than a formality. This documentation also does the work of catching contract drift over time. If the rate reviewer's note starts citing an outdated tariff version, that is visible in the record, not buried in an invoice PDF nobody reopens. 1. Usage sign-off: Facilities or operations confirms metered usage against a production or maintenance record for the billing period. 2. Rate sign-off: Procurement, AP or a controller confirms the tariff class and rate structure against the current contract or tariff schedule. 3. Basis recorded: Each sign-off names the document it was checked against, not just the approver's name. 4. Escalation trigger: A demand charge or surcharge with no operational explanation routes to a dispute review before payment, not after. ## 7. What does this look like across multiple sites? At a multi-site manufacturer, the same two-role split applies at each site, but the rate side benefits from centralizing at least the contract and tariff library so one reviewer isn't reconstructing which schedule applies to which account from memory. Usage review has to stay local, because only the site's facilities team knows what that plant ran. Centralizing only the document reference, not the judgment, is what scales the check without slowing it down. A company running several plants typically holds several separate utility accounts, each potentially on a different tariff class depending on load size and local rate structure. A rate reviewer covering all sites needs quick access to which contract or tariff applies to which account, otherwise the review becomes a research project every cycle and gets skipped under time pressure. A shared reference, whether a spreadsheet or a contract repository, that maps each account to its current rate schedule removes that friction. It does not replace the local usage check, which still depends on someone at the plant knowing what ran that month. For the full breakdown of what an audit of this category covers end to end, see how do you audit utilities and energy invoices, and for where utilities sits among the other categories worth checking, see indirect spend audit categories. The same two-role logic applies in adjacent categories: [telecom and connectivity invoices](/answers/how-do-you-audit-telecom-and-connectivity-invoices) carry a similar split between usage and contract review, as do [calibration and safety compliance invoices](/answers/how-do-you-audit-calibration-and-safety-compliance-invoices). For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. ## Common questions ### Should AP or facilities approve the electric bill? Neither alone. AP or procurement should confirm the rate and tariff match the contract, while facilities or operations confirms the metered usage matches what the plant actually ran. Splitting the check across both roles catches errors a single approver, working from either the invoice total or a production log alone, would miss. ### Does a utility invoice need a purchase order to be approved properly? No. Utility invoices rarely have a purchase order because they bill against a meter, not an order. The substitute for a PO match is a documented comparison against the contract or tariff schedule on file, done by whoever holds that document, alongside a usage check by whoever knows the plant's operations. ### What should a facilities lead actually check on a utility invoice? Whether the metered usage, kWh, peak demand, or therms billed, is consistent with the facility's actual operations for that period: production schedule, equipment startups, or known downtime. This check does not require reading the rate schedule; it requires knowing what the plant ran. ### Who is responsible for catching a stale rate schedule? Whoever reviews the rate side of the invoice against the current contract or tariff, typically procurement, AP or a controller. This requires having the current tariff version on hand, since a rate that was correct at signing can go stale if the utility revises its schedule. ### Can a small company combine both utility approval roles into one person? Yes, if that person has both the plant's operational context and the current contract or tariff in hand at review time. This is more feasible at a single-site operation than at a multi-site manufacturer, where usage knowledge and contract knowledge typically sit in different departments. --- ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms, for $100M+ US industrial manufacturers and distributors. Two to four weeks. The client retains 100% of recoveries. https://valuexpa.com/contact-us