Spotting billed scope beyond contract on facilities invoices

Executive Summary

Facilities contracts describe scope in an exhibit or schedule, a list of tasks, square footage and frequency, attached to a master service agreement. The invoice, by contrast, describes a period charge with a handful of line items. AP staff match the invoice to the PO and the contract total, not to the scope exhibit, because the exhibit rarely sits next to the invoice in the AP workflow.

The fix is not a stricter approval chain. It is a standing comparison between the scope exhibit and every recurring invoice line, checked at the task level rather than the total level.

What changes this is treating the scope exhibit as an active reference document rather than a filing artifact, reviewed against invoices on a schedule, not just at contract renewal.

1. What does billed scope beyond contract actually look like on a facilities invoice?

It looks like an invoice line for a task, frequency or square footage the scope exhibit never priced: an added area cleaned, a monthly service billed weekly, a one-time project folded into the recurring charge. The invoice format stays identical to every prior month, which is exactly why it passes review. The line that should trigger a question is the task description, not the total, and a standard review does not open the scope exhibit to compare it.

A facilities MSA typically attaches an exhibit that lists covered buildings, square footage, task frequency and price per task. The invoice, by design, summarizes that into a handful of lines: a monthly service charge, maybe a supplies line, maybe a project charge.

When a vendor's crew starts servicing a loading dock that was never in the original footprint, or moves a quarterly deep clean to a monthly one, the invoice line often just says "facilities services, [month]" with the new total folded in. Nothing on the invoice face announces the change.

The detection method: pull the scope exhibit, list every priced task and its frequency, and check each invoice period against that list, not against last month's invoice. Comparing month to month only catches a spike. Comparing to the exhibit catches drift that arrived gradually.

2. Why does scope creep survive a standard three-way match?

Three-way matching checks the invoice against the purchase order and the receipt of goods or services. It confirms a PO exists and the amount roughly lines up. It does not open the contract's scope exhibit and it has no field for task description, frequency or square footage.

A facilities PO is frequently a standing blanket PO for the contract term, so the match control has nothing period-specific to compare the new task against.

Three-way matching was built for goods: a PO quantity, a receipt quantity, an invoice quantity. Facilities services do not generate a receipt in the same sense. Someone confirms the building was cleaned, not that the specific task list matches the contract.

A blanket PO covering a twelve-month facilities contract authorizes spend up to a ceiling. It does not authorize a specific set of tasks. As long as the monthly invoice stays under that ceiling, or close to prior months, the match control has nothing to flag.

This is a structural gap, not a lapse by the AP team. The control was designed to confirm a delivery happened and a PO covers it. It was never designed to test whether the delivery matches a scope exhibit that lives in a separate contract file.

3. Which documents do you need side by side to catch this?

Catching billed scope beyond contract needs the scope exhibit, the change order log, a run of invoices rather than a single month, and where available the vendor's own work order detail, reviewed together rather than the invoice reviewed alone. Without the exhibit in hand, a reviewer has no fixed reference point and can only compare this month's total to last month's, which will not surface scope that expanded gradually over several periods.

The exhibit and the change order log establish what is actually priced. Without both, a reviewer cannot tell a legitimate scope expansion from an unauthorized one, since both look identical on the invoice.

A run of invoices matters because scope creep is rarely a single jump. A task added quietly in month three continues unremarked in month four, five and six, and by month twelve it reads as normal because it has appeared on several invoices already.

Work order or ticket detail, where the vendor provides it, is the most direct evidence: it states what was actually done on a given visit, which can then be checked against the exhibit's task list independent of what the invoice line item says.

1. The scope exhibit: The attachment to the MSA that lists covered locations, tasks and frequency. This is the reference document, not the invoice.
2. The change order log: Any amendment that legitimately expanded scope. A task not on the original exhibit is only in-scope if a change order added it.
3. A run of invoices: A single month shows a total. A run of invoices shows when a task first appeared or a frequency first changed.
4. Site walk or work order detail: Where available, the vendor's own work order or ticket detail shows what was actually performed, which is what the invoice should be billing against.

4. How do you build a check that catches this every month, not just at renewal?

Build a task-level checklist from the scope exhibit, one row per priced task with its contracted frequency and covered location, and run every invoice period against that checklist rather than against the prior invoice. A new row on the invoice that has no matching row on the checklist is a flag, regardless of dollar size. This turns scope-exhibit compliance into a repeatable monthly control instead of something reviewed only when the contract comes up for renewal.

Facilities contract review commonly happens once, at signing, and again at renewal. In between, the exhibit sits in a contract management folder nobody opens against a monthly invoice.

The practical fix is turning the exhibit into a checklist: task, location, frequency, one row each. Every invoice period gets checked against that list. A task on the invoice with no matching row is scope beyond contract. A task whose billed frequency does not match its row is also scope beyond contract, even if the task itself was always covered.

