3PL invoice audit trail: what to record so finance can rely on it

Why finance needs more than "we checked it"#

Without a record from the invoice review, finance can only book what the invoice says. Once the person who checked it is away or has left, nobody can show why a line was disputed, which project was approved or whether a promised credit arrived. Credits and corrections can also land on a later invoice than the work they relate to, so the link has to be written down.

Billing errors can come from process rather than bad faith, and the same file gives your 3PL the evidence behind each question you raise.

What an audit trail is, and what it isn't#

In software, an audit trail is an event log ("a chronological record of system activities" in NIST's glossary¹); in an accounts payable (AP) system it shows who entered, changed, approved or paid a record, and when. This article means the evidence file behind your own review of the 3PL's bill, which feeds your AP system's record.

Your invoice audit is your own check of a vendor's bill, not a financial-statement audit. An outside auditor reviewing your financial statements may ask how you check and approve vendor bills, including your 3PL's. Controls such as segregation of duties are covered in Internal controls over 3PL billing and inventory.

A useful test comes from the standard for public-company auditors, which doesn't govern brands: an experienced auditor "having no previous connection with the engagement" should be able to understand the work, its evidence and conclusions, and who did it and when (PCAOB AS 1215, paragraph .06)². For a 3PL file, that means complete, traceable line by line and dated by whoever checked, with originals unedited.

What to keep for each billing period#

Keep the three record sets that How to audit a 3PL invoice, step by step works from (what you agreed, what you were billed and what happened), plus approvals, the 3PL's written answers and your log.

A 3PL report that agrees with the 3PL's invoice proves the arithmetic, not the charge, so the file needs your own record beside it; where you have none, log the check as a tie-out (two of the 3PL's own records agreeing). For which detail files to request, see The supporting detail files you should always request.

Portal views and exports can change after you check them: orders get edited or cancelled, inventory gets adjusted after counts, and some 3PLs regenerate or stop showing older detail files. Save each file you checked under a name with the period and the date you pulled it, and point evidence at that file and row, not at a live portal view or an inbox search. A saved file can be tested later; auditors likewise test the accuracy and completeness of system-produced reports, or the controls over them (PCAOB AS 1105, paragraph .10)².

The variance log: one row per finding#

The variance log has one row for each line where the billed amount differs from what you expected, in either direction:

Each row records:

• Invoice number and date, and the line.
• Billed quantity, rate and amount.
• Expected quantity, rate and amount, and where each came from.
• The counting basis the expected quantity assumes: per order or per package; per unit, line or SKU; units or occupied locations; a count day or a daily average; per each or per carton, with any per-SKU minimum.
• The variance and its direction.
• Evidence: the saved file name and row.
• Status: overcharge, undercharge, legitimate item outside your order data, or question.
• Who checked it and the date, the decision and the next action.

We see undercharges as well as overcharges in the invoices we review, so log both with the same evidence (the FAQ covers why). For variances that aren't errors, see Not every variance is an overcharge: undercharges, manual items and special projects.

Decisions, disputes and credits: closing each line#

Record a decision for each logged line, with who approved it: pay as billed, accept as legitimate, dispute or hold as a question. A disputed or open line closes only on a credit, a corrected invoice or an explanation you accept, not on a promise. For a dispute, record the date sent, the date the window closes, the 3PL's acknowledgment and answer, and the outcome. A 30-day dispute window is common; 14 days is short. The window usually starts when the invoice carrying the charge lands, not when the work happened; check what your contract says.

For a credit, record its form, number, amount and where it landed, such as the invoice that carries it. A credit can arrive as a negative line on a later invoice, a separate credit note, or a credit to your account balance³, or as a refund. A credit on fees that count toward your monthly minimum, landing in a month you're under it, is worth nothing if it's applied before the shortfall is calculated. Unless your contract sets the order, ask for it to be applied after, and record which order was used. Record the fix you asked for (a rate-table update for a wrong rate, or a billing-rule fix for a scope, quantity, category or mapping error). For a recurring charge, keep the line open until the next invoice of the same type bills it correctly. For a one-off charge, such as a duplicate line or a single project, close on the credit and watch the next invoice for the same kind of error.

Record what you paid and when. If your 3PL charges a card, drafts your bank account or draws on a prepaid balance when it invoices, there's nothing to withhold, so the dispute record carries the whole claim. See Tracking disputes and credits to closure for the tracker and Short-paying vs. paying in full and disputing for whether to withhold.

What to hand finance each period#

Send finance a one-page summary each period and keep the variance log behind it, so anyone can open a line and see its evidence. The summary lists:

• Invoices received, by number, date and total.
• The amount checked and approved.
• The amount disputed, and the amount under question.
• Credits expected and credits received, each with where it landed. Include every expected credit, whatever its source (billing dispute, service-level (SLA) credit, damage or loss claim, carrier refund), labeled by kind.
• Undercharges logged that may be billed later.
• Charges or credits on this period's invoices that relate to a different activity period.

Finance decides how to accrue and book each of these; see Booking 3PL credits and disputed amounts and Accruing 3PL costs when invoices arrive late. Approval routing and limits belong in your approval workflow, not this file.

How to organize the file and how long to keep it#

Name one owner for the file and a backup. Keep one folder per billing period, with each invoice's files under its number. Keep originals read-only and work in copies; date anything added later and note who added it and why, as AS 1215 requires of auditors².

As of October 2026, the IRS says to keep records supporting a US federal income tax return until its period of limitations runs out, counted from when the return was filed: generally 3 years; 6 years if you leave out income over 25% of the gross income shown; 7 years for a worthless-securities or bad-debt claim⁵. Employment tax records are kept at least 4 years after the tax is due or paid, whichever is later⁵. Insurers or creditors may require longer⁵. Keep each period's file at least through your contract term plus any look-back or audit-rights period, and longer if your accountant says your tax records need it. Ask your accountant for your retention policy, and see Your data rights and keeping your own history for saving 3PL data before your access ends.

What a reliable audit trail looks like#

A reliable file lets someone who didn't do the audit check it without asking you:

• They can recompute any line from the saved files.
• Every rate traces to a dated rate card version, amendment or notice.
• Every variance has saved evidence, a direction and a status.
• Every credit traces from its dispute or claim to where it landed.
• The period summary ties to the invoices finance paid.
• An error that was fixed and then came back shows up in the log.