A useful supplier claim pack answers four questions: what was agreed, what happened, how the requested amount was calculated, and what response is needed. Build the pack around those questions, with a reference for every transaction and a clear owner for unresolved facts.
Use this checklist before submitting an operational claim such as a price correction, rebate, or shortage adjustment. Whether a claim is valid depends on the applicable agreement and evidence. Route disputed interpretation and commercial concessions to the authorised buyer; finance approves amounts and financial treatment.
Download the supplier claim evidence index and checklist (Excel) to prepare a pack another person can verify without reading your inbox.
Start with a one-page claim summary
State the supplier and buying entity, claim type, requested amount and currency, covered period or transactions, and requested resolution. Give the claim a stable identifier and use it in the subject line, transaction list, and evidence filenames.
Summarise the basis in a few sentences. “The accepted schedule specifies $7.20 for these orders; the listed invoice lines use $7.45” is more useful than “Pricing discrepancy, please see attachments.” If a fact is disputed or missing, state that fact and the decision it prevents.
Name the owner and include a requested response date appropriate to the agreement and operational timetable. Record submission requirements or deadlines from the agreement rather than borrowing a generic claim window.
Evidence of what was agreed
Attach the relevant agreement, accepted quotation, order acknowledgement, or approved amendment. Identify the exact revision and applicable clause or price line. Keep enough surrounding context for the supplier to check eligibility, including scope and date rules.
Check these questions before submission:
- Does the evidence cover the correct supplier and buying entity?
- Does it cover this material, specification, or qualifying activity?
- Which event and date determine whether the terms apply?
- Are there quantity conditions, exclusions, or required notices?
- Was a later amendment or order-specific exception accepted?
For rebate claims, product settings can affect transaction eligibility. Microsoft's vendor rebate documentation illustrates date and unit-of-measure conditions in Dynamics 365. Verify the actual agreement and configuration before treating a generated claim as ready to submit.
Evidence of what happened
Provide a transaction list with invoice and PO line references, dates, material identifiers, quantities, units, and currency. Link each line to the relevant document. Include shipment and receiving evidence when the claim depends on delivery or quantity.
Adapt the pack to the issue. A price claim needs the applicable price and invoiced price. A shortage claim needs the invoiced quantity, relevant shipment and receipt records, and evidence supporting the reported short quantity. A rebate claim needs the eligible population and adjustment rules. Sending every available document does not compensate for missing the one record that establishes the claim.
Keep original records and label explanatory extracts. If a screenshot shows only one line, identify its source document and page so the supplier can find the context. Exclude unrelated internal conversations and commercial information about other suppliers.
Evidence of the amount requested
Show the calculation at the transaction level and reconcile it to the claim total. Explain unit conversions, exclusions, previous credits, and any partial amounts. Keep currencies separate unless finance supplies an approved conversion basis.
Illustrative example: two invoice lines each cover 400 units, with a proposed price correction of $0.25 per unit. The initial difference is $200. A verified earlier credit already covers $60 of the first line. The new request is $140, with the earlier credit referenced against that line.
Without that reference, the supplier might reject the request as duplicative or the buyer might count the same $60 twice. Preserve the original calculation, previous adjustment, and remaining amount as distinct fields.
If a return, replacement, or invoice correction is still unresolved, show the uncertainty explicitly. Ask the relevant owner to settle the factual question before finalising an amount that depends on it.
Match the evidence to the disputed condition
Build a short proof map before assembling attachments. For each condition, record the claim line, the statement you need to establish, the evidence reference, and any remaining uncertainty. This makes the pack reviewable and prevents a large attachment set from hiding an unsupported conclusion.
For a rebate, the key question may be whether the transaction falls inside the qualifying population. Link the agreement's date rule to the actual transaction date and show excluded returns. For price protection, the question may be which inventory was covered at the agreed cutoff. Preserve the inventory snapshot and receipt references, using the price protection guide for the detailed calculation.
For ship-and-debit, link each sale to the approved customer, material, authorisation, rate, and qualifying event. A valid sale does not by itself prove that the supplier approved support for that sale. For a return, distinguish physical dispatch from supplier receipt and acceptance, using the returns and credit guide to track those milestones.
When a document establishes only part of a condition, say so. A carrier delivery scan can support arrival at a location; it may not establish the supplier's accepted quantity or agreed credit amount. A quality inspection can establish the reported defect without determining the commercial remedy. Name the person who can decide what the evidence does not settle.
Reconcile the pack from source population to final request
Use a reconciliation a reviewer can reproduce without opening every attachment. Consider an illustrative price claim spanning four candidate invoice lines:
- L1: 300 units × $0.40 difference = $120. A previous verified credit covers $30, leaving $90 requested.
- L2: 200 units × $0.25 difference = $50, all supported and requested.
- L3: 100 units × $0.60 apparent difference = $60. The material revision is disputed, so this amount remains under review and is excluded from this submission.
- L4: 100 units × $0.20 apparent difference = $20. An approved amendment validates the invoiced price, so no amount is claimed.
Initial candidate differences $250
Less valid-price line $20
Less unresolved line excluded from submission $60
Less previous credit $30
New submitted request $140
The supplier can reproduce the $140 request as $90 plus $50. Internally, the $60 uncertainty remains assigned to a buyer. The $20 is closed as valid price with the amendment attached. Neither amount is presented as settled benefit, and the existing $30 credit is not requested again.
If the supplier later accepts $100 of the $140 and disputes $40, record both against the submitted lines. Keep the $60 unsubmitted issue separate from the $40 submitted dispute. Combining them into a generic $100 balance would obscure the fact that they require different next steps.
Separate evidence repair from commercial approval
The claim owner can request a missing invoice or correct a transposed reference when the source proves the correction. They should record the old and new value in the version history. A changed eligibility rule, waived condition, substitute product, or proposed compromise goes to the commercial owner. Finance approves changes to the requested amount and final financial treatment.
A late-discovered fact can change a claim that was already sent. Freeze the old submission, create a revised calculation, and identify the delta and affected lines. Ask the supplier which correction channel to use. Retain acknowledgement of the replacement or adjustment so the two versions are not processed as separate claims.
For unavailable evidence, record who searched which source and when, then ask the owner to choose the next step. That might be requesting a supplier copy, obtaining a documented clarification, or withdrawing an unsupported line. An inferred date or convenient replacement identifier should never be presented as an original record.
Check whether better evidence reduces avoidable rework
Measure first-response evidence completeness for a defined set of submitted claims: claims whose first substantive supplier review requests no missing evidence divided by claims that received a substantive review. Report unanswered claims separately. A receipt acknowledgement does not qualify as a review.
Track rejection reasons at line level, distinguishing missing evidence, factual mismatch, commercial disagreement, and unsupported eligibility. These are working categories your team defines, not universal supplier codes. Retain the supplier's original reason beside your category.
A decrease in missing-evidence rejections is useful only if the mix and coverage are visible. Compare like claim types and include the submitted line count, claim amount by currency, and proportion still awaiting review. Do not use a high acceptance percentage to justify omitting difficult supported claims from the process.
Run a completeness review before sending
Have a colleague reconstruct the request from the summary and evidence index. They should be able to identify the governing terms, locate a sample transaction, reproduce its amount, and understand the requested action.
Use a simple index:
E01 — Accepted agreement, revision, applicable section
E02 — Transaction list and calculation, version/date
E03 — Issued PO and supplier acknowledgement
E04 — Invoice lines supporting the request
E05 — Receipt or shipment evidence, where relevant
E06 — Previous credits or related claim references
Remove irrelevant categories and add evidence the agreement requires. An absent category should be marked “not applicable” with a reason when that helps the reviewer; it should never be filled with invented or assumed evidence.
Preserve the submitted version and work the response
Save the exact pack sent, destination, submission date, and proof of receipt. If a supplier portal supplies a claim number, link it to your internal identifier. Record corrections as new versions so both parties know which transaction list they are discussing.
When the supplier disputes part of the pack, record the disputed line and requested evidence. When they agree, record the accepted amount and promised document date. Follow that agreement through the credit-note tracking process, including finance verification and the remaining balance.
Mandel's claims and entitlements work uses this evidence chain to support supplier follow-up and decision-ready escalation. A strong pack makes the next action clear, whether the final result is a supported credit, a corrected calculation, or an approved commercial resolution.
