Irvine Analytics Get in touch
Analytics Catalog/Workday/Financials/General ledger/Close status
Explore the catalogModulesGeneral ledgerJournal statusIntercompany
Workday · Financials · Report

Where the close days actually go

Every close ends; few are understood. May took thirty tasks and four days, twenty-eight tasks on plan, and the two late ones each traced to a control elsewhere in this module. When the calendar is data, the retrospective writes itself.

RuleRun the close as a calendar that is data: every task with its planned day and actual day, so where the days go is a report, not a recollection.
Nevermeasure the close only by its end date. A five-day close that finishes on day five every month can still hide two tasks that ran late and got absorbed.
Thirty tasks the close, enumerated Four days each task lands somewhere The two late ones absorbed, but recorded
The close always ends. The question this table answers is what it cost to end on time, and which tasks to fix.
◆ May close, by daythirty tasks, four days, two late.
Close dayTasks completed
Day 112
Day 29
Day 36
Day 43
Close tasks30
Against planTasks
On their planned day28
Late, absorbed by day 42
Close tasks30

Both partitions close on the same thirty. The two late tasks were the intercompany difference and one supplier accrual waiting on the stuck journals: the close calendar is where every other control in this module shows up as time. Sample values are illustrative, never client data.

◆ The owned answertasks as rows, months as a trend.

Each task lands with planned day, actual day, and owner, so the close trends: which tasks are always late, which days are overloaded, and what a process change actually bought. Anecdote becomes a series, and the series is drawn on the GL star’s calendar.

Use case
Problem
The close ends on time and nobody can say what it cost: late tasks get absorbed silently and every retrospective runs on memory.
What we build
The close calendar as data: every task with planned and actual days, partitioned by day and by lateness, trended month over month.
What you get
A close you can improve on purpose: chronic late tasks named, overloaded days visible, and process changes measured instead of felt.
Which close task is always late?
We build the close calendar that answers from data, not memory.
Talk to us
Terms on this page
GL
General ledger, the books this module lands and proves.
close task
One enumerated step of the period close.
close calendar
Tasks against planned days; here, data.
absorbed lateness
A late task hidden by an on-time close.
close trend
The same calendar, month over month.