Start with a 90 Day Audit: Rate Con Invoice Matching for AP Teams
Freight AP guide to rate con invoice matching: run a 90 day audit, set tolerances for linehaul, FSC and accessorials, then pilot with Logivo.
Start with a 90 Day Audit: Rate Con Invoice Matching for AP Teams
Rate con invoice matching compares the carrier invoice against the rate confirmation and, where accessorials are in dispute, the bill of lading, so accounts payable teams can approve clean bills automatically and send only genuine mismatches for review. The primary fields checked are linehaul, fuel surcharge and accessorials. When those three tie out within tolerance, the invoice posts; when they don’t, it lands in an exception queue with the variance flagged. Automation platforms such as Logivo can run this comparison without manual line-by-line review, which is where the rest of this guide picks up.
TL;DR:
- Most invoice discrepancies relate to fuel surcharge errors, unauthorized accessorials, or rate mismatches, which require targeted resolution rather than generic queries.
- Automating matching with structured EDI data or OCR-enhanced PDFs can automate up to 85% of freight invoice approvals, reducing manual review significantly.
- Conducting a 90-day discrepancy audit prior to automation helps identify precise issue patterns, enabling tailored exception templates and more effective rule setting.
- Using a low-cost trial to test automation setup on a subset of lanes ensures thresholds are correctly calibrated without disrupting overall payment flow.
- Proper cause coding during dispute management improves audit trails and prevents recurring issues by capturing root causes like index errors or unauthorized charges.
Table of Contents
What documents and fields do you need before matching?
You can’t match anything reliably without three source documents in hand: the rate confirmation, the proof of delivery or bill of lading, and the carrier invoice itself. Each one carries a different job.
The rate confirmation (rate con) is the contract for that specific move. It states the agreed linehaul rate, fuel surcharge terms, accessorial allowances, equipment type, pickup and delivery windows, and the load reference number both parties will use to identify the shipment later. Treat every field on it as the baseline the invoice gets tested against.
The bill of lading (BOL) and proof of delivery (POD) prove what actually happened on the road. If a carrier bills for two hours of detention, the BOL or driver’s check-in/check-out timestamps are what substantiate it. No supporting document, no approved accessorial, according to the freight-specific matching guidance from LaneProof.
The carrier invoice is the claim you’re testing. When it arrives via EDI 210, the data comes structured and machine-readable, which makes automated field-level comparison straightforward. A PDF invoice needs OCR extraction first, and even a well-formatted layout introduces a small margin of error that structured EDI doesn’t.
Fields to capture from every document set:
- Load reference number (or PO number, if your TMS uses that convention)
- Linehaul rate and total miles or flat rate
- Fuel surcharge percentage or per-mile rate
- Accessorial line items and amounts
- Fallback identifiers: PRO number, carrier MC/DOT number, shipper reference
Fallback identifiers matter more than most teams realise. When a load reference doesn’t match cleanly, a PRO number or MC/DOT code is often what lets a human reconciler find the right rate con in seconds rather than searching manually.
Two-way, three-way or four-way: which matching depth fits the load?
Not every load needs the same scrutiny. Matching depth is a control decision, and getting it wrong in either direction costs you: too shallow and errors slip through, too deep and you slow down payment for loads that never had a problem.
-
Two-way matching compares the carrier invoice directly against the rate con only, with no BOL check. This suits high-trust contract lanes with a long track record and low accessorial activity, where speed matters more than forensic detail. A tolerance of around 1 to 2% on linehaul is typical here.
-
Three-way matching adds the BOL or POD into the comparison, which is the standard for spot loads and any move carrying accessorial charges. Detention, lumper fees and layover charges all need the third document to substantiate the amount, and this is where most freight invoice matching should sit by default.
-
Four-way matching brings in a fourth reference point, commonly a receiving confirmation or a signed accessorial approval form, reserved for high-value freight, new carriers without a payment history, or lanes with a known dispute pattern.
Most AP teams run three-way matching as their default and reserve two-way for trusted, high-volume contract carriers where the audit history justifies the lighter touch.
What does the step-by-step matching workflow actually look like?
A repeatable sequence beats ad hoc review every time, and it’s what makes exception routing work later. Here’s the order that holds up in practice.
-
Identify the load. Pull the load reference number from the invoice and locate the matching rate con. If the reference doesn’t resolve cleanly, fall back to PRO number, MC/DOT number or shipper reference before escalating.
-
Compare linehaul first. This is the largest line item and the one most tolerance rules are built around. Flag anything outside your set threshold, typically 1 to 3% depending on lane volatility.
-
Compare fuel surcharge next. Re-run the FSC calculation using the index and formula named on the rate con rather than trusting the invoiced figure at face value.
-
Compare accessorials last. Every accessorial line needs a supporting document. No BOL entry, no timestamp, no signed approval means no automatic approval.
-
Substantiate and record variance. Log the exact dollar variance and its cause code (fuel, linehaul, accessorial, duplicate) rather than a generic “mismatch” flag. This is what makes your discrepancy data usable later.
-
Raise a dispute where needed. Use a standard template with load reference, disputed amount, cause, and supporting document attached, then route it to the exception queue rather than holding the whole invoice.
-
Post and close. Approved invoices go to the ERP with the full audit trail intact, linking rate con, BOL and invoice together. Regulatory recordkeeping expectations for transportation transactions generally require exactly this kind of linked audit trail, not just a payment record.
Pro Tip: Build your dispute template once, as a fixed set of fields (load ref, amount, cause code, evidence attached, carrier contact), and reuse it for every exception. Ad hoc emails to carriers take longer to resolve and are far harder to audit six months later.
What are the most common discrepancies and how do you resolve them?
Most invoice mismatches fall into a small number of repeatable categories, and each has a specific resolution path rather than a generic “query the carrier” response.
-
Fuel surcharge errors. These usually stem from an outdated index reference or a miscalculated per-mile rate. Re-run the FSC formula from the rate con against the DOE index for the invoice date, and send the carrier the recalculated figure alongside the disputed one rather than just flagging it as wrong.
-
Unauthorized accessorials. Detention, lumper and layover charges without a matching BOL entry, timestamp or signed approval should be held, not paid provisionally. Ask for the specific supporting document by name rather than a vague “please justify this charge.”
-
Linehaul mismatches. Usually a rate entry error or an unapproved lane change. Quantify the exact variance in dollars, not percentage, when you raise it. Carriers respond faster to a precise number.
-
Duplicate invoices. Cross-check load reference and invoice date against your payment history before assuming it’s new. Hold the second submission rather than paying and clawing back later.
-
Load reference mismatches. Place an immediate hold and switch to a secondary key (PRO number or MC/DOT) to locate the correct rate con before escalating to the carrier.
Automated matching engines resolve roughly 78 to 85% of freight invoices straight through without human intervention, leaving the remaining minority for exception review. That’s a meaningful shift from manual processing, where every invoice gets the same level of scrutiny regardless of risk, and genuine discrepancies are far more likely to be missed in the volume.
How do OCR, EDI and TMS integration reduce manual matching work?
The technical layer behind automated matching isn’t complicated in concept: capture the data, compare it against a set of rules, and route what fails. The execution detail is where implementations succeed or stall.
EDI 210 versus PDF and OCR. Where a carrier supports EDI 210, use it. Structured data removes the extraction step entirely. Where you’re stuck with PDF invoices, OCR accuracy on standard freight layouts runs 94 to 98% on modern document-processing benchmarks, which is workable but still needs a validation pass on the fields that drive payment decisions.
Mapping rate-con fields into the matching engine. Your TMS is the source of truth for linehaul, FSC terms and accessorial allowances. Mapping those fields into a matching engine typically takes a few weeks for a mid-sized fleet, not months, provided your rate con data is entered consistently at booking.
Setting tolerances. Configure thresholds so automation approves genuine matches and escalates real exceptions, not every trivial rounding difference. A 1 to 2% tolerance on linehaul and a tighter band on FSC is a reasonable starting point, adjusted after your first audit cycle.
Integration endpoints that matter:
- AP/ERP write-back for approved invoices and audit trail
- TMS API for live rate con and load data
- Document repository for BOL/POD storage and retrieval
- Carrier communication channel for dispute routing
Automation genuinely speeds up matching and reduces error rates, but the vendors closest to freight operations are consistent on one point: don’t let a matching engine replace the human relationship management that keeps carrier disputes from becoming carrier churn, as FreightWaves notes on digital freight matching.
How do you actually implement this without disrupting payments?
Rolling out rate con invoice matching works best as a staged process, not a single cutover. Skipping the audit step is the single most common reason implementations underperform their own targets.
- Run a 90-day discrepancy audit first. Pull every invoice from the last quarter and categorise mismatches by type and dollar value. This alone usually shows that linehaul, FSC and accessorials account for the bulk of your exceptions, which tells you exactly where to focus automation rules.
- Configure your top three exception templates based on what the audit surfaces, rather than building generic templates for every theoretical discrepancy type.
- Pilot on a defined subset of lanes or carriers before rolling out fleet-wide, tracking match rate, time saved per invoice, and cost recovered against disputed amounts.
- Maintain governance and an audit trail that links rate con, BOL and invoice for every transaction, satisfying recordkeeping obligations and giving you a clean trail if a carrier disputes a chargeback.
| Metric |
What it tells you |
| Straight-through match rate |
Percentage of invoices approved with no human touch |
| Exception volume |
Number of invoices requiring manual review per period |
| Time saved per invoice |
Reduction in AP processing minutes versus manual matching |
| Cost recovered |
Dollar value of disputed charges successfully clawed back or avoided |
How does Logivo handle rate con invoice matching in practice?
Logivo’s transport management platform builds this matching logic directly into its invoicing workflow rather than treating it as a bolt-on report. It extracts rate con, BOL and carrier invoice data through AI-driven capture, applies configurable tolerance rules across linehaul, FSC and accessorials, and routes anything outside those thresholds into an exception queue for review rather than blind approval.
- AI-assisted document extraction across rate cons, PODs and invoices
- Configurable tolerance and exception routing rules
- TMS and accounting integration for AP write-back
- Role-based access and a security architecture built for financial data
Firms running Logivo have reported clearer operational visibility and fewer invoicing errors, detailed in a transport invoicing efficiency case study. The platform’s free one-month guided trial gives AP teams a low-risk way to test their own tolerance rules and matching templates against real invoice volume before committing to a full rollout.
What should you do first?
Start narrow. Run the 90-day audit before you touch automation software, because it tells you which three fields actually drive your discrepancies rather than guessing.
- Run the 90-day discrepancy audit and categorise every mismatch by type and dollar amount
- Build your top three exception templates from what that audit actually shows
- Start a scoped pilot on a subset of lanes with your TMS connected, tracking match rate and time saved per invoice
Track four numbers through the pilot: match rate, exception volume, dispute resolution time and cost recovered. If match rate climbs and exception volume shrinks over the first few weeks, you’ve built the right rules. If it doesn’t, the audit data will tell you which field needs a tighter or looser tolerance before you scale it fleet-wide.
Where can you read more on this?
For the technical mechanics of two-way and three-way matching, the Microsoft Dynamics accounts payable documentation covers price, unit and charge matching in detail. For freight-specific implementation steps and OCR benchmarks, see the freight invoice reconciliation guide and Rillion’s overview of automated matching stages.
Why most AP teams get the rollout order backwards
The conventional advice treats automation as the starting point: buy a tool, connect the TMS, switch on matching. That order is backwards. The audit should come first, always, because it tells you where your money is actually leaking before you build a single rule.
What’s underrated here is the discipline of cause coding. Most teams log a mismatch as “resolved” once the carrier agrees to a credit, without ever recording whether it was a fuel surcharge index error, an unauthorised accessorial, or a duplicate. Six months later, they’re solving the same three problems from scratch because nobody kept the pattern data.
The gap between what automation promises and what it delivers is smaller than sceptics claim, but it’s not zero. A matching engine will catch what the rules tell it to catch. If your tolerance thresholds are set from guesswork rather than your own discrepancy history, you’ll either approve bad invoices or flood your exception queue with noise. Get the audit right first. Everything downstream, including the freight matching tolerance settings, depends on it.
— Vytautas
Put rate con matching on autopilot with Logivo
Logivo replaces manual, line-by-line invoice checking with automated rate con reconciliation built into a single transport management platform, so linehaul, FSC and accessorial checks happen without an AP clerk opening three separate documents for every load.
Where a spreadsheet-based process leaves you re-keying rate con data and chasing PODs by email, Logivo pulls that data automatically through AI-driven extraction and applies your own tolerance rules to route only genuine exceptions for review. It also connects directly to your driver app for live proof-of-delivery tracking, so accessorial disputes have the evidence attached before the invoice even lands. If you’re managing courier or distribution freight specifically, the platform’s courier and distribution transport software configuration handles the higher accessorial volume typical of that segment.
For fleets building out claims and evidence workflows around accessorial disputes, TruckPlant’s guide to claim process workflows is a useful companion reference.
The free 30-day guided trial lets you test your own matching rules against real invoice data before you pay for anything. Start by exploring Logivo’s transport management software and see how your current discrepancy rate compares once matching runs automatically.
Sources
FAQ
What does invoice matching mean in freight?
It means comparing the carrier invoice against the rate confirmation and, where accessorials are involved, the bill of lading, to confirm the billed amount matches what was agreed before payment is approved.
What is an example of a three-way match?
A carrier invoices an amount for a load; the AP team checks that figure against the rate con’s agreed linehaul and FSC, then checks the BOL to confirm any detention or lumper charges actually occurred before approving payment.
How does two-way invoice matching work?
Two-way matching compares only the carrier invoice against the rate confirmation, with no BOL check, and suits trusted contract lanes with low accessorial activity and a strong payment history.
How do you handle a rate mismatch between the rate con and the invoice?
Hold the invoice, quantify the exact dollar variance, and query the carrier with the specific line item and amount rather than a general dispute; platforms like Logivo route this automatically to an exception queue with the variance already flagged.
Recommended