Bill what the floor did

Where billing leaks

In most warehouses, billing is reconstructed at month end from the WMS, emails and memory. Storage is easy to bill and handling is mostly captured. What leaks are the accessorials: the rush order, the relabelling job, the hold for inspection, the after-hours receiving, the pallet that had to be rebuilt. Each is small. Together they are often the difference between a client worth keeping and one that quietly costs you money.

The fix is not a better spreadsheet. It is recording each billable event when it happens, against the client and the rate that applies, so the invoice is a sum rather than a reconstruction.

Bill from events, not from memory

1. 01

   Receiving

   Each receipt recorded with its units, pallets or cartons, and any exception: damaged, unlabelled, after hours.

2. 02

   Storage

   Occupancy measured the way the contract says: by pallet position, by cubic volume or by bin, on the agreed snapshot days.

3. 03

   Handling

   Picks, packs and shipments counted per order line, per unit or per carton, as each client's rate card defines.

4. 04

   Accessorials

   Special work started from a scanner or a tablet with a reason code, so it is billable the moment it is done.

5. 05

   Holds and returns

   Inspection holds, returns processing and disposals recorded as events with their own rates.

A rate card per client

Every 3PL contract is a little different. Rates belong in data, edited by your account managers, not in code: storage units and periods, handling units, minimums, accessorial lists and their prices, and the dates each version applies from. When a rate changes, history keeps the old one, so a past invoice can always be explained.

Let clients see why

Billing disputes take longer than billing. A client portal that shows each charge with the events behind it, the order, the date and the scan or the photo, settles most questions before they are asked. The same portal lets clients see their inventory, their orders in progress and their open holds, which is usually what they wanted to email about in the first place.

From invoice to the books

Once the invoice is a sum of events, it can go to the accounting system without retyping. A sync built on the QuickBooks Online API creates the invoice against the right customer and items, and payments recorded in QuickBooks flow back so account managers see who has paid. Larger operations do the same with their ERP.

Carriers and retailers

Shipping charges come from carriers, through a shipping platform or each carrier's API, and are passed to the client at cost or with an agreed markup. Retail clients often require EDI for orders, advance ship notices and invoices, each partner certifying on its own schedule. Both are worth scoping early, because they set the calendar more than the code does.

Storage snapshots and cycle counts

Storage is billed from what was on the floor on the agreed snapshot days, so the snapshot has to be right. That depends on locations being accurate, which depends on cycle counts. A billing project is often the moment a warehouse discovers how far its locations have drifted from reality.

Build the counts in: short daily counts by zone, with differences recorded and approved rather than silently corrected, and a snapshot that runs at the same time every period. When a client questions a storage charge, the answer is the snapshot and the count history behind it.

Minimums deserve the same care. A client with a monthly minimum should see on the portal how close they are to it during the month, not only on the invoice, which turns a surprise into a conversation.

Onboarding a new client

Most billing errors start on the first day of a contract. The rate card is typed in from a PDF, the client's item master arrives as a spreadsheet with missing dimensions, and nobody agrees what counts as a pallet. A billing system should make onboarding a checklist: the rate card entered and reviewed by a second person, items imported with their units of measure and dimensions validated, the accessorial list agreed and signed, and a test invoice produced from a week of sample events before the first real one.

The same checklist helps at renewal. When rates change, the new card is entered with its start date and the old one is kept, so the first invoice under the new rates can be checked line by line against the last one under the old.

What it costs, worked out now

The two worked examples below are priced by our estimator from the rate card in force when you open this page: billing from scan events in two buildings with rugged scanners and a two-way QuickBooks Online sync, and a client portal on its own with a one-way sync.

Where to start

1. 01

   List what you do not bill today

   Ask the floor leads which work they do that never reaches an invoice. That list is the business case.

2. 02

   Put rate cards in data

   Even before new software, write each client's rates in one structured place.

3. 03

   Capture accessorials at the source

   A reason code on a scanner or tablet beats an email at month end.

4. 04

   Show the client

   A portal with the events behind each charge pays for itself in shorter disputes.