Every trade tool on the market records what happened. This records what was agreed —
in a form that cannot be quietly changed afterwards. That difference is the whole reason a deduction
can be disputed six months later instead of simply paid.
STEP 1 · BEFORE THE MONEY MOVES
The commitment is written
What was agreed, with whom, for what quantity and period — recorded at the moment it is struck,
not reconstructed later from an invoice.
STEP 2 · IMMEDIATELY
It is sealed
The entry is fingerprinted, and that fingerprint includes the one before it. The entries form a
chain. Changing any earlier entry breaks every link after it.
STEP 3 · MONTHS LATER
The claim is tested against it
When the deduction arrives, the commitment is produced with its timestamp intact — and anyone can
verify for themselves that it has not been altered since.
Try to break it
This is a live ledger, not a picture of one. The fingerprints below are real SHA-256 hashes computed
in your browser right now. Change any value in the table and watch what happens.
Click into any amount or quantity and edit it — as someone might if they wanted a commitment to
say something different after the fact.
#
Retailer
Program
Committed
Cases
Agreed on
Fingerprint
Verify
Verifying…
Why this matters more than matching
Trade promotion tools are good at matching a deduction to a promotion. That is a genuinely useful
thing and worth having. But matching answers a different question than the one that decides a dispute.
Matching asks: does this claim correspond to something in our system?
If the record in the system was edited after the fact — or entered from the claim itself — the
match succeeds and proves nothing.
The ledger asks: what did we commit to, and can we show it is unchanged since?
That is the question a retailer's account team, an auditor, or a parent company actually needs
answered.
Time is the hard part. The commitment carries the moment it became true, kept
separately from when it was written down. A query about March cannot see an amendment made in
July — which is exactly the discipline a dispute requires.
And when it cannot ground an answer, it says so. A commitment that was never
written is reported as unprovable — not clean, and not fraud.
Where this fits — the gaps nobody is serving
Every platform in this category assumes the data going in is clean and consistently coded. In
middle-market CPG it very often is not, and that is where the value leaks out before any software
gets a chance to help.
Gap 1 — the deal is agreed before it is recorded
Commitments get struck on calls, in email, on a deal sheet in someone's folder. By the time
anything reaches a system it has been re-keyed at least once. The ledger moves the
record to the moment of agreement, which is the only moment it is certainly right.
Gap 2 — deduction coding is inconsistent
The same deduction reason gets coded three ways by three people. Matching on inconsistent codes
produces confident, wrong answers. Kevin's thirty-five years is what makes the coding
right — the technology cannot supply that judgment.
Gap 3 — no dedicated trade analyst
Most middle-market teams do not have one, and tools in this category quietly assume they do.
The engagement supplies the analyst; the ledger is what lets the work survive
after the engagement ends.
Gap 4 — proving it upward
For a subsidiary reporting to a parent — particularly a foreign one — a trade variance has to be
explained up a chain that was not in the room. Documentation that proves the number is
worth more there, not less.