Philippines staffing research · Published · Updated
How utility bill audit cycles shape an outsourced facilities administration desk
A utility bill review checks consistency against a meter, a tariff, and a prior period. The cycle decides whether the desk catches a rate change, a vacancy charge, or a credit before the next bill arrives.

Research findings
A utility bill is a recurring obligation with a complex tariff behind it, and the desk that reviews it is checking consistency, not renegotiating the rate. Meter readings, demand charges, taxes, and riders can change without a change in usage. The audit starts with the account and meter map, because a bill attached to the wrong meter cannot be reviewed. Build that map before the first bill enters the queue. A map built after the first review is a reconstruction, not a control.
Build the account map from the utility's own records and the client's site list. Record the service address, the account number, the meter number, and the rate schedule. Note which sites are vacant, sublet, or shared. A missing meter is a bill that will be paid without review. Reconcile the map with the utility portal each quarter. A new meter should be added before its first bill is paid.
Compare each bill with the prior period and the same month last year. Usage varies with weather and occupancy, so a single month is weak evidence. Look for a change in rate, a new rider, a demand spike, or a charge that appears on every bill. Record the explanation or the question. A blank field should be treated as an open question, not a clean bill.
Set a variance threshold that triggers review. The threshold can be a dollar amount, a percentage, or a change in a specific charge. Write it beside the audit step so the desk does not rely on instinct. A threshold that is too low creates noise; one that is too high misses the error. Test the threshold on a sample of past findings before adopting it.
Late fees and reconnection charges need their own category. They may point to a payment process problem rather than a billing error. Record the date the payment was due, the date it was sent, and the date the utility received it. The desk can show the timeline but should not promise a waiver. Route the waiver request to the client with the timeline attached.
Tariff changes are published by the utility and should be logged with an effective date. A new rider can raise a bill without any change in usage. The desk should flag the change and route the tariff question to the client's facilities or finance owner. Do not recalculate a bill from an assumed rate. Ask the utility or the client's rate consultant for the current tariff.
Discussion
Vacancy and seasonality change the baseline. A vacant site should show minimal usage, and a seasonal site should be compared with the same season. Record the occupancy assumption with the bill. A variance that is explained by vacancy is not an error, but an unexplained charge at a vacant site is. Record the occupancy source and the date it was confirmed.
Utility data can reveal occupancy patterns and personal activity, so treat the bills as confidential. Limit access to the accounts the desk supports and avoid sharing usage detail outside the review. The client's privacy or facilities owner should set the retention period. Share only the usage detail the review needs. Do not send a full bill to a site contact who does not need it.
Recoveries need a claim path and an owner. When the desk finds a probable overcharge, it should assemble the bills, the tariff reference, and a short timeline. The client decides whether to request a refund or a credit. The desk tracks the response and the credit memo. A credit without a memo is still an open claim. The memo should name the bill period and the amount.
Implications and limits
Budget reporting should separate price from volume. A higher bill may come from a rate change, a hotter month, or a leak. Show the drivers in the variance note. A single total hides the action the client can take. Show the price and volume effect in separate lines. A simple bridge from last month to this month is enough. Name the largest driver and the amount it explains.
Measure the audit by findings, recovered credits, repeat errors, and open claims. A low finding rate may mean the bills are clean or the review is shallow. Sample the reviewed bills to check that the steps happened. The count alone does not prove the control works. Sample the reviewer's notes, not only the bill file. A note that says reviewed without a reason is not evidence.
A bill audit cannot guarantee that every charge is correct. It can catch the patterns the desk knows how to check and keep the evidence for the ones it cannot. State that limit in the report. The client should know which tariffs and sites are outside the review. List those exclusions in the service report each month. The client can then decide whether to extend the scope.
Map accounts before auditing bills
Start with the utility portal export and the client's site list. Match every account to a site and a meter, and flag the ones that do not match. Record the rate schedule and the service start date. An account without a site is an orphan that will drift out of the review. Assign the orphan to a person before the next cycle.
Check the map when a site opens, closes, or changes tenant. A closed account that still receives a bill is a common finding. A shared meter needs a written allocation rule from the client. The desk can prepare the map, but the client confirms occupancy and responsibility. The allocation should be approved before the first shared bill is paid. A shared meter without an allocation is a dispute waiting to happen.
Set a variance threshold that triggers review
Choose a threshold the client can defend. It can be a percentage over the prior period, a dollar amount, or a change in a named charge. Apply it consistently and record every exception. A threshold that changes with the reviewer's mood is not a control. Write the threshold in the process guide and apply it to every bill. The guide should say who can approve an exception.
Review the threshold after a season or a tariff change. A threshold that worked in a mild month may miss a summer demand spike. The client's facilities owner should approve the change. Keep the old threshold and the date it changed so the trend stays readable. Report the threshold change with the variance note. Keep the old threshold in the file for comparison.
Route findings to the right owner
A billing error goes to the utility or the client's account manager. A payment problem goes to finance. A leak or a failed meter goes to facilities. Write the routing table into the process so the desk does not send every finding to one inbox. Each route should name a person and a response expectation. A route without a backup fails during leave.
Give each finding an owner, a due date, and a status. Record what was sent and what response came back. A finding that sits in a shared inbox for a month is not an audit result. Escalate when the due date passes. Record the escalation and the new commitment. A finding with no response should appear on the weekly list.
Close the loop on credits
When a credit is approved, compare the amount with the finding and the next bill. Record the credit memo and the period it covers. A credit that is promised but never applied should reopen the finding. Set a follow-up date before closing the row. The follow-up should name the utility contact and the bill period. Close the row only when the credit appears on a bill.
Report recovered credits and open claims to the client each month. Separate the value of the finding from the value recovered, because not every finding becomes a credit. The distinction keeps the report honest and shows where the process is still waiting. Report both figures beside the number of findings. A recovery that arrives without a finding is a different report.
Questions
Can the desk renegotiate a utility rate?
No. The desk reviews bills and routes findings. The client's facilities or finance owner decides whether to dispute a charge or change a rate.
What should trigger a bill review?
A variance above the client's threshold, a new charge, a tariff change, a vacant-site charge, or a late fee. The rule should be written down.
Who owns a refund request?
The client's facilities or finance owner, with the desk preparing the bills and timeline. The desk tracks the response.
How often should accounts be reconciled?
At least quarterly, and whenever a site opens, closes, or changes tenant. The account map should match the active bills.