Does freight invoice auditing software need an ERP integration?

Not necessarily. Many tools read PDFs, e-invoices and portal exports directly and match them to shipment records supplied as files, with the ERP taking only the approved result.

What is the difference between audit software and an outsourced freight audit service?

Software checks the invoices inside your own process, so your team sees each flag and keeps the contract knowledge. An outsourced service typically runs some or all of the audit and dispute work on your behalf, and depending on the provider may charge a fixed fee, a fee per invoice or a share of the amounts recovered.

What should the software do with a duplicate line?

It should match each line against previously billed lines by shipment reference, date and amount, across invoice numbers, and flag a repeat as grounds for a claim rather than as an overcharge. Whether the carrier owes a credit depends on the contract terms and on what the carrier's own records show.

Freight Invoice Auditing Software: What to Look For

Eight criteria a controller can test before choosing, and how four ways of checking carrier invoices usually compare.

Comparison · 6 min · Alexandre de Perregaux, CEO, Intellyse · Published October 9, 2026 · Last updated October 9, 2026

By Intellyse, makers of freight invoice audit software · About us

ShareLinkedIn X Email

A hand rests on a laptop showing tables of figures and bar charts, next to two labelled shipping parcels on a wooden table — Photo: Kampus Production on Pexels

Key takeaways

Freight invoice auditing software is judged on what it checks inside each invoice line and what it can show for a flag, not on how many invoices it ingests.
Manual checking, rule-based tools, AI-based platforms and outsourced audit services typically differ in who keeps the rates current and how a flag is evidenced; the table below sets out typical differences.
A two-week test on 100 of your own invoices, with the outcome of every flag recorded, tells a controller more than a demo.

Many freight controllers check carrier invoices the same way: the total against the quote or the order, a scan of the largest lines, then approval. That catches a wrong total and an invoice for a shipment nobody ordered. It misses what sits inside the line: a surcharge on the wrong basis, a rate from an expired validity period, a shipment billed twice under two references. Freight invoice auditing software exists to do that line-level work, and the useful question before signing is what to require of it.

What should freight invoice software check on each line?

Freight invoice software should confirm, for every line, that the shipment exists in your records, that the rate matches the contract valid on the shipment date, that each surcharge uses the basis the contract states, that the billed charges are consistent with the applicable Incoterm and shipment terms, and that the line has not been billed before. A carrier invoice check that stops at the header total is not an audit.

1. The inputs it accepts. Carrier invoices arrive as PDF, e-invoice, portal export and spreadsheet, and the tool should read all of them without a project. It should also work without an ERP integration, because many controllers cannot get IT time for one; our post on freight invoice reconciliation without ERP integration covers what a file-based setup needs.

2. What it checks per line. The minimum is shipment existence, contracted base rate, surcharge basis, consistency with the Incoterm and shipment terms, and duplicates across invoice numbers. The US General Services Administration sets the same core steps for federal freight bills: compare the invoice to the bill of lading, verify rates and charges, and confirm the service was performed (GSA, transportation invoice audit, updated 11 May 2026). Accessorial charges, which the Intermodal Association of North America's glossary defines as charges for services connected with the move such as loading, unloading, storage, pick-up and delivery, are often where differences hide, so ask how they are matched to the contract and to shipment evidence.

3. How it handles rates and contracts. A rate card typically holds rates with their validity dates, while the wider contract can add surcharge tables, minimums and other pricing rules; a shipment on 3 March should be checked against the terms that applied on 3 March. The tool should hold several versions per carrier, keep surcharge tables separate from base rates, and read several carriers' layouts; ask how a new layout is added and by whom.

4. What a flag looks like. A flag you cannot trace to a clause, a rate line or a shipment record is an opinion, and controllers do not dispute invoices on opinions. Each flag should show the invoice line, the rate or clause it was compared with, the shipment record and the difference. An invoice line is evidence, not proof: a duty line suggests DDP was applied, but whether it was payable depends on the contract terms, any tariff incorporated into it and the governing law, so the flag should say what to check. The tool should also report separately the charges it could not check because the contract, rate or shipment data was missing, rather than treating every unmatched line as an overcharge.

Header-level checking does not produce that. In the invoices we audited from March to August 2026, more than 318,000 freight and surcharge lines, line-level checks found 5.1 percent of spend invoiced above the negotiated price, and 29.9 percent of audited spend had no reference price available for comparison. The invoice total alone shows neither: a total can be the correct sum of charges priced on the wrong rate or basis, which is why the check has to happen per line.

What happens after freight invoice validation software flags a line?

Once freight invoice validation software raises a flag, someone has to decide, dispute and track the result, and the tool should carry that work rather than hand it back to a spreadsheet.

