Accrue road freight at month-end without counting the invoice twice

Why month-end freight accruals get double-counted in the next period

Indian road-freight billing rarely aligns with the calendar month-end close. A primary full-truckload (FTL) transporter dispatches vehicles in the final week of the month, waits for physical signed proof-of-delivery (POD) or lorry-receipt copies to return from upcountry hubs, and submits a consolidated paper or PDF annexure ten to twenty days later. To close the books on Day 2 or Day 3, the finance controller posts an unbilled freight accrual based on an operations spreadsheet of March dispatches.

Double counting happens in two ways. First, the operations spreadsheet often includes trips whose fast-track invoices were already booked in accounts payable on the 30th or 31st, causing the same shipment to sit in both booked freight expense and unbilled freight accrual. Second, when the carrier's consolidated invoice arrives in the following month, accounts payable posts the bill straight to the freight expense account without clearing the trip-level accrual—or reverses a blanket accrual while leaving older unbilled trips unmonitored.

Preventing both errors requires anchoring the accrual calculation and the subsequent invoice match to the same unique shipment or trip identifier (Trip ID / LR Number). Accounting cutoff rules and revenue/expense recognition policies must be set by the company's finance leadership and auditors; the operational workflow's job is to apply those approved rules consistently to every trip record.

Separate the four month-end states of a road shipment

Before generating an accrual journal at period close, every active road shipment near the cutoff boundary must be classified into one of four mutually exclusive states:

1. In-period and unbilled (Accrue): The shipment satisfies the company's approved period-cutoff event (for example, vehicle gate-out dispatch or confirmed delivery before 23:59 IST on the final day of the period, depending on policy) and has no posted AP invoice.
2. In-period and already invoiced (Do not accrue): The shipment belongs to the closing period, and the carrier's invoice has already been matched and posted in AP before the ledger cutoff. Including it in the accrual schedule double-counts the expense in the current month.
3. Post-cutoff movement (Exclude to next period): The shipment was created or planned in the closing month, but the qualifying execution event (such as physical dispatch or custody transfer) occurred after the period cutoff timestamp.
4. Cancelled or duplicate trip record (Purge from accrual base): A draft indent or replaced vehicle booking where no billable movement occurred.

Standardised operational event timestamps—conceptually aligned with how the GS1 — EPCIS and CBV Artefacts structure distinct business steps and dispositions—help finance and logistics teams agree on whether a trip has genuinely crossed the dispatch or delivery threshold rather than relying on when a clerk typed an order into the ERP.

Illustrative example: reconciling four month-end FTL trips worth ₹2,40,000

Consider a manufacturing shipper closing its October ledger on 2 November. The transport desk exports 4 FTL trips handled by Carrier NorthStar around the 31 October cutoff, with total estimated freight of ₹2,40,000. Finance applies the company's approved dispatch-cutoff policy and checks the AP sub-ledger before posting the October unbilled freight accrual.

Notice how the trip-level ledger reconciles every rupee across both periods:

• Out of ₹2,40,000 in total estimated freight across the 4 trips, ₹1,15,000 (TRP-101 ₹60,000 + TRP-102 ₹55,000) is legitimately accrued at October close, ₹65,000 (TRP-103) is excluded from the accrual because it is already posted in October AP, and ₹60,000 (TRP-104) is deferred to November because physical dispatch occurred after cutoff (₹1,15,000 + ₹65,000 + ₹60,000 = ₹2,40,000).
• On 4 November, when Carrier NorthStar submits a consolidated invoice of ₹1,80,000 covering TRP-101, TRP-102 and TRP-103 (₹60,000 + ₹55,000 + ₹65,000 = ₹1,80,000), the trip-level match rule clears ₹1,15,000 against the open accruals for TRP-101 and TRP-102 and flags ₹65,000 (TRP-103) as a duplicate billing line because LR-8803 was already settled on INV-901.

Without trip-level linkage, an AP clerk looking at a ₹1,80,000 consolidated bill would likely book the entire amount or reverse the wrong accrual balance.

Build the accrual estimate from contracted rate components

An accrual is only as reliable as the freight calculation behind each trip. As illustrated in the Oracle Transportation Management — Match Rule Manager documentation, transportation settlement systems match invoices against shipment cost lines using defined rules and tolerances. To keep the month-end accrual close to the eventual invoice:

1. Base lane rate or contracted spot rate: Pull the approved contracted tariff (FTL vehicle rate or PTL weight/zone rate) or the pre-approved spot-indent amount stored on the trip record.
2. Confirmed fuel surcharge: Apply the index-linked diesel surcharge valid on the dispatch date if your contract separates base freight and fuel.
3. Approved accessorials only: Include detention, multi-point drop or loading charges in the accrual only if an operational exception record has been verified or logged with supporting timestamps. Do not accrue speculative carrier claims that lack evidence.

When the carrier's invoice arrives with a ₹1,200 difference due to a toll receipt or a weight re-measurement, the system clears the original ₹60,000 trip accrual and posts only the ₹1,200 variance to the current period's freight variance account (subject to your match tolerance rules).

Prevent aged "zombie accruals" from lingering on the balance sheet

Whether your company uses an auto-reversing month-end accrual journal (reversing on Day 1 of the new month and re-accruing all still-unbilled trips at the next close) or a persistent goods/services-received-not-invoiced (GRNI / SRNI) sub-ledger cleared by invoice matching, one control is essential: an aged unbilled-trip register.

Review open unbilled trips by age bucket (0–30 days, 31–60 days, 61–90 days, >90 days) every month:

• Trips aged >60 days without a carrier invoice often turn out to be movements that were paid under a manual miscellaneous voucher without linking the Trip ID, or cancelled dispatches that were never closed in the TMS.
• Requiring every AP freight posting to reference a valid Trip ID / LR Number closes the side door through which manual vouchers bypass the accrual sub-ledger.

Next actions

1. Stop posting lump-sum freight accruals without a backing schedule of unique Trip ID and LR Number rows.
2. Run a pre-accrual cross-check against the AP sub-ledger at every month-end close to strip out trips whose invoices were already posted before cutoff.
3. Enforce a mandatory Trip ID / LR Number reference on all carrier invoice lines so consolidated annexures cannot bill the same trip twice across months.
4. Review open unbilled freight accruals aged over 60 days every month with Finance and Transport Operations to clear cancelled trips or unlinked manual payments.