A commercial waste invoice is a fixed charge, a variable charge, and between three and nine other lines whose names change from month to month.
Key takeaways
The contract becomes a rate card: every chargeable thing, with its agreed price.
Every invoice line matches a rate or becomes a question.
Surcharges are legitimate, negotiable, or wrong, and you cannot tell without asking.
Escalation clauses have a date and a cap. Both get exceeded.
One model read per invoice; everything after it is arithmetic.
The rate card
Fig 1. The contract becoming something an invoice can be checked against. Most businesses have the left-hand box and none of the others.
What the rate card contains
The standing charge, per container per period, which is most of the bill and the least examined part of it.
The lift rate, per collection, and whether it is included in the standing charge or additional.
Weight rates where the contract is weight-based, with the included tonnage if there is one.
Named surcharges that the contract does allow: contamination, overweight, return visits, container replacement.
The escalation clause — when the price can rise, by how much, and against what index.
The lines that appear from nowhere
Fig 2. What happens to each invoice line. The third lane is where the surprises live, and asking about them is a normal commercial conversation rather than a dispute.
App integration
Machine learning
Management
Analytics
New charges are usually legitimate and sometimes not
Waste contractors face genuine cost changes — disposal gate fees, landfill tax, fuel — and passing them on is often explicitly permitted. A new line is not evidence of anything on its own.
What is worth knowing is which clause allows it, because that clause usually contains a cap, a notice period, or a restriction to actual documented cost increases. A charge that turns out not to be permitted is normally credited without argument once you cite the clause, and never mentioned again if you do not.
Escalation clauses
Fig 3. An escalation clause applied generously. Each individual rise is small enough to approve without thinking, which is exactly why the comparison has to be against the signed rate.
The mechanism is always the same. A price rise arrives as a letter, it is filed, and the invoice quietly reflects it from the following month. Nobody compares it to what the contract permits, because the contract is a PDF and the letter is an email and they have never been in the same place.
Where the model runs
One call per invoice, turning a scanned or emailed document into lines with a description, a quantity, a unit rate and a total. That is a genuinely hard document problem and a good use of the tool.
Everything after that is arithmetic against the rate card, and it stays arithmetic on purpose. A discrepancy has to be explainable to a contractor in one sentence, and ’the model thought this looked unusual’ is not that sentence.