How to Audit a 3PL Warehouse Invoice

Match the warehouse bill to the work and the applicable rate

Audit a third-party logistics warehouse invoice by matching each service charge to three things: the applicable rate-card version, the billing unit defined for that service, and the warehouse activity supporting the billed quantity. Reconstruct the expected amount before deciding whether a difference is supported or needs an explanation.

For an Australian importer, this means examining the recurring warehouse bill after goods have arrived: receiving, pick-and-pack, storage, returns and authorised projects. Charges depend on extra picks, occupied space, inbound jobs or recorded hours, each with its own inclusions and minimums.

The useful output is a billing bridge that finance and warehouse operations can both follow. It should identify supported amounts, missing evidence, calculation differences and outstanding credits. This method does not determine contract enforceability, tax treatment or whether payment can be withheld. Those decisions need their own authorised advice and process.

The charge dictionary and worked reconstruction below are proposed OPL operational analysis, not a mandated industry billing method.

Define which services belong in this audit

Start with the warehouse-service invoice or the warehouse portion of a combined statement. Keep receiving, storage, fulfilment, returns and value-added work in scope. Separate carrier freight, border charges and unrelated supplier payments so they cannot obscure the warehouse calculation.

If a combined bill contains freight, retain the invoice reference and route those lines through the freight invoice audit. A parcel charge is not another pick-and-pack fee merely because both relate to the same order. This article does not re-audit carriage rates or import taxes.

Provider structures differ. efillship's published Australian pricing illustrates why the service dictionary matters: it distinguishes receiving formats, pick allowances, storage types, returns and kitting, with a minimum applying to a stated service group. These are examples from that provider, not rules for every warehouse or a substitute for your accepted rates.

Name the account, warehouse facilities, billing period, invoice currency and service groups being checked. Decide whether the audit covers all lines or a declared sample. A sample may identify a problem worth expanding; it cannot substantiate the unchecked balance.

Freeze the rate-card version before collecting counts

A rate comparison needs the version applicable to the activity being billed. Preserve the accepted rate card, written amendments and the relevant effective dates. Keep earlier versions when a billing period spans a change.

For each service, record the charge code, billing unit, unit rate, included allowance, volume tier and minimum scope. Identify any approved project quote or separately priced preparation work. Do not replace a missing accepted version with a current website price or a remembered rate from an earlier invoice.

An apparent rate change may be a tier change, a different service or an incorrect mapping. Ask for the documented basis before classifying it. If the answer depends on interpreting disputed contract language, keep that conclusion outside the operational audit and obtain qualified review.

The audit owner also needs an explicit time basis. Note the billing period and time zone, the activity date field used, and whether a late-posted adjustment belongs to an earlier period.

For a volume tier, confirm the qualifying quantity, service group and aggregation period. Establish whether the selected rate applies to all eligible activity or only the units within each band. When rates change during a period, map each activity to its applicable version; do not reset a monthly minimum for every export or rate segment unless the accepted rule requires that treatment.

Build a charge dictionary with one billing grain per line

The billing grain is the object being counted. Establish it before multiplying anything. An order, order line, item pick and physical unit may produce different quantities even when they come from the same fulfilment job.

This table is an OPL audit framework, not a universal rate-card schema. Add the actual charge codes alongside it. A warehouse may bill a case pick differently from an individual-item pick or use a separate wholesale schedule.

Do not convert cases into units until the pack conversion is verified. Preserve both raw values and the documented conversion. Likewise, a returned parcel, returned item and completed restocking job should not become interchangeable counts. The service definition determines which evidence belongs beside the charge.

Collect activity that can explain the billed quantity

Ask for exports that connect service events to invoice lines, with stable references and extraction timestamps. Preserve the raw files; work on a separate comparison sheet so the original evidence remains available.

ShipBob's billing documentation gives a first-party example of invoice-linked transaction records and charge references. It demonstrates that billing can be examined below the invoice total. Your provider may supply a spreadsheet or portal export instead; do not assume the same API, field names or data availability.

Collect only the records relevant to the selected service group. Fulfilment needs order and shipment detail; receiving needs inbound job records; storage needs the documented space/time calculation. A general stock-on-hand export is not automatically evidence for the storage basis used on an invoice.

Set a completeness check before drawing conclusions. Record the export filters, facility scope, first and last event dates, row count and known posting gaps. A missing transaction in an incomplete extract is an evidence exception, not proof of an invented charge.

Check repeated invoice lines against service-event IDs, charge codes, facility and period, including prior invoices and adjustment records. A repeated export row is not another billable event. Conversely, two charges attached to one order can represent distinct services. Flag a possible duplicate and request the underlying mapping; identical amounts alone do not confirm double billing.

Receiving and fulfilment

Match receiving charges to the inbound reference and service actually recorded. A mixed-SKU sorting job should have different supporting detail from a straightforward pallet receipt if the rate card distinguishes them. Do not infer job hours from the elapsed time between delivery and stock availability.

For fulfilment, reconstruct the base charge and additional-pick allowance from order-level detail. Compare cancelled, split and reprocessed orders according to the provider's defined billing event. Two shipments from one customer order may require explanation; neither a one-order nor a two-order assumption is automatically correct.

Where receipt quantities remain unresolved, link the warehouse receiving discrepancy report. Preserve the open receipt issue rather than forcing a billing count to match an unclosed warehouse record.

Storage, returns and project work

For storage, request the occupied-space object, dates and calculation rule. Confirm whether a record is a billed position, occupied position or stock quantity. These describe different things. If the provider bills a period maximum, a month-end snapshot alone cannot reconstruct that maximum.

