The retrospective
A number about your own channel that nobody has had to defend yet.
Twelve months of your own claims, read against your own contracts, in two weeks. At the end you have what was over-claimed, what was under-claimed, and the source row behind every line — or the finding that your claims are clean, which is the more valuable answer if it is the true one.
What you send
Claim history
Twelve months of chargeback or rebate claim lines, in whatever format they exist — exports, spreadsheets, PDFs from the distributor, or a database dump. Reading awkward files is the product.
The contracts
The price lists and agreements those claims were made under, including the tier and eligibility terms and any amendments.
Sell-through, if you have it
Optional. It makes eligibility and end-customer classification checks possible rather than just tier and duplicate checks.
One person
Someone who can answer perhaps three questions about how a term is meant to be read. Not a project team.
No system access, no integration, no IT project. If it is easier to send a folder than to export cleanly, send the folder.
What happens in the two weeks
Days one to three · the files are read
Extraction and mapping. You confirm the mapping once — it takes about twenty minutes — and anything unreadable is quarantined and listed rather than guessed at.
Days three to six · the contracts become rules
Tier thresholds, eligibility, expiry, end-customer classification. Each rule is shown to you with the clause it came from, and you confirm it before it is applied to anything.
Days six to ten · the reconciliation runs
Every claim line against its entitlement. Over-claims, duplicates, expired tiers, eligibility mismatches — and under-claims, which are reported as a separate payable line rather than netted off to make the headline larger.
Days ten to fourteen · we go through it together
Two hours, your finance lead in the room, every line open to the source row. The point of the session is for you to try to break the findings.
What comes back
- Every exception, with claimed credit, entitled credit and the delta as three separate lines, and the contract clause that decides it.
- A summary by exception type and by partner, with the ones that are recoverable separated from the ones that are arguable.
- Under-claims — money you were entitled to and did not take — as their own line.
- What was excluded and why: rows that could not be read, claims outside the period, partners with no contract on file. The excluded amount is stated, not hidden.
- The source row for every figure, and a file you can hand to your own auditor.
If the answer is that your claims are clean, that is the answer, and you will get it in writing with the same evidence attached.
Cost, and what it commits you to
The scope and the price are agreed on the first call, before any work starts, and it is two weeks of work rather than a subscription. It does not commit you to buying anything, and there is no auto-renewal to cancel because there is nothing to renew.
Your data is handled as described on the security page in the region you nominate, used for your retrospective and nothing else, and deleted on your instruction when it is done.
Start with an email, not a form.
Tell us roughly how many partners you have, which markets, and what a claim looks like when it arrives. That is enough for us to say whether a retrospective is worth your time, and if it is not we will say so.