Disputing a Carrier Invoice

A freight invoice audit doesn't end with the finding:

„This invoice is wrong.“

That's where the next question begins:

What exactly was calculated incorrectly – and can the deviation be documented in a way that is traceable for the carrier?

For that, the following must be clear:

• Which shipment is affected?
• Which invoice line item deviates?
• What was charged according to the invoice?
• What should have been charged according to the agreed tariff?
• How large is the difference?
• Does the same deviation affect other shipments?

ShipCheck checks invoice line items against stored rates, surcharges, and terms, and detects and categorises deviations.

This creates the basis for a documented claim:

Tariff → target cost → invoice → deviation → affected shipments → claim

The specific process after submitting a claim – such as communication, approval, or credit notes – can differ depending on the company and carrier. What matters initially is that the claim can be traced back to the underlying transport and tariff data.

1. A claim starts with a concrete deviation

A statement such as:

„The invoice is too high.“

is not yet a solid basis for a claim.

First, it must be clear which invoice line item deviates from which agreed tariff logic.

Typical deviations can, for example, involve:

• Weight brackets
• Zones
• Discounts
• Surcharges
• Ancillary services
• Duplicate or incorrect line items

ShipCheck checks individual invoice line items against the stored tariff logic and categorises the deviations found.

This makes it possible to ask the relevant question more precisely:

What was invoiced – and what should have been invoiced according to the agreed tariff?

2. Target cost and actual cost form the basis

The core of freight invoice auditing is the target-actual comparison.

Actual cost

This is the cost actually invoiced.

Target cost

This is the cost that results from the agreed rates and terms for the specific shipment.

Depending on the tariff, the following may be relevant, for example:

• Lane or zone
• Weight
• Base rate
• Fuel surcharge rule
• Tolls
• Discount
• Ancillary service

This makes it possible to calculate, for a specific shipment:

What should this shipment have cost under the agreed terms?

Only then can the invoiced amount be meaningfully checked against it.

The logic is:

• Shipment data + tariff rules = target cost
• Invoice line items = actual cost
• Target vs. actual = possible deviation

This is precisely why the structured digitisation of freight tariffs is a prerequisite for automated freight invoice auditing.

3. From the difference to a traceable justification

A pure difference amount is not enough for a claim.

Assume:

• Invoiced amount: €1,240
• Calculated target cost: €1,160
• Difference: €80

The €80 shows the financial deviation.

What matters, however, is why this difference arose.

A traceable audit therefore combines:

• affected shipment
• affected invoice line item
• tariff basis applied
• calculated target cost
• invoiced amount
• difference

This turns:

„You overcharged us by €80.“

into a verifiable statement:

„For this shipment, the invoiced line item deviates from the cost that results from the agreed tariff logic.“

That is the actual basis of a documented claim.

4. The individual shipment and invoice line item are the level of evidence

Aggregated evaluations are very useful for freight cost reporting.

For a tariff-related claim, however, the deviation must be traceable back to specific cases.

Assume an analysis shows:

„Carrier A has a total of €18,000 in deviations.“

Then it must be traceable:

• Which shipments are affected?
• Which invoice line items cause the difference?
• Which tariff rule applies in each case?

ShipCheck checks deviations at the invoice line item level and links them to the underlying shipment and transport data.

The total claim therefore doesn't arise from a flat difference.

It arises from traceable individual deviations.

5. After the first error: isolated case or pattern?

A detected deviation shouldn't automatically be viewed in isolation.

If the same tariff logic was applied to many shipments, the next question is:

Does the error occur there too?

A small error can become financially significant if it recurs systematically.

That's why, after finding a deviation, you should check:

Isolated case or recurring pattern?

ShipCheck supports the detection and categorisation of deviations at the invoice line item level. This can make identical or recurring errors visible across multiple shipments.

The decisive step is therefore:

Not only checking the invoice that was found, but quantifying the scope of the deviation.

We cover this aspect in more detail in the article „Detecting systematic errors in carrier invoices: why small deviations become expensive“.

6. Structuring deviations by error type and financial impact

If there are multiple deviations, you shouldn't just look at a total sum.

It makes sense to structure them by:

• error type
• affected shipments
• frequency
• financial difference

This makes visible, for example:

• Deviation A: frequent, small difference per shipment, high total amount
• Deviation B: one-off, larger individual difference

This categorisation helps to better assess the economic significance of each error.

A small systematic error can be more relevant than one large isolated case.

7. From tariff deviation to documented claim

This results in a clear audit process.

Step 1: Structure the tariff basis

