# 3PL billing errors: 10 ways an invoice goes wrong

A 3PL invoice rarely goes wrong in one large, visible way. It goes wrong in small, repeatable ways - a tier applied one level too high, a rate card version one revision too old, a minimum computed against the wrong base - and each small error bills again next month. These are the ten failure modes an audit looks for. Every example below is illustrative, with the arithmetic shown so you can check it against your own bill. The checks named for each one are the ones Feeproof runs on every invoice; the full method is in [what a 3PL invoice audit is](/guides/what-is-a-3pl-invoice-audit).

## 1. Tier error: billed in the wrong volume band

Your rate card prices work in bands: the more you ship, the less each unit costs. A tier error bills your volume at a band you did not actually fall into - usually the band below yours, because billing systems often key the tier to last month's volume, a single warehouse's volume, or a forecast rather than the month's actual count.

**Example.** Your pick rate is $0.85 per pick at 5,000–9,999 orders a month and $0.70 at 10,000+. You shipped 11,240 orders, but picks were billed at $0.85: 11,240 × $0.85 = $9,554 instead of 11,240 × $0.70 = $7,868. The difference is $1,686 for one month, from one line.

**On the invoice:** the unit rate on pick and pack lines does not match the band your shipped volume falls into. The quantities are right; the rate column is wrong.

**Checked by:** R4 (rate above contract) against the tier table, with SUM reconciling the order count the tier is judged on.

## 2. Wrong rate: an old or wrong rate card version

Rate cards get revised - annual uplifts, renegotiations, promotional periods that expire. A wrong-rate error bills a price that exists somewhere in your paperwork but is not the price in force for that billing period: last year's card, the card for a different warehouse, or a promotional rate that ended and was never replaced in the billing system (in whichever direction costs you).

**Example.** Your storage rate was renegotiated from $38 to $34 per pallet from 1 March. The April invoice still bills 210 pallets at $38: 210 × $38 = $7,980 instead of 210 × $34 = $7,140 - $840 over, and it will repeat every month until someone catches it.

**On the invoice:** a unit price you recognise, but from the wrong document. Nothing looks invented, which is why this error survives spot checks.

**Checked by:** R4, tested against the contract version in force for the invoice period - which is why the audit asks for the current agreement, not any agreement.

## 3. Unit mismatch: per piece billed as per order, or the reverse

Every rate has a unit: per order, per unit, per carton, per pallet, per hour. A unit mismatch applies a rate to the wrong count - a per-order packaging fee multiplied by units, or a per-unit pick fee applied to cartons. The rate is correct; the quantity it multiplies is the quantity of something else.

**Example.** Your contract prices additional picks at $0.60 per unit beyond the first. An order of 3 units should pay 2 × $0.60 = $1.20. Billed per order-line instead, a month with 6,400 multi-unit orders at 3 units each was charged on all 19,200 units: 19,200 × $0.60 = $11,520 instead of 12,800 billable extra units × $0.60 = $7,680 - $3,840 over.

**On the invoice:** quantities that match a different column of your order export than the fee's definition - units where orders belong, lines where pieces belong.

**Checked by:** MATH on each line's quantity basis, and SUM against the order export, which holds both counts side by side.

## 4. Channel misrate: one sales channel billed at another's rates

Brands selling through several channels - DTC, Amazon, wholesale, retail replenishment - often have different rate schedules per channel, because the work differs. A channel misrate bills orders under the wrong schedule: DTC orders at wholesale handling rates, or marketplace orders missing the channel-specific discount you negotiated.

**Example.** Your contract bills DTC pick and pack at $2.10 per order and wholesale case handling at $4.75 per case. In one month, 1,150 DTC orders were coded as wholesale: 1,150 × $4.75 = $5,462.50 instead of 1,150 × $2.10 = $2,415 - $3,047.50 over, caused by a channel code, not a price.

**On the invoice:** a rate that is genuinely in your contract, applied to orders whose channel - visible in your order export - puts them under a different schedule.

**Checked by:** R4 with the channel field from the order export (SUM), which is why a rate-only check against the invoice alone cannot see this error at all.

## 5. Minimum misapplied: the top-up computed wrong

Most contracts carry a monthly minimum: if your billable activity falls short, you pay a top-up to the minimum - the shortfall, not the whole minimum again. Misapplication takes several forms: the top-up charged on top of activity that already exceeded the minimum, computed against a minimum from the wrong tier, or calculated on gross charges including pass-through postage when the contract defines it on fulfilment fees only. The full mechanics are in the [monthly minimum](/guides/monthly-minimum) glossary page.

**Example.** Your minimum is $2,500 on fulfilment fees. The month's fulfilment fees were $2,310, so the correct top-up is $190. The invoice adds a "minimum adjustment" of $2,500 - the full minimum stacked on top of the fees - overbilling $2,310.

**On the invoice:** a minimum, adjustment or top-up line whose amount does not equal minimum minus eligible charges, or that appears in a month when eligible charges already cleared the minimum.

