3PL invoice backup: the supporting detail files to always request

Why supporting detail matters#

A summary invoice shows a total for each fee, not the activity behind it. The detail lets you re-add the bill, check each rate against your rate card and match rows to your own orders and receipts.

Billing errors are usually process slips rather than intent: rates can change one line at a time, and a 3PL's billing system can lag the rate card. Some lines carry no quantity at all. About a quarter of Implentio customers' 3PL contracts with storage charges have at least one storage line with a dollar amount and no quantity, so the count has to come from the detail file.

What a supporting detail file is#

Summary, line items and detail rows#

The summary gives totals; each line item gives one fee with its quantity, rate and amount; the detail rows show the orders, packages, receipts, locations, returns or tasks behind each line. The file is also called invoice backup, billing backup, backup file, detail file, support file or transaction detail. See Anatomy of a 3PL invoice: summary, line items and supporting detail.

How 3PLs deliver it#

Detail can arrive in four forms, and public sources show none of them as the norm:

• One combined file. One 3PL attaches a CSV "with every invoice that shows a breakdown of every charge"¹.
• A file per invoice line. One warehouse software product zips "a backup document for each line item"².
• Portal views or exports. One 3PL's portal shows billing views for orders, purchase orders and ad hoc charges, with no storage view mentioned³.
• EDI. An X12 810 invoice works as backup only when each activity is its own line⁴; an X12 210 carries motor-carrier freight (LTL/FTL) charges, not warehouse fees⁵.

See Invoice formats: PDF, spreadsheet, portal, EDI 210/810.

The detail files to request, fee by fee#

Every fee type on your invoice needs its own detail, except flat fees, whose backup is the contract line.

Picks. Two pick structures are both common. When picks count per unit, the expected quantity depends on the structure. Where the order fee includes the first pick, additional picks should equal units shipped minus orders. Where a lower order fee comes with a pick fee on every unit, picks should equal units shipped. Some contracts count picks per line or SKU, and a kit can count as one pick or one per component, so check the contract's definition.

Shipping. The 3PL's shipment-level file is the backup for postage it bills, at carrier cost, marked up or on its own rate card. In about nine in ten of Implentio customers' 3PL contracts, small-parcel postage is on the 3PL's invoice. If you ship on your own carrier account, the carrier bills you, and its invoice and billing downloads are the backup, such as the documents and reports in FedEx Billing Online¹⁰. See Shipment-level cost data: why you need it and how to ask for it.

Adjustments. Most 3PLs pass carrier adjustments through on a later invoice, as separate lines or folded into regular shipping lines; some brands see none.

Storage. A SKU can occupy a pick and a reserve location at once, each billed under per-location or per-pallet pricing, so the detail should list both. For cubic-foot billing, ask for each SKU's dimensions; stored dimensions are more often too large than too small. Storage charged at receipt should carry the receipt reference. Square-foot storage is a fixed rate for an area allocated to you, full or not¹⁴, so its backup is the area in your contract. See Verifying storage counts against inventory snapshots.

Fields every row should carry#

Every row should let you find the activity in your records and recompute its amount:

• Invoice number and billing period
• Activity date
• A reference you hold: channel order number, tracking number, PO, ASN (the advance shipping notice you send your 3PL before inbound stock arrives), RMA or work order
• SKU, where the fee is per item
• Fee name as the rate card writes it
• Billing unit, quantity, rate and extended amount (quantity × rate)

Ask for a sortable CSV or XLSX, not a PDF of rows. One 3PL's help page warns that many reference fields in its file will be blank on many charges¹, so ask for the same references in every file. Open CSVs with the tracking-number column as text, or a spreadsheet can turn long numbers into scientific notation and drop digits. Bundle SKUs can also differ between your store and the 3PL's system, so ask which SKU each row shows.

How to request supporting detail#

Ask in writing for a defined set of files with every invoice, then put the obligation in the contract.

1. Send the fee-by-fee list above, or the checklist below.
2. Ask for detail with every invoice, matching its invoice number and billing period, and for each invoice when there are several in a period.
3. Set the timing. Ask for detail to arrive with the invoice, and for the dispute window to start when you receive the complete detail, not on the invoice date. A 30-day dispute window is common and 14 days is short. Some windows count from month-end; IWLA's standard terms for merchandise warehouses (2026 revision) count 30 days "from date of invoice" where a contract adopts them⁶.
4. Agree the file type and columns once, with notice before any change.
5. Write it into the contract. Public companies file some of their contracts with the U.S. Securities and Exchange Commission (SEC), which publishes them, so a few 3PL contracts can be read in full. Two of them, both warehouse contracts, say nothing about what accompanies an invoice^12,13. See Data access, reporting obligations and format requirements.

A 3PL's billing system builds the invoice from activity data, and one software vendor tells 3PLs it should let them "trace any line item back to the specific warehouse activity that generated it"⁷. Most 3PLs can produce row-level detail from the same system that builds the invoice, and routine billing detail is usually included in what you pay. Custom reports can carry a fee, so agree their price before signing.

What good looks like#

Good supporting detail lets you rebuild the invoice yourself:

• Detail for every fee type, with every invoice, for the same period and invoice number
• A sortable file whose rows sum to each line and to the total
• Quantity, rate and amount on every row, with fee names that match the rate card
• A reference on every row that you can find in your own systems
• Flat fees tied to a contract line, shortfalls shown as a calculation, and each credit tied to the invoice it reverses