Multi-client billing is the single feature that separates a 3PL WMS from a general warehouse system. If the product cannot produce a defensible invoice for each customer from the data it already captures, the operator will rebuild the invoice in a spreadsheet — and every hour spent rebuilding is a direct hit on margin. This guide breaks down the six charge families a capable engine must handle, the rate-table rules that separate real engines from brochures, and the audit test that tells you which is which.
The six charge families
Any billing engine that claims to support 3PL work has to handle six groups of charges. Each one has a well-known failure mode. Evaluate candidates against all six, not just the first two.
| Charge family | What it covers | Common failure mode |
|---|---|---|
| Storage | Per pallet, per cubic foot, per SKU, per bin, or hybrid. Daily, weekly, or monthly accrual. Anniversary or calendar billing period. | Proration on partial months. A pallet that arrives on the 28th should not be billed for a full month in most rate structures. If the engine cannot prorate, the customer will notice. |
| Inbound handling | Per receipt, per pallet, per carton, or per unit received. Often includes a minimum per receipt. | Receipts that split across multiple appointments. Is that one receipt or two? Rate tables must define the rule explicitly or the ops team will guess differently every time. |
| Outbound handling | Per order, per line, per unit, or per carton picked. Picking method and service level often affect the rate. | Line-level billing with kitted or bundled SKUs. One line that picks five components is hard to bill consistently without a configured rule. |
| Value-added services | Kitting, labeling, re-packing, ticketing, poly-bagging, display-building, quality inspection, returns processing. | These are usually billed by time or by unit. Capturing the labor grain accurately requires the floor to scan start and stop on every VAS job. If the WMS cannot capture it, the bill is an estimate. |
| Accessorials | Rush orders, special routing, expedited documentation, hazmat handling, appointment scheduling, lumper fees, pass-through freight. | Pass-through freight with a markup is a common source of disputes. The engine needs to show the original carrier charge and the markup separately on the invoice. |
| Minimums and setup | Monthly minimums, onboarding setup fees, SKU setup fees, integration fees, reporting subscription fees. | Minimum enforcement against actual activity — if a customer did $800 of activity against a $1,000 minimum, the engine should invoice the $200 shortfall as a separate line, not as a mystery adjustment. |
Rate table versioning
Customer rates change mid-month more often than first-time WMS evaluators expect. A minimum gets raised in negotiation. A new accessorial gets added. A storage rate gets renegotiated after a quarterly review. The billing engine has to version the rate table and still produce a reconcilable invoice for the partial month where the rate changed. Engines that cannot do this force the finance team to back into the number manually, which defeats the purpose of the engine.
A capable versioning model tracks the effective date and end date of every rate row, applies the right row to each transaction based on transaction date, and exposes the version history on the invoice so the customer can see exactly which rate applied on which day. It is not a reporting feature — it is a core billing rule.
Billing leakage: the unseen margin drain
Billing leakage is revenue a 3PL earned but never invoiced. It happens when a charge is captured on paper and lost, when an accessorial is performed but not keyed into the system, when a VAS job is not scanned start-to-stop, or when a reconciliation gap between the WMS and the accounting system gets written off rather than researched.
In operations that rely on manual reconciliation, leakage commonly runs 1 to 5 percent of billable revenue. In a 3PL doing $5M a year, that is $50,000 to $250,000 of pure margin walking out the door. Closing the gap is often the fastest ROI line in a WMS swap — and it is the line a CFO can defend without any assumptions about productivity gains.
A well-built engine closes leakage in three places. First, every floor activity that generates a charge has to be captured at the point it happens, through a scanner prompt or a timer, not on a clipboard. Second, every captured activity has to tie to a rate row so the charge is computed automatically. Third, any transaction that does not tie has to land on an exception queue the billing lead reviews before invoice day — not in a quiet write-off column.
The audit test
There is one test that separates real billing engines from marketing pages. Pick a line on a finished customer invoice — any line — and ask the engine to show you the exact transaction that produced it. If the answer is one click to the receipt, the order, the storage day, or the accessorial request, the engine is real. If the answer is "let me build the number in a spreadsheet and get back to you," the engine is a brochure.
The audit test matters because invoice disputes are routine. A customer questions a charge, the 3PL needs to defend it inside a day, and the defense has to tie to transaction data the customer can also see. Engines that pass the audit test earn customer trust over time. Engines that fail it burn an account manager's week every month.
Accounting and ERP integration
The billing engine produces the invoice, but the accounting system holds the books. The two have to tie without manual re-keying. A capable integration pushes invoices, credits, and adjustments from the WMS into the ERP — typically QuickBooks, NetSuite, Sage Intacct, or Microsoft Dynamics — and reconciles cash receipts back against the original invoice in the WMS.
Broken ERP integration is the number one reason a finance team distrusts a WMS and goes back to the spreadsheet. Watch for two failure modes during evaluation: first, integrations that push invoices but not adjustments, which means every credit has to be entered twice; second, integrations that do not carry the WMS transaction ID through to the ERP line, which means the audit test breaks at the ERP boundary.
Frequently asked questions
What is multi-client billing in a 3PL WMS?
Multi-client billing is the ability to invoice each of a 3PL's customers for the storage, handling, value-added services, and accessorials performed on their behalf — using the transaction data the WMS already captures, with a per-customer rate table and a reconcilable audit trail.
What is billing leakage and how big is it?
Billing leakage is revenue a 3PL earned but never invoiced — usually because a charge was captured on paper, missed by the ops team, or could not be reconciled to a transaction. In operations that rely on manual reconciliation, leakage commonly runs 1 to 5 percent of billable revenue. In a $5M 3PL, that is $50K to $250K a year in pure margin.
What is the single biggest reason 3PL billing engines fail in year one?
Rate table versioning. Customer rates change mid-month more often than WMS evaluators expect — a minimum goes up, an accessorial gets added, a storage rate is negotiated. A billing engine that cannot version the rate table and still produce a clean invoice for the partial month will force the finance team to back into the number manually, which defeats the purpose of having the engine.
Can a general-purpose WMS do multi-client billing?
Usually not at production grade. Some general WMS products include a billing module, but the module typically handles only storage and basic handling. The moment an operator needs VAS billing, accessorials with markup, or rate versioning, the module runs out of expressiveness and the ops team goes back to a spreadsheet. If you have more than two customers with different rate structures, assume you need a purpose-built engine.
How long does a billing engine migration take during a WMS cutover?
The rate tables themselves migrate in days. The hard part is testing — running the new engine in parallel with the old billing for one or two full billing cycles, reconciling the outputs line by line, and fixing the gaps before cutover. Plan for four to six weeks of parallel billing, not one.
What does SC Codeworks do for billing specifically?
Our billing engine captures more automated billing data points than we have seen from competing mid-market products, and every line on every invoice can be drilled back to the exact transaction that produced it. Customers asking "where did this charge come from?" get a one-click answer from our team, not a spreadsheet. That is the audit test, and it is the feature finance teams tell us matters most.