Historic Deduction Audit
What a historic audit is
A historic deduction audit is a backward-looking analysis of retailer deductions taken against a supplier's invoice that have already been settled and closed. Where a forward process asks what can still be disputed, a historic audit asks a different question: of everything a retailer has already taken, how much was ever actually examined, and what patterns caused it. ROIAI One runs the audit against the deduction, remittance and dispute records a supplier already holds, over the period the supplier chooses. It is an analysis of what happened, not a recovery of it.
Historic Audit or Assessment?
Most readers should start with a Chargeback Recovery Assessment, not a historic audit. A deduction you can still dispute is worth more to you than a deduction you cannot, and the assessment is the one that looks at the deductions still inside a retailer's dispute window. The historic audit is the right first step only when your question is about the past.
Chargeback Recovery Assessment
What it looks at
Deductions that are open now and still inside the retailer's dispute window
The period
The current book as it stands today
The question it answers
What of our current book is disputable, and what is not
What you get back
An estimate of the disputable portion of the current book, net of published exclusions, with the exclusion workings shown
What it can lead to
A forward dispute process on the current book
Who it suits
Nearly everyone else, and anyone whose priority is the money still on the table
Historic audit
What it looks at
Deductions already taken and already closed, including those never disputed, disputes that were abandoned, duplicates, deductions taken more than once, and deductions repaid but never credited back
The period
Backward, over the period you choose, bounded by what your export covers
The question it answers
What did we absorb without ever examining it, and what caused it
What you get back
The categories found, the root-cause pattern by originator, and the portion of the book that was never examined
What it can lead to
Evidence for a trading-terms conversation, a root-cause fix at the originating function, and a shortlist of anything still inside a window
Who it suits
A reader whose question is about the past: inherited books, suspected duplicates, a renegotiation, or a root-cause decision
You are reading its page.
Who a Historic Audit Suits
A historic audit suits a reader whose open question is about deductions that are already closed. These situations recur:
A change of ownership or finance leadership. Someone has inherited a deduction book nobody examined and needs to know what is in it before they own the consequences of it.
A company that has never disputed. Before building a forward process, the reader wants to know the size and shape of what was absorbed, so the decision to build is made on evidence rather than instinct.
A company that suspects duplicates or double-taken deductions. The same deduction charged twice, or a deduction repaid and then never credited back, is a records question rather than a dispute question, and it is answerable from the historic record.
A company preparing a retailer trading-terms renegotiation. A negotiation about compliance terms and deduction practice goes better with the historic pattern documented than with it asserted.
A company deciding whether to fix a root cause. Before investing in a change at the originating function, whether that is routing, packing, labelling, ASN accuracy or pricing setup, the reader wants to know which originator the pattern actually traces to.
If none of these describe you, your question is probably about the money still on the table rather than the money already gone. Start with a Chargeback Recovery Assessment instead.
What We Would Need From You
A historic audit runs on the records you already hold. Samples suffice to begin, and a full document pull is not required to start.
| Field or artifact | Why we need it |
|---|---|
| Deduction detail export covering the historic period | The spine of the audit. Every line has to be classifiable by retailer, date, amount, reason and invoice reference before any pattern can be read from it. |
| Remittance or check detail | Shows what was actually paid against what was billed. This is where a deduction repaid but never credited back becomes visible, and where a deduction taken more than once shows up as a second hit against the same invoice. |
| Retailer deduction reports for your largest accounts | The retailer's own record of what it took and why. Reading it against your export is what separates a deduction you never examined from a deduction your system recorded differently. |
| Any dispute correspondence that exists | Identifies disputes that were opened and then abandoned, which is a distinct category from deductions never disputed at all, and which usually points at a process break rather than a merits problem. |
What a Historic Audit Can and Cannot Produce
A historic audit is an analysis, not a recovery. It produces no guarantee and no projection of an outcome. State these limits to yourself before you send anything.
A closed deduction outside a retailer's dispute window is generally not recoverable. Where that is the case, the value of the audit is the pattern and the evidence, not the money. If that is not worth the exercise to you, the audit is the wrong product and you should start with an assessment instead.
We publish no window length for any retailer, because we hold no sourced figure for any of them. Whether a given deduction is still inside a window is determined against that retailer's own terms as they apply to you, not against a number we have printed on a page.
The audit describes; it does not commit. Nothing in it is a statement of what a retailer would accept, what would be repaid, or how long anything would take.
What Comes Out of It
A historic audit returns the following.
The categories found.
Every classifiable line sorted into what it actually was: never disputed, disputed and abandoned, duplicate, taken more than once, repaid but never credited back, or examined and correctly absorbed.
The root-cause pattern by originator.
Which function inside your business the deductions trace back to, so a fix can be aimed at a cause rather than at the symptom.
What was absorbed without examination.
The portion of the historic book that was never looked at by anyone before it was written off.
What, if any, is still inside a window.
Anything the audit surfaces that has not yet closed belongs in a forward recovery process, and it moves there rather than staying in the audit. That is the Chargeback Recovery Assessment.
Questions
What is the difference between a historic audit and a chargeback recovery assessment?
- A Chargeback Recovery Assessment sizes the current book: the retailer deductions that are open now and still inside a retailer's dispute window, split into what is disputable and what is not. A historic deduction audit looks backward at deductions already taken and already closed, to identify what was absorbed without ever being examined and what caused it. The assessment is about money that may still be recoverable. The audit is about evidence and pattern. For most readers the assessment is the right starting point, because a deduction you can still dispute is worth more than one you cannot.
Can you recover a deduction that is already closed?
- Generally not, once the retailer's dispute window has passed. A historic deduction audit is an analysis, not a recovery, and it carries no guarantee and no projection of an outcome. Its value on closed deductions is the pattern: which categories the deductions fell into, which function inside the business they originated from, and what evidence exists to support a change in practice or a trading-terms conversation. Where an audit does surface a deduction that has not yet closed, that item moves into a forward dispute process rather than staying in the audit.
How far back does a historic audit look?
- Over the period you choose, bounded by what your deduction export actually covers. There is no fixed lookback. The practical constraint is the data: the audit can only classify lines that exist in your records with enough detail to identify the retailer, the invoice, the amount and the stated reason. If your export thins out beyond a certain point, that is where the audit's reliable view ends, and we will say so rather than extrapolate past it.
What data do I need to send for a historic audit?
- The artifacts are a deduction detail export covering the historic period, remittance or check detail, retailer deduction reports for your largest accounts, and any dispute correspondence that exists. Samples suffice to begin and a full document pull is not required to start. The deduction export is the only one that is strictly necessary to begin; the others sharpen the classification and are what make duplicates and uncredited repayments visible.
Does a historic audit find duplicate or double-taken deductions?
- Yes, where the records support it. Duplicates, deductions taken more than once against the same invoice, and deductions that were repaid but never credited back are all categories the audit classifies for. Finding them depends on having remittance or check detail alongside the deduction export, because the duplicate is usually only visible when what was billed is read against what was actually paid. A deduction export on its own can suggest a duplicate but rarely confirms one.
Is the historic audit a financial audit?
- No. A historic deduction audit is not a financial statement audit, a tax audit, or an IT or security audit, and it produces no opinion, attestation or certification of any kind. It is an operational analysis of retailer deductions taken against a supplier's invoice, run by ROIAI One against records the supplier already holds. It carries no regulatory standing and is not performed by or on behalf of an accounting firm.
Does a person review the work?
- Review is selective and exception-based. ROIAI One's own analysts review the exceptions that need judgment, not the customer's team. Auto-submission is off by default for every reason code, and enabling it for a given reason code is a deliberate change the customer makes and can reverse. A historic audit produces analysis rather than submissions, so nothing in it goes to a retailer at all.
Start With the Assessment
If you are unsure which of the two you want, start with a Chargeback Recovery Assessment. It looks at the deductions that are open now and still inside a retailer's dispute window, and it answers the question with the most value attached: what of your current book is disputable, and what is not. The data it needs overlaps almost entirely with what a historic audit needs, so starting there costs you nothing if you later decide you also want the backward look.
Choose the historic audit when your question is genuinely about the past: an inherited book, a suspected duplicate, a renegotiation, or a root-cause decision. Otherwise, the assessment is the better first step, and we will say so if you ask us.
Start a Chargeback Recovery Assessment