**Checked by:** R10 (minimum top-up too large), which recomputes the shortfall from the contract's own definition of what counts toward the minimum.

## 6. Quantity mismatch: billed for more than happened

The simplest error: the count itself is wrong. More picks than units shipped, storage for more pallets than were ever in the building, receiving billed per carton on a delivery that arrived palletised. Quantity mismatches survive because nobody reconciles the invoice's counts against their own records line by line.

**Example.** Your order export shows 8,930 orders shipped in the month. The invoice bills pick and pack on 9,412 orders at $2.30: the extra 482 orders cost 482 × $2.30 = $1,108.60, for fulfilment work that never happened.

**On the invoice:** quantities higher than the corresponding count in your order, receiving or inventory records - often by a plausible few percent, which is exactly why it passes a glance at the total.

**Checked by:** SUM, the reconciliation of every billed quantity against your order export and records; lines with no matching record are flagged, not assumed.

## 7. Duplicate charges: the same work billed twice

The same order, receipt or fee billed more than once - under the same description, under two different descriptions, or once in the regular cycle and again in an adjustment run. Duplicates are common after system migrations, credit-and-rebill corrections where the original was never reversed, and month-end invoices that overlap a mid-month run.

**Example.** A receiving delivery of 14 pallets at $11.50 per pallet is $161. The invoice shows the receiving line twice - once as "Receiving – pallets" and once as "Inbound handling" - for the same delivery note on the same date: $161 billed twice, $161 over.

**On the invoice:** two lines with the same date, reference or amount; or a re-billed line whose original was credited in words ("reversal to follow") but never in numbers.

**Checked by:** R1 (duplicate charges), matching on order, receipt and reference numbers as well as amounts, so a duplicate under a new name is still a duplicate.

## 8. Uncontracted fees: charges your agreement never mentions

A fee type appears that is not in your contract, rate card or quote at all - a "systems fee", a "compliance charge", a "peak readiness fee" - introduced by the 3PL's billing system or a general price-list update you never signed. A related form is a contracted fee billed outside its contracted conditions, such as a card surcharge when you pay by bank transfer.

**Example.** A "WMS licence fee" of $95 a month appears in January and recurs for eight months: 8 × $95 = $760, for a charge that appears nowhere in your agreement. Recurring and small is the pattern - it is priced to sit under the threshold of anyone's attention.

**On the invoice:** a charge description you cannot find in your contract with a search. If the document does not contain it, the invoice should not either.

**Checked by:** R3 (new fee) for first appearances and R2 (recurring surcharge outside the contract) for the ones that settle in, plus R11 where the fee contradicts your agreed payment method.

## 9. Promised credits missing: the credit that never arrived

Audits and negotiations end with promises: a credit for last month's error, a service-level credit for a missed dispatch target, a waived fee for a specific period. The promise is minuted, emailed, agreed - and then simply not applied, or applied in part, or applied and quietly reversed two invoices later.

**Example.** After a March dispute, your 3PL agrees a $1,275 credit for misrated storage. The April invoice contains no credit line; the May invoice shows a credit of $1,275 followed, in the adjustments section, by a "credit reversal" of the same amount. Net received: $0 of the $1,275 agreed.

**On the invoice:** nothing - that is the point. A missing credit is invisible on the document that should contain it, which is why it is tracked from the agreement, not from the invoice.

**Checked by:** R5 (promised credit missing), which carries every agreed credit forward until it is seen, in full, on an actual invoice. What a credit looks like when it does arrive is covered under [credit memo](/guides/credit-memo).

## 10. Unexplained variance: the total drifts and no line explains it

Sometimes every line you test is right, and the total is still wrong: the invoice total does not equal the sum of its lines, a subtotal carries an amount from a prior period, or the per-order cost jumps with no change in volume, rates or mix to explain it. Variance is the audit's smoke alarm - not proof of a specific error, but proof that something in the billing chain changed without documentation.

**Example.** An invoice lists lines summing to $18,442.60 but states a total of $18,917.60 - a $475.00 difference with no line to attach it to. The same month, cost per order rises from $2.61 to $2.94 on flat volume: 9,800 orders × $0.33 = $3,234 of the month's bill unexplained by any rate in the contract.

**On the invoice:** a total that fails addition, or a cost per order that moves while rates and volumes stand still.

**Checked by:** MATH on totals and subtotals, R9 (cost per order anomaly) and R13 (fee spike), which compare each period against the last so drift is measured, not felt.

## What an audit does with these

Each of the ten becomes one of five statuses on every billed amount - Supported, Calculation mismatch, Conflicts with terms, Needs evidence, or Not tested - and the statuses add up to the invoice total, so nothing is waved through and nothing is accused without its working shown. Lines the evidence cannot settle are marked honestly rather than guessed at; the limits of that approach are answered in the [FAQ](/guides/faq). To see it run on your own bill, the [free audit](/guides/what-is-a-3pl-invoice-audit) covers your latest invoice from any 3PL.
