Charging each client on its own activity model — and why month-end takes three weeks when it is done by hand.
A third-party logistics provider bills clients for the activities performed on their behalf: storage by pallet or square foot, inbound and outbound handling, picks, value-added services, and sometimes freight. Each client typically has a different rate card and a different definition of a billable event, which is why 3PL billing resists generic invoicing.
3PL billing is a volume problem disguised as an accounting one. Each movement is potentially a billable event under a client-specific rule, and there are tens of thousands of them a month. Done in spreadsheets, month-end becomes a reconstruction exercise, revenue leaks where events are missed, and disputes are impossible to settle because the underlying detail is gone.
Per client: receipts, putaways, picks, despatches, storage days, labels, kitting. The definitions differ and have to be explicit.
Per client, per activity, with tiers and minimums. Rate changes need effective dates so historical billing stays reproducible.
Each movement rated as it happens, so the charge exists with its evidence attached rather than being derived at month end.
Storage is time-based, not event-based, and typically billed on a period snapshot or a daily accrual.
Generate the invoice with a movement-level backup file the client can reconcile against.
A 3PL invoices a client 11.4 lakh for a month. The invoice has four lines: storage, handling, value-added services, and sundry. The client's finance team has no way to verify any of them and pays, with growing unease.
The problem is that the invoice summarises without supporting detail. Storage is charged on pallet-days, but the client does not know the daily pallet count. Handling is charged per line picked, but the client knows orders rather than lines. Value-added services are a lump. Disputes become arguments about plausibility rather than about facts, and the relationship degrades regardless of whether the invoice was right.
Billing derived directly from captured activity solves this for both sides. Each movement generates a billable event with its rate, so the invoice is a summary of a detailed log the client can reconcile against their own records. Good 3PLs supply this detail because it reduces disputes and accelerates payment. A 3PL that cannot produce it is either not capturing activity properly or is choosing not to share it, and both are worth knowing.
| Term | What it means |
|---|---|
| Storage charge | Billing for space or pallets held, usually per period. |
| Handling charge | Billing for movement — receipts, picks, dispatches. |
| Value-added service | Additional work such as labelling, kitting or repacking, billed separately. |
| Rate card | The agreed schedule of charges by activity type. |
| Activity capture | Recording what actually happened, which is what the invoice must derive from. |
Events missed or double-counted cannot be detected after the fact. Rate as work happens.
A rate change applied retrospectively makes last month's invoice irreproducible.
Clients dispute what they cannot verify. Supply the movement detail with the invoice.
Revenue leakage is invisible unless you compare activity performed against activity billed.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Invoice dispute rate | Billing clarity. High rates are usually a detail problem rather than a pricing one. | |
| Revenue per pallet position | Whether storage pricing reflects the space actually consumed. | |
| Activity captured vs billed | Work done but not invoiced, which is straightforward lost revenue. | |
| Days to invoice after period end | Billing cycle speed, which directly affects cash. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.