Month-End Close Blocked by Interface Errors and In-Transit Transfers
At the end of March, a distributor cannot close Oracle Cloud Inventory. The inventory period is open, but 4,000 receipt interface records are in error because supplier and item combinations are invalid. Eighteen inter-organization transfer orders were shipped from the U.S. warehouse but not received in the Canada warehouse, so they sit in transit. The OTBI on-hand quantity report ties to the subinventory quantity report, but the cost accountant's inventory valuation is 240,000 USD higher than the general ledger inventory account. A late freight invoice of 15,000 USD for February receipts was just entered, and the cost accountant wants to reopen February to absorb it. The March physical count is complete, but 12 count adjustments are pending approval. The close calendar allows three business days.
1. Propose a sequenced close plan for the three days. Identify what must be resolved before inventory period close and what can be handled in Cost Accounting.
Read the worked answer
Sequence the work by dependency. On day one, stop new nonessential transactions in the affected organizations, resolve the 4,000 receipt interface errors, and correct invalid supplier-item combinations in the source data. Process valid receipts and separate records that require master data changes. Also review the 18 in-transit transfer orders: receive them if physically received, or confirm and document in-transit status if they are legitimately still moving. Approve or reject the 12 count adjustments with the required reason codes.
On day two, run the inventory transaction and cost processes after interface cleanup, reconcile the subledger to the general ledger, and investigate the 240,000 USD valuation difference. Do not close the inventory period while receipt or transfer transactions are still unprocessed. The late February freight invoice should follow the company's prior-period policy; reopening February may be allowed only with approval and may disrupt an already-closed cost period. If policy permits, record it as a prior-period adjustment in March rather than reopening February. Close Inventory before Cost Accounting, because cost processing depends on complete inventory transactions. Day three should be reserved for reconciliation, exception approval, and documenting remaining differences.
2. How would you investigate the 240,000 USD valuation difference? Include likely causes and the reports or data you would compare.
Read the worked answer
Start by comparing the same population, not two different views. Confirm the inventory valuation report, the on-hand quantity report, and the general ledger balance all use the same organizations, subinventories, and date cutoff. The OTBI on-hand quantity report and the cost accountant's valuation may be on different bases: one is quantity, the other is value. Reconcile value by organization, subinventory, item, and cost method. Check for unprocessed receipt interface records, unprocessed cost adjustments, pending count adjustments, and transfer orders still in transit. In-transit transfers can explain a difference between shipping and receiving organizations, but the value should still be in an in-transit balance, not necessarily in the receiving organization's on-hand.
Also check cost profiles and standard cost updates, negative on-hand balances, expense versus inventory account mapping, and freight or landed cost adjustments. A 240,000 USD difference is large enough that it may combine several causes, such as receipt interface errors plus in-transit transfers plus a late cost adjustment. Do not force the difference into a single plug account. Build a reconciliation that ties the subledger valuation to the GL by organization and explain each component before closing.
3. What controls would you recommend for the next close to prevent late invoices and stale in-transit transfers?
Read the worked answer
Establish a close calendar with clear cutoff dates for receipts, transfers, and cost adjustments. Require receiving and shipping to clear or formally age in-transit transfer orders before period end, with an owner and an escalation path for orders over a defined age. Monitor receipt interface errors daily rather than discovering them at close, and assign master data corrections for invalid supplier-item combinations to a named team. For freight and landed costs, define how late invoices are accrued or recorded, and require approval before reopening a closed period.
Add a pre-close checklist that includes unprocessed transactions, pending count adjustments, in-transit transfers, negative balances, and subledger-to-GL reconciliation. Reconcile inventory valuation to the GL before the Cost Accounting period is closed, not after. Track the number and age of interface errors and in-transit orders as close metrics. The goal is to make the three-day close repeatable: resolve transactions first, process costs second, reconcile third, and use prior-period adjustments only under an approved policy.