Claim

A claim is a documented assertion that a specific invoice charge conflicts with contract terms, submitted to a vendor for credit, refund, or correction.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Claim

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. A claim is the formal step that follows once that gap has been found: a written assertion, tied to specific invoice lines and specific contract language, that a vendor owes money back.

A claim is not a complaint. It names the invoice, the contract clause, the dollar amount, and the reason the charge is wrong, in a form the vendor can verify and act on. Without that structure, a finding stays a spreadsheet note instead of recovered cash.

1. What is a claim?

A claim is a formal, documented assertion that a vendor billed an amount its own contract does not support, submitted for credit or refund. It cites the invoice number, the line item, the contract clause it violates, and the dollar amount owed back. A finding becomes a claim only once it is packaged for the vendor to review and act on, not left as an internal note.

A finding is internal: an auditor flags a line that looks wrong against the rate card. A claim is external: the same finding, restated with the evidence a vendor's accounts receivable team needs to approve it without a back-and-forth.

2. What information does a claim contain?

A complete claim contains the invoice number and date, the specific line item disputed, the contract section and page it references, the correct amount under that contract, the billed amount, and the dollar variance. It also states the drift type: a duplicate payment, a missed credit memo, a rate card mismatch, or a volume tier applied incorrectly. Vague claims without a cited clause are the ones vendors push back on or ignore.

The contract citation matters most. A vendor's AP team cannot approve a claim it cannot verify against its own records, so the clause reference does the work a phone call otherwise would.

3. How does a claim differ from a dispute?

A claim is the initiating document: one party's assertion, with evidence, that money is owed. A dispute is what happens if the vendor disagrees with that assertion and the two sides negotiate the outcome. Most claims resolve without becoming disputes, because the underlying contract language is clear enough that the vendor's own records confirm the error once it is pointed out.

Treating every claim as an adversarial dispute slows recovery. A claim built on a clear contract citation is usually a data correction request, not a negotiation.

4. What happens after a claim is submitted?

A submitted claim is tracked to one of three outcomes: the vendor issues a credit memo, the vendor adjusts a future invoice, or the vendor contests it and the claim moves to negotiation. Tracking matters because a claim without a follow-up date tends to sit unresolved. The claim record stays open until a credit posts or the adjustment appears on a later invoice.

A claim that is submitted but never tracked to resolution is functionally the same as a finding that was never submitted. The recovery only exists once it clears.

For the wider pattern this sits inside, start with the margin drift guide. See also margin drift vs. legitimate price increases: how to tell them apart and off-contract resources: people billed outside the agreement.

5. Frequently Asked Questions (People Also Ask)

What is a claim in an AP recovery audit?

A claim is a documented assertion that a specific invoice charge conflicts with the vendor contract, submitted to the vendor for credit or refund. It cites the invoice, the contract clause, and the dollar amount owed.

Is a claim the same as a finding?

No. A finding is an internal observation that a charge looks wrong. A claim is the same observation packaged with contract citations and evidence, formatted for the vendor to verify and act on.

Does a claim always lead to a dispute?

No. A claim built on a clear contract citation is usually resolved as a data correction once the vendor checks its own records. A dispute arises only when the vendor disagrees with the assertion.

What information makes a claim valid?

An invoice number, the specific line item, the contract section it violates, the correct amount, the billed amount, and the variance. A claim missing the contract citation is the kind vendors are most likely to contest.

Who submits a claim, the company or the auditor?

The company submits the claim to its vendor. An auditor or diagnostic engagement identifies the underlying finding and drafts the claim, but the claim itself is a company-to-vendor document.

How is a claim tracked to resolution?

Each claim needs a status and a follow-up date: submitted, credit issued, adjusted on a future invoice, or contested. A claim without a tracked follow-up date is unlikely to be resolved.

Can a claim cover more than one invoice?

Yes, if the same contract violation appears across multiple invoices, such as a rate card error applied repeatedly. Each affected invoice line is still listed individually so the vendor can verify each one.

What drift types typically generate claims?

Any contract violation can generate a claim. Common examples include a duplicate payment, a missed credit memo, a rate card mismatch, or a volume tier applied incorrectly. Each is described on its own terms, on its own page.

1. What is a claim?

A claim is a formal, documented assertion that a vendor billed an amount its own contract does not support, submitted for credit or refund. It cites the invoice number, the line item, the contract clause it violates, and the dollar amount owed back. A finding becomes a claim only once it is packaged for the vendor to review and act on, not left as an internal note. A finding is internal: an auditor flags a line that looks wrong against the rate card. A claim is external: the same finding, restated with the evidence a vendor's accounts receivable team needs to approve it without a back-and-forth.

2. What information does a claim contain?

A complete claim contains the invoice number and date, the specific line item disputed, the contract section and page it references, the correct amount under that contract, the billed amount, and the dollar variance. It also states the drift type: a duplicate payment, a missed credit memo, a rate card mismatch, or a volume tier applied incorrectly. Vague claims without a cited clause are the ones vendors push back on or ignore. The contract citation matters most. A vendor's AP team cannot approve a claim it cannot verify against its own records, so the clause reference does the work a phone call otherwise would.

3. How does a claim differ from a dispute?

A claim is the initiating document: one party's assertion, with evidence, that money is owed. A dispute is what happens if the vendor disagrees with that assertion and the two sides negotiate the outcome. Most claims resolve without becoming disputes, because the underlying contract language is clear enough that the vendor's own records confirm the error once it is pointed out. Treating every claim as an adversarial dispute slows recovery. A claim built on a clear contract citation is usually a data correction request, not a negotiation.

4. What happens after a claim is submitted?

A submitted claim is tracked to one of three outcomes: the vendor issues a credit memo, the vendor adjusts a future invoice, or the vendor contests it and the claim moves to negotiation. Tracking matters because a claim without a follow-up date tends to sit unresolved. The claim record stays open until a credit posts or the adjustment appears on a later invoice. A claim that is submitted but never tracked to resolution is functionally the same as a finding that was never submitted. The recovery only exists once it clears. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide. See also [margin drift vs. legitimate price increases: how to tell them apart](/guides/margin-drift-vs-legitimate-price-increases-how-to-tell-them) and [off-contract resources: people billed outside the agreement](/guides/off-contract-resources-people-billed-outside-the-agreement).

Questions & Answers

What is a claim in an AP recovery audit?

A claim is a documented assertion that a specific invoice charge conflicts with the vendor contract, submitted to the vendor for credit or refund. It cites the invoice, the contract clause, and the dollar amount owed.

Is a claim the same as a finding?

No. A finding is an internal observation that a charge looks wrong. A claim is the same observation packaged with contract citations and evidence, formatted for the vendor to verify and act on.

Does a claim always lead to a dispute?

No. A claim built on a clear contract citation is usually resolved as a data correction once the vendor checks its own records. A dispute arises only when the vendor disagrees with the assertion.

What information makes a claim valid?

An invoice number, the specific line item, the contract section it violates, the correct amount, the billed amount, and the variance. A claim missing the contract citation is the kind vendors are most likely to contest.

Who submits a claim, the company or the auditor?

The company submits the claim to its vendor. An auditor or diagnostic engagement identifies the underlying finding and drafts the claim, but the claim itself is a company-to-vendor document.

Margin Drift Resources