What Real-Time GL Coding Changes for Finance

Month-end reconciliation is not a financial control. It is a delayed reckoning. The distinction matters.

Ask a finance director at a large CPG company what they know about freight cost at any given point in the month and you will often get a candid answer: they know what was budgeted, they know what cleared last month, and they have a rough estimate of what is accruing. The estimate is based on historical run rates and whatever visibility their freight platform provides, which is typically linehaul and fuel but not accessorials, and typically lags the actual shipment activity by several days.

This is the standard state of freight financial visibility. It is not considered a problem by the finance teams who live with it, because it has always been this way and reconciliation at month-end is built into the close process. What it means in practice is that the freight liability on the balance sheet at any point during the month is an educated guess rather than an accurate figure.

Why the educated guess is more expensive than it looks

The cost of the educated guess is not just the reconciliation work at month-end. It is the decisions that get made with incomplete information during the month. A brand manager evaluating whether a promotional campaign can absorb a freight rate increase is working from accruals that do not include the accessorial charges that are accumulating as the promotion ships. A regional VP making a carrier strategy decision is looking at freight cost data that does not reflect the detention charges the carrier has been applying for the past two weeks because those invoices have not arrived yet.

These are not edge cases. They are the normal operating condition of freight finance in an enterprise that reconciles at month-end. Decisions are made on incomplete data, not because the data does not exist, but because the systems that hold it are not connected to the finance view in real time.

What GL coding requires to be accurate in real time

Accurate GL coding at the point of tender rather than at the point of payment requires three things working simultaneously. First, expected cost calculation at tender time: the system needs to know the contracted rate for this shipment on this lane with this carrier, including the applicable fuel surcharge and accessorial schedule. Second, cost allocation logic: the system needs to know which cost center, GL account, and business unit this shipment belongs to, which requires connecting shipment attributes to the GL hierarchy. Third, accrual maintenance: as the shipment moves and actual costs become known, the accrual needs to update to reflect what was actually charged.

The third requirement is where most platforms fall short. Calculating an expected cost at tender is achievable. Maintaining that accrual through the shipment lifecycle, updating it when the carrier applies an unexpected accessorial, revising it when the invoice arrives with a different fuel surcharge rate, and closing it against the final payment, requires a data pipeline that most freight finance systems are not built to run.

“Real-time freight accruals are not a reporting feature. They are a financial control. The difference between those two categories matters to your auditors.”

What finance actually gains

When GL coding runs in real time from tender through payment, finance gains three things they previously lacked during the month.

First, accurate freight liability at any point in the reporting period. The accrual reflects actual shipments in transit, actual contracted rates, and actual accessorial charges based on current carrier billing patterns, not last month's run rate.

Second, SOX-compliant audit trails on the freight cost recognition itself. Every accrual is traceable to the tender event, the rate card version that produced it, and the actual invoice that closed it. The audit trail is not reconstructed at month-end; it is built continuously.

Third, no month-end reconciliation surprises. Accruals that are maintained through the shipment lifecycle close cleanly against invoices. Variances that do exist are surfaced during the period rather than discovered during close, when the options for addressing them are more limited.