The goods receipt that won't post
What the user reports
Monday 2 November at Rockford. Orrin's 20 motors arrived early and the warehouse clerk can't book them in: the goods receipt is refused. On Friday the general ledger accountant reopened October to post a late accrual.
The error: Goods receipt for the Orrin motor purchase order refused: posting period 2026-11 is not open for company code CP10.
What you'll do
- See the problem as the warehouse clerk: On Goods receipt, post the full 20
CP-MTR15on the purchase order from Orrin Motor Works (supplier 20000001). - Find the cause: The message says period 2026-11 is not open for CP10. What is the right fix?
- Fix it as the general ledger accountant.
- Prove it: run the step that failed again.
The drill runs in the lab on its own prepared copy of the fictional Calder Pumpworks, saved in this browser apart from your company. All codes and values are fictional course labels.
Answer and explanation (open after the drill)
The fix: Open November again on the posting periods for CP10, keeping October open only while its accrual is posted.
A goods receipt posts a journal entry on the day the goods arrive, so the month it falls in must be open. The receipt is fine and the purchase order is fine; the period range is wrong. Back-dating the receipt into October would put November's stock and liability in the wrong month, and a new purchase order wouldn't change which period is open.
Why it broke
Every posting carries a date, and finance controls which months accept postings per company code. The range here was set to October only, so every November posting was refused: goods receipts, invoices, deliveries, payments. In the lab the error names the period and the screen, which is the quickest route to the cause.
How teams prevent it
Change period ranges by a checklist at month end (open the new month first, close the old one after its last posting), and keep the change with the general ledger team. Many companies also open the next month for a few days of overlap, then close the old one once its accruals are in.
Across teams
The warehouse saw the error, but the cause sat in finance. That is typical: one setting owned by one team stops work in another. Whoever takes the call needs to read the message, find the owner of the setting and ask for the change, not work around it.
Where AI fits
An assistant that reads the error, looks up the setting it names and who owns it, and drafts the request to that team fits well here (retrieve). It shouldn't change the period range itself: opening a month is a finance control.
Learn more: Record to report, end to end