Two people working on laptops in a busy office
Thought leadership · Logistics

Per load profitability lives outside the ledger

The transport system knows what each load earned and cost. The ledger knows what the month earned and cost. Neither can reconcile to the other.

Key Takeaways
  • Transport management systems calculate load level revenue and cost, and the general ledger records financial totals.
  • The two rarely reconcile, because the operational system uses estimates and the ledger uses invoices and accruals.
  • That gap means load profitability reporting and financial reporting can tell different stories about the same month.
  • The reconciliation is worth building, because it validates the operational data everyone is already using to make pricing decisions.
  • Driver and carrier settlement is usually the largest reconciling item and the most sensitive one.

Ask a carrier or a broker which lanes are profitable and you will get an answer from the transport system, at load level, with margin per load.

Ask the finance function what the month's gross margin was and you will get an answer from the ledger, which does not agree with the sum of the load level margins.

Both numbers are used. One drives pricing and lane decisions, the other is reported to lenders and owners, and nobody reconciles them because it has never been anyone's job. When they are quoted in the same meeting the difference is usually explained as a timing effect, which is true and is not the whole answer.

TransportProfitabilitySystemsReconciliationReporting
01

Why the two numbers differ

The operational system calculates margin when the load is planned or delivered, using rated revenue and estimated cost, including a purchased transport rate agreed at booking. Those inputs are the best available at the time and they are estimates, which means the operational margin is a planning number presented with the precision of an actual one.

The ledger records revenue when it is invoiced and cost when the carrier or driver settlement is processed, which happens later and often at a different amount.

Accessorials are the largest single cause of divergence, because they arise after the load was priced and are frequently unverified before payment, as freight invoices nobody matches describes, as accessorials without a purchase order describes.

Add fuel adjustments, claims, detention and rebilling, and the difference becomes structural rather than occasional. Several of those arise from the operational events described in a close that starts before the period ends, which means the same underlying data fixes both the verification problem and the margin one.

Colleagues working together on financial documents
One system prices the load, another records the money.
02

Four reconciling items to expect

These four account for most of the difference in the operations we see, and each has a different owner.

Carrier and driver settlement differences: Agreed rates against settled amounts, including deductions, advances and adjustments, which is usually the largest item.
Accessorials billed and incurred: Charges added after the load was priced, on both the revenue and cost side, which rarely net out.
Cut off: Loads in transit at period end, where revenue and cost recognition depend on the point of transfer rather than on the operational status.
Claims and adjustments: Damage, shortage and service failure credits, which appear in the ledger and often not in load level margin, distorting master data as the automation project as well.
03

Why the reconciliation is worth building

The operational margin is the number used to make commercial decisions: which lanes to pursue, which customers to price up, which carriers to use.

If it is systematically optimistic, every one of those decisions inherits the bias, and the error is invisible because the ledger is reported separately and explained separately.

A reconciliation does not require the two systems to agree. It requires the difference to be understood, categorised and stable.

Once it is, the operational number can be used with a known adjustment, which is far more useful than either treating it as accurate or dismissing it.


The operational margin sets prices. Nobody checks it against the money.
04

Building the bridge

A monthly bridge with a small number of categories, which is a report rather than a project.

Bridge lineSourceFrequency of movement
Operational marginTransport system, summed for the period.The starting point.
Settlement differencesLedger settlement records against operational rates.Every period, and it should be stable in proportion.
Accessorials and adjustmentsLedger, by charge category.Volatile, and it is the line that indicates whether operations is pricing accurately.

Revenue and cost recognition for transport services depend on the applicable framework and the terms of carriage. Confirm cut off and recognition policies with your auditors.

"

Two systems, two margins, and one of them is used to set prices.

ChatFin
05

Making the bridge routine

The objective is a stable monthly bridge with a small number of explained categories.

Agree the categories once

Four or five reconciling categories, defined, so the bridge is comparable month to month rather than reinvented.

Extract both sides on the same cut off

Operational and financial data for the same period boundary, which is where half the apparent differences come from.

Explain the movement, not the balance

A stable difference is informative. A moving one is the thing to investigate, which is the same logic as flux analysis.

Feed the adjustment back to pricing

So the operational margin used in commercial decisions carries a known correction rather than an unknown bias.

A finance professional counting notes in an office
A stable difference is information. A moving one is the thing to investigate.
06

Two ways carriers organise this

The difference decides whether the two numbers ever converge.

Pattern

Two separate truths

Operations reports load margin, finance reports gross margin, and both are presented to the same board without reference to each other.

Pattern

One bridged number

Load margin is reported with a bridge to the financial result, so commercial decisions are made on a number that has been validated against cash, as with reconciling project schedules to the ledger.

07

How ChatFin builds the bridge

This is a reconciliation between an operational system and a ledger, which is the category of work we exist for.

Reads both sides: Operational load data and ledger transactions in NetSuite, SAP Business One, JD Edwards, Acumatica, Dynamics 365 or Sage Intacct, matched at load level where identifiers allow.
Categorises the difference: Each reconciling item assigned to a defined category with the supporting records attached rather than presented as a residual.
Prepares the settlement reconciliation: Carrier and driver settlements against agreed rates, with variances surfaced for review before payment.

Pricing decisions, lane strategy and carrier selection remain commercial judgements for your team.

Free tool

AI Cost Estimator for the CFO Office

Four inputs. A first year range, a timeline, and three delivery models compared. No login required.

Frequently Asked Questions

Why do load margin and financial margin differ?

Because they are measured at different times from different inputs. Operational margin uses rated revenue and estimated cost at the point of planning or delivery. The ledger records invoiced revenue and settled cost, including accessorials, claims and adjustments that arise afterwards.

Should the two numbers agree?

Not exactly, and the difference should be understood, categorised and reasonably stable. A stable, explained difference lets the operational number be used with a known adjustment, which is more useful than expecting convergence that will not happen.

What is usually the largest reconciling item?

Carrier and driver settlement differences, followed by accessorials arising after the load was priced. Both are also the items most likely to move, which is why they are worth reporting separately rather than as a single residual.

Who should own the bridge?

Finance should prepare it and operations should use it. A bridge prepared and read only within finance changes nothing, because the decisions that depend on the operational margin are made elsewhere.

Bridge the two numbers

The margin used to price loads should be validated against the money.

Agreeing a small set of reconciling categories and preparing the bridge monthly turns two competing truths into one number with a known adjustment.

If you want a first year range for operational to ledger reconciliation, the estimator will produce one before any scoping. The practical test is whether someone outside the team could reach the same answer from the records you keep, which is usually a stricter standard than the one applied internally.

Open the estimator
Book a Demo
Put it on your own numbers

See what this looks like in your ERP.

We will walk through the workflow behind this article on the system you already run, using your own data, and show what a first phase would actually cover.

✓Runs on the ERP you already have, on the version you already run
✓Every action prepared as a draft that a person approves before it posts
✓A first phase scoped against your real workflows, not a generic package
Schedule a Demo
Confidential & private

This article is general information for finance and accounting teams. It is not legal, tax, accounting or investment advice. Dates and thresholds are given as published at the time of writing and several of these timelines have moved before, so confirm the current position with your advisers and with the relevant authority before acting.

Photos by Pavel Danilyuk, free to use under the Pexels License (commercial use, no attribution required).