Oracle Fusion Period Close: A Practical Checklist
Oracle Fusion period close checklist
Also searched as
- how to close a period in Oracle Fusion GL
- Oracle Fusion Close Monitor steps
- Fusion GL period close in progress cannot close
- Oracle Fusion month end close process
Short answer
Closing a Fusion GL period cleanly means closing every feeder subledger first (Payables, Receivables, Costing, Fixed Assets), running Create Accounting to post everything to GL, reconciling subledger-to-GL balances, and only then setting the GL period status to Closed - not Close Pending, which still allows adjustments. Close Monitor gives a single dashboard of every subledger's close status instead of checking each module separately.
Applies to: Oracle Fusion Cloud ERP Financials, General Ledger and Subledger Accounting, all monthly updates
Run an Oracle Fusion period close in the right order
- 1Open Navigator > Tools > Close Monitor (or the specific General Accounting > Close Monitor task) to see every subledger's current period status in one place before starting.
- 2Close subledgers in dependency order: transaction-generating modules first (Payables, Receivables, Costing, Fixed Assets, Projects), since GL cannot cleanly close while unposted subledger activity remains.
- 3Run Create Accounting for each subledger with the Final mode and Post to General Ledger option, not Draft, so journals actually post rather than just generating a preview.
- 4Reconcile subledger balances to GL using the Subledger Accounting reconciliation reports or trial balance comparisons - do this before closing, since a closed period blocks further posting corrections.
- 5Review and clear any Blocked or Error scheduled processes tied to close (Create Accounting, Import journals) - a Blocked job will silently stall the close if nobody checks it.
- 6Run and review standard close-related reports: unposted journals, unaccounted transactions, and any custom close checklist reports your implementation maintains.
- 7In General Accounting > Manage Accounting Periods, change the period status to Close Pending first to confirm nothing further should post, then to Closed once confirmed - avoid jumping straight to Closed without the pending check.
- 8Open the next period (status Open) before or immediately after closing the current one so transaction entry is not blocked for the new period.
Why Subledger Order Matters
General Ledger balances are built from subledger journals created through Create Accounting; if Payables or Receivables still has unaccounted transactions when you try to close GL for the period, those transactions either get pushed into the next period unintentionally or block the close outright. Closing subledgers first, then GL, keeps the accounting period genuinely complete rather than just marked closed with gaps underneath.
What Close Monitor Actually Shows
Close Monitor aggregates the period status of every subledger and GL into one view, flagging modules still Open or with unprocessed transactions, so a close coordinator does not need to log into Payables, Receivables, and Fixed Assets separately just to check whether each one is ready. It is a status dashboard, not an automation tool - you still trigger the actual close actions in each module.
Close Pending Vs Closed
Close Pending still allows certain corrective actions and is meant as a checkpoint - subledger transactions dated in that period are blocked from new entry, but the period is not yet permanently sealed. Closed is the final state; once set, reopening a period is a deliberate, auditable action, not a routine correction step, so confirm reconciliation is genuinely finished before moving from Close Pending to Closed.
Common Reasons A Close Stalls
A Create Accounting job left in Draft mode never posts to GL, giving the illusion that subledger activity is accounted for when it is not. An ESS job Blocked behind an earlier identical run silently delays the whole close timeline if nobody is watching Scheduled Processes. And unposted or error-status journal batches in GL itself, often from a failed import, block the period from closing until someone manually resolves or reverses them.
Common pitfalls
- !Running Create Accounting in Draft mode and assuming subledger activity is posted, when Draft never actually posts to GL.
- !Closing GL before every feeder subledger is closed, which pushes transactions into the wrong period or blocks the close with an error.
- !Jumping straight from Open to Closed without a Close Pending checkpoint, skipping the last chance to catch a missed reconciling item.
- !Not checking Scheduled Processes for a Blocked or Error Create Accounting job before assuming the close is simply slow.
- !Reopening a Closed period casually to fix a small item instead of treating it as the deliberate, auditable action it should be.
- !Forgetting to open the next period, which blocks transaction entry for new-period activity right after close.
How an ERP-grounded AI assistant handles this
ERPray grounded on your Fusion instance can run the equivalent of a Close Monitor check on demand and explain, in plain language, exactly which subledger or scheduled process is holding up a close - a Blocked Create Accounting job, an unreconciled balance, or a subledger still Open - instead of a close coordinator manually stepping through each module and the Scheduled Processes list every close cycle.
Frequently asked questions
Can I close GL before all subledgers are closed?
Technically the system may allow it depending on configuration, but it is not good practice - any subledger activity not yet accounted for through Create Accounting will not be reflected in the GL balances for that period, creating a reconciliation gap that is harder to trace after the period is closed.
What is the difference between Close Pending and Closed?
Close Pending blocks new transaction entry dated in that period while still allowing a final review and correction window. Closed is the permanent state; reopening it afterward is an explicit, auditable action rather than a routine step, so treat Close Pending as your last checkpoint before finalizing.
Why does Close Monitor still show a subledger as not closed after I ran Create Accounting?
Check whether Create Accounting ran in Final mode with Post to General Ledger enabled, not Draft - Draft mode generates a preview only and does not change the subledger's close-readiness status. Also confirm the job actually completed rather than sitting Blocked in Scheduled Processes.
How do I reopen an accounting period that was closed too early?
Use General Accounting > Manage Accounting Periods to change the period status back to Open, which is a deliberate action typically restricted to a controller-level role. Document the reason, since reopening a closed period affects reported financials and is usually reviewed as part of audit controls.
Related
Clear An Oracle Fusion ESS Job Stuck In Blocked Status
A Blocked status on an Oracle Fusion Enterprise Scheduler (ESS) job almost always means an earlier instance of the exact same job is still running or stuck, and the job definition does not allow simultaneous requests. Find and finish, or cancel, the earlier request first; only then does the Blocked request move to Running.
How-toFix Wrong Row Counts When Joining Across OTBI Subject Areas
Most subject areas in Oracle Fusion OTBI are self-contained and only support reliable analysis within their own folders; dragging a folder from a second subject area into the same analysis without a genuine shared join key silently produces duplicated or missing rows because OTBI has no way to correctly relate the two fact grains. Fix it by staying inside one subject area where possible, or by explicitly using a subject area that Oracle designed to cross domains, rather than combining arbitrary folders yourself.
Error fixFix FBDI Import Failures From Interface Table Validation Errors
When a Fusion FBDI import job errors out, the cause is almost always bad data in the interface tables (an invalid value set, a wrong date format, or a missing required column), not the ESS job itself. Open the process's Interface Errors Report or the Correct Import Errors spreadsheet to see the exact rejected rows and reason codes, fix the source data, and resubmit from the interface tables instead of re-running the whole FBDI load.
How-toOTBI vs BI Publisher: Which One Should You Use
Use OTBI when a business user needs ad hoc, self-service, real-time analysis with no fixed layout. Use BI Publisher when you need a pixel-perfect, scheduled, high-volume, or externally distributed document such as an invoice, check, or statutory report. Most Fusion implementations end up using both, not one instead of the other.
How-toPaginate And Authenticate Oracle Fusion REST API Calls Correctly
Oracle Fusion Cloud REST APIs authenticate with HTTP Basic Authentication, an integration user's credentials, over HTTPS by default, and paginate with limit and offset query parameters rather than a page number. Loop on the hasMore flag in the response until it returns false to retrieve a full result set.
Error fixFix The Oracle Fusion "You Don't Have Access To This Data" Error
This generic Oracle Fusion security message means the function privilege and the data security scope did not both line up for that user on that record - most often the job role is assigned but the matching data role, security profile, or business unit and ledger context in Manage Data Access for Users is missing. Fix it by checking data access setup for the user's role, not by re-granting the same job role again.
AI for ERPFusion Cloud ERP AI: OCI Generative AI Service vs. a Private LLM
Oracle's OCI Generative AI Service is a real option for Fusion Cloud ERP, but not the only one. Compare it honestly against a private LLM for sensitive data.
AI for ERPOracle ERP AI Consulting: What a Partner Should Deliver
What to demand from an Oracle ERP AI consulting partner across EBS, JD Edwards, NetSuite, and Fusion Cloud: interface tables, APIs, and buyer questions.
Stuck on Oracle Fusion Cloud ERP?
Talk to engineers who work inside Oracle Fusion Cloud ERP every week, and who build private AI that answers these questions from your own ERP data.