The agreed terms must be available in a form that allows the target cost for a shipment to be calculated.

Step 2: Match invoice and shipment

The invoiced line items are linked with the relevant transport data.

Step 3: Calculate target cost

The agreed tariff logic is applied to the specific shipment.

Step 4: Compare target and actual

Invoiced costs and tariff-calculated costs are compared.

Step 5: Categorise the deviation

It becomes clear which tariff or cost logic is causing the difference.

Step 6: Identify further affected shipments

For recurring logic, it is checked whether the same deviation also occurs in other cases.

Step 7: Document the deviations

Affected shipments, invoice line items, tariff basis, target cost, actual cost, and differences form the basis of the claim.

This turns a noticeable invoice into a traceable basis for a claim.

8. Why a solid tariff basis is decisive

An automatically detected difference is only as good as the underlying data.

Before filing an actual claim, it must therefore be ensured that:

• the relevant tariff basis is correctly stored,
• the shipment data is accurate,
• the surcharge logic has been correctly represented,
• the correct terms have been applied.

That's why ShipCheck combines automated processing with a structured representation of the agreed tariff logic.

A detected difference initially means:

The invoice and the stored tariff calculation do not match.

The documented claim then makes it traceable what this deviation is based on.

9. Why sampling doesn't show the scope of an error

Many invoice errors are discovered by chance.

• An invoice stands out.
• The specific line item is checked.
• The error is found.

At this point, the company initially only knows:

This one invoice line item is conspicuous.

If the cause stems from a recurring tariff logic, the more important question is:

How many other invoice line items are affected?

This is precisely why systematic auditing of larger volumes of invoices and shipments matters.

From:

„We found an error.“

comes:

„We can quantify which shipments show the same deviation and what financial difference results from it.“

For a documented claim, this distinction is essential.

10. A cost increase and a disputable deviation are not the same thing

Not every cost increase can be disputed.

Assume: the fuel surcharge share rises significantly.

Freight cost reporting initially just shows a cost driver – why freight costs are rising is a separate analytical question.

For a tariff-related claim, it must additionally be checked:

Was the fuel surcharge calculated according to the agreed rule?

If so, the amount may be high yet still contractually correct.

That's why two questions must be distinguished:

• Freight cost analysis: where are our costs changing?
• Freight invoice auditing: does the invoicing match the agreed tariff?

Only a tariff deviation creates the basis for a claim.

11. An unfavourable tariff is also not automatically disputable

The same applies to a tariff's market attractiveness.

An invoice can be fully compliant with the contract even though the agreed terms are unfavourable relative to the current market.

That's why three questions differ:

• Analysis: what are we paying?
• Audit: was the contract applied correctly?
• Benchmarking: are our terms competitive?

As freight cost management software, ShipCheck addresses the analysis of your own transport costs and contractual invoice auditing.

External market assessment, within the current ShipCheck/HDS structure, belongs to the consulting or benchmarking context.

For a claim, what matters is therefore not:

„This price is too high.“

But rather:

„This invoiced amount does not correspond to the agreed tariff logic.“

How ShipCheck supports the process

ShipCheck connects several steps of freight invoice auditing.

Freight tariffs are made calculable

The agreed terms form the target side of the audit.

Invoice line items are checked

The actual invoicing is checked against rates, surcharges, and terms.

Deviations are detected and categorised

This makes it visible where target and actual costs diverge and what type of deviation is involved.

Affected shipments can be quantified

This allows checking whether an error is isolated or recurring, and what financial impact results from it.

The deviations form the basis for claims and recovery

The existing ShipCheck materials support claim and recovery workflows.

The specific organisational process after handing over the claim – for example, communication with the carrier, approval, rejection, or credit note – can differ depending on the carrier and the company.

The solid ShipCheck core therefore doesn't end at:

„We found something unusual.“

But rather at a structured, quantified, and traceable deviation that can be pursued further.

Conclusion: A claim needs a traceable target-actual chain

Disputing a carrier invoice shouldn't mean:

„This amount seems too high to us.“

The solid basis is:

• Which shipment is affected?
• Which invoice line item was charged?
• Which tariff basis applies?
• What target cost results from it?
• How high is the actual cost?
• How large is the difference?
• Does the same deviation affect other shipments?

ShipCheck supports this with line-item-based freight invoice auditing against stored rates and terms, as well as the categorisation and quantification of deviations found.

This turns:

„Something here doesn't add up.“

into a traceable chain:

Tariff → target cost → invoice → deviation → affected shipments → documented claim

And this is precisely the difference between merely finding an invoice error and a deviation that can be pursued economically.