How to audit facilities and janitorial invoices step by step

Executive Summary

Facilities and janitorial invoices drift because the billing basis, square footage, headcount, service frequency, and consumable add-ons, changes more often than the contract file AP checks against gets updated. A vendor billing correctly against last year's scope is billing incorrectly against this year's building.

The mechanism is simple: an invoice gets approved because the total looks roughly right, not because someone re-tested it against current contract terms. That approval habit is what an audit has to interrupt.

Fixing it requires a specific sequence: assemble every current contract and amendment, rebuild the rate and scope basis vendor by vendor, pull twelve to eighteen months of invoices, test each line against the rebuilt basis, and separate a pattern of drift from a one-time error. What changes afterward is not the audit itself but whether the reference file used for the next invoice matches the building as it actually operates today.

1. Where do you start when auditing facilities and janitorial invoices?

Start with the contract file, not the invoices. Pull every current facilities and janitorial contract, every amendment, every renewal letter, and every side agreement that changed scope, square footage, service frequency, or pricing. Build one master file per vendor listing the rate basis, the billing unit, and the effective date of each term.

Only once that file exists does it make sense to open a single invoice, because without it there is nothing correct to compare the invoice against.

Most facilities contracts accumulate amendments over several years: a scope reduction when a floor was vacated, a frequency change when a shift moved, a rate escalation clause that triggered on a renewal date nobody diaried. Each of these lives in a separate document, often in a different system than the one AP checks.

Collect them all before touching an invoice. If a term cannot be located, mark it unverifiable rather than assuming the invoiced rate is correct. An unverifiable term is itself a finding: it means the current billing basis exists nowhere that AP can check it.

This assembled file becomes the reference every subsequent step compares against. Without it, an invoice audit tests invoices against memory, and memory is not a control.

2. How do you rebuild the correct billing basis for each vendor?

For each vendor, translate the contract language into a specific, checkable number: rate per square foot, rate per unit of frequency, a fixed monthly fee, or a headcount-based charge, along with any minimum, cap, or escalation clause. Note the building's current square footage and service scope from facilities or lease records, not from the vendor's own account notes, since the vendor's notes are the thing being tested.

Contract language is often written in ranges or conditions: a rate that steps up above a certain square footage, a frequency that varies by season, a supply add-on billed only above a usage threshold. Each of these needs to become one specific number or rule that a reviewer can hold an invoice line against.

Cross-check the building facts, square footage, floor count, headcount, against a source independent of the vendor: a lease abstract, a facilities management record, or a floor plan. A vendor invoicing against a square footage figure the client itself never confirmed is a common way outdated scope survives multiple renewals unnoticed.

Document the source and date for every basis figure. This paper trail is what lets someone dispute a vendor's invoice later without relitigating the contract from scratch each time.

A. Rate basis

Convert every pricing clause into an arithmetic rule: dollars per square foot per month, dollars per cleaning event, or a flat fee with a defined scope. Where the contract states a tiered rate, write out each tier and its trigger explicitly rather than trusting a single blended number.

B. Scope basis

Record the exact scope the rate assumes: which floors, which service days, which consumables are included versus billed separately. A janitorial contract that includes restroom supplies at one rate and bills them separately at another is a common source of double coverage if the scope line is not read carefully.

3. How far back should you pull invoices for the audit?

Pull 12 to 18 months of invoices per vendor, across ValueXPA diagnostics a comparable window is used to surface a pattern rather than a single mispriced month. A shorter window can miss a quarterly or annual charge, such as a deep-clean fee or an escalation that only shows once a year, and a single month cannot distinguish a recurring error from a one-time correction already reversed by the vendor.

A window shorter than a year risks missing anything billed less often than monthly: an annual strip-and-wax charge, a seasonal snow or landscaping add-on folded into the facilities line, or a rate escalation that only appears at the renewal anniversary.

Pulling the full window also lets a reviewer separate a systemic issue from a fixed one. If a rate error appears in month three and is corrected by month seven without a credit memo, that is a different finding than the same error persisting for eighteen straight months.

Request invoices as line-item detail, not summary statements. A summary total hides exactly the breakdown the audit needs: which line is the base service, which is a surcharge, and which is a pass-through supply charge.

4. What should each invoice line be tested against?

Test every line on every invoice against the rebuilt billing basis: the rate, the billed unit and quantity, the scope it claims to cover, and any minimum or cap the contract states. Flag a line the moment any one of those four elements does not match, even if the total dollar amount looks unremarkable, because a wrong rate offset by a wrong quantity can still net to a plausible-looking total.

Four checks catch most of what drifts in this category. First, is the rate on the invoice the rate the contract currently states, not a prior rate carried forward past a renewal. Second, does the billed quantity, square footage, unit count, service frequency, match the current scope rather than a stale figure.

Third, is anything billed that the contract scope already includes, such as supplies invoiced separately when the base rate covers them. Fourth, does the invoice respect any stated minimum, cap, or not-to-exceed clause.

