A claim letter over three exhibits: the workpaper, the governing clause with the page it came from, and the remittance line the buyer sent. It goes out under your name, on your channel, when you say so.
You approve every package · nothing is filed on your behalf
The paperwork behind a claim is gathered while the audit runs, so a dispute does not begin with somebody digging through a shared drive for the contract.
The letter is a deterministic template filled from the verified quote and the arithmetic. A model never drafts it, so a doctored contract cannot talk one up.
Packages come out as documents your team files, through whichever channel that buyer uses. We never log into a portal and never email your customers.
A letter over three exhibits, each pinned to the page it came from. A buyer’s AP team reads a package looking for the one thing in it they can reject, so nothing in this one is asserted without its source.
Dispute of deduction — Invoice INV-90512
To the accounts payable team at Buyer B:
Our audit of invoice INV-90512 identified a deduction of $8,410.50 that is not supported by the vendor agreement on file.
The agreement states:
We request repayment of $8,410.50 for invoice INV-90512. Please reference this invoice number in your response.
One document, not a folder of attachments. Exhibit A is the workpaper the finding became; B and C are the two pages it argues from.
“Unit pricing for all Schedule B items is fixed at the rates set out in Appendix 1 for the term of this agreement. No price adjustment may be applied by Customer without a written amendment executed by both parties.”
The quote resolved as an exact substring of the uploaded contract, so the page number is a location rather than a guess. A quote that does not resolve is dropped in the engine and no claim is built on it.
PRICE DIFF PER CONTRACT RATE
The package is finished and it is still sitting here. Nothing in Axiom sends it, schedules it or files it on your behalf — your team reads it, signs it, and puts it through whatever channel that buyer uses. Your customer hears from you.
A buyer’s AP team reads a package looking for the reason to reject it. Half of what follows is a refusal, and that is the half that holds.
A fixed template filled from the verified quote and the arithmetic. A language model reads contracts here; it does not write a word that goes to your buyer.
Drafting refuses outright unless the finding carries both a clause quoted from your document and a positive recoverable amount. There is no fallback that guesses.
The package comes out as a single workpaper carrying the line, the clause with its page, and the arithmetic. Nothing for anyone to chase down separately.
Amounts are computed in code, in integer cents, and the derivation is printed beside them. A reviewer with a calculator can arrive at the same number.
Packages sit finished until somebody on your team approves them. Axiom never logs into a buyer portal and never emails your customers on your behalf.
A portal upload, an email to a deductions analyst, an attachment on an existing thread. The package is a document, so it fits the route you already use.
Send a short-pay and the contract behind it. What comes back is the document your team would file: the letter, the workpaper, the clause with its page, and the arithmetic — and it sits there until you decide it goes anywhere.