Confirm the adopted snapshot time or day-count convention, start/end boundaries, partial-period treatment and any rounding or minimum-space rule. Reconstruct daily, average, maximum or snapshot occupancy only when that is the stated basis. Do not substitute today's stock count or assume proration because inventory left before month-end.

For returns, match the return reference to the recorded service and any additional-item rule. A customer authorisation to return an item is not itself evidence that the warehouse received and processed it. Avoid approving a stock release or product-quality decision through this billing check.

For projects, retain the approved job scope, reference, service date and recorded quantity or hours. Separate packaging materials from labour when the rate card does. An invoice description such as “special handling” needs enough detail to connect it to the approved work.

Reconstruct the charge without counting allowances twice

Calculate expected amounts from the defined service rule, then preserve the invoiced quantity, rate and amount beside them. Keep an allowance or minimum visible as its own calculation step rather than hiding it inside a blended unit rate.

For a hypothetical order schedule with one included pick, an order containing three billable picks has two additional picks. It does not have three additional picks. If the provider counts picks differently, use that documented definition; this arithmetic example does not establish a warehouse's rule.

A scoped minimum also needs careful treatment. If a hypothetical agreement sets a $250 monthly minimum for pick-and-pack only, and calculated pick-and-pack totals $220, the minimum adjustment is $30. Adding $250 on top would produce $470 and apply the minimum twice. Storage and receiving should not be included in the calculation unless the actual accepted rule includes them.

Use a four-part result for every line: expected amount, billed amount, difference and evidence state. Define the sign convention once. In this article, a positive difference means the invoice exceeds the reconstructed expected amount. It does not automatically mean the amount is recoverable.

Worked example: one month, four service groups

The following example is hypothetical OPL analysis. It represents no customer, provider quotation or Australian market benchmark. All amounts are AUD service amounts on one consistent illustrative basis; it makes no tax conclusion.

Assume the accepted hypothetical rate card defines:

• Pick-and-pack at $3 per shipped order, including one billable pick, plus $0.50 for each additional pick; a $250 monthly minimum applies to this service group only.
• Receiving at $20 per evidenced standard pallet, with no receiving minimum in this example.
• Storage at $12 per billed pallet position for the month, using a specified snapshot that the provider supplies.
• Authorised kitting at $40 per completed recorded hour.

The activity pack contains 60 shipped orders and 80 billable picks, all with at least one pick. Therefore, additional picks are 80 - 60 = 20. Pick-and-pack is 60 × $3 + 20 × $0.50 = $190. The minimum adjustment is $250 - $190 = $60, bringing that service group to $250.

The pack also evidences four receiving pallets, six storage positions under the stated snapshot rule and two completed kitting hours. Here is the reconstructed bridge:

Expected services total $250 + $80 + $72 + $80 = $482. The invoice totals $280 + $80 + $84 + $80 = $524, a $42 positive difference against this reconstruction. Two supported service groups do not explain the other two.

For pick-and-pack, ask how the provider reached $280 from the accepted inputs and scope. For storage, ask for the seventh position's identifier and the controlling snapshot. If additional evidence changes an input legitimately, revise the expected calculation and preserve the earlier version. Do not call $42 a saving or post a credit merely because the comparison found a difference.

Separate arithmetic differences from unresolved evidence

Give each exception a classification that describes what is known. “Invoice wrong” is less useful than “seventh storage position not present in supplied snapshot”. The latter directs the provider to a specific evidence request.

Use supported when the applicable rate, activity quantity and calculation reconcile. Use clarification when an input, rule or activity record is missing. Use calculation difference when complete documented inputs produce a different amount. Use specialist referral when the operational records are insufficient because resolution requires legal, tax or accounting judgment.

Keep the exception owner, requested record, response date and next action. Do not invent a universal provider response deadline. Any payment or formal dispute decision should follow the organisation's authorised process and the governing provider arrangements, separately from this calculation worksheet.

If the warehouse activity cannot be reconciled across systems, preserve that issue and use the 3PL WMS, ERP and ecommerce reconciliation method. Equal invoice totals do not prove equal stock quantities, and stock quantities do not establish every billable service event.

Close the billing bridge before using final costs

An explanation, corrected invoice and credit note are different records. Preserve each with its reference, amount and version. Match an agreed correction to the actual credit or rebill and retain the before-and-after calculation. A provider email saying “resolved” does not show which balance changed.

Link a replacement invoice to the superseded bill and any cancellation or credit, so both are not carried forward as separate service charges. Check that the correction covers the agreed lines and amount; partial corrections leave the remaining exception open. This documents the billing outcome without deciding accounting entries or payment rights.

Keep unresolved amounts identifiable when supported charges are handed to finance. The audit should supply evidence and status; it should not choose financial-statement recognition, provision or tax treatment.

Once charges are supported, the inventory carrying-cost model can use relevant storage costs, and the contribution-margin method can use relevant fulfilment costs. Preserve the period and service allocation so one charge is not copied into several cost buckets without explanation.

Start with a reproducible monthly check

Choose one facility and one complete billing period. Freeze the applicable rate-card versions, map charge codes to billing grains, and request the activity extracts needed for those services. Reconstruct the expected calculation before comparing totals.

Give exceptions specific evidence requests and owners. Close each against the provider's documented response and any actual credit or corrected invoice. Retain the raw data, formula version and final reconciliation so the next period can reproduce the check without inheriting an unexplained adjustment.

The practical standard is traceability: a colleague should be able to move from a warehouse invoice line to the rate, counted activity, allowance or minimum, calculation and final disposition. That is a stronger basis for approval and cost planning than a total that merely looks familiar.

Sources

• efillship: 3PL fulfilment pricing Australia.
• ShipBob: Billing documentation, version 2026-07.