5. What happens after a flag. There should be an approval step where a controller accepts or rejects the flag, a dispute record with the claim sent to the carrier, and a credit note linked back to the claim and the shipment. Every decision should leave an audit trail; ask what happens when the carrier answers with a partial credit note.

6. Reporting. This is where freight invoice analytics software overlaps with auditing: cost per shipment, cost by lane and by carrier, and the share of surcharges in total spend. Ask whether reports separate billed, approved, disputed and recovered amounts, so the effect of disputes is visible rather than hidden in one spend figure.

7. Effort to start and who owns it. Ask how many hours your team spends before the first checked invoice, and whether logistics or finance owns the tool afterwards. Freight invoice automation that only captures data leaves the checking with the same people as before.

8. Pricing model. Models vary: per shipment, per invoice, per module, a yearly licence, or a share of amounts recovered. Ask what the price does when volume doubles and when a quarter produces no flags.

How does freight audit software compare with manual checking and outsourced services?

Freight audit software sits between a controller with a spreadsheet and an outsourced service that takes the invoices away and returns findings. Software itself splits into rule-based tools, which check what someone has written a rule for, and AI-based platforms, which can need less manual mapping or rule configuration when they interpret different invoice layouts and match charges to supporting data. The table shows typical differences; a given supplier can differ from its column, and the criteria are the same whether the search is in English or for Frachtrechnungsprüfung Software.

Criterion	Manual spreadsheet	Rule-based tool	AI-based platform	Outsourced service
Inputs	Usually whatever a person can open; re-keying is common	Depends on the formats and integrations configured	Often built for varied formats such as PDF, e-invoice and exports; can run without ERP integration	The provider defines the intake process
Checks per line	Usually header total and a sample of lines	Usually the lines a rule exists for; new charge types can be missed	Designed to review every line, subject to the source data and configured coverage	Usually every line, on the provider's checklist
Rates and contracts	Usually the current table; old validity periods are often lost	Usually versioned tables maintained by the client	Usually versioned tables; can read contract documents, with client confirmation	Usually maintained by the provider
What a flag looks like	Usually a note in a cell	Usually the rule that fired and the difference	Usually line, clause or rate, and shipment record; can include a draft claim	Usually a findings report; source detail can be on request
After the flag	Usually email to the carrier, tracked by hand	Usually an approval step; dispute tracking can be separate	Usually approval, dispute and credit note in one record	Usually the provider files the claim
Reporting	Usually a pivot table when someone has time	Usually fixed reports	Usually cost per shipment and by lane from checked lines	Usually a periodic provider report
Effort and owner	Usually low to start; the check can stop when the controller is away	Usually weeks to months of rule setup; client owns the rules	Usually days to weeks; client owns rate confirmation and decisions	Lower operational effort for the client; some audit knowledge and process ownership stays with the provider
Pricing model	Staff time	Usually per module or yearly licence	Usually per shipment, per module or yearly licence	Usually a share of recoveries or a fee per invoice

Why do evaluations pick the wrong tool?

A common evaluation mistake is to measure invoices processed per hour rather than the quality and outcome of the flags produced. A demo of freight auditing software may run on a relatively clean invoice, and the buyer's hardest layout, the one with three surcharge tables and a validity change mid-quarter, is never in the room. Often nobody has decided whether logistics or finance owns the flags, so the tool that wins is the one that asks least of either.

How do you test freight invoice auditing software in two weeks?

Run every shortlisted tool, and the outsourced service if one is in the running, on the same 100 invoices, and score the outcome of each flag rather than the count. Using the same sample for every supplier compares detection, evidence and setup effort rather than different datasets, and two weeks can be enough for a first comparison if invoices, shipment data and contracts are ready on day one.

The two-week test

Tick a step to reveal the next

Pick 100 invoices from the last quarter, across at least two carriers and two modes, including the layout your team finds hardest.
Hand over contracts and rate tables as they are, with validity dates. The cleaning effort is part of what you are measuring.
Require every flag to show its source: the clause, rate line or shipment record it was compared with.
Have your team resolve 20 flags by hand and record each as grounds for a claim, a gap in your own data, or a false flag.
Time the setup hours on both sides, and ask each supplier for its pricing model against your annual volume in the same week.

Step 1 of 5

Intellyse can be tested against the same eight criteria: it reads invoices in the layouts carriers send, checks every line against the contracted rate and surcharge basis, shows the source of each flag, and carries approval, dispute and credit note through to settlement, with cost by shipment and lane reported from checked lines. It works across ocean, air, parcel and road from the files you already receive. The freight audit platform page describes the modules and how a client starts.

FAQ

Sources