Amazon Shortage Claims: Reconcile and Dispute

Amazon shortage claims are Vendor Central invoice deductions for units Amazon has not matched to fulfillment-center receipts. They are 1P vendor payment issues, separate from chargebacks and seller Fulfillment by Amazon (FBA) reimbursements. Check the SC entry and matching status, then compare invoice, purchase order, shipment and receipt. Wait during review, correct a real discrepancy, or dispute a remaining deduction with line-level evidence.

The finance question is usually, “We shipped the units; why did Amazon deduct them?” A carrier's delivered status and an invoice total do not answer how many units Amazon matched to the correct product and purchase order. The decision depends on the account's actual records, not an assumed lost carton.

With authorized Vendor Central MCP purchase-order and shipment reads, and Selling Partner MCP Finance Remittance reads, an agent can assemble the transaction trail. Amazon Agent Atlas grounds the claim codes and dispute rules in Amazon's named help pages. Your invoice export, receiving view, carrier documents and approval rule supply the missing account evidence before anyone files.

An SC deduction is a shortage claim; a later SCR is its reversal

Start with the invoice and remittance, not the shipment tracking page. Amazon's Shortage claims and shortage claim reversals help page identifies an SC suffix as a shortage claim and an SCR suffix as a shortage claim reversal. An SCR is a credit against a prior shortage deduction, not another shortage to recover. The same page distinguishes other adjustment codes, including MAC and DSC; do not add unlike deductions into one shortage total.

The operator can inspect Payments → Invoices and Payments → Remittance in Vendor Central. The Finance Remittance API, listed under Sources, exposes vendor remittance headers and detail through getRemittanceHeaders and getRemittance, when the connected account has the Finance and Accounting role. Those authorized reads can help the agent link an SC and any later SCR to the invoice. They do not establish that Amazon received every unit.

Amazon's Financial Scorecard separates potential shortages from remaining shortages. A potential amount can still change as Amazon matches records. Dispute an invoice shortage says Amazon automatically reviews matching before the final shortage is settled; use the current account view and due date rather than filing as soon as a provisional amount appears.

Match invoiced units to the purchase order, shipment and Amazon receipt

A shortage can begin with a mismatch among the purchase order, invoice and received units. Amazon's Reduce shortage claims guidance calls out quantity, product-identifier, advance shipment notice, labeling and catalog problems. Its Supply chain, invoicing, and catalog issues guidance also warns that unit-versus-pack mismatches can make an apparently correct shipment look short. Compare one invoice line at the same unit of measure all the way through.

Build the line comparison from these records:

• Use the purchase order and shipment data available to the authorized Vendor Central MCP to identify the order, line, item and shipped quantity. Check the submitted advance shipment notice or shipment confirmation against the warehouse record.
• Bring the actual invoice and Amazon receiving view or export into the case; the currently verified connection does not establish an invoice-read or receipt-read operation for this workflow. Capture the product identifier, case pack, invoiced quantity, shipped quantity, Amazon-received quantity and each source's timestamp. Do not infer received units from a purchase-order status field.

Amazon's North American Vendor Manual explains that advance shipment notice errors and quantity mismatches can prevent Amazon from matching the purchase order, invoice and receipt. A delivered pallet may therefore coexist with an unmatched invoice line. A bill of lading or proof of delivery helps trace that pallet, but Reduce shortage claims says those documents alone are not used to decide payment. The decisive comparison is the line-level match in Amazon's records, supplemented by evidence of what left your facility.

A dispute needs one source-labeled packet and an operator handoff

When matching has finished and an SC balance remains despite records supporting the invoiced units, prepare a packet for the authorized Vendor Central operator. Dispute an invoice shortage asks for evidence of shipped quantities, product identifiers or barcodes and shipment dates. Include:

• The purchase order, invoice, advance shipment notice or shipment record, and Amazon receipt view.
• The SC remittance line, any SCR, and the relevant carrier document. Label each value by source; do not convert a carrier signature into an Amazon unit receipt.

Amazon's About Dispute Management and Dispute an invoice shortage pages place claim creation, correspondence and tracking in Vendor Central. The operator can use Payments → Invoices → Review/Dispute shortages or Dispute Management, subject to the account's current interface and instructions.

The Atlas source warns that an invoice has one dispute attempt, so check all affected lines and attachments before submission. If the claim is denied, use the current account guidance for any follow-up; older help text describes a re-dispute route that may have changed.

The agent's output is a proposed decision and evidence packet, not a filed dispute. An authorized person verifies the source files and submits it in Vendor Central. Keep the case ID, submission date, Amazon correspondence and later remittance entries together. A dispute submission does not equal a recovered payment; confirm the final outcome and any SCR in the remittance.

What happens next: decide one invoice line at a time

Use this one-invoice decision record. It is an illustrative artifact; fill it with your account's records and current policy before acting. Store source links or file IDs alongside each value so another operator can reproduce the comparison.

A Skill can make the checks repeatable and flag missing sources. The Amazon Agent Data layer and Agent Flow can retain the case and approval handoff in Private Cloud.

Where the business also sells or advertises the same item, the Amazon Ads MCP and Selling Partner MCP can surface adjacent activity, but those signals do not prove a vendor receipt or decide a shortage dispute. Managed MCP and Private Cloud are deployment choices for the connected reads; the manual Vendor Central handoff remains the same.

The useful result is a dated wait, correct, or dispute decision with a traceable invoice line and named next owner.

For a separate compliance deduction, use the vendor purchase-order chargeback dispute guide.