If you own operations or systems at a 3PL, billing questions can send you back through warehouse records long after the work is finished. Your client agreement says “additional picks”. The warehouse records products, inserts and a line identifying a subscription order. Which of those count?

One client’s allowance applies only to subscription orders. Another pays for additional units on every order. A leaflet might be excluded from the pick charge and billed separately as an insert. The warehouse can record all that work correctly and still leave finance without enough information to price it.

These differences can be part of the service you agreed to provide. If someone interprets them in a spreadsheet every month, that spreadsheet is doing part of the billing. To bring the work into your system, you’ll need to define what counts for each client and keep enough evidence to explain each charge.

Define the activity and the agreement

Choose one client’s completed billing period. Gather the warehouse records, the agreement that applied and the issued invoice. List the decisions someone had to make to turn the work into a charge.

Establish what is chargeable, what another fee includes and whether each charge applies per order, shipment, unit or another measure. Decide how cancellations, returns and late records affect it. The commercial owner should resolve ambiguous contract terms before you automate them.

Each charge needs a source activity you can identify later. An order number may be too broad: one order can produce two shipments, several picks and a return. Keep the source event ID and type, client, quantity, unit and time of the work. Distinguish a repeat export of an event from new activity so importing a file twice cannot create another charge.

Rates need effective dates and versions. Retain the units, currency, rounding and client exceptions that explain an earlier invoice. Specify which event determines the rate date; a file’s arrival time shouldn’t silently set the price. Check for gaps or overlaps in rate periods.

A worked example: which picks are additional?

The following quantities and allowances are fictional. This is an illustration, not a customer invoice or a live product demonstration. It calculates only additional-pick quantities, before rates or other service charges.

Client A pays for picks above eight physical units on subscription orders, excluding flyers and virtual lines. Client B includes four picks, also excluding flyers and virtual lines, and its rule applies to all orders.

The first order’s flyers could still produce two insert charges under a separate agreement. Excluding an item from additional picks doesn’t make every service associated with it free. Similarly, the virtual marker identifies a subscription order; exclude it from quantity only if the agreed classification says to.

Before using the formula, confirm whether the allowance applies per order, parcel or another unit. Decide which items consume it, how you identify subscription status and who reviews a missing classification. Correct arithmetic won’t rescue a misread agreement.

Put the agreement into the working process

Keel is an operations platform that can be shaped around your billing team’s work. For this example, an implemented review step could show the classified picks, the client’s allowance and the resulting quantity together, so the reviewer can explain the seven additional picks against the source order. The implementation defines the client, agreement and source-activity records, then adds the calculation and review workflow. Models describe the data; flows combine processing and operator steps. The calculation connects the allowance and subscription condition to item classifications, while keeping references to the work behind each charge.

An implemented parameter might let you change an allowance. A new charging method may need code, additional data capture and testing. Ask where the rule lives and who maintains it.

During a demonstration, follow one order from its agreement through the quantity and rate to invoice review. Change the allowance, then correct the order so a previously calculated charge no longer qualifies. Check the result and how much work each change requires.

Reconcile in both directions

Every in-scope event should be billed, explicitly excluded or waiting for a named reviewer. Every charge should lead back to supporting work and the rate used. A total that resembles last month’s invoice doesn’t establish either.

Reconcile control totals by client, source, activity and period. Each event should appear once in an outcome category. Keep quantities in their units; adding pallets to items won’t help. Track missing files and late imports separately, because a calculation can balance on an incomplete export.

Give each exception a reason and an owner. A missing rate needs a different response from a disputed quantity or duplicate event. Preserve the original record when correcting it, along with the reason and reviewer. For an issued invoice, follow the agreed adjustment process and retain the link to the original charge.

Check the options before replacing a WMS

Your existing billing module may cover the process. Mintsoft documents client charging for picking, storage and goods-in. Have the vendor demonstrate your subscription, insert and allowance rules together, including the evidence behind the charge.

A separate billing workflow may be useful when work spans systems or agreements need different logic. Check that it can obtain complete source data, retain rate history, explain charges and send approved results to finance.

Billing problems alone don’t establish that receiving, picking or dispatch needs replacing. Compare configuration, a connected billing workflow and wider replacement against the same requirements and their costs.

Run a period before going live

Run a completed period through the proposed workflow alongside your existing process. Investigate every difference, including possible errors in the old process. Use a client with representative exceptions.

Before the first live run, agree how you’ll establish that source data is complete and resolve material discrepancies. Name the reviewers, document recovery and get finance’s acceptance of the output.

During handover, have the future billing owner add a rate period, investigate a held event and reproduce an earlier invoice. Record which changes they can make and which need technical support.

Keel leads implementation around the agreed process, with integrations, handover and ongoing support agreed per customer. Discuss your billing workflow with Keel, using one client agreement, a representative order and the calculation your current system cannot support.