3PL billing software in Australia: activity-based billing, rate cards & Xero/MYOB sync explained

If you run a third-party logistics operation in Australia, your warehouse is your factory, but your rate card is your product. The difference between a healthy 3PL and one that quietly bleeds margin is rarely the picking speed on the floor. It is whether every billable activity that happens in the building actually makes it onto an invoice, at the right rate, for the right client, on time.

This guide is for Australian 3PL operators, ops-finance leads and warehouse managers who are evaluating 3PL billing software, or trying to fix a billing process that leaks. We will cover how 3PLs bill, what activity-based billing and rate cards mean in practice, how billing leakage happens and how to stop it, how invoice sync to Xero or MYOB should work, and why multi-client segregation matters. We will also be honest about where a dedicated billing-only tool might suit you better than a broader platform.

How 3PLs actually bill clients

Before you shop for software, get clear on the charge types your contracts already contain. Most Australian 3PL rate cards are built from four families of charges, and good billing software has to capture all four without manual spreadsheets stitched in between.

• Storage. Charged by pallet, bin, shelf, cubic metre or square metre, usually per week or per month, and often with a minimum. The tricky part is that occupancy changes daily, so the basis (peak, average, or a snapshot date) has to be defined and measured, not guessed.
• Receiving and inbound. Charged per container, per pallet, per carton or per line received, sometimes with an unload fee and a putaway fee as separate items. This is where labour-heavy work often goes unbilled because nobody captured the receipt detail.
• Pick-pack and outbound. Charged per order, per pick line, per unit, per carton, plus packaging consumables and a despatch or handling fee. High-volume D2C clients live and die on the per-line and per-order rates here.
• Value-add services (VAS). Kitting, labelling, relabelling, quality checks, returns processing, stocktakes and ad hoc project work. VAS is the most profitable and the most frequently under-billed, because it is irregular and easy to forget.

Add carrier freight recovery on top, where you pass through or mark up shipping cost, and you have the full picture. The job of 3PL billing software is to turn the events that happen in your warehouse management system into accurate line items against the right client rate card, with as little re-keying as possible.

Activity-based billing, explained

Activity-based billing means you charge for what actually happened, not a flat monthly retainer that hopes to average out. Every billable event in the warehouse, a receipt, a putaway, a pick line, a carton packed, a pallet stored for a week, generates a transaction, and each transaction maps to a rate on the client's rate card.

Done well, this is the fairest and most defensible model for both sides. The client pays in proportion to the work they generate, and you stop subsidising your busiest, most demanding accounts with revenue from your quiet ones. The catch is that activity-based billing is only as good as your activity capture. If a pick is not scanned, a receipt is not logged, or a VAS task is not recorded, that activity is invisible, and invisible activity is unbilled activity.

• The data has to come from the operation, not a clerk. Charges should be derived from the same scans and confirmations your warehouse-floor staff already make in the WMS, so billing is a by-product of doing the work, not a separate data-entry exercise.
• Rates have to be client-specific. The same activity (say, a pick line) costs different clients different amounts. The system needs per-client rate cards, not one global price list.
• Periods and minimums have to be enforced automatically. Weekly storage, monthly minimums, tiered volume breaks and free-period rules should calculate themselves at run time, not be patched in by hand.

The payoff is a billing run that you trust. You press a button, the period's activity is rated against each client's card, and the invoice that comes out reflects the building's real work.

Rate cards: where margin is won or lost

A rate card is the contract between your operation and your finance system. It is the list of every chargeable activity for a given client and the price for each. The quality of your rate-card tooling decides how much of your real work you can actually invoice.

• Per-client, per-activity granularity. Each client gets their own card. Within it, every activity family above (storage, receiving, pick-pack, VAS, freight) has its own units and prices, with effective dates so a rate change is auditable rather than overwritten.
• Tiered and volume-based pricing. Real contracts have breaks: the first 1,000 pick lines at one rate, the next band cheaper, storage that steps down past a threshold. Your software should model these, not force you to average.
• Minimums and recurring charges. Monthly storage minimums, account fees and SLA charges need to apply automatically even in a quiet period.
• Easy, audited rate changes. When you renegotiate a client up or down, the change should be dated and logged, so a disputed invoice can be traced back to the rate that was in force on the day.

If your rate cards live in a spreadsheet that one person maintains, you do not have a billing system, you have a single point of failure. Moving rate cards into software that rates activity automatically is usually the single biggest margin recovery a growing 3PL can make.

Billing leakage: the quiet margin killer

Billing leakage is revenue you earned but never invoiced. It rarely shows up as a single big miss. It accumulates in small, repeated gaps that are individually trivial and collectively brutal. For a 3PL on thin operating margins, a few percent of leaked revenue can be the difference between a profitable account and a loss-making one.

• Unrecorded activity. The pick that was not scanned, the receipt logged on paper, the carton packed but never confirmed. If it is not a transaction, it is not on the invoice.
• Forgotten value-add work. Ad hoc relabelling, an unplanned stocktake, a one-off kitting job done as a favour and never charged. VAS leakage is the most common and the most expensive.
• Storage measured wrong. Billing off a stale snapshot, or off average when the contract says peak, or simply not capturing pallets that came and went mid-period.
• Stale rate cards. Invoicing at last year's rates because the renegotiated card never made it into the system.
• Manual re-keying errors. Every time a number is copied from the WMS into a spreadsheet and then into the accounting package, there is a chance to fat-finger it, usually downward.

