Closing January with Unposted Journals, a Duplicate Recurring Journal, and Suspense
A services company is closing January 2026 in Oracle Cloud GL. The close checklist requires subledger accounting finalized for Payables, Receivables, and Assets; journals transferred to GL; journals posted; revaluation and translation run; and the period closed. On day 3, the GL period status is Open, but Close is disabled. The team finds 14 unposted GL journals and two subledger accounting periods still open. It also finds that the recurring rent journal, $48,000, posted twice because the "Run Recurring Journals" checklist step was executed again after the first run's journal had been posted. The GL suspense account holds $12,300 from an interface journal that used an invalid cost center. The controller wants to close by day 5 and asks whether the duplicate can simply be deleted and whether the suspense balance can be left until next month.
1. Why is Close disabled, and what is the correct close sequence?
Read the worked answer
Close is disabled because the GL still has unposted journals and two subledger accounting periods are open. Oracle expects the subledgers to be complete and closed and all GL journals posted before the GL period can close. The sequence is: finish and close subledger accounting for Payables, Receivables, and Assets; transfer final entries to GL; resolve validation errors; post all GL journals; run revaluation and translation if required; reconcile suspense and intercompany; then close. "Close Pending" is useful only when you want to allow subledger processing while blocking GL postings; it is not a substitute for posting. Do not close the period to hide unposted journals, because they remain and resurface later.
2. The recurring rent journal posted twice at $48,000. What went wrong and how should it be corrected?
Read the worked answer
The recurring journal was generated twice, and both generated journals were posted. Rerunning the recurring journal definition creates another journal; it does not overwrite the first. Reverse one $48,000 entry in an open period if possible, or post a correcting journal if the period is closed. Then fix the definition: set a last date or a number of periods, and restrict who can run recurring journals. Add a close-checklist control that compares recurring run counts to the expected count. Do not delete the posted journal; the audit trail matters, and deletion may not be allowed. The controller should treat the duplicate as a control failure, not just a $48,000 adjustment.
3. What should be done about the $12,300 suspense balance, and what control prevents a recurrence?
Read the worked answer
The suspense balance is a symptom: the interface used an invalid cost center or a combination that failed validation, and the journal posted to suspense because that option was enabled. Do not close with $12,300 in suspense. Find the source journal and invalid segment, correct the source data, rerun the interface, and reverse the suspense entry. Keep "Post to Suspense" as a controlled exception, not a routine; add pre-validation in the interface to reject invalid accounts, and monitor suspense daily during close. Leaving it until next month misstates both the P&L and the balance sheet and makes the next close harder.