How to reconcile a facilities vendor statement

Executive Summary

A facilities vendor statement is a summary, not a source document, and paying against the summary is how a stale rate, a re-billed truck roll, or a lapsed contract line survives another month unnoticed. Reconciliation means tracing every line on the statement back to an invoice, the invoice back to a work order or PO, and the work order back to the contract's rate and scope terms, before the balance is approved.

The mechanism that lets errors persist is simple: a statement aggregates, and aggregation hides. A duplicate service call and a correct one net to the same subtotal a reviewer glances past. The fix is not more scrutiny of the statement itself but a line-level trace that never touches the summary number until the detail underneath it is verified.

What changes this is a repeatable sequence: pull the detail, match it to contract terms, isolate the exceptions, and resolve them before the check goes out, not after. Build the sequence once as a checklist and an AP team runs it in minutes per vendor instead of re-deriving it under deadline pressure every statement cycle.

1. What documents do you need before you start reconciling?

Reconciling a facilities vendor statement requires four documents side by side: the vendor statement itself, the itemized invoice or invoices behind it, the signed work order or purchase order authorizing each service call, and the current contract rate schedule including any amendments. Missing any one of these forces a reviewer to trust the vendor's own summary math, which is exactly the number reconciliation exists to check.

Start by pulling the statement period's full invoice detail, not just the total. A facilities vendor statement typically nets multiple invoices, credits, and adjustments into one balance, and the netting is where a duplicate or a stale rate hides.

Next, pull every work order or PO tied to those invoices. A work order should show the location, the service performed, and who authorized it. Without it, there is no way to confirm the vendor actually performed the work being billed, only that they said they did.

Finally, pull the current contract rate schedule, including any signed amendments or renewal letters. Facilities contracts often carry annual escalators, seasonal rates for snow or landscaping, and per-location pricing that a single master rate sheet will not show. Confirm you have the version in force for the statement period, not last year's.

If any of these four documents is missing, note it as a gap before proceeding rather than reconciling around the hole. A missing work order is itself a finding.

• Vendor statement: The summary balance the vendor is asking you to pay, covering one or more invoices for the period.
• Itemized invoices: The line-level detail behind the statement: date, location, service, quantity, and rate for each charge.
• Work orders or POs: The internal authorization proving the service was requested and by whom, tied to a specific location and date.
• Contract rate schedule: The current rate card and scope terms in force for the period, including amendments and escalators.

2. How do you trace each statement line back to an invoice?

Take the statement's ending balance apart into its component invoices and credits before touching any judgment call. List each invoice number, its date, its amount, and the running total it contributes to the statement balance. Confirm the sum of the listed invoices and credits equals the statement total exactly.

Any unexplained difference between your sum and the vendor's number is a reconciling item to resolve before payment, not after.

This step exists because a vendor statement is arithmetic performed by someone else, on data you have not yet seen at the line level. Rebuilding the total from its parts is the only way to confirm the vendor's math matches the underlying invoices rather than a correction made somewhere upstream that never reached you.

List every invoice and credit memo the vendor claims makes up the period balance. Mark which ones you can locate in your own AP system and which ones you cannot. An invoice on the statement that never reached your inbox is common enough to check for every time, and it usually means a duplicate submission or a billing address error rather than fraud.

When your sum does not match the statement total, isolate the difference to a specific invoice or credit before moving forward. A vague variance carried forward as a "true-up" is how a real overcharge survives three statement cycles in a row.

3. How do you match each invoice line to the contract rate?

For each invoice line, identify the contract clause that governs it: the base rate for the service type, any location-specific pricing, and any escalator or seasonal adjustment scheduled for that date. Compare the billed rate to the contracted rate exactly, not approximately. A rate that is off by a small percentage is still off, and a facilities contract with dozens of service lines makes small, consistent overcharges easy to miss without a line-by-line check.

Facilities contracts bundle several rate structures in one document: a flat monthly fee for routine service, per-call rates for on-demand work, and material markups for parts or supplies. Each needs its own check, because a single review of the header rate will miss a markup applied on top of a rate that was already inclusive.

