Claims Proof Library
These examples use sample supplier and retailer data. They show how to review a deduction before treating it as settled.
Names, claim IDs, dates, and amounts below are illustrative only.
Illustrative, not a recovery guarantee.
Not legal advice.
Each line starts with the retailer assertion, then checks the proof trail, timing basis, and any Code condition that could change the answer. The point is to surface the missing document, mismatch, or precondition before the supplier replies.
A retailer claims late arrival against a booked 10:00 to 12:00 window. The supplier packet has a dock timestamp at 10:41. The scorecard note uses gate-in time instead. That mismatch is enough to ask which timing rule drove the debit.
The remittance shows a rebate amount and a campaign code. The scan extract is missing by SKU, store group, and promo dates. That line stays in missing proof until the volume basis appears.
Once the scan report shows the exact SKU set, store scope, rate, and dates against the signed mechanic, one line can still look supportable even if the current evidence pack is incomplete.
The claim note describes store-level shrink after signed delivery. That creates Code risk only if three preconditions hold: the retailer is Code-covered, possession had already passed, and the loss is post-possession shrinkage rather than a delivery variance.
Source note: this example follows ACCC Food and Grocery Code guidance and the current Code text. Illustrative only. Not legal advice.
Send a remittance with a shrinkage charge