A line can pass a total-dollar sanity check and still fail all four of these individually, which is why the total is not a useful screen on its own. Test each line against its specific basis rather than judging the invoice as a whole.

Where a contract states a rebate or credit tied to volume or performance, check separately whether it was ever applied. An unclaimed rebate does not appear as an error on the invoice; it appears as an absence, which is easy to miss without a dedicated check.

5. How do you tell a one-time billing error from a recurring drift pattern?

Line up every flagged exception by vendor and by month across the full review window. A single flagged month with no repeat elsewhere is likely a one-time error, worth a credit request but not a process fix. The same discrepancy appearing across multiple consecutive invoices, or the same type of discrepancy recurring across different vendors, points to a stale reference file or an unmonitored contract term rather than a one-off mistake.

The distinction matters because the fix is different. A one-time error is resolved with a credit memo and closed. A recurring pattern means the vendor's invoice generation process, or the client's own reference file used to approve it, is producing the same wrong number every cycle, and a credit memo only recovers one instance of it while the next invoice repeats the error.

Group exceptions by type as well as by vendor: rate mismatches, scope mismatches, duplicate supply charges, and unapplied credits each point to a different root cause even when they show up on the same invoice.

A recurring pattern is also the strongest evidence for prioritizing which vendor relationship needs a structural fix first, since the recovery value compounds every month it continues uncorrected.

6. How do you close out the audit and prevent the same drift from recurring?

Close each exception with a specific, dated action: a credit memo requested, a contract amendment filed, or a reference file correction logged, not a general note that the vendor was contacted. Then update the billing basis file built in step two so it reflects the corrected terms, and set a review date tied to the vendor's next renewal or amendment rather than leaving the file to go stale again on the same multi-year cycle that created the original drift.

An audit that ends with a list of findings and no tracked resolution has not recovered anything. Each exception needs an owner, a requested dollar amount, and a status: submitted, disputed, credited, or written off with a reason.

The billing basis file is the more durable output. Updating it with the corrected rate, scope, and effective date means the next invoice, and the next reviewer, starts from an accurate reference instead of repeating the reconstruction work done here.

A periodic audit like this one finds what already happened. A forward control tests the next invoice as it arrives, against the same basis file, before payment rather than after. The two are complementary rather than substitutes for each other, and which cadence fits a given facilities spend level is worth deciding deliberately rather than by default.

For the wider pattern this sits inside, start with the margin drift guide. See also the three-way match gap: what your erp structurally cannot see and price file governance: why annual uploads create twelve months of drift.

7. Frequently Asked Questions (People Also Ask)

How often should facilities and janitorial invoices be audited?

There is no single interval that fits every contract, since renewal cycles and amendment frequency vary by vendor. What matters more than the interval is tying the review to actual triggers: a renewal, an amendment, a scope change, or a move, so the billing basis file gets refreshed exactly when the contract terms it depends on change.

What documents do I need before I can start this audit?

Every current contract and amendment for each facilities and janitorial vendor, a source of current building facts such as square footage and floor count independent of the vendor, and line-item invoice detail, not summary statements, for the full review window.

Can this audit be done in a spreadsheet?

Yes, mechanically: a spreadsheet can hold the billing basis file and the line-by-line test results. What it will not do on its own is flag drift automatically as new invoices arrive, or catch a stale reference file before an invoice is approved against it.

What counts as a red flag on a single invoice line?

Any line where the billed rate, quantity, or scope does not match the current contract terms, or where a charge appears that the contract scope already includes. A total that looks reasonable is not evidence the line is correct, since an offsetting error can still produce a plausible total.

Should supply and consumable charges be reviewed separately from the base service rate?

Yes. Many janitorial contracts bundle supplies into the base rate while also permitting certain consumables to be billed separately. Reviewing the two together risks missing double coverage, where an item included in scope is also billed as a pass-through.

What happens if a contract term cannot be located during the review?

Mark it unverifiable rather than assuming the current invoice is correct. An unverifiable term is a finding in itself: it means AP has no current document to check the invoice against, regardless of what the invoice states.

Is this the same process as a three-way match in the ERP?

No. A three-way match checks the invoice against the purchase order and receipt. It does not test whether the rate or scope on the invoice matches current contract terms, which is a separate check this audit performs against the contract file directly.

How do unclaimed rebates get missed in a facilities audit?

A rebate tied to volume or performance does not appear as a wrong number on the invoice. It appears as an absence: a credit that should have posted and did not. Catching it requires a dedicated check against the contract's rebate clause rather than reviewing the invoice total alone.

What should be done with a vendor that shows a recurring pattern of drift?

Prioritize a structural fix over a one-time credit request: update the reference file with the corrected terms, confirm the vendor's invoice generation reflects the current contract, and consider a forward control that tests each new invoice before payment rather than relying on periodic review alone.

Does this general information constitute legal advice on contract disputes?

No. This is general information about an audit process, not legal advice. Any dispute over contract interpretation or a vendor's obligation to issue a credit should be reviewed with legal counsel before formal action is taken.