EDI 210 Invoice Matching in Your TMS, Step by Step

Configure EDI 210 inbound mapping and three-way match rules in your TMS so carrier invoices auto-reconcile against BOL and POD before payment.

Share

If your accounts payable team is still keying freight invoices off a PDF while your TMS sits there holding the load tender and the signed BOL, you're paying twice: once in labor, once in whatever the carrier decided to bill you. EDI 210 invoice matching fixes that, but only if you configure the inbound mapping and the three-way match logic correctly inside your TMS. This walkthrough covers the actual segments, fields, and failure points you'll hit doing it.

What You Need Before You Start

You need four things in place before you open your TMS's EDI mapping screen. Skip any of these and you'll spend your first week debugging instead of configuring.

  • An active EDI/AS2 or VAN connection already receiving inbound 210 transactions from at least one carrier, even if they're currently landing as unmapped data.
  • A documented reference-number standard (PRO, BOL, or PO) that's already enforced in your tender and dispatch workflow, not just written down somewhere.
  • Access to your TMS's EDI mapping or translator screen, not just the user-facing invoice UI. If your admin login only gets you the UI, go find whoever owns the integration layer.
  • A sandbox or test trading partner so you can push sample 210s without touching production invoice queues.
  • A GL coding sheet or cost-center table, if any of your loads carry freight for more than one business unit.

Step 1: Confirm the Inbound 210 Structure Your Carrier Sends

