Goods in Transit at Period End: Ownership and Cutoff Testing

On the last night of the year a container of 1,240 cartons is somewhere off the coast, a branch transfer truck is parked at a toll plaza, and a customer delivery booked as "shipped" will not be signed for until the third. The supplier has already recognised its sale. Your warehouse has not received anything. Unless someone decides, shipment by shipment, who owns each load, the same goods end up on two balance sheets or on none.

Period-end cutoff for goods in transit is a short list of facts per shipment: the agreed delivery term, the date the goods left, the date they arrived, and whether anything in the contract moves title or control at another point. Put those facts into one register before the ledger closes, test the shipments either side of the cutoff date, and the inventory, payables, revenue and Indian input tax credit balances agree with the paperwork an auditor will ask for.

• Covered here: the four transit situations at a close, how FOB terms and Incoterms decide who records the inventory, which logistics documents date each movement, and how auditors in the US and India test the boundary.
• Worked material: a US ledger in dollars and an Indian ledger in rupees, an SQL extract for the in-transit register, an incident trace, and a rollout checklist for the finance and transport teams.

Four positions a shipment can occupy when the ledger closes

Every load moving at the close falls into one of four positions, and each has a different owner of the inventory line. Sort shipments into these positions first; the accounting follows almost mechanically once the position is known.

Inbound purchases may already belong to you while still on a truck or vessel. Outbound sales may still belong to you after they leave your dock. Transfers between your own sites never change the owner but do leave the warehouse system, and stock held by a carrier, port or third-party warehouse sits outside your four walls with your name on it. Each of these is easy to lose in a count that only looks at shelves.

The nearest existing page on this site, warehouse stock reconciliation across WMS and ERP, deals with bridging bin balances, open waves and unposted receipts inside a warehouse. This article looks outward instead: the loads that are on the road, on the water or at a carrier terminal, and the legal question of whose asset they are on the balance sheet date.

Reading FOB terms and Incoterms to decide who owns the load

The delivery term in the purchase or sales contract decides ownership; the date the paperwork reaches finance does not. Capture the term and the named place as structured fields on every order line, because a term buried in a PDF cannot drive a period-end rule.

For US domestic sales of goods, the Uniform Commercial Code gives the default when the parties have not agreed otherwise. Section 2-401(2)(a) passes title at the time and place of shipment when the seller is only required to send the goods; Section 2-401(2)(b) passes title on tender at destination when the contract requires delivery there. Section 2-509 runs risk of loss along the same split between shipment and destination contracts.

Goods in transit at period end belong to the buyer under an FOB shipping point contract because UCC Section 2-401(2)(a) passes title at shipment, so the buyer's in-transit register lists every load with a bill of lading dated by the cutoff and no receipt; omitting one $186,400 container understates inventory by that full amount.

Revenue accounting adds a second test. ASC 606-10-25-30 and Ind AS 115 paragraph 38 both list indicators that control has passed, including legal title, physical possession and the significant risks and rewards of ownership. IFRS 15 paragraph 38, which carries the same list, notes that a seller keeping title only as protection against non-payment does not stop the customer obtaining control.

India has no statutory equivalent of the UCC defaults that a ledger rule can quote; ownership follows the contract, and the accounting test under Ind AS 115 still looks at control. Our comparison of EXW and FCA export terms explains why the handover point under each term matters for loading risk, which is the physical event this register dates.

Logistics documents that prove the dispatch and receipt dates

Each transit decision rests on two dates, and each date needs a document from outside the accounting team. Rank the evidence by how hard it is to backdate, and record which document supplied each date on the register line.

A bill of lading signed by the driver is stronger than an internal pick confirmation, and a carrier's own scan event is stronger than a planner's estimate. In India, the e-way bill carries a system timestamp from the government portal, and the lorry receipt (LR or consignment note) is the transporter's acknowledgement of the goods. Neither replaces the other: the e-way bill can be generated hours before the truck leaves.

On an outbound destination contract, the delivery record does double duty. The same signed and time-stamped proof that settles a customer's claim of short or late delivery is the document that dates the transfer of control, so a POD captured the morning after a night arrival should carry the actual arrival time, not the signing time.

