The current status of the GL accounting period (Open, Closed, Closed Pending, or Never Opened) and whether the close is tracking against its published deadline. The pulse of the month-end close.
At a glance
GL Period Close Status reports where the General Ledger accounting period currently stands and whether the close is on schedule. It surfaces the period’s state (Open, Closed, Closed Pending, or Never Opened) and flags when the close has run past its published deadline. For a Fortune 500 finance team the close is a high-stakes, calendar-driven event, and a period sitting open past deadline is one of the clearest signals that something is blocking the books from being finalised. Sourced from the Oracle Fusion General Ledger period statuses across all in-scope ledgers.
| What it counts | The current accounting-period status in the Oracle Fusion General Ledger per ledger (Open, Closed, Closed Pending, Never Opened) and the number of days the close is running past its published deadline, if any. It is a status indicator, not a monetary total. |
| Business Unit scope | Period statuses are held at ledger level. The card respects the dashboard’s ledger and Business Unit filter and surfaces the status for each in-scope ledger, flagging the worst case at the consolidated view. |
| Time window | RT (real time). The status reflects the live period state as of the last sync window. |
| Alert trigger | Fires when a period remains open more than 5 days past its published close deadline (overdue >5d). |
| Roles | owner, finance |
Calculation
Calculated automatically from your Oracle ERP Cloud data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US Fortune 500 omnichannel speciality retailer running Oracle ERP Cloud across three ledgers: US ledger (USD), UK ledger (GBP) and EUR ledger. The reading is taken on 06 Jun 26. The published deadline to close the May 26 (Jun-26 fiscal) period is the fifth working day, which fell on 05 Jun 26.| Ledger | Period | Status | Days past deadline |
|---|---|---|---|
| US ledger | May 26 | Closed | 0 |
| UK ledger | May 26 | Closed Pending | 1 |
| EUR ledger | May 26 | Open | 1 |
| GL Period Close Status (this card) | May 26 | Open (worst case) | 1 |
- The card reports the worst case across ledgers. The US ledger is fully Closed, but the EUR ledger is still Open one day past the deadline, so the consolidated headline shows Open / 1 day past. The close is only finished when every in-scope ledger is closed.
- “Closed Pending” is a real Oracle state, not an error. The UK ledger is in Closed Pending, meaning closing entries are run but the period is held briefly before final closure, often to allow a last reconciliation pass. It is on the way to Closed, not stuck.
- One day past deadline does not trip the alert. The threshold is more than 5 days overdue, so a single day of slippage shows as a flag on the card but stays quiet on the alerting layer. This avoids crying wolf during a normal close that runs slightly long.
- The blocker is usually upstream. A period cannot close cleanly if subledger journals have not finished posting. If the EUR ledger is stuck, the first place to look is Subledger to GL Posting: Failed (any source) and Open / Unposted Journals.
- The headline flips to Closed only when all ledgers agree. Once the EUR ledger reconciles and closes, the card moves to Closed / 0 days past, and the on-time-rate history (tracked separately) records whether this close beat its deadline.
Sibling cards merchants should reference together
GL Period Close Status is the headline of the close. Pair it with these to find what is blocking it and how this close compares historically.| Card | Why pair it with GL Period Close Status |
|---|---|
| GL Period Close Past Deadline | The dedicated overdue view, quantifying exactly how far past the deadline the close has run. |
| Period Close On-Time Rate (12mo) | The historical track record. One late close is noise; a falling on-time rate is a process problem. |
| Open / Unposted Journals | A common blocker. Unposted journals must clear before a period can close cleanly. |
| Subledger to GL Posting: Failed (any source) | Failed subledger postings hold the GL open. The first place to look when a close stalls. |
| Journals in Error | Journals in error state cannot post and can block the close. |
| Accrual Reversals (last close) | Confirms the prior period’s accruals reversed cleanly into the new one, a routine close step. |
| Oracle Fusion Health Score | The composite roll-up that close health feeds into alongside other integrity signals. |
Reconciling against Oracle ERP Cloud
Where to look in Oracle ERP Cloud: The closest native equivalents in the Oracle Fusion UI are:Navigator → General Accounting → Period Close → Manage Accounting Periods Navigator → General Accounting → Period Close → Close Monitor Reports and Analytics → OTBI → Financials → General Ledger Period Status Real Time Subject AreaThe Manage Accounting Periods page shows each ledger’s period status directly, and the Close Monitor gives the cross-ledger close view that this card mirrors. Read the status for the same ledger and period scope as the dashboard filter and the card should agree. The Close Monitor is the tool most Fortune 500 controllers run during the close window itself. Common mistakes when comparing against Oracle’s own reports:
- Confusing GL period status with subledger period status. Receivables, Payables and other subledgers have their own period statuses that close before the GL. A subledger can be closed while the GL is still open, and vice versa. This card reads the GL period status.
- Reading one ledger and assuming it speaks for all. Each ledger closes on its own. The US ledger being Closed does not mean the UK or EUR ledgers are. This card reports the worst case across in-scope ledgers.
- Treating “Closed Pending” as a fault. Closed Pending is a normal intermediate state, not an error. It indicates the period is held briefly before final closure.
| Reason | Direction | Why |
|---|---|---|
| GL vs subledger period status | Either | The card reads the GL period. A subledger close monitor can show a different state because subledgers close on their own schedule ahead of the GL. |
| Worst-case roll-up vs single ledger | Either | The card surfaces the worst case across in-scope ledgers. A single-ledger view in Oracle shows only that ledger and may look further ahead than the consolidated card. |
| Deadline definition | Either | ”Past deadline” depends on your published close calendar. If the card’s configured deadline differs from the one a report assumes, the days-past figure differs. |
| Closed Pending interpretation | Minor | The card treats Closed Pending as not yet fully closed. A report that counts Closed Pending as closed will look further along. |
| Sync timing | Small | The card reflects the period state as of the last sync window. A status changed in Oracle moments ago appears in the native UI before the card refreshes. |