The fix is structural, not heroic. When billing is derived automatically from the activity your operation already records, leakage shrinks because there is no manual step in which to lose a charge. The closer your billing engine sits to your warehouse floor, the less escapes it. This is the core argument for running billing inside the same system that runs your receiving-inbound, wave-picking, zone-picking and shipping-outbound work, rather than reconstructing it after the fact.

Xero and MYOB invoice sync done right

Most Australian 3PLs keep their books in Xero or MYOB, and they should. Your accounting system is the highest-stakes thing you run, and there is no good reason to migrate it just to bill clients better. What you want instead is for your operations system to generate accurate, rated invoices and push them cleanly into your ledger.

• One-way invoice push, two-way where it counts. The billing run rates each client's activity, produces an invoice, and sends it to Xero or MYOB as a draft or approved invoice against the right customer. Payment status and customer master data can flow back so your operation and your ledger agree.
• Correct customer, account and tax mapping. Each client maps to the right contact, each charge type to the right revenue account, and GST is handled correctly on the line, so your invoices are clean the first time and your BAS is not a reconciliation nightmare.
• No double entry. The whole point is that nobody re-keys an invoice. The activity is captured once on the floor and travels through to the ledger without a human copying numbers between systems.

A word on honesty here, because it matters in this category. With OpsUI, bidirectional NetSuite sync is live in production today. Bidirectional Xero and MYOB sync is wired during rollout, via the finance-accounting module, so the connection is configured and validated as part of bringing you live rather than being a box you tick on day one. If Xero is your ledger, start at /integrations/xero to see how the sync is set up.

Multi-client segregation: non-negotiable for a 3PL

A 3PL is, by definition, running many clients' inventory and operations in one building. Your software has to keep them cleanly separated, in the data and in the billing, or you will eventually ship one client's stock against another's order and invoice the wrong account for it.

• Separate inventory ownership. Each client's stock is tracked as theirs, even when it sits in shared locations, so on-hand, allocations and storage charges are always attributed correctly.
• Separate rate cards and invoices. Each client bills against their own card and gets their own invoice. No cross-contamination, no averaging across accounts.
• Client-scoped visibility. When a client logs in or asks for a report, they see their inventory, their orders and their charges, and nobody else's.
• Clean per-client reporting. You should be able to see margin, throughput and storage utilisation by client, so you know which accounts actually make money. The dashboards-reporting module is built for exactly this kind of per-client cut.

Segregation is not just a compliance nicety. It is what lets you have a defensible conversation with a client about their bill, because you can show their activity, their rates and their invoice as one consistent chain.

When a dedicated billing-only tool is the better fit

Honesty wins trust, so here is the fair version. A standalone 3PL billing engine, bolted onto your existing WMS, can be the right call in some situations, and you should not over-buy.

• You already run a deep, specialised WMS you are happy with, and your only real gap is the billing and rate-card layer on top of it.
• Your operation is stable and single-purpose, and you do not need orders, CRM, procurement or finance workflows in the same system.
• You want the lightest possible change and are comfortable maintaining the integration between your WMS, the billing tool and your ledger yourself.

If that is you, a focused billing add-on may be all you need. The trade-off is that every seam between systems is a place where activity can fall through and leakage can creep back in. The fewer hand-offs between the floor and the invoice, the less you lose. Weigh the simplicity of a single add-on against the leakage risk of another integration to maintain.

How OpsUI fits

For a 3PL, the appeal of OpsUI is that billing stops being a separate tool reconstructing what happened and becomes a by-product of the warehouse work your team already does. You keep the ledger you already trust and add OpsUI as the operations and billing layer over the top, so nothing leaks between the floor and the invoice.

• Billing close to the floor. Receiving, picking, packing, despatch and value-add tasks are captured as activity in modules like receiving-inbound, wave-picking, zone-picking and shipping-outbound, so the events that should be billed are recorded as a by-product of doing the work, which is the single best defence against leakage.
• Modular, predictable pricing. Flat modular pricing from A$399/module/mo — full breakdown at /pricing, so you buy the warehouse and finance pieces a 3PL needs, not a bundle you will not use, and your bill does not climb per head as you grow.
• Keep Xero, MYOB or NetSuite. Bidirectional NetSuite sync is live in production today, and bidirectional Xero and MYOB sync is wired during rollout via the finance-accounting module, so your rated invoices flow into the ledger you already trust instead of forcing a migration.
• Carriers, stated plainly. Carrier integrations are wired during rollout: NZ Couriers is the one live carrier API today, while Australia Post, StarTrack, Sendle, Toll, DHL, Aramex, CouriersPlease and the Shippit aggregator run through the shipping-outbound workflow (direct API, aggregator or file-based), confirmed during scoping so freight recovery is captured against the real cost.

If you want to see how the warehouse and billing modules stack together for a logistics operation, start at /solutions/3pl. If you are weighing OpsUI against a purpose-built 3PL platform, read /compare/opsui-vs-cartoncloud for a fair head-to-head. And when you are ready to pressure-test it against your own rate cards, book a session at /book-demo and bring a real client contract and a month of activity so the conversation is concrete.

The goal is not to sell you the biggest system. It is to make sure every billable activity in your building ends up on an invoice, at the right rate, for the right client, with as few manual steps in between as possible.