Mon – Sat: 9:00 AM – 7:00 PM IST
Logistics

Third-party logistics billing

Charging each client on its own activity model — and why month-end takes three weeks when it is done by hand.

In short

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.

Why It Matters

Why this matters in practice

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.

Billable events captured as work happens, not reconstructed later
Client-specific rate cards applied automatically
Disputes answerable with movement-level evidence
Revenue leakage from unbilled activity becomes visible
How It Works

How it works in practice

Define billable events

Per client: receipts, putaways, picks, despatches, storage days, labels, kitting. The definitions differ and have to be explicit.

Hold the rate cards

Per client, per activity, with tiers and minimums. Rate changes need effective dates so historical billing stays reproducible.

Rate at the transaction

Each movement rated as it happens, so the charge exists with its evidence attached rather than being derived at month end.

Handle storage separately

Storage is time-based, not event-based, and typically billed on a period snapshot or a daily accrual.

Invoice and support

Generate the invoice with a movement-level backup file the client can reconcile against.

Worked example

A worked example: an invoice nobody could check

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.

Key terms

The vocabulary, briefly

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.
What Goes Wrong

Common mistakes worth avoiding

Rating at month end from reports

Events missed or double-counted cannot be detected after the fact. Rate as work happens.

Rate cards without effective dates

A rate change applied retrospectively makes last month's invoice irreproducible.

No backup detail with the invoice

Clients dispute what they cannot verify. Supply the movement detail with the invoice.

Unbilled activity never measured

Revenue leakage is invisible unless you compare activity performed against activity billed.

What to measure

Numbers worth tracking

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.
FAQ

Questions we are asked about this

By pallet position, square foot or cubic volume, over a period — often on a snapshot basis, sometimes accrued daily. Daily accrual is fairer and needs the system to hold daily positions.
It needs client-specific rate cards and billable-event definitions. A system with one global rate structure cannot, which is the usual reason 3PLs end up billing in spreadsheets.
Storage by pallet, square metre or cubic volume per period; handling per receipt, per pick line, per order or per dispatch; value-added services by time or by unit; and sometimes a fixed management fee plus variable activity charges. Most arrangements combine several. What matters more than the model is that each charge maps to a recorded activity, so the invoice can be reconciled rather than accepted.
By defined unit wherever possible — per label applied, per kit assembled, per pack reworked — with time-based billing reserved for genuinely variable work. Per-unit billing is predictable for the client and rewards the provider for efficiency. Time-based billing for repeatable work creates an awkward incentive and is harder for the client to verify, which is where disputes concentrate.
Both parties keep records and they must reconcile regularly, typically monthly. The 3PL's warehouse system is the operational record of what is physically there; the client's ERP is the financial record of what they own. Differences arise from timing, damage, miscounts and unrecorded movements, and a monthly reconciliation catches them while they are still traceable. Annual reconciliation produces differences nobody can explain.
The rate card with each charge tied to a defined activity, the measurement method for each, the billing cycle, the supporting detail to be provided, the dispute process and timescale, and how rates change. The detail requirement is the clause most often omitted and most often regretted, because without it the client has agreed to pay for activity they have no means of verifying.
Related

Where to read next

What is a WMS?

Read more

Freight cost management

Read more

ERP with warehouse management

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.