A live alert feed: any GL accounting period whose close has slipped more than 5 days past its published deadline. A late close holds up board packs, statutory filings, and the next period’s reporting.
At a glance
GL Period Close Past Deadline is a real-time alert feed, not a trend KPI. It watches the close status of every accounting period across your Oracle Fusion ledgers and raises an entry the moment a period is still Open or in a partial close state more than 5 days after the deadline the controllership published in the close calendar. A delayed close cascades: the board pack is late, the 10-Q or statutory filing risks slipping, intercompany cannot be eliminated, and the next period cannot open cleanly. Each row in the feed is a single ledger-period that has breached its deadline, so finance can act on the specific book that is stuck rather than chasing a single summary number.
| What it counts | Each row is one ledger-period combination whose GL period status is not Closed (still Open, or stuck in a partial / pending close) more than 5 calendar days past the deadline set in your close calendar. The feed lists the ledger, the period name, the days past deadline, and the current period status from Oracle Fusion. |
| Why 5 days | Most Fortune 500 close calendars target a 3 to 5 working-day soft close. A breach beyond day 5 is the point at which a slip stops being normal variance and starts to threaten downstream reporting and filing dates. |
| Business Unit scope | Respects the dashboard’s selected Business Unit and Ledger filter. By default watches every primary, secondary, and reporting ledger the connected role can see. |
| Time window | RT (real-time alert feed, re-evaluated each sync) |
| Alert trigger | close deadline >5d past - any ledger-period more than 5 days late raises a feed entry |
| 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 retailer runs Oracle ERP Cloud across three primary ledgers: US Retail Inc (USD), UK Retail Plc (GBP), and EU DTC NV (EUR). The published close calendar set the Mar 26 period deadline at 06 Apr 26 (working day 4). On 12 Apr 26 the Nerve Centre feed shows two ledgers still not closed.| Ledger | Period | Deadline | Days past | Period status |
|---|---|---|---|---|
| US Retail Inc (USD) | Mar-26 | 06 Apr 26 | 6 | Closed |
| UK Retail Plc (GBP) | Mar-26 | 06 Apr 26 | 6 | Open |
| EU DTC NV (EUR) | Mar-26 | 06 Apr 26 | 6 | Open |
- Only the breached rows appear in the feed. US Retail Inc closed on 11 Apr 26 (day 5), so it cleared before the 5-day breach and never raised an entry. The feed surfaces UK Retail Plc and EU DTC NV, the two books actually holding up consolidation.
- The root cause is upstream, not in GL itself. Both EUR and GBP ledgers were waiting on subledger transactions to finish accounting. Pair this feed with Subledger-to-GL Posting Failed (any source) and Open (Unposted) Journals; a period cannot close while subledger events are still unaccounted.
- Consolidation is blocked. The Financial Consolidation Hub cannot eliminate intercompany and produce the consolidated reporting ledger until all contributing primary ledgers are closed. Two late books mean the whole group pack is late, which is why owner is on the role list alongside finance.
- The feed clears row by row. As each ledger reaches Closed status, its row drops out of the feed on the next sync. There is no single number to “improve”; the goal is an empty feed by the next close.
Sibling cards merchants should reference together
A late close is almost always a symptom of something stuck upstream. Pair this feed with the cards that show what is blocking the books.| Card | Why pair it with GL Period Close Past Deadline |
|---|---|
| GL Period Close Status | The live status view of every ledger-period. This feed is the alert layer on top of it. |
| Period Close On-Time Rate (12mo) | The trailing trend. This feed is today’s breach; the rate is whether late closes are a pattern. |
| Open (Unposted) Journals | A period cannot close with unposted journals outstanding. Often the direct blocker. |
| Subledger-to-GL Posting Failed (any source) | Subledger events that never reached the GL hold the period open. Read this first when a close stalls. |
| Accrual Reversals Last Close | Unreversed accruals from the prior close can block the new period. |
| Intercompany Business Unit Imbalances | Unbalanced intercompany lines block consolidation, which keeps the group close late. |
| Oracle Fusion Health Score | The composite that a late close drags down sharply. |
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 (period status per ledger) General Accounting → Period Close → Close Monitor (the dashboard view of close progress across ledgers and subledgers) Reports and Analytics → OTBI → Financials → General Ledger - Period Status Real TimeThe Close Monitor shows each ledger and subledger as Open, Closed, or in transition. Any primary or reporting ledger whose period is still not Closed, compared against the deadline in your close calendar, is what this feed surfaces. Match the deadline used by the card to the date your controllership published, not to the system’s last day of the period. Common mistakes when comparing against Oracle’s own reports:
- Confusing the subledger close with the GL close. Receivables and Payables have their own period status. This feed tracks the GL accounting period; a subledger can be closed while the GL period is still open, and vice versa.
- Reading the calendar period-end as the deadline. The breach is measured against your published close deadline, not the last calendar day of the accounting period. Those are different dates.
- Ignoring reporting and secondary ledgers. A primary ledger can be closed while its reporting ledger is not. The feed watches all ledgers in scope.
| Reason | Direction | Why |
|---|---|---|
| Deadline source | Either | The card measures against the close-calendar deadline you configured. If Oracle’s Close Monitor is read against the calendar period-end instead, the days-past figure differs. |
| Ledger scope | Either | The feed spans every ledger in the dashboard filter; a single-ledger view in Oracle shows fewer rows. |
| Status sampled at sync | Card lagging | If a ledger closes between syncs, its row persists in the feed until the next refresh. |
| Soft close vs hard close | Either | A period marked Close Pending in Oracle may still appear in the feed until it reaches final Closed status, depending on how your controllership defines “closed”. |