How to set janitorial tolerance thresholds

Executive Summary

Facilities and janitorial contracts combine labor rates, consumable pricing, and site-specific surcharges in a single invoice, and AP review commonly checks the total against the purchase order rather than each line against its contract clause. A tolerance threshold is what makes line-level review possible at scale: it names the variance that triggers a look and lets everything inside that band pass without one.

The mechanism that causes drift to survive is a threshold set once, for the whole category, and never revisited. A flat percentage applied uniformly across line types of very different dollar exposure treats very different risks the same way. What changes it is building the threshold from the contract structure itself: setting it per line type, capping it in dollars as well as percentage, and tying its review to the same cadence as the rate card it protects.

This page sets out how to build that threshold: what it is, how to size it by line type, how to handle multi-site and multi-vendor programs, what happens when a line falls outside the band, and how often to revisit it.

1. What is a tolerance threshold in a facilities and janitorial contract?

A tolerance threshold is the variance an AP team allows between a facilities or janitorial invoice line and its contracted price before that line is flagged as an exception. It can be set as a percentage of the line value, a flat dollar amount, or the smaller of the two. The threshold does not decide whether a charge is correct.

It decides which charges get a human's attention and which pass through unreviewed, so its size is a direct control.

A janitorial contract typically prices several line types differently: a labor rate per hour or per visit, a markup on consumable supplies, and a schedule of add-on services billed only when performed. A single tolerance threshold applied across all three treats a rounding difference on a supply line the same way it treats a rate change on the labor line, even though the two carry very different dollar consequences.

The three-way match a facilities invoice runs against checks the invoice, the purchase order, and the receipt of service. It confirms the vendor showed up and billed the agreed quantity. It does not test whether the rate on that line still matches the contract, which is exactly the gap a tolerance threshold is built to cover.

See the three-way match gap for what that control structurally cannot see on its own.

Setting the threshold, then, is a separate decision from setting up the match itself: it is the variance rule that sits on top of the match and decides what counts as close enough.

2. How do you set the right tolerance band for janitorial rate lines?

Set the band from the contract's own rate structure, not from a single company-wide default. Start with the contracted rate for each line type, express the threshold as a percentage of that rate with a dollar cap on top, and size both to the dollar exposure of the line, not its label. A percentage-only rule lets high-value labor lines drift by large dollar amounts before anything fires; a dollar-only rule floods AP with exceptions on small supply lines.

The rate the threshold is measured against has to come from the current contract, not from last year's invoice or an average of recent bills. A threshold measured against the prior invoice inherits any drift already baked into that invoice, and the band stops meaning what it was built to mean.

Once the reference rate is set, size the band to the line's dollar exposure rather than to its category. A janitorial program with a handful of high-labor-hour sites and many low-volume sites should not run the same dollar cap everywhere; the cap should scale with the volume on that specific line.

Two threshold shapes, and what each catches or misses on a facilities invoice.

Two threshold shapes, and what each catches or misses on a facilities invoice.

3. Which janitorial and facilities line items need tighter tolerances than others?

Line items differ by how easily a small rate change compounds into a large invoice total, and the tolerance band should differ accordingly. Recurring labor hours and consumable markups carry meaningful exposure because they repeat on every invoice. Seasonal or one-time add-on services carry less repeat exposure but are easier to bill at the wrong rate because they appear infrequently and the negotiated price from the last time they were used is easy to lose track of.

A line's frequency and its price structure both change how tight its threshold should be. A percentage-based markup line needs the underlying cost basis checked, not just the markup itself, because a correct markup applied to an inflated cost still produces an inflated total.

Add-on and surcharge lines are the ones exposed to price file governance issues, since those issues tend to show up first on the lines that change least often and get the least attention when a price list is updated. That makes them worth a tighter dollar cap even where the dollar amounts are small individually.

• Recurring labor hours: Priced per visit or per hour and billed on every invoice, so a small rate error compounds across the full contract term.
• Consumable supply markups: Priced as a percentage over cost, which makes the underlying cost basis, not just the markup rate, worth checking.
• Seasonal add-on services: Billed a few times a year, such as strip-and-wax or exterior window service, and easy to bill at a stale or unlisted rate.
• Emergency or after-hours callouts: Priced at a premium multiplier over the standard rate, which only holds if the base rate it multiplies is itself current.
• Site-specific surcharges: Added for square footage, access requirements, or specialty flooring, and often absent from the master rate card entirely.

4. How should tolerance thresholds handle multi-site and multi-vendor facilities spend?

A single threshold applied across every site and every janitorial vendor treats programs with very different rate structures as if they were one contract. Multi-site programs need the threshold tied to each site's own contracted rate, and multi-vendor programs need it tied to each vendor's own rate card, because a percentage that looks reasonable against one vendor's pricing can be far too wide against another's.

Both cases share one requirement: the reference point the threshold measures against has to be the specific rate that specific line was billed under, not a portfolio-wide average.