Watch specifically for rates that reference an old contract year. A facilities vendor with an annual escalator sometimes continues billing the prior year's rate past the renewal date, or applies the new rate before its effective date. Both directions are drift, and both are invisible if the reviewer only checks that a rate exists rather than which rate applies to which date.

Where the contract sets a not-to-exceed cap on a category, confirm the invoice total against that cap directly, line by line, rather than trusting the vendor's own capped total. See how three-way matching handles this gap structurally in the-three-way-match-gap-what-your-erp-structurally-cannot.

4. What exceptions should stop a statement from being approved?

Four exception types should hold a facilities statement from approval: a billed rate that does not match the contract, a service line with no corresponding work order, a charge for a location outside the contract's scope, and a credit memo the vendor claims was issued but that does not appear on the statement. Each of these represents a specific, checkable mismatch rather than a judgment call, so each should have a documented resolution before the balance moves to payment.

Build a short exception list rather than a long one. A checklist with too many soft categories, like "unusual charge" or "looks high," gives a reviewer nowhere concrete to stop, so everything ends up approved anyway under deadline pressure.

A rate mismatch is the clearest exception: the invoice states one number, the contract states another, and the difference is the finding. Document both numbers and the contract clause, then route it back to the vendor rather than adjusting it internally.

A missing work order means the AP team has no internal record authorizing the charge. This does not mean the work was not done. It means there is no basis yet to confirm it was, and the invoice should hold until one is produced.

A credit memo mismatch, where a previously promised credit does not appear on the current statement, is worth a specific line in the exception log because it is the easiest of the four to lose track of across statement cycles.

5. How does duplicate vendor setup affect facilities reconciliation?

A facilities vendor billed under two different vendor records in the same ERP splits its statement history across two account balances, so a reconciliation run against only one record misses the other entirely. This is a vendor master problem, not a facilities-specific one, but it shows up disproportionately in facilities spend because regional subcontractors and franchise locations are often onboarded separately under slightly different names for the same parent vendor.

Before reconciling, confirm the vendor record you are working from is the only active record for that vendor. Search the vendor master for name variants, alternate tax IDs at the same remit-to address, and duplicate entries created by different regional buyers who did not know a record already existed.

If two records exist, the statement you are reconciling may not reflect the vendor's full activity with your company, which means a credit sitting against one record can offset a charge sitting against the other without either statement showing it. Consolidating the records, or at minimum cross-checking both, is a precondition for a reconciliation to mean anything.

The underlying cause and fix for this pattern are covered in vendor-master-hygiene-and-the-duplicate-vendor-problem, which this reconciliation checklist assumes as a prerequisite rather than repeats.

6. What is the step-by-step process to close out the reconciliation?

Closing a facilities vendor statement reconciliation is a fixed six-step sequence: gather the four source documents, rebuild the statement total from invoice detail, match each line to its contract rate, log every exception with the specific mismatch, route exceptions to the vendor for correction, and approve only the confirmed remainder for payment. Running the same numbered sequence every cycle is what makes the check fast enough to survive a real AP deadline.

1. Pull the statement, the itemized invoices behind it, the work orders authorizing the work, and the current contract rate schedule for the period.

1. Rebuild the statement total from the individual invoices and credits, and confirm it matches the vendor's stated balance exactly.

1. For each invoice line, identify the governing contract clause and compare the billed rate, quantity, and any markup against it directly.

1. Log every mismatch as a specific exception: which line, which contract clause, and the dollar difference. Do not net exceptions against each other.

1. Send the exception log to the vendor with a hold on the disputed lines, and route it internally for a corrected invoice or credit memo.

1. Approve the confirmed, undisputed portion of the statement for payment on schedule, and track the disputed portion separately until it resolves.

A facilities account with a high volume of small service calls benefits from running this sequence on a sample of lines each cycle rather than skipping it under volume pressure. See sampling-vs-full-population-testing for how to size that sample without giving up coverage of the categories most likely to carry a stale rate.

