Freight accrual accounting works when you accrue off the shipment event rather than the invoice. The load delivered in the period, so the expense belongs in the period, whether or not a carrier bill has arrived. Take the rate confirmation or contract rate as the base, add a separately estimated fuel surcharge using the published index week that applies, add an accessorial reserve derived from your own history, book it as accrued freight liability, and reverse it against the actual invoice when it lands.
The hard part is the tail: freight invoices keep arriving for weeks after the load moves, and a meaningful share of them are wrong when they do arrive. So an accrual built on “what the carrier will eventually bill” inherits every billing error in your carrier base. An accrual built on “what we agreed to pay” does not, and the gap between the two is your audit finding rather than your accounting error.
One honest note before the mechanics. You will see claims that some specific fraction of freight invoices are outstanding at any month-end. We have not found a verifiable public dataset that quantifies invoice lag, and freight accrual is a thinly covered topic generally. Rather than borrow someone else’s percentage, measure your own. The method for that is in the second section, and your own number is the only one that should drive your policy.
Why freight is harder to accrue than the rest of AP
Most accruals have one unknown: did the service happen in the period. Freight has four.
The bill has not arrived. There is a regulatory expectation about promptness. Under 49 CFR 377.205, a carrier is to present its freight bill within 7 days of receiving the shipment on prepaid moves, or within 7 days of delivery on collect moves, and the bill must state the credit time limit, the late-payment penalty, the service or collection charge, and the discount terms. In practice that timeline is not what your inbox looks like, and the regulation’s scope is narrower than most people assume: Part 377 Subpart B applies to for-hire non-exempt motor carriers and household goods freight forwarders, per the part 377 scope note. Contract carriage runs on your agreement’s terms.
The amount is not final even after the bill arrives. Accessorials show up late. Under 49 U.S.C. 13710, a carrier has 180 days from your receipt of the original bill to bill charges additional to those originally billed and preserve its collection rights. That is a six-month tail on any load you thought was closed.
One shipment is several charges with different certainties. Linehaul is contractual and knowable at tender. Fuel moves with a published index. Detention, lumper, layover and redelivery are events that may or may not have happened. Averaging them into one number throws away the part you actually know.
A material share of arriving invoices need correction. That is the premise of this whole site, and it means the invoice is not automatically a better estimate than your accrual. Sometimes the accrual is right and the invoice is wrong.
Measure your own invoice lag first
Everything downstream depends on this number, and it takes an afternoon to produce.
Pull twelve months of paid freight invoices. For each, capture the delivery date and the date the invoice was received. Compute the difference in days. Then build a cumulative curve: what percentage of a delivery month’s invoices had arrived by day 7, day 15, day 30, day 45, day 60, day 90.
Cut that curve three ways.
- By carrier. Lag is a carrier attribute, not an industry constant. Your two worst carriers usually explain most of the tail.
- By mode. LTL, truckload and parcel bill on different rhythms.
- By charge type. Linehaul-only invoices and invoices carrying accessorials will not have the same curve. The accessorial tail is the longer one.
That gives you three usable outputs: an expected accrual coverage percentage for month-end, a carrier-level exception list, and a defensible basis for your accessorial reserve rate. It also gives you the number to quote when someone asks how much of the accrual is estimated, which is the question an auditor will ask.
If your lag curve shows a carrier still delivering invoices at day 60, that is a conversation to have with them separately. It is also a reason to check whether those late bills are additional charges on already-billed loads, which run against the 180-day clock in 13710 and are covered in the freight billing deadlines reference.
Build the accrual in three layers
Do not accrue a single blended number per load. Split it, because each layer has a different confidence level and a different true-up behavior.
| Layer | Source of the estimate | Confidence | True-up behavior |
|---|---|---|---|
| Linehaul | Rate confirmation, contract lane rate, or accepted tender | High | Should be near-exact; a variance here is a rate dispute, not an estimate error |
| Fuel surcharge | Contract fuel schedule applied to the published index week for the shipment date | High to medium | Small variances are normal; large ones usually mean the wrong index week |
| Accessorials | Historical rate per load by lane, carrier and consignee | Low | Expect variance; this is the reserve, not a prediction |
Layer one: linehaul
If you tender loads with a rate confirmation, you already have the number. Accrue the rate con amount. If you move on a contract rate table, apply the table to the lane and the billable weight or mileage basis in your contract. If you moved a spot load, accrue the accepted quote.
Because linehaul is contractual, a variance between accrual and invoice on this layer is not an estimating problem, it is a billing exception, and it should be routed to your audit process rather than absorbed into a variance account. The mechanics of catching it are in reconciling the rate confirmation against the carrier invoice.
Layer two: fuel surcharge
Fuel is estimable to the cent because both inputs are published. Your contract gives you a base price peg and a rate per gallon or a surcharge table. The index gives you the week.
The EIA On-Highway Diesel Fuel Price Survey collects the cash self-serve pump price including taxes as of 8:00 a.m. local time on Monday from 590 retail outlets in the contiguous United States, and publishes around 10:00 a.m. Eastern on Tuesday, moving to Wednesday when Monday is a government holiday. It reports a national average, a California figure, and PADD regional breakouts. For the week ending July 27, 2026, the U.S. average was $5.313 per gallon, with the Midwest at $5.196 and the West Coast at $6.067, which is a useful reminder that a national-average accrual on a heavily West Coast network will run low.
For accrual purposes the only judgment call is which week’s index applies to a shipment date, and your contract should answer it. If it does not, that ambiguity is itself worth fixing, and the failure modes are laid out in which DOE index week applies to a fuel surcharge. Accruing fuel with the same rule your contract specifies means the accrual and the correct invoice agree, which turns any variance into a signal.
Layer three: the accessorial reserve
This is the layer people either skip or guess at. Neither works.
Derive a rate from your own history: total accessorial dollars divided by total loads, computed separately for the segments where behavior differs. Detention concentrates at particular consignees. Lumper fees concentrate in grocery and retail DCs. Liftgate and residential concentrate on specific delivery profiles. A single blended rate across a mixed network will be wrong in both directions at once.
Two rules keep this honest.
Reserve for what you expect to owe, not for what you expect to be billed. If a consignee generates detention charges you routinely and successfully dispute, reserving the full billed amount overstates the liability and hides the recovery. Reserve net of your historical dispute success rate on that charge type.
Track the reserve’s accuracy monthly. Accrued accessorials versus actual accessorials, by segment. If the reserve runs consistently light or heavy for three months, re-derive the rate. If it swings unpredictably, the problem is upstream in operations, not in accounting.
The entries and the true-up
Keep the accrual in its own liability account, separate from the AP trade balance. You want to be able to answer “how much of freight expense this period is estimated” without a query.
At period close, debit freight expense by cost center or lane and credit accrued freight liability, for every load delivered in the period with no invoice received. When the invoice arrives, book it to AP and relieve the accrual. Route the difference to a freight accrual variance account rather than burying it in expense, because the variance account is the only thing that tells you whether your estimating method works.
The reversal policy is the part that decides whether this is sustainable.
- Reverse and re-accrue each period rather than carrying load-level stubs forever. Load-level stubs age into a reconciliation project that nobody wants to own.
- Age the accrual anyway. Any load with an open accrual past your lag curve’s day 60 point gets flagged. Either the invoice is missing, or it went somewhere else, or the load was cancelled and nobody told finance.
- Close the tail deliberately. Because 13710 gives the carrier 180 days from your receipt of the original bill to add charges, a load with an original invoice already paid can still generate a supplemental bill months later. Decide whether your policy is to hold a small tail reserve for that or to expense it in the period received, and document the choice. Either is defensible. Undocumented is not.
- Do not release an accrual because an invoice is disputed. A disputed charge you expect to lose is still a liability. A disputed charge you expect to win was never a liability, and it should not have been accrued at full billed value in the first place.
Where accrual meets the audit desk
Treat the variance report as an audit input, not a housekeeping task. A structured variance tells you which of three things happened.
| Variance pattern | Most likely cause | Where it goes |
|---|---|---|
| Invoice above accrual on linehaul | Rate applied does not match the rate confirmation or contract table | Billing dispute |
| Invoice above accrual on fuel, consistently | Wrong index week, wrong region, or surcharge applied to accessorials | Billing dispute |
| Invoice above accrual on accessorials, at one consignee | Real operational problem at that facility | Operations, then contract |
| Invoice below accrual, repeatedly | Accrual method is stale, or you are reserving for charges you win | Re-derive the reserve rate |
| Invoice with no matching accrual | Load not in your system, or a duplicate | Check for a duplicate before paying |
That last row deserves specific attention at month-end. An invoice arriving for a load your system has no record of is either a data gap or a second bill for something already paid, and the two look identical until you check. The tests are in how to tell a duplicate freight invoice from a legitimate rebill. Under 49 CFR 378.9, a carrier that itself discovers an overpayment, duplicate payment or overcollection must refund it within 30 days, but the discovery is usually yours to make.
Making the estimate defensible
If your accrual is material, someone will eventually ask you to support it. Three things make that conversation short.
A written method. One page: what triggers an accrual, what source each layer uses, how the accessorial rate is derived, when it gets re-derived, and what the reversal policy is. Written before the period, not after the question.
A retrospective accuracy measure. Accrued versus actual, by layer, for the last twelve periods. This is the single strongest piece of support you can offer, and it takes one query once the variance account exists.
Traceable inputs. The rate confirmation for linehaul, the published index week for fuel, the historical dataset for the reserve. Every layer traces to a document or a public number. Nothing traces to judgment alone.
Month-end checklist
- Pull all loads with a delivery date in the period.
- Match them against invoices received and posted. The unmatched set is your accrual population.
- Accrue linehaul from the rate confirmation, contract rate or accepted tender.
- Accrue fuel using the contract schedule and the index week your contract specifies for the shipment date.
- Apply the accessorial reserve rate by segment, net of your historical dispute success.
- Book the accrual to a dedicated liability account, not to trade AP.
- Age open accruals against your own lag curve and flag anything past the day 60 point.
- Reverse prior-period accruals against invoices received, routing differences to the variance account.
- Review the variance report by layer and carrier, and route linehaul and fuel variances to the audit desk rather than absorbing them.
- Check every invoice with no matching accrual for duplication before it gets approved.
- Re-derive the accessorial reserve rate quarterly, or sooner if it misses three periods running.
Steps 9 and 10 are the ones that turn a compliance exercise into money. A freight accrual that is merely close is an accounting result. A freight accrual whose variances get read every month is an early-warning system for billing errors, and it finds them before the payment goes out rather than after.
Sources
- 49 CFR 377.205, Presentation of freight bills and required terms (Cornell LII)
- 49 CFR part 377, Payment of transportation charges, scope (Cornell LII)
- 49 U.S.C. 13710, Information and records, billing and contesting windows (Cornell LII)
- 49 CFR 378.9, Refunds on carrier-discovered overpayments within 30 days (Cornell LII)
- EIA On-Highway Diesel Fuel Price Survey methodology (U.S. Energy Information Administration)
- EIA weekly retail on-highway diesel prices by region (U.S. Energy Information Administration)
- Freight accrual: what it is and how it works (ZDS Consulting Services)