What it means
A pallet arrives Monday, but the receiving clerk records it Thursday. Sales may promise from inaccurate stock, while accounts payable cannot match the supplier invoice.
The goods exist physically, yet the system remains behind. Set the physical start event, since gate arrival, unloading and completed count can differ, and use a consistent event that proves custody and quantity under the warehouse process.
Set the posting endpoint too, because a receipt saved in the warehouse system, approved by quality and posted to the ledger are different milestones. An illustrative posting lag is inventory receipt timestamp minus documented physical receipt timestamp, so a Monday 10 AM arrival and Thursday 10 AM posting create 72 elapsed hours.
QuickBooks' inventory-receiving guidance explains entering an item receipt when goods arrive, even before the supplier bill in some workflows, which supports stock visibility without waiting for invoice processing. Oracle's receipt-accounting cutoff guidance describes how backdated receipts can be accounted in a prior general-ledger period under configured rules.
That is a system-specific accounting treatment, not permission to silently backdate operational events, so preserve both the original timestamp and the posting timestamp, since editing the arrival date to match posting hides the delay and can misstate the supplier delivery record. Record item, quantity, location, lot and purchase-order reference at receipt, because a fast posting with wrong quantities is not a quality improvement.
Separate quarantine, as goods can be received physically but unavailable pending inspection, and track partial deliveries by posting the 80 that arrive of 100 ordered and keeping the balance open. Avoid the opposite error as well, since posting before physical inspection or confirmation can create phantom inventory.
Watch period end, because a late posting across a month boundary can distort inventory, accruals and supplier performance, so finance should reconcile physical receipts near cutoff. Use calendar and working hours deliberately, since a Friday-night arrival and Monday-morning posting may be two-plus elapsed days but within a defined staffed receiving window.
Show a distribution, because the median lag and old unposted receipts reveal more than an average and a few high-value delayed shipments can dominate risk. Investigate reasons such as a missing PO, uncertain item code, inspection hold, staffing gaps or a handheld scan not synchronised to the main system, because each needs a different fix and staff should not be pressured to invent a record to improve the clock.
Check downstream effects, since picking, invoicing and payment matching may depend on receipt visibility and delayed posting can trigger duplicate orders or mistaken shortages. Segment by supplier only after separating internal warehouse processing time, assign old items to an owner under an escalation rule, and review the oldest unposted high-value receipt first, because the measure shows how long the stock record trails reality.
In practice
Real-world examples.
Example
A Monday 10 AM delivery posted Thursday 10 AM has a 72-hour elapsed lag. The receiving log shows the gate time and the system time side by side. The supervisor reviews why the pallet waited in the dock area for three days.
Example
A partial shipment records only the units physically received. Of 100 ordered, 80 arrive and are posted that day, and the remaining 20 stay open on the purchase order. Accounts payable matches the invoice only to the 80 received.
Example
A quarantined item is received but not made saleable. The system shows the quantity on site with a blocked status, so the sales team cannot promise it to a customer. Once quality staff release it, the status changes and the available stock updates.
Formula
Calculation
Illustrative posting lag = system inventory receipt time - verified physical receipt time. Thursday 10 AM - Monday 10 AM = 72 elapsed hours.
A distribution shows more than one case. Suppose five receipts in a week have lags of 2, 3, 4, 6 and 72 hours. The average is (2 + 3 + 4 + 6 + 72) / 5 = 87 / 5 = 17.4 hours, but the median is 4 hours, and the one 72-hour receipt is the item to investigate.
If that late receipt was worth $18,000 of stock, the delayed posting hid $18,000 of inventory from sales and from invoice matching for three days. A posted inventory receipt and its ledger accrual should still be reconciled, although their timestamps need not be identical under company policy.Case study
Seen in the real world.
In this entirely fictional example, Maple Parts finds month-end deliveries waiting in a manual receiving queue. It adds a same-day scan and a quality-hold status, then reconciles the inventory and accounting records. It does not backdate the gate event to make the lag disappear. Before the change, the warehouse manager had reported only an average lag, which looked acceptable.
A review of individual receipts showed a handful of high-value deliveries that waited several days, mostly because a handheld scanner was not synchronising with the main system. After the fix, the manager reported the median lag, the number of receipts older than one working day, and the oldest unposted high-value receipt each week. Supplier performance was reviewed only after the internal processing time had been separated out.
Watch out
Common mistakes.
- Using system posting time as if it were the physical arrival time.
- Making quarantined or uncounted stock available just to post quickly.
- Waiting for a supplier invoice before any physical receipt is recorded when the workflow allows separate receipt.
Questions
People also ask.
Is posting lag the same as supplier lateness?
No. It measures the recording delay after physical arrival.
Can received goods remain unavailable?
Yes. Inspection or quarantine can restrict use.
Why keep two timestamps?
They preserve actual custody timing and the later system event.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%