7. Should you run this reconciliation monthly or build a standing control?

A monthly manual reconciliation catches drift that has already happened; it does not stop the next stale rate from being billed. Whether that trade-off is acceptable depends on the volume and dollar size of the facilities account: a single-location contract may only need a periodic check, while a multi-site portfolio with dozens of vendors and frequent work orders accumulates enough exceptions between reviews to justify a standing control that checks invoices as they arrive.

A periodic audit, run monthly or quarterly, tests history: it finds what already went wrong and recovers or corrects it. A forward-looking control tests the next invoice before it is paid, which prevents the same rate error from repeating across several statement cycles before anyone notices.

Neither approach is free. A periodic reconciliation costs staff time concentrated at statement close. A standing control costs setup time to encode the contract's rate rules once, so each invoice can be checked against them automatically as it arrives, rather than reconstructed by hand every month.

The choice depends on how much facilities spend is at stake and how often the underlying contracts change. A portfolio with frequent rate escalators, seasonal terms, or vendor turnover accumulates more between-cycle drift and gets more value from a standing check. A single stable contract may not.

For a fuller comparison of the two approaches and how to decide between them for a given spend category, see continuous-enforcement-vs-periodic-audit-choosing-a-cadence. This is general information, not legal advice; contract dispute rights and cure periods vary by agreement and should be confirmed against your specific vendor contract.

For the wider pattern this sits inside, start with the margin drift guide.

8. Frequently Asked Questions (People Also Ask)

What is the fastest way to spot an error on a facilities vendor statement?

Rebuild the statement's total from the individual invoices and credits behind it rather than reviewing the summary number alone. A statement that nets several charges into one balance can hide a duplicate or a stale rate that only shows up once the detail is separated back out line by line.

Do I need the work order for every facilities charge, or just large ones?

Every charge should trace to a work order or PO, regardless of size. Facilities accounts accumulate many small service calls, and a pattern of small unauthorized charges across a portfolio of locations can add up to more than a single large one, while being far less likely to draw scrutiny individually.

What if the vendor's statement total is correct but individual line items are wrong?

This is common and is exactly why line-level reconciliation matters more than checking the final total. Two offsetting errors, one overcharge and one undercharge, can net to a correct-looking balance while both lines are wrong against the contract. Only a line-by-line match against the rate schedule catches this.

How do I handle a facilities vendor that bills from multiple regional offices?

Confirm first whether those regional offices are set up as separate vendor records in your ERP for what is contractually a single vendor relationship. If so, reconcile against the consolidated activity, not one record at a time, since credits and charges can sit on different records without either statement reflecting the full picture.

Should facilities reconciliation include material and parts markups, or only labor rates?

Both. A facilities contract that sets a labor rate and a separate material markup requires checking each independently. A markup applied on top of a labor rate that was already fully loaded is a specific, checkable overcharge that a review of only the labor rate would miss entirely.

What counts as a valid reason to hold payment on a facilities invoice?

A rate that does not match the contract, a charge with no corresponding work order, a charge for a location or service outside the contract's scope, or a promised credit memo missing from the statement. Each is a specific, documented mismatch rather than a general concern, which is what makes a hold defensible if the vendor disputes it.

How far back should I check if I find one error on a facilities statement?

Check the same contract clause across the trailing statements you still have supporting detail for, since a rate error usually starts at a specific date, such as a renewal or amendment, and persists until caught. There is no fixed number of periods; check back as far as usable invoice detail exists.

Can three-way matching in my ERP catch these facilities billing errors automatically?

Three-way matching checks the invoice against the purchase order and receipt of goods or services. It confirms quantity and PO price alignment; it does not test whether the PO price itself still matches the current contract rate or whether a seasonal or escalator clause applies to that date. Those checks require a separate comparison against the contract.

What should I do if the vendor disputes an exception I've logged?

Send the specific line, the contract clause, and the dollar difference in writing, and hold only the disputed portion of the statement rather than the full balance. This lets undisputed charges pay on schedule while the specific disagreement resolves, which keeps the vendor relationship functional during the dispute.