Getting wholesale invoices paid: reminders, pay links, statements

Extending net terms is a decision you make once per account. Collecting on them is a job you do every week, forever. Most guides stop at "send invoices promptly," which is like ending a delivery guide at "load the truck." This one covers the other half: why invoices actually go late, the reminder cadence that gets you paid without souring the relationship, and how to make paying so easy that the check in the mail becomes the exception. It is the collections companion to our guide on offering net terms to restaurant customers, which covers when to extend terms and how to size credit limits in the first place.

Why invoices go late (it is usually not malice)

Chasing money feels personal, so it helps to know what late usually means. In food distribution, most overdue invoices are one of these:

The invoice never made it into their system. It went to the chef's inbox instead of the bookkeeper's, or arrived as a paper slip on a wet pallet. An invoice that is not in their accounts-payable pile does not exist.
Their payment run has a rhythm yours does not match. Plenty of restaurants cut checks once or twice a month. A net-30 invoice that misses this run waits for the next one and arrives at day 40 through nobody's decision.
Something on the invoice is disputed. A shorted case, a credit that was promised but never issued. The whole invoice sits while one line is argued about.
Cash is genuinely tight. The minority case, but the important one, because it is the one where your credit limit is protecting you and where speed of detection matters.

Each cause has a different fix, and none of the fixes is "call and be angrier." The system below handles the first three automatically and surfaces the fourth early.

Send invoices the moment the truck rolls, to the right inbox

The collection clock starts when the invoice lands in accounts payable, not when you generate it. Two habits move real days:

Invoice on delivery, not at week's end. If orders come through a portal, the invoice should be born from the order itself, with the due date already computed from that account's terms. Batching invoicing to Friday afternoon quietly adds up to four days of aging to every account.

Bill to the bookkeeper, deliver to the chef. Every account should carry a billing email that is allowed to differ from the ordering contact. When an invoice needs to reach two people, copy them on one email rather than forwarding: everyone sees the same document, and nobody can claim they never got it.

A reminder cadence that keeps the relationship

The awkwardness of chasing money is the main reason it happens late and inconsistently. The fix is to make reminders a system rather than a judgment call, because a reminder nobody wrote cannot be taken personally. A cadence that works for weekly-delivery wholesale:

A few days before due: a short heads-up with the invoice attached and a payment link. Not a nag, a convenience. This one catches the "never reached AP" failure while the fix is still cheap.
On the due date or the day after: a polite note that the invoice is now due, same attachment, same link. Most accounts pay here.
A week overdue: still friendly, but now it asks a question that requires an answer: "Can you confirm when this is scheduled to be paid?" Questions get replies; statements get archived.
Two weeks overdue: the phone call. By now you know this is not a lost email, and a conversation will tell you whether you are dealing with a dispute, a cash problem, or a habit.

Two rules across all of it. Every reminder carries the invoice and a way to pay inside it, because a reminder that requires the recipient to go find the invoice is half a reminder. And the tone stays level from step one to step four: you are a supplier they need twice a week, and the goal is the money and the relationship.

Make paying easier than not paying

A wholesale buyer who has to find the checkbook, write the check, find a stamp, and mail it will do that in a batch, on their schedule. Every step you remove moves payment closer to the moment they read your email.

Put a pay link in the invoice email. A pay link takes the buyer straight to a page that shows what is owed and takes payment, no login hunt, no phone call to read a card number to your office manager. For the accounts that pay by card anyway, this alone can turn a two-week lag into a same-day payment.

Offer bank debit (ACH), not just card. Wholesale invoice totals are large, and card processing fees scale with the total while ACH fees mostly do not. ACH is also how larger accounts prefer to pay: their bookkeeper authorizes it once and payment stops being an errand. Card remains the right answer for speed and for smaller accounts.

Let buyers pay from their account, any time. If your customers order through a wholesale ordering portal, their open invoices should live behind the same login, each one payable on the spot. The buyer who thinks of you at 9 PM on a Sunday should be able to settle up at 9 PM on a Sunday.

One operational note: an online payment is not money in the bank the instant the buyer clicks. Card settlements take a couple of days and ACH a few more, which matters when you record the payment in your books. Our guide to recording customer payments in QuickBooks Online covers that timing question properly.

Statements: the backstop for accounts with many invoices

Reminders work invoice by invoice. But your busiest accounts might carry six or eight open invoices at once, and their bookkeeper does not reconcile invoices one at a time; they reconcile against a statement. A month-end statement, one page per account, listing every open invoice with its due date and an aging summary (current, 30, 60, 90+), does three jobs at once:

It is the document their bookkeeper actually wants, so disputes and missing invoices surface in one email instead of eight.
It quietly communicates the total. An account can rationalize one late invoice; a statement showing $4,300 across five invoices lands differently.
It gives your collections calls a shared reference: "looking at your August statement" is a better opening than a pile of invoice numbers.

Send statements only to accounts that owe something, and send them on the first of the month, every month, without deciding each time. Consistency is the point.

When the system says stop

Reminders and statements collect from the accounts that were always going to pay. The credit limit handles the ones that were not. If limits are enforced when orders are placed, an account sliding into trouble stops accumulating exposure on its own: the next order simply will not go through until the balance comes down. That converts an awkward judgment call ("should we still be delivering to them?") into a rule that was agreed to when the account was opened. How to size those limits, and what to do when a good account genuinely hits a rough patch, is covered in the net terms guide.

Where Minori Midori fits

Minori Midori runs this whole loop for food distributors on the Growth plan ($599/mo). Orders on terms become numbered invoices with due dates automatically, overdue accounts get reminder emails without anyone writing them, and buyers pay by card or bank debit (ACH) from the invoice email or their account page, with the invoice marking itself paid when the money lands. From any order, staff can email a payment link in a couple of clicks, with the invoice PDF attached, extra recipients in CC, and a personal note when the situation calls for one; sending a fresh link retires the previous one. Month-end statements with aging summaries go out on the first of the month to every account with a balance, and you can generate a current one mid-month before a collections call. The rest of the wholesale flow, from account approval to the delivery route, is in the full B2B ordering guide.