Every finding binds to the invoice line it came from and the clause that governs it — quoted word for word, anchored to the page it was read from, with the arithmetic set out to be redone by hand.
Intake, extraction, adjudication, verification, delivery. Each one records what it received and what it produced, so any figure on the last page can be walked back to the file it came in on.
Every clause is checked back against the extracted document text as an exact substring, and the page is derived from where the match lands. No match, no term, no finding built on it.
Your workpapers and their evidence chain stay yours. The source documents you uploaded are purged on schedule thirty days after the deliverables land — they existed to be audited, not kept.
A trail that keeps only its successes is not a trail.
Five links on one threaded spine, each hung beside what it recorded and what a reviewer can re-derive from it. One of these two dockets closed. The other parted at the second link — and was delivered anyway, with the break drawn where it happened.
Docket
WP-2026-0801-9041
Intake
Recorded here
The AR export, the remittance advice, and the signed agreement, as delivered. Row 412 of the export; remittance advice #8841.
What a reviewer re-derives
Open your own export at row 412. The invoice, the billed total and the amount that cleared are the same three numbers this chain starts from.
Extraction
Recorded here
The governing term, quoted verbatim, with the page it resolved on computed from where the match landed in the document text.
“Promotional case pricing under Schedule B applies to orders shipped between 1 March and 30 April. Orders shipped outside that window are billed at the standard case rate.”
What a reviewer re-derives
Turn to page 12 and find the sentence, word for word. It matched exactly or the term would have been dropped and no finding built on it.
Adjudication
Recorded here
4,150 cases × ($22.40 standard − $20.25 promotional) = $8,922.50. Ship date 2026-05-14, fourteen days past the window the clause names.
What a reviewer re-derives
Redo the multiplication by hand. It is deterministic code working in integer cents, not a model estimating a number — the same inputs give the same result every run.
Verification
Recorded here
Ruled recoverable on 2026-08-03 against the quoted clause and the arithmetic above it, then reviewed before delivery on this illustrative account.
What a reviewer re-derives
Nothing here rested on a reading of intent. The ship date is on the document you sent and the window is in the clause.
Delivery
Recorded here
The workpaper and the dispute package, delivered as files. The activity trail keeps who ran the audit and when it was delivered.
What a reviewer re-derives
The package goes out under your name or it does not go out. Axiom never contacts your buyer and writes nothing back to your systems.
From 03 · Adjudication
$8,922.50
Auditor rationale
The clause resolved verbatim in the signed agreement and the day count is arithmetic. The promotional rate the buyer paid at was not available on the date the order shipped.
D. Whitfield
Illustrative reviewer
Illustrative invoice and figures
Showing docket WP-2026-0801-9041, Unit price variance, auditor verdict Signed.
No certification stands behind this. The mechanism does, and it can be explained to your auditor line by line.
When someone asks where a recovery came from — an external auditor sampling write-offs, or the buyer disputing your dispute — the answer already exists rather than being reconstructed from memory.
Extraction is page-anchored: the citation is derived from where the quoted text actually resolves in the document, so the reference cannot drift away from the sentence it points at.
A language model does one job: reading a contract and returning the terms it found. Every dollar after that is computed deterministically in integer cents, so any amount can be recomputed by hand.
Findings that do not hold are delivered alongside the ones that do, each with the clause it was tested against. A docket that only lists winners tells you nothing about what was tested.
No connectors, no credentials into your ERP, no IT ticket. Results leave the same way they arrived, which is also why there is no integration to approve before the first audit runs.
Who ran the audit, what was ingested, and when the deliverables went out are recorded alongside the findings — the operational half of the story, kept for the moment somebody asks.
Send your short-pay remittances and the contracts behind them. Every finding comes back with the clause it rests on, the page it resolved on, and the arithmetic that produced it — including the ones the audit ruled out, which stay on the trail with their reasons.