Operations: fulfilment, packaging & compliance
Wholesale invoicing is the process of asking a retailer for money you have already earned, and then making sure the request survives their accounts payable system. It is the part of selling wholesale that nobody warns an Amazon seller about, because on Amazon there is no asking. The settlement runs, the fees come out, and a fortnight later the balance lands in your bank account whether you thought about it or not.
Off Amazon, nothing happens until you raise a document. If that document is wrong, nothing happens after it either. This article is about the process and the machine on the other side of it. The document itself, field by field, is covered in wholesale invoice for an Amazon seller.
Nobody sends the money automatically any more
The Amazon payout cycle trains a particular habit. Revenue is a number you read in a report. Cash is a number that appears on a schedule you do not control and did not have to trigger. Your only job is to watch the reserve and the disbursement date.
Wholesale reverses that. The retailer has your goods on their shelf and your money in their bank, and they are entirely comfortable leaving it there until an invoice shows up that their system can process without a human thinking about it. Accounts payable is not being difficult. They pay thousands of suppliers on a fixed cycle, and anything that cannot be matched automatically drops into an exceptions queue where it waits for somebody's attention.
The practical consequence is that invoicing becomes an operational function of your business, not a piece of admin you do when you remember. Somebody has to raise invoices the day goods ship, watch what is outstanding, and chase what is late. On Amazon that person did not need to exist.
When may you raise the invoice?
There are three moments a new supplier confuses, and only one of them is right.
The purchase order arriving is not an invoicing event. A purchase order is an intention to buy at stated prices and quantities, and the anatomy of one is worth reading before you accept your first, which is what purchase orders covers. Nothing is owed until goods move.
The goods leaving your building is the event. On almost every set of wholesale terms you invoice on ship, against the quantity actually shipped rather than the quantity ordered. Ship forty cases against an order of forty-eight and you invoice forty, and you tell the buyer why before they find out from their receiving report.
The exception is advance shipment notice sequencing. Where a retailer expects an electronic shipping notice, that notice must reach them before the invoice does, and preferably before the truck does. An invoice that arrives ahead of the shipping notice has nothing to attach to. It sits, and it ages, and the first anyone notices is when you are chasing at day forty-five.
One more timing rule worth internalising. Do not invoice before the goods are collected because the paperwork is convenient to do on Friday. If the pickup slips to Monday, your invoice date is now earlier than your ship date, and on receipt-date terms that mismatch is an automatic hold.
Where does the invoice actually go?
Not to your buyer. Your buyer is a merchant: they choose products, negotiate prices and own the shelf. They do not pay invoices and in most companies cannot see one. Sending the invoice to the person who placed the order is the single most common reason a first wholesale payment runs late.
Where it goes depends entirely on the size of the account, and it is worth asking at the point you accept the purchase order rather than thirty days later.
| Buyer type | Where the invoice goes | What they need from you |
|---|---|---|
| Independent store | Owner or bookkeeper email | A clear PDF and bank details |
| Regional chain | Accounts payable inbox or portal | Purchase order number, vendor number |
| National chain | Supplier portal or electronic invoice feed | Vendor setup, item numbers, strict format |
| Distributor | Accounts payable inbox, sometimes a network | Remittance terms agreed in writing |
The large accounts are the interesting ones. A national retailer will usually route you into either a supplier portal where you key or upload the invoice, or an electronic data interchange feed where your system transmits a structured invoice document directly into theirs. There is also a middle path: third-party invoicing networks that sit between suppliers and large buyers, where you submit once and the network delivers in whatever format the buyer consumes. Some of those networks charge the supplier a fee per invoice or a subscription, and that cost belongs in your wholesale price rather than in a surprise.
Whichever route applies, get it in writing during vendor setup, along with the vendor number they have assigned you. That number is how their system knows the invoice is yours.
The three-way match, and why your invoice is parked
Inside accounts payable, an invoice is not read. It is matched. Three documents have to agree before payment is released: the purchase order they issued, the receiving record their warehouse created when the goods were counted in, and your invoice.
Purchase order to invoice checks the prices and the item numbers. Receiving record to invoice checks the quantities. If all three agree, the invoice is approved without human involvement and enters the payment run for its due date. If any two disagree, it parks.
The mismatches that park invoices are boringly consistent. A price on the invoice that differs from the price on the purchase order, usually because a discount was agreed by email and never reissued on the order. A quantity that differs from what receiving counted, because a case was damaged, or because you shipped complete and they received short. A missing or mistyped purchase order number, which means the invoice cannot find an order at all. An item number that is yours rather than theirs, so their system does not recognise the line.
The cruel part is that nobody tells you. A parked invoice does not generate an email to the supplier in most systems. It generates a task for an accounts payable clerk, who works through a queue, and your invoice is in it with several hundred others. You will discover the problem when you chase, which is why chasing is a scheduled activity rather than a reaction.
Two habits prevent most of this. Invoice against the purchase order document rather than against your own record of the conversation, and invoice the quantity that shipped rather than the quantity you meant to ship.
Invoice numbering and one invoice per purchase order
Your invoice number is the key their system files you under, and it has to be unique across your entire business forever. Reusing a number, even years apart, triggers a duplicate check and stops the payment.
Keep it simple and sequential. A prefix and a running number is enough. Resist the temptation to encode the customer and the month into the number, because the moment you change the scheme you create collisions with the old one.
The other discipline is one invoice per purchase order. It is tempting to combine three orders that shipped the same week into a single invoice with a bigger total, and it fails every time, because the three-way match cannot reconcile one invoice against three orders and three receiving records. Split them. If a single purchase order ships in two parts, raise two invoices, each showing the purchase order number and each marked as a partial shipment with the line quantities it actually covers.
Credit notes follow the same rule. A damaged case, an agreed allowance or a short shipment gets its own credit document referencing the original invoice number, not a handwritten adjustment to a figure on the original.
Statements, aging and knowing what you are owed
Once you are running more than a handful of accounts, you need two reports that no Amazon seller has ever had to build.
An accounts receivable aging report lists every unpaid invoice grouped by how overdue it is: not yet due, one to thirty days past due, thirty-one to sixty, and beyond. It answers the only question that matters in a cash crunch, which is not how much you are owed but how much is late and by whom.
A statement is what you send the customer: a list of their open invoices, dates, amounts and total balance. Sending a monthly statement to every wholesale account is unglamorous and it works, because it lands in accounts payable rather than with your buyer, and it surfaces invoices that never made it into their system at all. More than once the reply is that they never received it, which is a five-minute fix at day thirty and a serious problem at day ninety.
If you have been living off the Amazon settlement rhythm, seeing the aging report for the first time is a useful shock. The way the two cycles interact is worked through in Amazon payout versus net 30.
How do you chase a late payment without losing the account?
Assume the invoice is stuck, not refused. In nearly every case a late wholesale payment is an administrative fault rather than an unwillingness to pay, and the tone that gets it moving is the tone of somebody helping fix a filing problem.
A workable sequence, with no drama in it:
- Five days before due. A short note to accounts payable confirming the invoice is on the schedule and asking whether anything is needed. This single email catches most parked invoices before they are late.
- Three days after due. Re-send the invoice as an attachment with the purchase order number in the subject line, and ask directly whether it has been approved for payment.
- Day fifteen past due. Ask for the specific reason it is on hold and who can release it. A named person and a reason turns a silence into a task.
- Day thirty past due. Tell your buyer. Not as an escalation, but because a buyer who wants the reorder can walk to finance in a way you cannot.
What not to do early: threaten to stop supply, mention interest, or copy in executives. Those are tools for a genuinely delinquent account, and using them on a stuck invoice costs you a customer over a clerical error. What you can do quietly is hold the next shipment while the current one is unpaid, and say so plainly when asked.
Who owns the chase in your business
The honest answer for most Amazon brands starting wholesale is that nobody does, which is why the first retail order is often paid in sixty days when the terms said thirty.
It does not need a hire. It needs a named person and a recurring slot in the week. Somebody raises invoices the day freight leaves, somebody looks at the aging report every Monday morning, and somebody sends the pre-due email. That can be the founder for the first year, as long as it is on the calendar rather than in their head.
Two decisions make the job small. Keep the number of terms you offer down to two or three, so the due dates are predictable. And write the terms on the invoice itself rather than assuming the customer remembers what was agreed, which is why the net 30 terms an Amazon seller signs up to deserve a deliberate decision rather than a default.
If you are still upstream of all this and trying to work out which retailers and distributors would carry your product, that is a cheaper question to answer first. Paste your product link into WholesalePilot and the preview shows who would plausibly stock it. The invoicing machinery only becomes worth building once there is a real purchase order to bill against, and the cash-flow consequences of that first order are set out in Amazon seller cash flow.