Back to blogs

    Know Detention Charge Codes and Fix Freight Spend Reporting

    By TransportOne Editorial Team•October 20, 2026•7 min read
    Trucks parked in the truck parking area of an I-10 rest area in Suwannee County, Florida

    Your spend report says detention cost more last quarter than the quarter before. Pull the invoice lines behind the number and the picture dissolves. Three carriers billed a code that reads DET. Two used WTG. One sent a free text line saying DRIVER WAIT 2.0 HRS AT CONS. A drayage provider folded the same event into something it calls terminal delay and billed it by the day instead of the hour.

    The dollars are real, but the category is an accident of carrier formatting. Freight accessorial codes are the codes carriers put on invoice lines to label extra services and charges beyond linehaul, and detention is one of them. Detention charge codes are the labels carriers attach to a waiting truck, and there are many of them for one event. You can't negotiate detention down, prove it's rising or attribute it to a facility until every one of those lines resolves to the same thing.

    Why standard detention charge codes don't settle the question

    Most shippers assume the EDI code set settles this. It doesn't. The set was built so any carrier can describe any charge, and nothing in it makes two carriers describe one charge identically.

    Eight codes for one waiting truck

    IBM publishes the charge and allowance code list its Sterling transportation product supports, the codes meant to travel in EDI data exchange. Count the entries that mean a vehicle sat waiting:

    • DET, detention of trailers
    • DEP, detention of power units
    • DTL, detention loading
    • DTU, detention unloading
    • DTV, detention of a vehicle
    • TDT, truck detention
    • SDC, special detention charge
    • DSF, detention of a special type flat car

    Eight codes, one operational event, and no free text yet.

    Storage, notification and the escape hatches

    The same list offers five ways to bill for goods sitting still: SRG storage, STR storage in transit, WHC warehouse charge, DEM demurrage and DES demurrage special. It also has a short set for telling somebody the freight is coming: APT appointment notification, MNC notify consignee and NFY carrier notification charge.

    When none of those fit, a carrier can reach for MSC, other accessorial service charge. Or MSG, miscellaneous charge. Or SUR, surcharge. Or SER, service charge. Or ZZZ, mutually defined.

    With five escape hatches, the list works as a vocabulary. It governs what a carrier is permitted to say. It's silent on what two carriers saying different things have in common, and that's the only question your audit and your analytics both need answered.

    How Do Free-Text Charges Affect Freight Invoice Matching?

    An audit engine comparing freight accessorial charges to a contract has to settle a prior question for every billed line: which clause prices it? With a canonical code, that's a lookup. With a raw description, the engine is guessing and calling it a string comparison.

    The two failure modes don't cost the same, and you pay for both:

    • A line that fails to map lands in an exception queue and consumes an analyst, even when the charge is perfectly valid.
    • A line that maps to the wrong clause gets checked against the wrong rate and waved through. It looks exactly like a clean audit until somebody reconciles the contract by hand.

    Ardent Partners' 2025 Accounts Payable Metrics That Matter report puts the average invoice exception rate at 22 percent, against 9 percent for best-in-class teams, with the average cost of processing an invoice at $9.40. Freight bills sit at the hard end of that distribution. A single truckload invoice can carry a dozen accessorial lines, each needing its own clause, and an LTL consolidation invoice carries hundreds.

    Normalisation won't make the hard charges easy, but it strips away the ambiguity on top of them. The real question, whether the event happened and who caused it, becomes the first thing an auditor reaches instead of the third.

    What a canonical code has to carry

    Renaming alone buys you very little. Map WTG and DET to a shared label called DETENTION and the report looks tidier, but you still can't audit the line. The canonical entry has to carry the attributes that make the charge checkable.

    AttributeWhat it settles
    Canonical codeOne identifier per operational event, so every carrier's spelling collapses to a single row
    Event definitionThe physical thing that must have occurred for the charge to be valid at all
    Unit of measurePer hour, per day, per shipment, per container. Demurrage billed daily and waiting time billed hourly can't be compared until this is explicit
    Free time and roundingWhen the clock starts, what's free, how a partial unit rounds
    Causality ownerShipper, consignee, carrier, terminal, customs. This attribute is what turns a payable charge into a disputable one
    Required evidenceThe record that proves the event: gate in and gate out, geofence dwell, appointment booked against arrival observed
    Clause pointerThe paragraph that prices it, resolved per carrier, lane and equipment type

    How the attributes get used in an audit

    Those seven attributes are what separate a canonical code from a label. In automated freight invoice audit, Penny uses them in order. She resolves the billed line to one entry in the taxonomy, recomputes the amount from the clause that code points at, then tests the event against the evidence the code says is required.

    Take a detention charge on a lane with four hours free and no dwell record. There's no variance to escalate here, because nothing stands behind the charge, and Penny drafts the dispute saying so. The evidence chain behind that decision is laid out step by step in what a detention charge has to prove before you pay it.

    Mapping is the work, and it never finishes

    The taxonomy is the easy half. The hard half is the mapping layer between it and the freight accessorial codes each carrier actually bills, and teams routinely get that layer wrong.

    Keep maps per carrier

    The same three letters mean different things in different tariffs. A map keyed on the code alone will quietly merge two charges that your contracts price separately, so build the map per carrier.

    Give free text its own path

    Descriptions arrive misspelled, abbreviated, concatenated with a reference number, or typed by a dispatcher at 2am. Pattern matching handles the common shapes. The rest needs a model that reads the line in the context of the shipment it sits on. When we map a new shipper's history, the long tail is rarely creative. It's usually the same handful of dispatchers abbreviating the same three words a dozen ways.

    Leave unmapped lines unmapped

    The most damaging default in freight data is routing an unrecognised description into a bucket called other. It clears the queue and destroys the evidence that your taxonomy has a gap. An unmapped line should block, surface, and get a canonical code added once, permanently.

    Track coverage in dollars

    That last point is why mapping coverage deserves its own metric: the share of accessorial spend that resolves cleanly, measured in dollars. The figure tells you how much of your freight bill you can currently reason about.

    What normalisation buys on the reporting side

    Matching is the immediate payoff. The larger one arrives at the negotiating table, because a rate conversation needs a quantity.

    Fuel is the clearest case. The Q3 2026 TD Cowen/AFS Freight Index, published in July 2026, reported that the average LTL fuel surcharge in the second quarter ran more than 60 percent above its June 2025 level. A shipper whose fuel lines are scattered across FUE, a numeric 405, a generic SUR and three free text variants can't see that movement in its own data. It certainly can't separate the part driven by diesel from the part driven by a table change. The same blindness applies anywhere a charge is computed from several inputs instead of quoted as one rate.

    With codes normalised, the questions become answerable and ordinary:

    • Which three consignee facilities generate most of your detention hours?
    • Which carrier charges a notification fee that two of its competitors include in linehaul?
    • What's your true cost per stop once stop-off, driver assist and inside delivery are counted together?

    For freight rate negotiation, Miles takes those numbers into the room as positions instead of impressions. An accessorial you can quantify is one you can ask to have folded into the base rate. That matters most where consignee dwell drives the bill, which is a familiar pattern in freight audit for retail distribution networks.

    A one-afternoon test for your own detention data

    Export every accessorial line from last quarter and group by the raw description string exactly as it arrived. Count the distinct values. Most shippers find several hundred where they expected a few dozen, and the long tail is almost entirely one carrier's formatting.

    Then take the top twenty by spend. For each one, write down the unit of measure and the party responsible. Where you can't answer either question, you're paying on trust, and that's where a canonical taxonomy pays for itself first.

    If you'd like to see your carriers' descriptions mapped against your own contracts, book a walkthrough with us and bring last quarter's export.

    Frequently asked questions

    How do you identify detention charges on freight invoices?
    Don't rely on one code. Detention arrives under at least eight EDI codes, under general codes like MSC or SUR, as free text such as driver wait, and sometimes as a daily terminal delay charge. Map each carrier's codes and descriptions to one canonical detention code, keep the map per carrier, and block any line that doesn't map so someone reviews it.
    How can you improve freight spend reporting?
    Normalise every accessorial line to a canonical code that carries its unit of measure, so hourly and daily charges stop landing in the same total. Track mapping coverage as the share of accessorial spend, in dollars, that resolves cleanly. Once codes are normalised you can answer questions like which consignee facilities drive your detention hours, or what a stop really costs once stop-off, driver assist and inside delivery are counted together.
    What is the difference between detention and demurrage?
    Detention is charged for holding equipment or a driver beyond free time outside the terminal, for example at your dock. Demurrage is charged when a loaded container sits inside the terminal past its free time. Demurrage is often billed by the day, so you can't compare it with hourly waiting time until the unit of measure is explicit.
    What are the common detention charge codes on freight invoices?
    The EDI charge and allowance list IBM publishes for its Sterling transportation product includes DET, DEP, DTL, DTU, DTV, TDT, SDC and DSF, all describing a vehicle that sat waiting. Carriers also bill detention under general codes like MSC, MSG, SUR, SER or ZZZ, or as free text such as driver wait. That means one event can appear under many labels across your carriers.
    How do I spot duplicate detention charges billed under different codes?
    Normalise every accessorial line to a canonical code first, then look for the same canonical event on the same shipment and stop. Two lines that read DET and WTG, or a code plus a free text driver wait line, will then show up as one event billed twice. Without normalisation they look like separate charges and both get paid.

    See it on your freight

    Stop Overpaying On Freight Invoices

    Penny checks every invoice against your contracts and what the shipment actually did, then disputes what doesn’t hold up. You pay 30% of what she saves you, and nothing if she saves nothing.

    See how Penny works

    Found this useful? Share it with your team.

    Share on LinkedIn