Why storage billing is easy to misread
Storage charges may use average, peak, end-of-period, daily, weekly, or monthly occupancy. Some schedules change by season or inventory age. The invoice may summarize many receipt lots into one line, while the contract prices them separately.
1. Identify the billing unit
Find the contract’s exact unit: pallet, bin, shelf, square foot, cubic foot, unit, SKU-location, or another defined measure. “Storage” is a category, not a unit. Confirm whether the fee recurs daily, weekly, monthly, or per billing period and whether partial periods are prorated.
- Does the invoice quantity use the same unit as the rate card?
- Is the fee per location or per inventory unit inside that location?
- Are standard, oversized, hazardous, or climate-controlled items priced differently?
- Does a minimum occupancy or account minimum apply?
2. Check the quantity source
Reconcile the invoice quantity to the operational source the contract names. That might be a warehouse inventory statement, daily snapshots, pallet ledger, bin occupancy export, or receipt-lot history. A store’s current on-hand count may not represent the billed period or the provider’s contractual measurement.
For unexplained quantity growth, compare receipts, putaway, transfers, disposals, returns, and shipments. If those facts are missing, record an unpriced data question with no expected amount or variance rather than assigning the entire increase as a discrepancy.
The engineering corpus made this guard explicit after documented rows showed that a displayed receiving quantity can use the wrong unit for the candidate rule. See the unit-conflict and receipt-lot regression notes.
3. Check storage age and seasonal bands
Aged-storage pricing requires receipt-lot identity and age at the contract-defined date. Do not infer that all inventory shares the age of the oldest unit. Confirm boundary behavior: day 120 and day 121 may price differently.
candidate variance = billed storage − Σ(supported quantity by band × active band rate)Invented rates, quantities, references and amounts; not a customer record or provider allegation.
An invented rule charges $9 per pallet per month for days 0–120 and $15 from day 121. Forty pallets documented at age 60 are billed at $15: billed $600, expected $360, creating a $240 review candidate.
Counterexample: if that receipt lot actually reached day 121, the same $9-to-$15 change is contract-supported and should suppress the question. The $240 is not automatically owed, claimable, submitted, credited, or recovered.
Seasonal schedules similarly need their exact effective window. A higher rate during peak season may be correct even when the inventory quantity is unchanged.
4. Compare history carefully
Month-over-month analysis can surface rate drift, quantity jumps, new descriptions, and missing reversals. Treat those as observations that direct the next evidence request. History cannot replace the signed contract or operational quantity source.
| Observation | Useful next question | What it does not prove |
|---|---|---|
| Rate increased | Which amendment, seasonal band, or age tier applied? | That the prior rate remained active |
| Quantity increased | Which receipts, returns, or measurement method explain it? | That every extra unit is unsupported |
| New storage code | What unit and inventory class does it represent? | That an undefined description is invalid |
| Charge persisted after depletion | What is the ledger cut-off and final billing period? | That the inventory was absent for the billed period |
Evidence required
- Storage invoice lines with period, quantity, unit, rate, amount, facility, and source coordinates.
- Active storage schedule, amendments, minimums, seasonal dates, age bands, and boundary semantics.
- The contract-named inventory or occupancy quantity source for the complete period.
- Receipt-lot dates and identity for aged-storage conclusions.
- Receiving, transfer, return, disposal, and shipment activity when investigating quantity movement.
- Dispute-window clause and supported anchor date.
Use the rate-card guide to normalize time bands and the audit checklist to record the quantity evidence.
How Auditario treats this check
Storage continuity and time-tier conclusions remain review-only because they depend on complete period and receipt-lot state. Invoice-history rate drift is an observation, not proof of contract breach. Unexplained quantity growth remains unpriced until the source quantity is established.
Auditario is prelaunch: secure document intake is not open, there are 0 certified publication cells, and $0 is presently claimable. Read the methodology, inspect the synthetic sample, and see the current product status.
Related 3PL billing checks
Volume-tier pricing
Confirm a complete measurement period before selecting a bracket.
Check the tier →Contract comparisonRate mismatch
Compare one billed rate with one active contract rule.
Check the rate →See all five billing patterns
Compare the proof and false-positive guard each check needs.