# Freight invoice audit in the Memphis market > Memphis freight invoices carry rail-drayage and hub-transfer charges most lane audits never check. Here is what to verify and why. Read the full guide. Source: https://valuexpa.com/insights/freight-invoice-audit-in-the-memphis-market Publisher: ValueXPA (https://valuexpa.com) Updated: 2026-09-06 --- Margin drift is the gap between what a vendor contract says and what the invoice actually charges. In freight, that gap widens wherever a lane runs through unusual physical infrastructure, and Memphis has more of that than most US markets. Memphis sits at the junction of five Class I railroads and hosts the world's busiest cargo airport by tonnage. Freight moving through it crosses more handoff points, per mile, than freight moving through a single-mode corridor. Each handoff is a place a charge can be added, misapplied, or duplicated. ## Executive Summary A freight invoice audit in Memphis has to check for something most lane audits do not: charges generated by a transfer between modes, not just charges generated by the move itself. Because Memphis is a convergence point for BNSF, Union Pacific, Norfolk Southern, CSX and Canadian National, a shipment routed through it may pick up drayage, chassis, and rail fuel surcharge lines that never appear on a straight truckload invoice between two other cities. The contract has to specify who owns each leg and each surcharge; the invoice has to match it leg by leg, not as one blended charge. The mechanism is structural, not seasonal. A carrier's linehaul rate can be correct and the total invoice can still be wrong, because the drift sits in the accessorial lines attached to the intermodal transfer, not in the base rate. National fuel surcharge tables apply the same published index to a Memphis lane as to any other lane, so the index itself is not the local variable. The local variable is how many transfer-related charges get layered on top of it, and whether the contract named who is billing for each one. What changes it is treating the transfer point as its own line of the audit, separate from the linehaul. That means confirming the contract states a chassis and drayage rate table specific to the Memphis ramp, checking that fuel surcharge percentages tie to the index actually named in the contract, and verifying that a single shipment is not billed a drayage fee by more than one party in the chain. ## 1. What is different about freight billing in Memphis? **Memphis is a convergence point for five Class I railroads and the world's busiest cargo airport by tonnage, so freight moving through it changes hands more often than freight on a single-mode lane. Every mode transfer is a place a drayage fee, chassis charge, or terminal handling fee can attach. A lane audit built for point-to-point truckload misses these because it checks the linehaul rate and stops there. Memphis invoices need a leg-by-leg check, not a lane-total check.** A truckload move from, say, one mid-sized city to another typically has one carrier and one rate card to check against. A Memphis intermodal move can have a rail carrier, a drayage provider, and a terminal operator on the same shipment, each billing against a different agreement, or in some cases no written agreement at all if the drayage step was subcontracted informally. The audit question is not whether the linehaul rate matches the rate card. It usually does. The question is whether every party that touched the load between the rail ramp and the dock has a contract term that specifies its charge, and whether that charge appears once, not twice, on the combined invoice. This is not a claim about how often the error happens across shippers generally. It is a statement about the mechanism: more handoffs create more billing surfaces, and a contract audit has to cover each one by name. ## 2. Why does the rail and intermodal transfer point matter for the audit? **The transfer point between rail and truck is where drayage, chassis usage, and terminal handling charges originate, and Memphis has five Class I rail connections generating that transfer traffic. A contract that names a linehaul rate but does not separately name a drayage rate table for the Memphis ramp leaves that leg unpriced in writing, which means the invoice sets the price by default. The fix is a rate table that names the ramp, not just the corridor.** A rate card written for a lane, origin city to destination city, treats the move as one line. A Memphis intermodal move is at minimum two lines: the rail leg and the drayage leg from ramp to final dock. If the contract only prices the corridor, the drayage leg is priced however the carrier's invoice says it is priced, because there is no contract term to check it against. Chassis charges are a related and separate issue. The chassis that carries a container off the rail car is sometimes owned by the railroad, sometimes by a pool, and sometimes by the drayage carrier itself, and the per-diem or usage charge differs by owner. An invoice that bills a chassis fee needs a contract line that says whose chassis it is and what the fee should be. - **Drayage rate table:** A rate specific to the ramp-to-dock leg, separate from the linehaul rate, naming the Memphis ramp by name. - **Chassis ownership clause:** States who owns the chassis on a given move and what the associated usage or per-diem charge should be. - **Terminal handling charge cap:** A ceiling on what the terminal operator can bill for lifting a container on or off a rail car. ## 3. How does fuel surcharge pricing apply on a Memphis lane? **Fuel surcharge tables are set against a published national index, and the index itself does not change by city. The Bureau of Labor Statistics Producer Price Index for gasoline, series WPU0571, stood at 302.759 in July 2026, up 37.1% year over year, read September 6, 2026. The audit question in Memphis is not whether that index moved, it is whether the contract names that specific index and whether the invoiced surcharge percentage actually reconciles to it, on both.** Because a Memphis shipment often carries two fuel surcharge lines, one for the rail carrier and one for the drayage carrier, it is possible for both to be correct against their own contract and for the shipper to still be paying a surcharge twice against overlapping mileage, if the two contracts were never checked against each other. The check is mechanical: pull the fuel index named in each contract, confirm both invoices compute their surcharge percentage against that same named index and not a different one, and confirm the mileage or fuel-consumption base each surcharge is applied to does not overlap the other leg's base. ## 4. What does the current freight cost environment mean for a Memphis contract review? **Per the Bureau of Labor Statistics Producer Price Index for truck transportation of freight, series WPU3012, the July 2026 index stood at 170.984, up 10.9% year over year, read September 6, 2026. The industry-specific series for long-distance truckload, PCU484121484121, stood at 195.575, up 8.1% year over year, same read date. Rising input costs raise the odds a carrier requests a rate increase mid-contract, which is exactly the moment a rate card without a Memphis-specific drayage line.** A carrier renegotiation triggered by rising linehaul cost is a normal, defensible request. The risk for a Memphis shipper is procedural: if the existing contract already blended the linehaul and drayage rates into one number, a renegotiation is a chance to separate them and price each leg on its own table, this time naming the ramp. If the contract stays blended through a renegotiation, the shipper loses the one opportunity a rate change creates to fix the underlying documentation gap. The renegotiation conversation is the right moment to ask the carrier for a drayage rate specific to the Memphis ramp and a fuel surcharge clause that names the index by series, not by a general reference to 'DOE diesel prices.' ## 5. Can duplicate charges hide across a rail and drayage handoff? **Yes, and the mechanism is structural rather than accidental: when a rail carrier and a drayage carrier each invoice separately for the same container move, a terminal handling fee or a fuel surcharge can appear on both invoices if the two billing systems never cross-reference the container number against the other party's charge. Checking for this requires matching container or trailer numbers across every invoice touching one shipment, not just checking each invoice against its own contract in isolation.** A single-carrier truckload move has one invoice, so a duplicate charge on that move usually means the same invoice was paid twice, which standard three-way matching catches by checking the invoice number against payment history. A multi-party intermodal move through Memphis does not have one invoice number to check against. It has several, from several vendors, referencing the same container by different reference numbers on each one. Three-way matching against a purchase order does not catch this, because each invoice is a legitimate, distinct transaction against its own vendor. Catching it requires reconciling the container or trailer ID across all invoices tied to one shipment, a step outside what standard AP matching is built to do. ## 6. What should a Memphis contract specify that a generic freight contract does not? **A freight contract covering Memphis lanes should name the specific rail ramp or terminal by location, price the drayage leg on its own table separate from linehaul, state chassis ownership and usage fees by name, and name the exact published fuel index series the surcharge reconciles against. A generic lane contract that prices origin to destination as one number and references fuel surcharges generically leaves every one of those items to be set by whichever invoice arrives first.** The contrast is not that Memphis needs a different kind of contract. It needs the same kind of contract with more legs named in it, because the physical move has more legs. A services contract that would be complete for a two-party truckload lane is incomplete for a Memphis intermodal lane if it stops at linehaul and fuel surcharge. The additional terms, drayage rate table, chassis clause, terminal handling cap, and named fuel index, are not extra protections. They are the minimum needed to make the invoice checkable at all, because without them there is no written rate to check the drayage or terminal charge against. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. See also [the six categories drift hides in](/guides/indirect-spend-audit-categories) and [accessorial charge audit: the surcharges nobody validates](/guides/accessorial-charge-audit-the-surcharges-nobody-validates). ## 7. Frequently Asked Questions (People Also Ask) ### Does the Memphis rail hub add cost to every shipment through the city? It adds billing surfaces, not necessarily cost. A well-documented drayage rate table and named fuel index can keep the added legs priced correctly. The risk is not the transfer itself, it is a contract that never separately priced it, leaving the invoice to set the rate by default. ### Is the fuel surcharge on a Memphis lane different from other US lanes? The published index, such as the Bureau of Labor Statistics series WPU0571 for gasoline, applies nationally and does not change by city. What differs in Memphis is that a shipment can carry two separate fuel surcharge lines, one per mode, so the audit has to confirm both reconcile to the index named in each contract without double-counting mileage. ### What is a drayage rate table and why does Memphis need one named separately? It is a contract schedule pricing the short truck move between a rail ramp and the final dock, separate from the long-haul rail rate. Memphis needs it named because the city is a rail-to-truck transfer point for five Class I railroads, so that leg exists on shipments where it would not exist on a single-mode lane. ### Who owns the chassis on an intermodal move through Memphis? It depends on the specific move: a railroad, a chassis pool, or the drayage carrier can each own it, and the usage or per-diem fee differs by owner. The contract should state ownership and the associated fee by name rather than leaving the invoiced carrier to bill whichever rate applies to whichever chassis showed up. ### Can three-way matching catch duplicate charges on a multi-carrier Memphis shipment? Not reliably. Three-way matching checks one invoice against one purchase order and one receipt. A Memphis intermodal move can generate several legitimate invoices from different vendors referencing the same container, so catching an overlap requires cross-referencing the container or trailer ID across all of them, a step outside standard matching. ### Should we ask our carrier to separate drayage pricing from linehaul pricing? Yes, if the current contract blends them into one lane rate. A blended rate has no line to check the drayage leg against, which means that leg is effectively unpriced in writing. Separating the two at the next renegotiation gives you a rate table to audit each invoice against. ### Does rising freight cost make a Memphis contract review more urgent? It raises the chance a carrier requests a mid-contract rate change, and per the Bureau of Labor Statistics Producer Price Index for truck transportation of freight, series WPU3012, the July 2026 index was up 10.9% year over year, read September 6, 2026. A requested increase is the natural moment to also separate any blended drayage and linehaul pricing. ### What is a terminal handling charge and where does it show up on a Memphis invoice? It is the fee a terminal operator bills for lifting a container on or off a rail car. It shows up separately from both the linehaul and drayage charges on an intermodal invoice, and a contract without a stated cap leaves that fee to be set by the terminal operator's own tariff. ### Is this audit approach specific to Memphis or does it apply anywhere? The mechanism, checking every leg of a multi-party move rather than just the linehaul rate, applies at any rail-to-truck transfer point. Memphis is named here because its concentration of five Class I rail connections and major air cargo volume makes that transfer pattern common on lanes running through it. ### Is contract complexity quietly draining your operating margin? A small systematic drift between your negotiated contracts and your actual vendor billing compounds quietly across a year of invoices. Stop guessing at your exposure and run a targeted audit. **[Take the Free Screener → https://valuexpa.com/margin-drift-screener](https://valuexpa.com/margin-drift-screener)** ## Executive Summary A freight invoice audit in Memphis has to check for something most lane audits do not: charges generated by a transfer between modes, not just charges generated by the move itself. Because Memphis is a convergence point for BNSF, Union Pacific, Norfolk Southern, CSX and Canadian National, a shipment routed through it may pick up drayage, chassis, and rail fuel surcharge lines that never appear on a straight truckload invoice between two other cities. The contract has to specify who owns each leg and each surcharge; the invoice has to match it leg by leg, not as one blended charge. The mechanism is structural, not seasonal. A carrier's linehaul rate can be correct and the total invoice can still be wrong, because the drift sits in the accessorial lines attached to the intermodal transfer, not in the base rate. National fuel surcharge tables apply the same published index to a Memphis lane as to any other lane, so the index itself is not the local variable. The local variable is how many transfer-related charges get layered on top of it, and whether the contract named who is billing for each one. What changes it is treating the transfer point as its own line of the audit, separate from the linehaul. That means confirming the contract states a chassis and drayage rate table specific to the Memphis ramp, checking that fuel surcharge percentages tie to the index actually named in the contract, and verifying that a single shipment is not billed a drayage fee by more than one party in the chain. ## 1. What is different about freight billing in Memphis? Memphis is a convergence point for five Class I railroads and the world's busiest cargo airport by tonnage, so freight moving through it changes hands more often than freight on a single-mode lane. Every mode transfer is a place a drayage fee, chassis charge, or terminal handling fee can attach. A lane audit built for point-to-point truckload misses these because it checks the linehaul rate and stops there. Memphis invoices need a leg-by-leg check, not a lane-total check. A truckload move from, say, one mid-sized city to another typically has one carrier and one rate card to check against. A Memphis intermodal move can have a rail carrier, a drayage provider, and a terminal operator on the same shipment, each billing against a different agreement, or in some cases no written agreement at all if the drayage step was subcontracted informally. The audit question is not whether the linehaul rate matches the rate card. It usually does. The question is whether every party that touched the load between the rail ramp and the dock has a contract term that specifies its charge, and whether that charge appears once, not twice, on the combined invoice. This is not a claim about how often the error happens across shippers generally. It is a statement about the mechanism: more handoffs create more billing surfaces, and a contract audit has to cover each one by name. ## 2. Why does the rail and intermodal transfer point matter for the audit? The transfer point between rail and truck is where drayage, chassis usage, and terminal handling charges originate, and Memphis has five Class I rail connections generating that transfer traffic. A contract that names a linehaul rate but does not separately name a drayage rate table for the Memphis ramp leaves that leg unpriced in writing, which means the invoice sets the price by default. The fix is a rate table that names the ramp, not just the corridor. A rate card written for a lane, origin city to destination city, treats the move as one line. A Memphis intermodal move is at minimum two lines: the rail leg and the drayage leg from ramp to final dock. If the contract only prices the corridor, the drayage leg is priced however the carrier's invoice says it is priced, because there is no contract term to check it against. Chassis charges are a related and separate issue. The chassis that carries a container off the rail car is sometimes owned by the railroad, sometimes by a pool, and sometimes by the drayage carrier itself, and the per-diem or usage charge differs by owner. An invoice that bills a chassis fee needs a contract line that says whose chassis it is and what the fee should be. - Drayage rate table: A rate specific to the ramp-to-dock leg, separate from the linehaul rate, naming the Memphis ramp by name. - Chassis ownership clause: States who owns the chassis on a given move and what the associated usage or per-diem charge should be. - Terminal handling charge cap: A ceiling on what the terminal operator can bill for lifting a container on or off a rail car. ## 3. How does fuel surcharge pricing apply on a Memphis lane? Fuel surcharge tables are set against a published national index, and the index itself does not change by city. The Bureau of Labor Statistics Producer Price Index for gasoline, series WPU0571, stood at 302.759 in July 2026, up 37.1% year over year, read September 6, 2026. The audit question in Memphis is not whether that index moved, it is whether the contract names that specific index and whether the invoiced surcharge percentage actually reconciles to it, on both. Because a Memphis shipment often carries two fuel surcharge lines, one for the rail carrier and one for the drayage carrier, it is possible for both to be correct against their own contract and for the shipper to still be paying a surcharge twice against overlapping mileage, if the two contracts were never checked against each other. The check is mechanical: pull the fuel index named in each contract, confirm both invoices compute their surcharge percentage against that same named index and not a different one, and confirm the mileage or fuel-consumption base each surcharge is applied to does not overlap the other leg's base. ## 4. What does the current freight cost environment mean for a Memphis contract review? Per the Bureau of Labor Statistics Producer Price Index for truck transportation of freight, series WPU3012, the July 2026 index stood at 170.984, up 10.9% year over year, read September 6, 2026. The industry-specific series for long-distance truckload, PCU484121484121, stood at 195.575, up 8.1% year over year, same read date. Rising input costs raise the odds a carrier requests a rate increase mid-contract, which is exactly the moment a rate card without a Memphis-specific drayage line. A carrier renegotiation triggered by rising linehaul cost is a normal, defensible request. The risk for a Memphis shipper is procedural: if the existing contract already blended the linehaul and drayage rates into one number, a renegotiation is a chance to separate them and price each leg on its own table, this time naming the ramp. If the contract stays blended through a renegotiation, the shipper loses the one opportunity a rate change creates to fix the underlying documentation gap. The renegotiation conversation is the right moment to ask the carrier for a drayage rate specific to the Memphis ramp and a fuel surcharge clause that names the index by series, not by a general reference to 'DOE diesel prices.' ## 5. Can duplicate charges hide across a rail and drayage handoff? Yes, and the mechanism is structural rather than accidental: when a rail carrier and a drayage carrier each invoice separately for the same container move, a terminal handling fee or a fuel surcharge can appear on both invoices if the two billing systems never cross-reference the container number against the other party's charge. Checking for this requires matching container or trailer numbers across every invoice touching one shipment, not just checking each invoice against its own contract in isolation. A single-carrier truckload move has one invoice, so a duplicate charge on that move usually means the same invoice was paid twice, which standard three-way matching catches by checking the invoice number against payment history. A multi-party intermodal move through Memphis does not have one invoice number to check against. It has several, from several vendors, referencing the same container by different reference numbers on each one. Three-way matching against a purchase order does not catch this, because each invoice is a legitimate, distinct transaction against its own vendor. Catching it requires reconciling the container or trailer ID across all invoices tied to one shipment, a step outside what standard AP matching is built to do. ## 6. What should a Memphis contract specify that a generic freight contract does not? A freight contract covering Memphis lanes should name the specific rail ramp or terminal by location, price the drayage leg on its own table separate from linehaul, state chassis ownership and usage fees by name, and name the exact published fuel index series the surcharge reconciles against. A generic lane contract that prices origin to destination as one number and references fuel surcharges generically leaves every one of those items to be set by whichever invoice arrives first. The contrast is not that Memphis needs a different kind of contract. It needs the same kind of contract with more legs named in it, because the physical move has more legs. A services contract that would be complete for a two-party truckload lane is incomplete for a Memphis intermodal lane if it stops at linehaul and fuel surcharge. The additional terms, drayage rate table, chassis clause, terminal handling cap, and named fuel index, are not extra protections. They are the minimum needed to make the invoice checkable at all, because without them there is no written rate to check the drayage or terminal charge against. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. See also [the six categories drift hides in](/guides/indirect-spend-audit-categories) and [accessorial charge audit: the surcharges nobody validates](/guides/accessorial-charge-audit-the-surcharges-nobody-validates). ## Common questions ### Does the Memphis rail hub add cost to every shipment through the city? It adds billing surfaces, not necessarily cost. A well-documented drayage rate table and named fuel index can keep the added legs priced correctly. The risk is not the transfer itself, it is a contract that never separately priced it, leaving the invoice to set the rate by default. ### Is the fuel surcharge on a Memphis lane different from other US lanes? The published index, such as the Bureau of Labor Statistics series WPU0571 for gasoline, applies nationally and does not change by city. What differs in Memphis is that a shipment can carry two separate fuel surcharge lines, one per mode, so the audit has to confirm both reconcile to the index named in each contract without double-counting mileage. ### What is a drayage rate table and why does Memphis need one named separately? It is a contract schedule pricing the short truck move between a rail ramp and the final dock, separate from the long-haul rail rate. Memphis needs it named because the city is a rail-to-truck transfer point for five Class I railroads, so that leg exists on shipments where it would not exist on a single-mode lane. ### Who owns the chassis on an intermodal move through Memphis? It depends on the specific move: a railroad, a chassis pool, or the drayage carrier can each own it, and the usage or per-diem fee differs by owner. The contract should state ownership and the associated fee by name rather than leaving the invoiced carrier to bill whichever rate applies to whichever chassis showed up. ### Can three-way matching catch duplicate charges on a multi-carrier Memphis shipment? Not reliably. Three-way matching checks one invoice against one purchase order and one receipt. A Memphis intermodal move can generate several legitimate invoices from different vendors referencing the same container, so catching an overlap requires cross-referencing the container or trailer ID across all of them, a step outside standard matching. --- ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms, for $100M+ US industrial manufacturers and distributors. Two to four weeks. The client retains 100% of recoveries. https://valuexpa.com/contact-us