A payment schedule template answers one question for every order you fulfill: on which date does each piece of this money become yours to collect. Not “when will they pay,” which is their decision. When you are entitled to collect, which is yours.
The gap between those two things is where small businesses lose their cash flow. About 55% of all B2B invoiced sales in the US are overdue (The Kaplan Group), and 56% of small businesses report being owed money on unpaid invoices, averaging $17,500 per business (Intuit QuickBooks). A written schedule does not make anyone pay faster on its own. What it does is make “you are late” a statement of fact rather than an argument.
This is the template, the four moments that an order’s money should be tied to, and how to handle the customer who holds back payment because something arrived wrong.
The Bottom Line
Tie payment milestones to fulfillment events you can prove (order confirmed, van loaded, signature collected), not calendar dates that drift when the order does.
For anything you produce to order, take a deposit at confirmation. It is the only payment you can collect while the order is still in your hands.
US small businesses were paid an average of 7.8 days late in the December 2025 quarter, with invoices taking 27.9 days to clear (Xero). Set terms knowing the real number, not the number on the invoice.
Write the late fee into the schedule before the first order, not into the reminder email after the third.
Lower your delivery costs by 23%
How we reduce costs:
- No delivery vehicle expenses
- Optimized local routes
- Pay-per-delivery model
- Average 23% delivery cost reduction
What goes in a payment schedule template
Six columns, one row per payment. If a payment does not have a trigger and an amount, it is not a scheduled payment. It is a hope.
| Column | What it holds |
|---|---|
| Payment # | 1, 2, 3 in the order they come due |
| Trigger event | The fulfillment moment that makes it due: confirmation, dispatch, handover, or a date counted from one of those |
| Amount | A fixed sum or a stated percentage of order total |
| Due date | The actual date, filled in once the trigger fires |
| Method | Card, ACH, check, cash on delivery |
| Status | Invoiced, received, overdue, disputed |
The trigger column is the one that does the work, and it is the one generic templates leave out. A payment schedule built on calendar dates breaks the moment an order moves, and orders move constantly. A payment schedule built on triggers survives, because “50% on dispatch” is still true whether you dispatched on Tuesday or Thursday.
Note the difference between this and an invoice. The invoice is the document you send for one payment. The schedule is the map of all of them, and it exists before the first invoice does.
The four payment points in a delivered order
Almost every order you fulfill and deliver can be described with four moments. Most orders use two or three of them.
| Point | Trigger | Typical share | What it protects |
|---|---|---|---|
| Deposit | Order confirmed | 25–50% | Your production cost if they cancel |
| On dispatch | Van loaded, order leaves your building | 0–50% | Your exposure once the goods are out of your control |
| On handover | Driver collects a signature at the door | 0–100% | Everything, for one-off and retail customers |
| On terms | A set number of days counted from handover | Balance | Nothing; this is credit you are extending |
Read that last row carefully. Net terms are not a payment method, they are a loan you are making to your customer, unsecured, at 0% interest. Average B2B payment terms run around 45 days from invoicing, and roughly 43% of the total value of B2B invoices is overdue (Agiled). That is what you are signing up for when you write “net 30” without thinking about it.
Every one of those triggers except the deposit keys off a specific moment in your delivery day, which means the payment schedule and the operating schedule have to agree. Dispatch is not a vague concept here. It is the actual departure time on your delivery schedule template, and “50% on dispatch” is only enforceable if you can point at the row that says when the van left.
Payment terms for wholesale and standing accounts
Standing accounts are where terms are unavoidable. A restaurant receiving product three times a week is not paying at the door, and asking them to will cost you the account.
What works:
Net 15, not net 30, for new standing accounts. Move them to net 30 after six months of clean payment. Starting at 30 and tightening later is a conversation nobody wins.
Consolidated weekly or biweekly invoicing. One invoice covering six drops beats six invoices covering one drop each. It cuts your admin and theirs, and it gives you a single clear overdue date instead of six fuzzy ones.
A stated credit limit per account. When outstanding balance hits the limit, the next order is prepay. Write the number down at account opening so it is a policy rather than a confrontation.
Terms counted from delivery, not from invoice date. “Net 30 from delivery” removes the argument about when you sent the invoice.
For event and one-off orders the opposite applies: deposit at confirmation, balance due before or at handover, no terms at all. The customer has no ongoing relationship to protect, so you have nothing to hold back once the goods are delivered.
Around 65% of businesses spend roughly 14 hours a week chasing overdue invoices (Clockify). Most of that time is spent on accounts that should never have been on terms.
When a customer withholds payment over the delivery
This is the hard case, and it is common for anyone shipping food, flowers, or anything with a condition on arrival. The customer does not dispute the price. They dispute what showed up.
Your payment schedule needs a disputed status and a rule for what happens next:
Dispute the line, not the invoice. If four of twenty crates were a problem, the other sixteen are still due on the original date. Say so in writing the same day.
Require the claim within a stated window. 24 hours for perishables, 48 for everything else. A condition complaint that arrives a week later cannot be verified by anyone.
Ask for a photo at the point of complaint. Not to be adversarial, but because it is the only evidence either of you will have.
Settle with a credit against the next order, not a refund. It keeps the account, and it keeps the cash.
What decides most of these disputes is whether you can show the order left in the right condition. Temperature logs and vehicle sanitation records are what turn “your product arrived warm” into a factual question, which is why a cleaning and cold-chain schedule for your delivery vehicles and crates belongs in the same filing cabinet as your payment schedule. Signed daily checks mean a condition dispute gets resolved from records instead of from whoever sounds more certain on the phone.
Late payment fees and how to write them in
A late fee you invent after the fact is a threat. A late fee in the original schedule is a term of sale.
Put it in three places: the account application, the payment schedule itself, and the footer of every invoice. The wording only needs to cover four things: the grace period, the rate, how it compounds, and when the account moves to prepay.
A workable default for small operations: five business days’ grace, then 1.5% per month on the outstanding balance, calculated monthly rather than daily, with the account moving to prepay at 45 days past due. Check your state’s cap on commercial late-payment charges before you set the rate; several states limit it.
Then actually apply it, at least once, early, to a small balance. The first time you charge a late fee is the only time it teaches anything. A fee that exists in the paperwork and never on an invoice trains customers to treat your terms as decorative, and the most common reason customers give for paying late is simply their own liquidity (Agiled). You are competing with their other suppliers for position in a queue. Being the supplier whose terms have consequences moves you up it.
Reconciling the schedule against what actually happened
Once a month, put the schedule next to your bank feed and fill in the status column honestly.
You are looking for three patterns, and each has a different fix:
A customer consistently 10 days late. Their internal process is slower than your terms, not broken. Move their due date to match reality and stop spending time on reminders.
A customer whose lateness is growing. That is a credit risk signal, not an admin problem. Tighten terms or move them to prepay before the balance gets large.
Payments that were never triggered. Usually a dispatch or handover payment where nobody invoiced because nobody noticed the trigger fired. This is the leak that a trigger-based schedule is supposed to close, and finding several means your operating schedule and your payment schedule are not being read together.
Internal payment-process delays on the customer’s side account for about 33% of late payments (Agiled), and a good share of that is fixable by sending the invoice to the right person in the right format. Ask each standing account, once, who receives invoices and what they need on them. It is a ten-minute conversation that removes a recurring week of delay.
Frequently asked questions
What is a payment schedule template?
A payment schedule template is a reusable document that lists every payment due on an order, the event or date that makes each one due, the amount, and its current status. For a business that fulfills and delivers orders, the triggers are typically order confirmation, dispatch, handover at the door, and a set number of days after delivery.
How much deposit should you take on a made-to-order job?
Enough to cover your material and labour cost if the customer cancels. For most food, floral, and catering work that lands between 25% and 50% of the order total. The test is not what feels fair. It is whether you would be whole if they walked away the morning of.
Should you offer net 30?
To standing accounts with a payment history, yes. To new accounts, start at net 15 and earn the way to 30. To one-off and event customers, no: collect at or before handover. Net terms are unsecured credit, and average B2B terms of 45 days with 43% of invoice value overdue (Agiled) is the market you would be lending into.
What is the difference between a payment schedule and an invoice schedule?
The payment schedule says when money is due. The invoice schedule says when you send the paperwork asking for it. They are usually offset (you might invoice weekly on Friday for payments that came due on Tuesday and Thursday), and keeping them as separate columns stops you from assuming an invoice went out just because a payment came due.
How do you handle cash on delivery?
Treat it as a handover-triggered payment with a method of cash or card, and make the driver’s proof of collection part of the same record as the proof of delivery. The risk with COD is not the customer, it is the gap between money changing hands at a door and money appearing in your reconciliation.
Build it once for your three order types
You do not need a payment schedule per customer. You need three: one for standing accounts on terms, one for made-to-order event work with a deposit, and one for one-off orders collected at handover. Every order you take fits one of them.
Write the triggers down, check them against your own dispatch records for last month, and see how many payments fired without being invoiced. That number is what the template is for.