Building the in-transit register before the last working day

The register is a query, not a spreadsheet assembled from email. Run it from the order, shipment and receipt tables at the cutoff timestamp, store the output with its run time, and let finance post only from that frozen extract.

The minimum fields are the order and line, counterparty, delivery term and named place, the title or acceptance override if the contract has one, the dispatch date and document, the receipt or delivery date and document, quantity, value at cost, and for India the GSTIN pair and e-way bill number. The query below shows the inbound half; the outbound half mirrors it against sales orders and proofs of delivery.

-- Inbound loads owned by us but not yet received at the cutoff (illustrative schema)
SELECT po.po_no, po.line_no, po.supplier_id, po.delivery_term, po.named_place,
       sh.bol_or_lr_no, sh.dispatch_ts, sh.ewb_no,
       rc.grn_no, rc.receipt_ts,
       po.qty_shipped * po.unit_cost AS value_at_cost
FROM   purchase_line po
JOIN   shipment sh   ON sh.po_no = po.po_no AND sh.line_no = po.line_no
LEFT JOIN receipt rc ON rc.shipment_id = sh.shipment_id
WHERE  po.title_point = 'ORIGIN'              -- derived from term + override, never free text
  AND  sh.dispatch_ts <= :cutoff_ts           -- e.g. '2026-12-31 23:59:59' local site time
  AND  (rc.receipt_ts IS NULL OR rc.receipt_ts > :cutoff_ts);

-- Test statistic per site
-- cutoff_error_rate = misdated_lines / sampled_lines            (target: 0)
-- net_cutoff_misstatement = SUM(value_at_cost * s), s = +1 if omitted, -1 if double-counted
-- escalate when ABS(net_cutoff_misstatement) > 0.5% of the site's period-end inventory

Time zones cause more cutoff errors than contract terms. A load dispatched at 22:40 in Los Angeles on 31 December carries a 1 January timestamp in a system that stores Eastern time, so the register must compare dates in the dispatching site's local time and state that rule in the close manual.

How auditors in both markets test the shipping and receiving boundary

Expect the auditor to work from the boundary outward: the last documents issued before the cutoff and the first documents after it, traced to the period in which each entry was posted. Prepare that pack in advance and the test becomes a review rather than a search.

For US public-company audits, PCAOB AS 2510 sets the expectations for observing inventories. Paragraph .09 makes attendance at a balance-sheet-date count ordinarily necessary, paragraph .12 requires tests of intervening transactions when counts are not at period end, and paragraph .14 calls for direct written confirmation from public warehouses or other outside custodians holding the entity's goods.

Cutoff testing for goods in transit under PCAOB AS 2510 paragraphs .12 and .14 and ICAI's SA 501 implementation guidance traces the last receipt and dispatch documents before the balance sheet date to the correct period, and confirms stock held by carriers or third-party warehouses, for example sampling the final and first five working days.

In India, SA 501 governs evidence about the existence and condition of inventory. ICAI's Implementation Guide to SA 501 (May 2013) tells the auditor at paragraph 2.25 to obtain cut-off information for both receipts and dispatches, and its Appendix 2 template records the last goods receipt note, the last sales invoice and the challan reference. Paragraphs 2.64 to 2.66 cover stock with clearing and forwarding agents, bonded godowns and consignees, which the auditor confirms externally.

The trace below shows how a single misdated outbound load slipped through a month-end that had no register, and how the boundary sample caught it.

1. 31 Dec, 18:05: Sales order SO-88214 (FOB destination, value $92,000) is picked and loaded at the Ohio distribution centre; the ship confirmation in the warehouse system triggers invoice INV-31877 dated 31 December.
2. 31 Dec, 18:06: The ERP posts revenue of $92,000 and relieves $61,300 of inventory to cost of sales, because the billing rule fires on ship confirmation for every term.
3. 3 Jan, 10:20: The customer signs the proof of delivery in Tennessee; the carrier's delivery event arrives the same morning.
4. 21 Jan, 14:00: The audit team selects the last ten invoices of December, finds a destination term with a January delivery, and raises a cutoff exception for $92,000 of revenue and $30,700 of margin.
5. Corrected state: Billing for destination terms now waits for the delivery event; until then the load sits in an "in transit to customer" inventory account and appears on the outbound register.

