Exceptions, disputesand corrections.
Most cycles run without an exception. Some do not. The exception desk runs to a written process, a documented response time and a separate budget line in the cycle. The supplier sees what is logged the moment it is logged.
An exception is any deviation from the cycle plan that has a financial or timing consequence. Some are supplier-side, some are platform-side, some are partner-side, some are force-majeure. The category does not change the response, it only changes the resolution path and the cost allocation.
The supplier despatches fewer units than authorised. Logged at pre-shipment inspection or at hub receipt depending on where it surfaces. Cycle authorisation is adjusted, members are notified of the revised quantity.
Goods at pre-shipment, hub receipt or in-channel use do not meet specification. Routed to the inspection desk for the technical adjudication. Outcome can be release, partial release, rework or rejection.
The supplier or the platform misses a date on the cycle calendar. Logged with the cause. Recovery plan posted within 24 business hours.
In-transit damage, customs damage or hub damage. Carrier claim opened on the day. Goods photographed, weighed and held while adjudication runs.
Documents-side or compliance-side hold at destination. Operations desk works the broker, supplier provides any missing original. Hub costs accrue against the cycle and are allocated against the cause party.
Channel partner misallocates, mishandles or under-performs against the agreed window. Logged against the channel partner. Settlement reflects the actual not the planned.
Every exception, regardless of category, runs the same four steps. The steps are the same whether the cause is supplier, platform, partner or force-majeure. Only the resolution route differs.
Every cycle authorisation includes an exception reserve set against the documented risk profile of the cycle. Routine exceptions, customs clearance variance, minor damage, partial channel deviation, draw against the reserve before the supplier balance is touched. Where the reserve is exhausted, the cycle margin and then the platform fee absorb the residual before any supplier-side recovery is considered.
Supplier-side recovery is reserved for material supplier-cause exceptions: out-of-spec goods, falsified certification, undisclosed change of facility, refusal to address a corrective action. Even there, the recovery process runs through the master agreement’s dispute clause, not as a unilateral deduction at settlement.
Raise an exception the supplier sees first, before the desk sees it. Suppliers who self-report consistently track better in the integrity domain of the scorecard than suppliers who let the desk discover deviations. The platform values written candour at the time, not retroactive explanation at settlement.
Disagree on the record. Where the supplier disputes an exception entry, the supplier writes a statement into the ledger and the entry is marked contested. The exception desk reviews and either amends the entry, holds it for the master-agreement dispute pathway, or closes the dispute with a written reason. The original entry is never deleted, the contested record is the record.
How exception outcomes feed into the settlement statement and the supplier balance.
How exception incidence and resolution affect tier movement at the quarterly review.
A field-note walk through cycles that settled below their published base case.
Logged early.Resolved cleanly.
The exception desk is paid to record matters accurately, not to allocate blame. The blame conversation comes after the record is straight.