GL coding freight charges well comes down to one decision: do you code the invoice or do you code the lines on it. Code the invoice, and every load lands in one account called Freight, where a legitimate linehaul, a fuel surcharge computed off the wrong week, and a detention charge nobody can prove all look identical. Code the lines, and your general ledger becomes the first place a billing problem shows up.
The working structure is four buckets. Linehaul, split by inbound and outbound because they get different accounting treatment. Fuel surcharge, in its own sub-account under each. Accessorials, broken into enough accounts that you can see which ones are growing. Claims and recoveries, which are not freight expense at all and should never be netted into it.
None of this is dictated by regulation. Freight coding is an accounting-policy question your controller and your auditors settle, and the right answer depends on your chart of accounts. What follows is the structure that survives contact with real freight invoices, and the places where a standard AP approach breaks on freight documents.
Why the freight invoice does not tell you how to code it
A three-line AP invoice from a supplier codes itself. A freight invoice does not, for two reasons.
The first is that the carrier’s line labels describe its own billing system, not your cost structure. “ACC 87.50” is a real line on real invoices. So is “OTHER CHARGES.” You cannot code what you cannot read.
You have a rule behind the request for better. Under 49 CFR 373.103, a freight or expense bill must show the consignor and consignee names, shipment date, origin and destination, package count, freight description, weight or volume, the exact rates assessed, and the total charges due with the nature and amount of each charge, plus the route, participating carriers, transfer points, and remittance address. “The nature and amount of each charge” is the phrase to quote. A line item with a code and no description is a defective bill on its face, and asking for itemization is a reasonable request with a regulation attached rather than a favor.
The second reason is that one invoice can carry charges that belong in three different places. A single truckload bill might contain linehaul that capitalizes into inventory, a lumper fee you will rebill to a customer, and detention that is under dispute. Coding that invoice to one account is not a shortcut. It is a decision to never find out.
The four buckets
Freight-in versus freight-out
The first split is direction, because the two are treated differently and always have been.
Inbound freight on goods you are buying, freight-in, is conventionally treated as part of the cost of acquiring inventory and capitalized into inventory cost, then released to cost of goods sold as the goods sell. Outbound freight, freight-out, is a cost of delivering to the customer, and companies commonly present it in cost of goods sold or in selling expense depending on how they view the function. Both treatments exist. Pick one, document it, and apply it consistently, because switching mid-year makes your margin trend meaningless.
This is an accounting-policy call, not a freight call, so confirm it with whoever signs your financials. The freight side of the job is making sure direction is coded correctly on every invoice, which is harder than it sounds when a carrier bills a return, an interplant transfer, and a customer delivery on one consolidated statement.
Fuel surcharge gets its own line
The most common structural mistake in GL coding freight charges is folding fuel surcharge into linehaul. It is understandable, since the surcharge follows the linehaul and lands in the same period. It is also the reason most controllers cannot answer “what happened to our freight cost” when the number moves.
Fuel surcharge is a formula output, not a price. It is computed from a published diesel index, a peg, and a scale, and it moves for reasons that have nothing to do with your negotiated rate. The EIA On-Highway Diesel Fuel Price Survey, the source most contracts point to, collects the cash self-serve pump price including taxes as of 8:00 a.m. local time Monday from 590 retail outlets and publishes around 10:00 a.m. ET Tuesday, broken out by PADD region plus national and California. Anyone can recompute the surcharge from a public number, which is exactly why it should sit in its own account.
Keep it as a sub-account under each direction, not a single company-wide fuel account. Inbound and outbound fuel move for different reasons, and merging them makes the ratio useless. The recomputation is worked end to end in how to calculate a truckload fuel surcharge per mile from the DOE index.
Accessorials, split by whether you can do anything about them
One accessorial account is barely better than none. Two or three, split by controllability, changes what the ledger tells you.
Practitioners work from a fairly stable list of accessorial types: liftgate, redelivery, layover, reweigh, limited access, lumper, residential, inside delivery, sort and segregate, TONU, additional stops, storage, and detention among others, documented in a practitioner reference of the top 20 accessorial charges. Twenty accounts is too many. The useful cut is three.
| Account | What goes in it | What it tells you |
|---|---|---|
| Structural accessorials | Residential delivery, limited access, inside delivery, metro, liftgate at known no-dock sites | Cost of serving the customers and locations you chose to serve. Reduce it by changing the network or the quote, not by disputing invoices. |
| Operational accessorials | Detention, layover, TONU, redelivery, storage, reconsignment, additional stops | Cost of your own scheduling and your facilities. This account going up is an operations signal, not an AP signal. |
| Labor and handling | Lumper, driver assist, sort and segregate, unloading | Frequently rebillable and frequently double-billed under overlapping names. Needs its own visibility for that reason alone. |
Once accessorials sit in named accounts, the accessorial-to-linehaul ratio becomes computable per month and per carrier, and a carrier whose ratio drifts from 8 percent to 14 percent while its linehaul stays flat is telling you something the invoice total never would.
Claims and recoveries are not freight expense
A loss and damage claim is a separate transaction from a freight bill, on a separate clock, and it should not be netted against freight expense. Code the claim as a receivable when you file it, with an allowance judgment when it ages, and record the recovery against that receivable rather than as a credit to freight.
The clocks matter for when you reserve. Under 49 U.S.C. 14706(e)(1), a carrier cannot impose a claim-filing period shorter than 9 months or a suit period shorter than 2 years, with the 2 years running from the carrier’s written disallowance notice. Under 49 CFR 370.9, the carrier must pay, decline, or make a firm written compromise offer within 120 days of receiving the claim, and issue a written status report at 120 days and every 60 days after that if it remains unresolved. A claim receivable sitting past two status-report cycles with no disposition is telling your controller something specific about collectibility.
One detail changes the number: salvage. Under 49 CFR 370.11, carriers disposing of rejected or damaged property must keep itemized lot-numbered records tying the salvage back to the original shipment and record the salvage recovery amount and the date funds were transmitted on the claim file. Salvage proceeds reduce the claim, so the recovery you book may be smaller than the claim you filed. Ask for the salvage record instead of being surprised by the math.
Keep all of this separate from billing disputes, which are a different process on a different clock, with different deadlines and a different documentation standard.
The messy parts: disputes, short pays and recoveries
Coding an invoice that is partly in dispute
The clean pattern is: code the full invoice, pay the undisputed portion, and carry the disputed line in a contra or receivable account rather than reducing freight expense.
Reducing expense at dispute time creates two problems. It overstates the period’s margin on an outcome you have not won, and it destroys the audit trail: three months later the disputed $400 has simply vanished from the account and nobody can reconstruct what happened. A dispute account, cleared when the corrected invoice or the denial arrives, keeps both facts on the ledger.
Whether to short-pay or pay in full and claim it back is a separate decision, and the coding follows it. Short-pay and you have a contested balance on the carrier’s aging. Pay and then claim and you are on the overcharge process instead. Under 49 CFR 378.8, the processing carrier must pay, decline to pay, or settle each written overcharge claim within 60 days of receipt unless you agree in writing to extend, so the receivable has a defensible expected life.
Where recoveries go
Code a recovery back to the account it came out of, in the period it is recovered. A detention credit reduces the operational accessorial account. A fuel surcharge correction reduces the fuel account. A duplicate payment refund reduces linehaul.
The temptation is to book recoveries to miscellaneous income, because it looks like found money. Resist it. Recoveries against the originating account are what let you say freight cost per unit fell, which is the number finance asks for. Recoveries in other income are a rounding entry nobody reads. This is also the only honest way to answer the “prove the savings were real” question when you are evaluating what freight audit actually costs across pricing models.
Duplicate payments are a coding problem before they are a recovery problem
A duplicate freight invoice paid twice hits your GL as two legitimate-looking entries in the same account, and if the second one arrives in a different month with a different invoice number, nothing in the ledger flags it. Coding by load reference rather than by invoice number is the fix, and it is why catching duplicate freight invoices across rebills and corrected bills belongs in the AP process rather than in a quarterly review.
The carrier has affirmative duties here that most payors never invoke. Under 49 CFR 378.9, when a carrier itself discovers an overpayment, duplicate payment, or overcollection, it must refund within 30 days, and on receiving payor information for an unidentified payment it must refund or respond within 14 days.
Timing: the period the charge belongs to
Freight invoices arrive after the freight moves, sometimes long after. Two timing rules keep the coding honest.
Code to the shipment date, not the invoice date, for anything that flows into inventory or into a per-unit cost. An invoice received in October for a September move belongs to September’s freight cost regardless of when AP touched it, and accruing on the shipment event rather than the invoice is the only way freight cost per unit means anything month to month.
Watch the late rebill. Under 49 U.S.C. 13710, a carrier must bill charges additional to those originally billed within 180 days of your receipt of the original bill to preserve its collection rights, and you must contest a bill within 180 days of receipt to preserve your right to challenge. A supplemental charge landing in month seven is a deadline question before it is a coding question. All of these clocks are collected in every freight billing deadline that can cost you money.
A worked chart of accounts
Illustrative, and meant to be cut down rather than adopted whole. A 300-load-a-month operation does not need twenty freight accounts.
| Account | Contents | Notes |
|---|---|---|
| Freight-in, linehaul | Base transportation on inbound purchases | Capitalizes into inventory under the conventional treatment |
| Freight-in, fuel surcharge | Inbound FSC | Separate so it is independently recomputable |
| Freight-in, accessorials | Inbound accessorials, structural and operational | Split further only if inbound accessorials are material |
| Freight-out, linehaul | Base transportation on customer deliveries | COGS or selling expense per your policy |
| Freight-out, fuel surcharge | Outbound FSC | |
| Freight-out, structural accessorials | Residential, limited access, inside delivery, metro | Network and customer-mix cost |
| Freight-out, operational accessorials | Detention, layover, TONU, redelivery, storage | Your scheduling and facility cost |
| Labor and handling accessorials | Lumper, driver assist, sort and segregate | Often rebillable, often double-billed |
| Freight billing disputes | Contested line items pending resolution | Contra or receivable, cleared on resolution |
| Freight claims receivable | Filed loss and damage claims | Not freight expense; separate clock |
| Rebilled freight recovery | Freight billed on to customers | Never net against freight expense |
Two columns to carry alongside every entry, whether or not your GL calls them dimensions: the load or shipment reference, and the carrier. Without the load reference you cannot match to a rate confirmation or detect a duplicate. Without the carrier you cannot compute the per-carrier ratios that make the accounts worth having.
The month-end checklist
- Confirm every invoice is coded by line, not by total.
- Confirm direction: inbound and outbound coded to the right side, with returns and transfers checked specifically.
- Confirm fuel surcharge is in its own account and not folded into linehaul.
- Review the operational accessorial account for the month against the same month last quarter, by carrier.
- Reconcile the dispute account: anything older than 60 days needs a decision, and anything older than the applicable contest window needs a write-off decision.
- Reconcile claims receivable against the carrier’s 120-day disposition and 60-day status-report obligations.
- Accrue unbilled freight on ship date, not invoice date.
- Check that recoveries landed in the originating account and not in other income.
- Spot-check that the load reference is populated on every freight entry, since it is the field every downstream check depends on.
None of this is about tidiness. A chart of accounts with named accessorial accounts and a separate fuel line makes billing errors visible as a trend, weeks before anyone opens an invoice. That is the same reasoning behind reconciling a carrier invoice against the rate confirmation field by field: the earlier a mismatch has a place to show up, the cheaper it is to fix.
Sources
- 49 CFR 373.103, Freight or expense bills (Cornell LII)
- 49 CFR 378.8, Overcharge claim resolution within 60 days (Cornell LII)
- 49 CFR 378.9, Carrier refund duties on duplicate payments and overcollections (Cornell LII)
- 49 CFR 370.9, Carrier disposition and status report deadlines (Cornell LII)
- 49 CFR 370.11, Salvage records and recovery reporting (Cornell LII)
- 49 U.S.C. 14706, Carmack claim and suit time limits (Cornell LII)
- 49 U.S.C. 13710, Balance-due billing and contest windows (Cornell LII)
- EIA On-Highway Diesel Fuel Price Survey methodology (U.S. Energy Information Administration)
- Top 20 accessorial charges, practitioner taxonomy (Zipline Logistics)