This check does not require software. It requires the checklist to exist once and to be applied every period, rather than trusting that an invoice which looks like last month's invoice must also match the contract.

5. How is facilities scope creep different from scope drift on a maintenance work order?

Facilities scope creep is a recurring-service problem: a fixed monthly contract quietly absorbs tasks, locations or frequencies it was never priced for. Maintenance work order drift is a project-level problem: a single work order authorized for a defined repair expands during the job itself. The review method differs accordingly.

Facilities needs a standing checklist run every period. Maintenance needs the closed work order checked against its original authorization before the invoice is paid.

A facilities contract runs for a year or more and bills the same categories of task on a recurring basis. The drift accumulates slowly, one added task at a time, across many invoice periods.

A maintenance work order is opened for a specific job with a specific authorized scope, then closed and invoiced once. The drift there happens inside a single job, when the crew finds additional work and keeps going without a new authorization.

Both are scope problems, but the timing of the check differs. Facilities needs a recurring, period-over-period comparison against a standing exhibit. A maintenance work order needs a one-time comparison between the closing invoice and the original authorization before payment. Treating them with the same control misses one or the other.

6. What should you do when you find billed scope beyond contract?

Document the specific task, location or frequency that exceeds the scope exhibit, with the invoice period it first appeared in, before raising it with the vendor. A vendor conversation grounded in the exhibit and a dated invoice history gets a faster resolution than a general dispute about the total. Decide separately whether the added task should be formalized with a change order going forward, since some scope expansion is legitimate and simply never got documented.

The first step is not a vendor call. It is building the record: which task, which location, which invoice period it first appeared in, and what the exhibit says instead. That record is what makes the vendor conversation short.

Some scope expansion turns out to be legitimate. A building was added to the footprint, the vendor started servicing it, and the change order was simply never issued. In that case the fix is a change order, not a credit, and the priced rate for the added scope should be checked against comparable rates elsewhere in the contract.

Where the expansion was not authorized and not wanted, the recovery conversation is straightforward once the exhibit and invoice history are in hand: this task was never priced, here is when it started, here is what is owed back.

For the wider pattern this sits inside, start with the margin drift guide. See also the six categories drift hides in and accessorial charge audit: the surcharges nobody validates.

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

7. Frequently Asked Questions (People Also Ask)

Is scope creep on a facilities invoice the same as overbilling?

Not exactly. Overbilling usually means a priced task billed at the wrong rate or quantity. Scope creep means a task, location or frequency that was never priced in the contract at all. Both need the scope exhibit to catch, but the fix differs: overbilling is corrected against the existing price, scope creep needs a new change order or a credit.

Who should own the scope exhibit once the contract is signed?

Whoever owns vendor performance for facilities, often a facilities manager or procurement lead, should hold the current exhibit and update it whenever a change order is signed. AP should have a copy to check invoices against, but AP alone should not be the only party who knows what the current scope is.

Does a facilities management software platform catch this automatically?

A facilities platform can track work orders and schedules, but it only flags scope creep if someone has loaded the contracted scope exhibit into it as the reference and configured a comparison against invoiced tasks. The software does not do that comparison on its own without the exhibit entered as data.

What if the scope exhibit itself is outdated or was never fully documented?

Then the check starts by rebuilding the exhibit from the original contract, any amendments, and the vendor's own service description. An incomplete exhibit still gives a reviewer more to compare against than the invoice alone, and rebuilding it is a one-time cost that makes every future invoice check possible.

Can the vendor's own invoice detail be trusted as evidence of scope?

It is a starting point, not proof. The invoice line item reflects what the vendor chose to bill, not necessarily what the contract authorizes. Work order or ticket detail, where the vendor provides it, is more useful because it describes the specific work performed on a specific visit.

Should you dispute a small scope addition or let it go?

Dollar size on its own is not the right test. A small unauthorized task repeated over many invoice periods adds up, and letting it pass sets a precedent the vendor will read as approval. Document it regardless of size, then decide whether to formalize it with a change order or ask for a credit.

How far back can you go to recover for unauthorized scope?

That depends on the contract's own audit or billing dispute clause, which typically states a window for raising billing discrepancies. Check that clause before assuming any particular period. This is general information, not legal advice; confirm the applicable window against your specific contract language.

Does adding a stricter approval workflow fix scope creep?

No. Approval workflows check whether an invoice was authorized to be paid, not whether the tasks on it match the scope exhibit. A stricter approval chain still approves a scope-creep invoice unless someone in that chain is actually comparing the invoice to the exhibit line by line.

What is a change order, and why does it matter here?

A change order is a signed amendment to the contract that adds, removes or reprices scope. It matters because it is the only document that turns an added task into authorized, priced work. A task performed without one is either an error to correct or a gap to formalize, but it is not yet in-scope.