A truck is unloaded on March 28. The carrier invoice arrives on April 7. Finance closes March on March 31. The freight cost belongs to March, but on closing day there is no bill for it.
Across thousands of shipments, that gap is the freight accrual. Most companies fill it with an estimate: last month's run rate, a percentage of dispatch value, or a logistics spreadsheet. Because the estimate is not tied to shipments, the variance lands in next month's freight line unexplained, and margin is misstated in both periods.
Yet the data to calculate freight accruals accurately already sits in the ERP, TMS, rate contracts and proof of delivery.
Definition: A freight accrual is the liability, and matching expense, a company records for transportation services performed in a period but not yet invoiced by the carrier.
IAS 37 and its Indian equivalent Ind AS 37 treat accruals as obligations for services received but not yet invoiced, usually reported within trade and other payables. Indian finance teams often call it a freight provision.
The accrual is the shipper's estimate; the invoice is the carrier's claim. When the invoice is booked, the accrual is reversed and any difference is recognised as a true-up.
The final cost of a shipment is often unknown at delivery. Carriers bill on their own cycles, often bundling weeks of loads. Rates vary by trip, kilometre, tonne or container, and spot rates often sit outside the contract system. Detention and damage deductions depend on delivery events, and diesel-linked contracts change rates after the truck has moved.
Manual processes absorb this in a spreadsheet: pull the period's shipments, remove invoiced ones, price the rest with an average where the rate cannot be found, add a flat allowance for accessorials, and post one journal entry that auto-reverses. Missing shipments are never accrued, and because invoices are booked to expense instead of matched to the accrual, the same error repeats every month.
Automated freight accruals price each shipment from the records used to plan, execute and pay for it, then reconcile that estimate when the invoice arrives. The unit of work is the shipment, not the month.
> 1. Capture shipment data as each load is planned and dispatched, not at month end.
> 2. Apply the accrual trigger (dispatch, delivery or proof of delivery, per accounting policy) using time-stamped milestones.
> 3. Find the applicable rate for the carrier, lane, vehicle and date, including spot awards, with a labelled fallback when none exists.
> 4. Calculate base freight on the billing basis, leg by leg for multi-leg moves.
> 5. Add accessorials and fuel adjustments only where events or contract clauses support them.
> 6. Allocate the accrual to entity, plant, cost centre, GL account and, where needed, product.
> 7. Post to the ERP, summarised by GL account with shipment detail behind each line.
> 8. Match the carrier invoice to the shipment and its accrual.
> 9. Route variances above tolerance to the right owner with a reason code.
> 10. Release or true-up the accrual on approval, and age any accrual that stays unmatched.
Illustrative only; amounts exclude taxes. A truckload moves from Chennai to Bengaluru at a contracted ₹40,000 per trip, with detention at ₹2,000 per day beyond 24 hours of free time.
|
Date |
Event |
Accrual view |
|
March 28 |
Unloaded after 48 hours at the dock |
1 detention day recorded |
|
March 31 |
Month closes; no invoice yet |
Accrual of ₹42,000 (₹40,000 + ₹2,000) |
|
April 7 |
Invoice arrives for ₹43,200 |
₹1,200 variance, tagged as a fuel adjustment |
|
April 8 |
Exception resolved |
Diesel revision from March 15 was missing from the rate table |
|
April close |
True-up |
₹1,200 booked to April; rate table corrected |
A run-rate estimate might have produced a similar March number. Only the shipment-level method shows why it was off and fixes the cause before the next close.
|
Data |
Why it matters |
|
Shipment and order references |
Defines what is accrued |
|
Carrier, lane, vehicle and weight |
Selects the rate and billable quantity |
|
Contract and spot rates with validity dates |
Drives base freight |
|
Freight terms |
Excludes freight the company does not pay |
|
Milestones and proof of delivery |
Applies the trigger and evidences accessorials |
|
Accessorial schedule and fuel clauses |
Prices charges beyond base freight |
|
Invoice lines with shipment references |
Enables reconciliation |
|
Accounting dimensions |
Posts and allocates the accrual |
A variance means either the estimate or the invoice is wrong. Common causes are rate differences, unsupported accessorials, fuel revisions, shipment data errors, timing and duplicate charges. An automated process should surface each one, using tolerances by charge type, a reason code on every exception, and a feedback loop that corrects rates and master data.
Invoices above the accrual may be overbilling, so the accrual doubles as a freight audit reference. Accruals never invoiced should be aged and reviewed, not released by default.
> Earlier visibility: freight liability builds as shipments complete, before period end.
> One method: the same trigger and rate logic apply across every plant, replacing spreadsheets.
> Faster reconciliation: most invoices clear against an expected cost.
> Auditability: every accrual traces to a shipment, rate version and evidence.
> Shipment-level calculation, not aggregate estimates
> Rates valid on the shipment date, including spot awards
> Accessorials accrued from event evidence, not flat allowances
> A configurable accrual trigger and invoice matching at charge level
> ERP posting plus reporting on accrued versus invoiced freight
The deciding question: does the accrual use the same rate and shipment data the invoice will be audited against?
Pando builds the accrual and the invoice check from one freight-to-pay record, carrying contracted rates, time-stamped milestones and digital proof of delivery. Its Freight Audit & Payments module includes automated freight accruals and cost allocation, reconciliation of detention, shortages, damages and demurrage against ePOD, carrier self-billing, and four-way invoice matching, with ERP integration through Pando's API layer.
In Pando's case study with a leading Indian electrical appliances manufacturer, automatic reconciliation of invoices against contracted rates, shipment and PO value delivered an 89% first-time match rate and full visibility of freight spend. It measures invoice matching, not accrual accuracy, but both depend on complete shipment records.
If your close still depends on a freight spreadsheet, talk to Pando about shipment-level freight accruals.
Shipment by shipment: apply the contract or spot rate valid on the shipment date, add accessorials supported by delivery evidence and any fuel adjustment, then allocate the result to accounting dimensions.
Each invoice line is matched to its shipment's accrual. Differences within tolerance clear; larger ones are routed with a reason code. On approval, the accrual is released and any difference is trued up.