Worked ledgers for one US distributor and one Indian manufacturer

Three loads explain nearly every entry a controller will make at a cutoff: an owned inbound purchase, an outbound sale that has not yet transferred control, and a transfer between two sites of the same company. The figures below are illustrative.

The US distributor closes on 31 December. The Indian manufacturer closes its financial year on 31 March and holds separate GST registrations in Maharashtra and Karnataka, so its branch transfer is also a taxable supply between distinct persons under CGST Section 25(4) and Schedule I paragraph 2, even though ownership never changes in its own books.

The US errors together understate inventory by $251,550 at cost ($190,250 omitted plus $61,300 relieved early) and overstate gross margin by $30,700. The Indian errors understate stock by ₹70,52,000 and, without the IGST receivable, misstate the tax position by ₹8,74,800. None of these would show up in a perfect shelf count, because none of the goods were on a shelf.

Indian GST timing: tax invoice at removal, credit only after receipt

In India, ownership and tax credit run on different clocks, so the register needs a separate tax column. A buyer may own goods at the year-end and still be barred from taking the input tax credit on them until they arrive.

CGST Section 31(1)(a) requires the supplier to issue the tax invoice before or at the time of removal where the supply involves movement of goods. Section 16(2)(b) then makes receipt a condition of the recipient's credit, and its first proviso allows credit on goods arriving in lots only when the last lot is received. The Explanation treats delivery to another person on the recipient's direction, including by transfer of documents of title during movement, as receipt.

Indian buyers owning goods in transit at 31 March record the stock under Ind AS 2 but hold the IGST in a pending-receipt account, because CGST Section 16(2)(b) allows input tax credit only after receipt; an ₹8,74,800 credit claimed in the March return would precede the receipt condition by at least one day.

• Pending-receipt tax account: Post IGST on owned in-transit purchases to a balance sheet account that is excluded from the March return, and release it when the goods receipt note posts.
• Branch transfer credit: The receiving GSTIN takes credit on the transfer invoice only after receipt, so the sending site's output tax and the receiving site's credit fall in different months at a year-end.
• Endorsed documents of title: Where a lorry receipt is endorsed to a third party on your instruction during movement, the Explanation to Section 16(2) may treat that as receipt; record the endorsement date on the register line.
• Approval and sale-or-return loads: Under Section 31(7), goods sent on approval need an invoice before or at supply or within six months of removal, whichever is earlier, so track their age on the outbound register.

The freight on an owned inbound load is part of the purchase cost, and coding it consistently is a separate control. Our article on freight GL coding for inbound and outbound charges sets out the account rules that the accrual lines in the table above rely on.

Where fixed rules decide and where reviewers use software assistance

Ownership, the period and the tax account are decided by rules that use structured fields; nobody should reason them out again at each close. Software and AI help with reading documents and matching events, with a person accepting each suggestion.

Close calendar and sign-off duties around the cutoff date

Cutoff fails when each team assumes another one owns the boundary. Assign named owners to each record and a fixed day in the close calendar for each hand-off, then hold the sign-off sequence even in a short month.

A workable sequence starts two working days before the period end, when transport freezes the list of loads expected to cross the boundary, and ends on the fifth working day after it, when the boundary sample has been traced and any adjustment posted. The table assigns each record to a team and names who signs.

For the physical side of the same close, our guide to running a wall-to-wall physical inventory covers tag control, blind counts and the book-to-physical journal; the in-transit register is the list of goods that count cannot see.

Rollout checklist for an in-transit register and boundary test

Treat the first two closes after go-live as a parallel run: produce the register, compare it with the old manual adjustments, and switch over only when every difference has an explanation. The checklist below is what to verify, and what evidence proves each step.

If your current ERP or transport system cannot hold the delivery term as a structured field, stamp the gate-out time in local site time, or keep the tax column separate from the inventory line, those gaps belong in the requirements for the next system review. You can describe them in a request for proposal to NextEdge Labs, and the wider set of finance and transport guides sits in our logistics and supply chain library.