Every 210 follows the same skeleton, but carriers fill it in differently. Pull the implementation guide from the specific carrier before you map anything blind.

  1. Check the ST (Transaction Set Header) and confirm the transaction set identifier your translator expects matches what the carrier sends.
  2. Review the B3 segment (Beginning Segment for Carrier's Invoice). This segment is optional, used once, and specifies the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items at the summary level, but the field you actually care about here is B307, the Net Amount Due. B307 carries the total charges due for the invoice.
  3. Pull every N9 (Reference Identification) loop and note which qualifier codes the carrier actually populates, PRO, BOL, or PO. Don't assume; carriers mix and skip these constantly.
  4. Check the L3 (Total Weight and Charges) segment. L305 is the total charges for the invoice, and it needs to tie back to B307. If a carrier's L3 segment is populated but doesn't equal B307, your mapping should flag it immediately, not pass it through.
  5. Confirm the SE trailer count matches the segments actually transmitted. Mismatches here usually mean a dropped loop somewhere upstream.

Grab the FedEx 210 implementation guide if you want a real-world reference; C.H. Robinson and Ryder publish similar public specs, and most asset carriers will hand you theirs on request. Build your mapping against the actual guide, not a generic 210 template, because every carrier flexes the optional segments differently.

Step 2: Build the Reference-Number Crosswalk

This is where most 210 projects quietly fail six months after go-live. Map each N9 qualifier to your TMS's internal shipment ID field now, before invoices start flowing.

  1. List every reference qualifier your top carriers actually send in production (not what the spec allows, what they send).
  2. Map PRO numbers to your TMS's carrier-tracking field, BOL numbers to your shipment document field, and PO numbers to your order field, one mapping table per carrier if formats differ.
  3. Set a primary match key and a secondary fallback key in the mapping logic.

The audit logic matches an invoice to a load using reference numbers: load ID, PRO number, BOL number, or PO number, and the single biggest failure mode is a format mismatch. If your TMS uses a load ID format and the carrier's invoice references a PRO number instead, your matching engine needs a cross-reference table or a secondary matching field or every invoice from that carrier lands in your exception queue. Fix it two ways: enforce one reference format in your carrier routing guide at tender time, and build a fallback match on pickup date, lane, and total weight for the invoices that still don't hit on reference number alone.

Step 3: Set Tolerance Thresholds by Charge Type

Don't use one blanket tolerance for the whole invoice. Linehaul charges and accessorials behave differently, and lumping them together either auto-approves bad accessorial billing or kicks every clean linehaul invoice into manual review.

Charge TypeSuggested ToleranceWhy
Linehaul±2%Rounding and fuel index timing differences are common and usually immaterial
Fuel surcharge±1%Index-based, should match closely if your rate table is current
Accessorials (detention, liftgate, residential)±$10 flatPercentage tolerances don't work well on small flat fees
Hazmat$0 variance, manual reviewFlat regulatory fee, any deviation usually signals a coding error

The three-way match is the standard in freight financial control, and when configured well it turns most freight payments into a touchless process. When the purchase order, the bill of lading, and the carrier invoice align within your predefined tolerances, payment gets auto-approved, and anything outside that band routes to exception review instead of sitting in an AP inbox.

Step 4: Configure GL Coding for Mixed Loads

If one truck carries freight for two business units, your invoice matching logic needs to split the charge before it ever reaches the GL, not after finance notices the number is wrong at month-end.

For mixed loads, advanced integrations split costs at the line-item level using BOL data, which automates what is usually a manual month-end reconciliation headache. In practice that means configuring your mapping so the rules engine splits GL codes at the line-item level based on the weight or unit count attributed to each cost center on the BOL, not an even 50/50 split that nobody actually agreed to.

Step 5: Build the Exception Queue and Routing Rules

Every invoice that doesn't clear the match goes somewhere specific, with someone specific owning it. Vague "send to AP" rules are how invoices sit for three weeks.

  1. Auto-hold on missing POD, missing reference number, duplicate invoice number, or rate mismatch beyond tolerance.
  2. Route reference-number failures and rate disputes to transportation ops, not AP. They know the lane, the carrier, and the tender history.
  3. Route coding and GL split exceptions to AP or finance, since they own the chart of accounts.
  4. Set a 48-hour SLA for first-touch on any held invoice. Anything older than 10 business days should escalate automatically.

Step 6: Test With a Live Batch Before Go-Live

Don't flip the switch on full volume. Run a real batch through the new mapping in parallel with your existing manual process for one billing cycle. Export 50 to 100 load records from your TMS and run them through the matching engine before you trust it with everything.

You'll know it worked when your first-pass match rate, touchless processing rate, and invoice exception rate all move in the right direction, the same metrics freight invoice processing programs track for accuracy and automation. Target a touchless rate in the 80-90% range, zero duplicate payments in the test batch, and a measurable drop in AP cycle time before you cut over fully.

Failure Mode: When the Reference Crosswalk Breaks Mid-Flow

Your match rate was fine for eight months, then it dropped 15 points in a week. Nine times out of ten, a carrier changed how they invoice, swapping a PRO number format or switching billing systems entirely, and nobody told you.

The fix isn't heroic manual review. Add the pickup-date, lane, and weight fallback match from Step 2 so these invoices don't all pile into the exception queue at once, then set an alert that fires when unmatched invoice volume from a single carrier crosses a daily threshold. That alert is your early warning the crosswalk needs an update, not a wall of PDFs AP has to chase down manually.

Tool Landscape Note

How much of this you configure natively versus bolt on with a separate audit module depends entirely on your platform. Confirm this before you scope the project, not after.

PlatformNative 210 Inbound MappingTypical Approach
MercuryGateYesBuilt-in EDI translator with configurable field mapping
DescartesYesNative mapping plus optional audit add-on
Blue YonderPartialOften paired with a separate freight audit module
Oracle TMYesConfigurable via integration layer, heavier setup lift
SAP TMPartialUsually integrated with SAP's broader invoice verification flow
e2open/BluJayYesNative mapping with carrier-specific implementation guides
AlpegaPartialVaries by module and region
3GtmsYesNative EDI configuration screens
CargosonPartialMulti-carrier platform, check current carrier-integration scope

If you're evaluating a multi-carrier platform like Cargoson alongside the larger enterprise TMS players, ask specifically about inbound 210 mapping and reference-number crosswalk support, not just "do you handle EDI."

What to Do Next

Start with Step 1 this week: pull the actual 210 implementation guide from your highest-volume carrier and compare it segment by segment against what your TMS currently maps. You'll likely find at least one N9 qualifier getting dropped on the floor. Fix that crosswalk before you touch tolerance thresholds, because no tolerance setting saves a match that never had the right reference number to begin with.