In This Article
At some point, Amazon will ask you to prove where your stock came from. The trigger might be an authenticity complaint, a brand verification check, or an application to sell in a gated category. Whatever prompts it, the request looks the same: send us your invoices. And the clock starts immediately, because some violation response windows are as short as 17 days or two appeal attempts. Miss the deadline and the violation is upheld.
Amazon publishes its documentation standards in Seller Central help page GDQ9K277NYP6WNEW, but the gap between what the help page says and what actually passes verification catches sellers out constantly. Plenty of sellers with entirely genuine stock have had invoices rejected over a missing supplier website, a slightly mismatched address, or a price redaction done in the wrong software.
This guide covers what Amazon accepts as an invoice, the fields reviewers actually check, the most common reasons documents get rejected, and how to keep your paperwork ready before the request ever lands.
What Counts as an Invoice (and What Doesn't)
Amazon wants a real commercial invoice. That means a bill issued by your supplier after a completed purchase, showing what you bought, in what quantity, from whom, and when. Much of what sellers submit doesn't meet that bar.
Pro forma invoices are the most common near-miss. A pro forma is a preliminary bill or formal quote issued before the transaction completes. It looks like an invoice, but it doesn't prove you actually bought anything, so it doesn't demonstrate sourcing.
Order confirmations sit in the same bucket. A confirmation email or screenshot from an online marketplace shows that you placed an order, not that a verifiable supplier sold you authentic goods. Amazon explicitly rejects platform confirmations from overseas wholesale marketplaces.
Retail receipts fail too, for reasons worth their own section below. And handwritten invoices receive automatic rejection regardless of how legitimate the purchase was. Documents must be computer-generated or professionally printed, with consistent fonts throughout.
The Fields Reviewers Actually Check
Once a document clears the basic format test, reviewers work through the details. Knowing what they look for lets you check your own documents first.
Supplier information comes first. The invoice must display the supplier's complete company name, contact phone number, physical address, and website URL. The website requirement has become mandatory: a supplier with no web presence is treated as unverifiable, and the invoice is rejected on that basis alone. Before you submit, check the site loads and matches the invoice details.
Your own details need to mirror your Seller Central registration exactly. That means your registered business name rather than a personal name, and a complete, unabbreviated address. An invoice addressed to "J. Smith" when the account is registered to "JS Trading Ltd" is a genuine rejection risk, not a technicality.
Dates matter more than most sellers realise. Invoices dated within 365 days before the performance notification are acceptable, though anything within 180 days is considerably safer. An invoice from eleven months ago is technically valid and practically weak.
The products themselves must be clearly identified: product names, model numbers, and barcodes or UPCs that correspond to the flagged ASINs. A line reading "Assorted Electronics" fails verification because a reviewer cannot tie it to anything you sold. Quantities should match or exceed your documented sales volume for those products. If you've sold 300 units and your invoice covers 50, the reviewer will ask the obvious question.
Finally, presentation. Acceptable formats are PDF or image files (JPG, PNG, GIF), scanned at a minimum of 300 DPI. Blurry scans, cropped images, and low-resolution files get rejected before anyone reads the content.
Then there's pricing, the one field Amazon permits you to redact. Sellers debate whether to bother. Leaving prices visible signals you have nothing to hide, while redacting protects your margins from anyone who sees the document. Both are acceptable to Amazon. What matters far more is how you redact, which brings us to verification.
How Amazon Verifies, and the Redaction Trap
Verification is more thorough than many sellers expect. Automated systems scan submitted documents for formatting inconsistencies, metadata anomalies, and technical irregularities, and Amazon maintains records of authentic invoice templates from recognised suppliers to compare against. Investigation teams also telephone suppliers directly to confirm the customer relationship and validate invoice details, and they examine supplier websites for professional presentation and basic legitimacy.
This is exactly where redaction goes wrong. Open a PDF in editing software to black out a price and the file's metadata changes. Amazon's systems flag the document as manipulated, even though you only covered a number you were allowed to cover. The safe method is deliberately low-tech: print the invoice, cover the pricing with a black marker, scan the marked page, and save it as a JPG. Keep unaltered documents as PDFs and never edit an invoice digitally under any circumstances.
The supplier phone call deserves preparation too. Tell your suppliers that Amazon may contact them to verify invoices, and make sure the person answering recognises your business name. A confused supplier who can't confirm the relationship undermines an otherwise perfect document.
Why Retail Arbitrage Documentation Usually Fails
If you source stock from retail stores or consumer websites, the documentation problem is structural, not procedural. A retail receipt names you as a consumer, not a business customer. There's no trade account behind it, no phone number that leads to someone who knows you as a wholesale buyer, and the retailer's website is a shop, not a supplier site in the sense Amazon means. Quantities on retail receipts also rarely come close to covering the sales volume of an established listing.
That's why retail receipts from consumer retailers appear on Amazon's rejection list outright. The goods can be completely genuine and the receipts completely real, and the documentation still fails, because verification is built around traceable supplier relationships rather than proof of purchase. Sellers running retail arbitrage should understand this before an authenticity complaint arrives, not after.
Keeping Your Documentation Audit-Ready
The sellers who pass verification are almost always the ones whose paperwork existed before Amazon asked for it. Obtain proper commercial invoices at the time of purchase, not retrospectively when a notification lands. Brief suppliers on Amazon's requirements so their invoices carry the right details from the start. File everything with descriptive names, organised by supplier and date, so you can retrieve the right document inside a 17-day window without a frantic search.
Watch the calendar as well. An invoice's usefulness effectively expires at 365 days, so regular reorder cycles should be generating fresh documentation for every live ASIN. If you manage dozens of suppliers, document management tools with OCR can pull supplier names, dates and quantities from scanned invoices automatically and flag documents approaching the 180-day mark. It's a modest use of automation, and it won't rescue a non-compliant invoice, but it takes the tracking burden off whoever currently does it in their head.
Before Amazon Asks
Pull the invoices for your top ten ASINs today and check them against the list above: supplier name, phone, address and working website, your details matching Seller Central exactly, product identifiers tied to ASINs, quantities covering sales, dates inside 180 days, clean 300 DPI scans.
Fixing gaps now takes an email to a supplier. Fixing them during an enforcement window takes luck.
Which Tools Can Do This?
Power Automate (part of Microsoft 365) can file supplier invoices into a structured archive and send reminders as documents approach the 180-day and 365-day marks. Make and Zapier handle the same filing and reminder workflows. OCR services and AI models such as OpenAI, Claude and Gemini can extract invoice fields at volume if you're processing serious paperwork, and custom API work covers more complex setups. None of it substitutes for a proper commercial invoice from a legitimate supplier.
If you'd rather have someone build and run the whole documentation process, that's what Fulcrum Three does: audit-ready supplier records, deadline tracking, and support when Amazon comes asking.
Get your sourcing paperwork audit-ready before Amazon asks.
Book a Free Operations Audit →