Verified transaction set reference
Amazon EDI 810 Invoice Validation
A syntactically valid invoice can still delay payment when it bills unshipped quantities, uses a mismatched product identifier, disagrees with agreed terms, has inconsistent tax totals, or supplies an address Amazon cannot match.
Direct answer
Direct answer
An 810 should not be approved from invoice arithmetic alone. Resolve it to the accepted purchase order and actual shipment, compare item identities and billed quantities, recompute line, allowance, charge, tax and document totals, validate party and payment details, and enforce invoice-number uniqueness and correction behavior.
What to check
- Require a unique invoice identity and non-future date.
- Resolve the invoice to the accepted PO and shipment.
- Prevent billed quantity from exceeding eligible shipped quantity.
- Recompute item, charge, allowance, tax and grand totals.
- Compare product identifiers and units with the PO.
- Validate remit-to, ship-to, bill-to and payment terms.
Accepted shape
PO line accepted 10 EA, 856 shipped 10 EA, 810 bills 10 EA and all detail sums to the invoice total.Rejected shape
The 810 bills 12 EA after only 10 EA were accepted and shipped, or the header tax differs from line tax totals.How to fix it
Build invoices from a three-way eligible-to-bill ledger derived from the active PO, acknowledgement and shipment. Recalculate totals independently, validate parties against controlled master data, and make correction/retry behavior explicit rather than reusing arbitrary IDs.
Evidence boundary
Amazon publishes current invoice business requirements through SP-API, but EDI 810 placement and code usage require the current account guide and appropriate X12 licence. Full 810 validation is not yet advertised by the live checker.
Sources