Capability
The channel was marked.Nobody checked the marker had not moved.
Agreements define what was owed on specific dates. Payment systems almost never carry that history, so approval verifies arithmetic instead of entitlement.
The rate in force
Entitlement is a date question before it is a money question.
Reconstruct the terms
Base agreement, schedules, amendments and side letters assembled into a single history with effective dates.
Bind terms to events
Each transaction is matched to the terms in force on the date of service, not the terms currently on file.
Test entitlement
Every invoiced or paid amount is compared to what the governing terms actually authorised.
Isolate real variance
Negotiated allowances, exceptions and documented waivers are excluded before anything is quantified.
Identify unexercised rights
Clawback, audit, representment and offset provisions that were enforceable and never triggered.
Quantify recoverable value
Separated from total variance, because recoverable and wrong are not the same figure.
Why it is missed
The failure is structural, not careless.
- Rate schedules live outside the systems that approve payment.
- Amendment effective dates are applied differently by each party.
- Clawback triggers depend on operational events that never cross into finance.
- Audit rights carry deadlines that nobody is accountable for tracking.
- Invoice approval checks that the maths is right, not that the charge was owed.
- Disputes are handled one at a time, so the pattern never becomes visible.