Invoice each load or one monthly invoice?
The trade-offs between invoicing every load and sending each shipper one monthly invoice, and how statements, receipts and ageing support either choice.
By Achekam · · 4 min read · For Logistics businesses in South Africa, Nigeria, Kenya
Every transporter eventually has this argument in the office. The operations manager wants an invoice out the moment a load is delivered, because the business has already paid for the diesel, the tolls and the driver. The accounts clerk would rather send each shipper one tidy invoice at month end, because forty small invoices to the same customer means forty documents to chase. And the shipper's own payables team has an opinion too, usually expressed by paying slowly whichever way you choose.
There is no single right answer, but there is a right answer for each shipper. This article sets out what each method costs you, what it gives you, and how statements, receipts and ageing in Achekam support whichever one you pick.
Per load: faster cash, more paperwork
Invoicing each load as it is delivered has one big advantage: the payment clock starts sooner. If a shipper pays on terms counted from the invoice date, a load invoiced the day after delivery is paid weeks before the same load bundled into a month-end invoice.
It has other strengths:
- Disputes stay small. A query about one load holds up one invoice, not the whole month.
- Evidence is fresh. The proof of delivery, the weighbridge ticket and any waiting-time notes are still on the desk.
- Cash flow follows the work. A busy week shows up in receipts within the shipper's terms, not a month later.
The cost is volume. More invoices means more numbers, more e-mails and more receipts to allocate. For a shipper sending dozens of loads a week, it can also irritate their payables team, who may batch your invoices anyway.
Monthly: fewer invoices, longer wait
One invoice per shipper per month, with a line for each load, is easier to produce and easier for the shipper to approve in one go. Large shippers often prefer it, and some insist on it.
The price is time. Default terms on a new invoice in Achekam are 30 days. Whatever the terms, a load delivered early in the month waits until month end to be invoiced, and then for the shipper's terms on top. Over a year, that is a meaningful amount of money sitting with your customers rather than in your bank.
A monthly invoice also concentrates risk. If one load on it is disputed, some shippers will hold the entire invoice until it is resolved.
Which to choose
| Shipper profile | Better fit |
|---|---|
| Occasional loads, new relationship, or doubtful payer | Per load |
| High volume, reliable payer, asks for consolidated billing | Monthly |
| Mixed: regular contract work plus ad hoc spot loads | Monthly for the contract, per load for the spot work |
Investopedia's explanation of days sales outstanding shows how to measure how quickly customers pay. Working it out per shipper, before and after a change of method, tells you whether the change helped.
Statements that list every load
Whichever way you invoice, a statement of account keeps the shipper and you looking at the same list. Achekam's server produces a customer statement of account as a PDF that can be e-mailed, and the screen tells you whether it was sent.
For per-load billing, the statement is what turns forty invoices back into one conversation: the shipper sees every open invoice in one place, with its number and date, and can pay against the statement. For monthly billing, the statement shows whether last month's invoice is still open when this month's arrives.
Whichever method you use, invoices begin as drafts that can be changed or deleted. Issuing one gives it the next number in your sequence and posts it to the ledger as debtors, sales and output VAT. Check the load references on the draft, because once issued the invoice is fixed.
Payments across several invoices
Shippers on per-load billing rarely pay invoice by invoice. They pay a round sum against a remittance advice, or simply a sum. Achekam lets you record a customer payment against one invoice or spread it across that customer's invoices. A part payment leaves an invoice part-paid, and anything paid over is held on the customer's account rather than lost. A receipt allocated wrongly can be re-allocated later, and administrators can refund or reverse one.
A sensible habit: allocate to the oldest invoices first unless the remittance names specific loads, and keep the remittance advice with the receipt. When a shipper pays short without explaining, allocate what you can and ask about the rest the same week, while the loads are still remembered.
Agreeing the method with each shipper
Do not let the method drift. Agree it when the shipper is taken on, write it into the trading terms or the rate confirmation, and record it on the shipper's file. Cover:
- per load or monthly, and for monthly, the cut-off date;
- payment terms and the date they count from;
- what supporting documents go with each invoice (the signed POD, at minimum);
- how disputes on one load affect the rest.
Then watch the results. Achekam ages receivables into 0-30, 31-60, 61-90, 91-120 and over 120 days, with overdue totals. A shipper moving steadily into the later columns on monthly billing is a candidate for per-load invoicing and closer follow-up; shipper accounts that drift past their terms covers what to do next. And because so many disputes come down to proof of delivery, it pays to have the paperwork ready before the invoice goes; see filing signed PODs and sending them with invoices.
A practical next step
List your ten biggest shippers, note how each is invoiced today and how quickly each pays, and pick the two where a change of method would make the biggest difference. Agree the change with them in writing, and compare their payment speed after a quarter.
General guidance only, not advice on your own circumstances. Tax and payroll rules change: check the current position with the authority or your adviser.
