A waste invoice arrives. The total looks close to last month’s bill. Someone approves it.
That may feel like a review, but it leaves the most important questions unanswered. Did the base rate increase? Did a new fee appear? Was a credit applied against the wrong charge? Is the location still being billed for a container that was removed?
Exception-based invoice auditing compares invoice details with the records that define what should have been billed, then directs reviewers to discrepancies, meaningful changes, and missing evidence. It turns “this bill looks normal” into a specific, testable assessment.
For waste brokers, consultants, and multi-site operators, that distinction matters. A portfolio can contain hundreds of familiar-looking invoices while individual rates, service levels, and account conditions drift underneath the totals.
The goal is to give every invoice consistent comparison checks and give each exception a clear path to resolution.
What Is Exception-Based Invoice Auditing?
Exception-based invoice auditing is a review method that identifies charges or billing details that do not match an expected condition.
That condition may come from:
- The applicable hauler contract and approved amendments.
- The location’s approved service profile.
- Documented service events and work orders.
- Account activation, suspension, or cancellation records.
- Previously validated invoices.
- An expected credit or correction.
For example, an invoice might show a recurring collection rate of $525 while the applicable approved rate is $500. The exception is the $25 difference, tied to a specific service, billing period, and agreement.
An analyst can then investigate why the difference exists. Perhaps an authorized increase took effect. Perhaps an amendment has not been recorded. Perhaps the invoice is wrong.
An exception is a question requiring resolution. It is not automatically proof of overbilling.
This approach also depends on broad coverage. Comparing only selected invoices and investigating their differences remains a sampling process. A reliable exception workflow applies the defined checks across the invoice population and identifies records that cannot be evaluated because data is missing.
For a broader foundation, see IntellaWaste’s waste invoice audit checklist.
Why Comparing Invoice Totals Misses Billing Changes
A total combines several components into one number. Changes can offset one another and disappear at the invoice level.
Consider this simplified example:
| Invoice component | Previous month | Current month | Change |
|---|---|---|---|
| Base collection charge | $500 | $525 | +$25 |
| Recurring fee | $50 | $65 | +$15 |
| One-time service | $40 | $0 | −$40 |
| Total | $590 | $590 | $0 |
Illustrative example; taxes and other charges are excluded.
The total has not changed. However, recurring charges increased by $40.
If the previous month’s one-time service was legitimate, its disappearance does not justify the new recurring amounts. Each change needs its own explanation.
The same problem occurs when a credit masks a rate increase or when reduced service quantities offset a new fee. A total-level comparison can identify a spending movement, but it cannot establish whether the underlying charges are correct.
There is another limitation: an unchanged charge can still be wrong. If an unauthorized rate increase was accepted three months ago, comparing this month only with last month will carry the error forward.
Historical comparison helps identify movement. Contract and service comparison help establish correctness.
The Six Changes a Waste Invoice Audit Should Surface
Effective exception-based invoice auditing examines the components that determine the bill.
1. Rate Changes
Compare recurring and event-based rates with the terms effective during the billed service period.
Questions to investigate include:
- Did the base collection rate increase?
- Did the per-haul or per-ton rate change?
- Was the increase effective during this billing period?
- Is there an approved amendment or applicable adjustment provision?
- Does the billed rate match the correct container, waste stream, and service?
A rate change may be permitted, but the amount, timing, and applicable service still need verification.
An approved future rate should not replace the historical rate for earlier service periods. Keeping effective dates preserves the ability to audit both current bills and retrospective corrections.
2. Fee Changes
A fee exception can involve a new charge, a changed amount, or a different calculation.
For percentage-based charges, compare both the percentage and the amount to which it applies. An unchanged percentage can produce an incorrect fee if the calculation base changes.
Review recurring fees separately from event-based charges such as extra pickups, blocked access, contamination, or container exchanges.
The useful question is specific: “What agreement provision and service evidence support this charge?”
A familiar description alone does not answer it.
3. Quantity Changes
Waste invoice quantities may represent containers, hauls, tons, rental days, or other billable units. Those units need to be understood before they can be compared.
Investigate changes such as:
- Two containers billed where only one is approved.
- More hauls billed than supported by available tickets.
- A disposal quantity that does not match the associated weight record.
- Rental charges continuing after documented equipment removal.
- Overlapping billing periods that repeat the same service.
A quantity increase can reflect legitimate activity. The review should connect that activity to an approved request or supporting operational record.
4. Tax Changes
Tax review should identify changes in the stated rate, taxable amount, jurisdiction, or recorded exemption status.
These are investigation triggers. Whether a tax applies depends on the service, location, and applicable requirements.
Keep taxes separate from hauler-described regulatory, environmental, or governmental pass-through charges. A label that sounds official does not establish how a charge should be classified.
If a tax change cannot be explained by the supporting records, route it for qualified verification before treating it as correct or incorrect.
5. Service Changes
Compare the billed service with the approved service configuration:
- Container count and size.
- Waste or recycling stream.
- Pickup frequency.
- Equipment type.
- Recurring versus temporary service.
- Effective dates for service changes.
A site may have reduced pickup frequency without receiving the corresponding billing adjustment. Another may have received an additional container that was approved locally but never added to the central record.
Both situations require investigation, although their outcomes differ.
Billing records also cannot establish service completion on their own. Where an event-based charge depends on a specific pickup or visit, connect the invoice to available service documentation.
IntellaWaste’s waste service verification guide explains the difference between scheduled, completed, documented, and billed service.
6. Account-Status Changes
Account status affects whether a charge belongs in the review population at all.
Flag invoices associated with:
- Closed locations.
- Cancelled or suspended services.
- Replaced hauler accounts.
- Newly activated accounts without a confirmed service profile.
- Unmapped account numbers.
- Multiple accounts appearing to bill the same service period.
A final invoice after cancellation may be legitimate. It may include service provided before termination or an applicable equipment-removal charge. The review must compare the service dates and charge basis with the documented account history.
Also check for missing invoices. A complete audit needs to know which active accounts were expected to bill, not merely which invoices arrived.
Structured Data Makes Comparison Possible
Before a system can identify meaningful changes, it needs consistent records.
“8 yd,” “8 cubic yards,” and “8-yard container” may describe the same equipment. “Twice weekly” and “Mon/Thu” may describe the same frequency. Without normalization, equivalent services can appear different.
Conversely, grouping different charges under a broad label such as “waste service” can hide important distinctions.
At minimum, the comparison process should connect each invoice to:
- A unique location and hauler account.
- The invoice number and service period.
- Individual charge categories.
- Quantities, units, and rates.
- The applicable contract version.
- The approved service configuration.
- Relevant account-status dates.
Preserve the original invoice alongside the extracted data. If a reviewer questions a parsed amount or description, they need a direct path back to the source.
Missing information should create a visible exception. An invoice that cannot be matched to a contract should be marked “unable to validate,” with an owner responsible for obtaining the record.
For the underlying cleanup work, see Waste Data Quality: The Foundation of Accurate Audits, Budgets, and Reports.
What True Exception Review Looks Like
A useful exception queue explains what changed, why it needs attention, and what happens next.
Compare two entries:
Vague: Site 42’s invoice looks high.
Actionable: Site 42’s recurring collection rate increased from the approved $500 to $525 for October service. No supporting rate amendment is attached. Assigned to the contract analyst; request supporting notice from the hauler.
The second entry gives the reviewer a starting point and preserves the basis for the question.
Prioritize exceptions using more than the current dollar amount. Consider whether the issue recurs, affects multiple locations, has been open for a long time, or needs action before a payment or response deadline.
A small recurring discrepancy may deserve attention because it repeats across a portfolio. A large one-time charge may be quickly validated with a service ticket.
Use thresholds to organize the queue carefully. A threshold that hides every small discrepancy can allow repeated errors to accumulate.
What Case Management Must Preserve
Flagging a discrepancy starts the work. Case management preserves the information required to finish it.
The Original Finding
Record the location, account, invoice, service period, affected line item, billed amount, expected amount, and reason for review.
Keep the original finding even if later information changes the assessment. This allows another reviewer to understand what triggered the case.
The Supporting Evidence
Attach or link the controlling contract language, amendments, service requests, tickets, cancellation notices, and relevant communications.
Record the source and date of the evidence. “The site confirmed it” is less useful than a dated message identifying the service and request.
Ownership and Next Action
Every open case needs a named owner and a specific next step.
Useful statuses might include awaiting internal evidence, awaiting hauler response, validated, disputed, credit promised, and credit verified.
A status should describe the case’s actual condition. “In progress” alone does not explain who must act next.
The Financial Outcome
Track the amount questioned separately from the amount confirmed as an error and the amount recovered.
If a hauler promises a credit, retain the expected amount and follow-up date. When it posts, connect the credit memo or invoice adjustment to the original case.
Partial credits should leave the remaining balance visible.
A promised credit is not a verified recovery. A case should not disappear from follow-up simply because someone agreed that an adjustment was needed.
The Prevention Step
After resolution, determine whether the underlying record or process needs correction.
An approved rate amendment may need to be added. A cancelled container may still appear in the service profile. A recurring invoice error may need monitoring on subsequent bills.
Closing the case should improve the next audit.
How to Measure the Process
Invoice review speed matters, but speed alone does not establish audit quality.
Track measures such as:
| Measure | What it helps reveal |
|---|---|
| Expected invoices received | Whether the review population is complete |
| Invoices successfully matched | Whether account and contract data support validation |
| Exceptions by category | Where recurring problems originate |
| Open-case age | Where follow-up is stalled |
| Confirmed discrepancy amount | The value supported by investigation |
| Credits verified | Recoveries that actually posted |
| Repeated exceptions after closure | Whether corrective action worked |
Keep suspected discrepancies, confirmed errors, and recovered amounts separate. Combining them can overstate results and obscure unresolved work.
How IntellaWaste Supports the Workflow
IntellaWaste’s published capabilities include automatic invoice uploads and parsing, service-level tracking, hauler contract tracking and invoice auditing, and hauler overbilling case management. These capabilities bring the records needed for invoice review into a connected workflow. intellawaste.com
The operational value comes from connecting a charge to its location, service, agreement, and resolution history.
For brokers and consultants, that connection helps preserve the evidence behind a discrepancy. For multi-site operators, it makes billing changes easier to investigate consistently across locations.
Explore IntellaWaste’s waste management software capabilities or schedule a demo to discuss your invoice-review process.
Frequently Asked Questions
Is exception-based invoice auditing the same as spot-checking?
No. Spot-checking examines selected invoices or charges. Exception-based auditing applies defined comparisons across the review population and directs human attention to flagged items and records that cannot be validated.
Should invoices be compared with the previous month or the contract?
Both comparisons serve a purpose. Previous invoices reveal changes and patterns. The applicable contract, approved service profile, and supporting records help determine whether the current charge is correct.
Does every invoice change indicate an error?
No. Approved rate adjustments, documented extra services, quantity changes, and account transitions can produce legitimate differences. An exception prompts verification.
Can an unchanged invoice contain an error?
Yes. An incorrect rate, unsupported recurring fee, or charge for removed equipment can repeat without changing the total. That is why audits need an approved baseline beyond the previous invoice.
When should a credit-related case close?
After the agreed correction is verified against the relevant credit memo, invoice adjustment, or accounting record, and any remaining balance or follow-up requirement is documented.