Overdelivery isn't a month-end surprise anymore.

Correcting a pricing mistake normally means either living with it or breaking your settled accounts. This re-prices historical revenue after an agreement correction, with a preview that flags overpayment and underpayment risk on money already settled, showing the consequence before you commit.

Contracts have limits, and enforcing them in a spreadsheet just means arguing about overdelivery later. A contractual ceiling per version stops delivery permanently once it's reached, until a new version opens.

Buyers give you limits at different granularities, and all three need enforcing at once. Overall contract cap, weekly cap resetting Monday 00:00 UTC, and daily cap resetting at midnight UTC, evaluated in that order.

A desk that takes 200 leads Monday to Thursday, 50 on Friday, and nothing on holidays is a normal arrangement, not an edge case. Daily caps resolve as a specific date override, then a day-of-week rule, then unlimited.

Batch cap checks let leads slip through in the gap between checks. Caps are checked on every routing attempt, no queue, no pending state, making overdelivery structurally impossible.

Discovering you filled a cap at 2pm means four hours of traffic went nowhere. Set remaining-capacity thresholds per agreement and get alerted at 80% so you can rebalance before it happens, deduplicated so the same threshold never spams the team twice.

Renegotiating volume mid-contract is routine. Finding out the financial consequence after the fact is not something you want. Change a cap on a live CRG batch and every historical FTD gets re-evaluated against it, with a dry-run preview showing exactly what would flip before anything commits.