A. Multi-site facilities programs

A national facilities contract often carries a single blended rate in the master agreement but different local rates by site, driven by labor market and square footage. If the threshold is set against the blended rate, every site's invoice is being checked against a number that does not describe its actual contract. The threshold has to reference the site-level rate schedule, not the contract-level average, or it will pass genuine site-level drift as if it were normal variance.

B. Multi-vendor janitorial spend

Where more than one janitorial vendor serves the same portfolio, each vendor's rate card sets its own reference point. A duplicate vendor record in the vendor master can also cause the same site to be billed under two different rate schedules without anyone noticing, which is a distinct failure from a tolerance band being wrong. Vendor master hygiene has to be checked separately from the threshold itself before the threshold can be trusted.

5. What happens when an invoice line falls outside the tolerance band?

A line outside the band becomes an exception, which means a person compares the billed rate to the contract clause and decides whether it is a legitimate change, a data entry error, or drift. The threshold's job ends at flagging the line; it does not resolve the exception. A program without a defined resolution step for flagged lines accumulates a backlog of exceptions that never get reviewed, which makes the threshold no better than having none.

The resolution step needs an owner and a deadline, not just a queue. An exception that sits unresolved for a full billing cycle allows the same drift to repeat on the next invoice before anyone has confirmed whether the first one was even wrong.

Where the exception turns out to be a legitimate rate change, such as an agreed annual increase, the reference rate the threshold is measured against needs to be updated at the same time the exception is closed. Otherwise every future invoice at the new, correct rate gets flagged again, and the exception queue fills with lines that were already resolved once.

6. How often should tolerance thresholds be reviewed and adjusted?

A tolerance threshold should be reviewed on the same schedule as the rate card it protects, and again whenever the contract itself is renegotiated. A threshold left unchanged after a rate increase, a new site addition, or a vendor consolidation is being measured against a reference point that no longer matches the current agreement, which quietly widens the real gap between what passes and what should have been checked.

A janitorial or facilities contract renewal is the natural trigger: new rates mean the reference point the threshold measures against has changed, so the band needs to be rebuilt from the new rate card rather than carried forward from the old one.

A structured review cadence, run on a fixed interval rather than only at renewal, catches the gap that accumulates between contract events: a site added mid-term, a vendor's supply cost basis shifting, or a surcharge introduced without a corresponding update to the master rate file. The quarterly margin drift review is one pattern for building that cadence into a recurring control rather than a one-time setup step, and tolerance thresholds are one input among the several that pattern is built to revisit.

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

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 n-way invoice matching explained.

7. Frequently Asked Questions (People Also Ask)

What percentage tolerance is standard for janitorial invoices?

There is no standard figure that applies across contracts. The right percentage depends on the line's dollar exposure and how often it repeats, which is why the threshold has to be built from each contract's own rate structure rather than copied from a default.

Should the tolerance threshold be the same for every vendor?

No. Each vendor's rate card sets its own reference point, and a percentage that is reasonable against one vendor's pricing can be too wide against another's. The threshold needs to reference the specific vendor's own contracted rate for each line.

Can a tolerance threshold be set in dollars instead of a percentage?

Yes. A flat dollar cap on top of a percentage catches large dollar exposure on high-value lines that a percentage alone would let through, while the percentage catches proportional drift on smaller lines. Using only one shape leaves a gap the other would have caught.

Who should own resolving flagged exceptions?

The threshold only flags a line; someone still has to compare the billed rate to the contract clause and decide what happened. That role needs a named owner and a deadline, not a shared queue, or flagged lines accumulate without ever being resolved.

Does a three-way match already catch this kind of drift?

No. A three-way match confirms the invoice, purchase order, and receipt of service line up on quantity. It does not test whether the rate on that line still matches the current contract, which is the specific gap a tolerance threshold is built to cover.

How does a tolerance threshold interact with an annual price increase?

When a rate change is confirmed as legitimate, the reference rate the threshold measures against has to be updated at the same time the exception is closed. Otherwise every future invoice at the new, correct rate keeps getting flagged as an exception.

What is the risk of setting the tolerance threshold too wide?

A threshold set too wide lets real drift pass through as if it were normal variance, since the line never crosses the point where it would be flagged for review. The wider the band, the more of the actual gap between contract and invoice goes unchecked.

What is the risk of setting it too narrow?

A threshold set too narrow flags rounding differences and immaterial variance as exceptions, which fills the review queue with lines that need no action. That volume makes it harder to find the exceptions that represent real drift.

Does a multi-site program need one threshold or one per site?

One per site, or at least one per site-level rate schedule. A national contract's blended average rate does not describe any single site's actual contract, so measuring against it would pass real site-level drift as normal variance.

How does vendor master data affect the threshold's accuracy?

A duplicate vendor record can cause the same site to be billed under two different rate schedules without anyone noticing, which is a separate failure from the tolerance band itself being wrong. Vendor master hygiene needs to be checked on its own before the threshold can be trusted.