Runs the close as a shared checklist per entity and day, with each task's status read from the ledger and every sign-off recorded.
Today the close runs on a spreadsheet with 300 rows, updated by email and in the daily stand-up, and the controller checks the ledger by hand to see whether a task is really done. Sign-offs live in mail threads, and the group learns that an entity is late on day 4.
The app holds the close calendar: every task per legal entity, its working day, its owner and the tasks it depends on. Tasks tied to the ledger complete themselves when the data shows the condition, for example when every supplier invoice for the entity is posted, when all cost center allocations have run or when the assets under construction are settled. Accountants attach evidence and post accruals from the task, the accounting manager signs each entity, controllers review the results by cost center, and the CFO signs the close. The board shows every entity against the calendar, hour by hour, and the group controller sees which dependency holds a late task.
| Function | Level | Does |
|---|---|---|
| Accounting | Level 1: accountants | complete tasks, post journals, attach evidence |
| Accounting | Level 2: accounting manager | reviews and signs each entity |
| Controlling | Level 1: business controllers | review results by cost center and confirm allocations |
| Controlling | Level 2: group controller | signs the consolidation |
| Finance leadership | Level 1: CFO | signs the close |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 My tasks | the owner's tasks for today and overdue, with entity, dependency status and the ledger check result; complete button |
| S02 Task detail | description, evidence upload, journal preview with account, cost center and amount; post button; comment thread |
| S03 Entity sign-off | task list for the entity by day with status and evidence; sign or return |
| S04 Cost center review | results by cost center against plan, items still to post, allocations run; confirm |
| S05 Close board | entities by working day, tasks done, blocked and late; drill to the dependency |
| S06 Calendar setup | task templates, owners, days and dependencies per entity; copy to next period |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Journal line | journal lines and posting status by entity, period and user | S/4HANA · Oracle Fusion · Workday · Snowflake |
| Supplier invoice | supplier invoices still to be posted for the period | S/4HANA · Oracle Fusion · Workday · Snowflake |
| Capital request | assets under construction to settle | S/4HANA · Oracle Fusion · Workday · Snowflake |
| Cost center | the cost centers each entity closes | S/4HANA · Oracle Fusion · Workday · Snowflake |
| Object | What changes |
|---|---|
| Journal line | accrual, reclassification and correction journals posted from a task through the released journal interface; the document number stored on the task |
Start: The close calendar starts on the last working day of each month for every entity, or when the accounting manager opens it early.
| Step | Moves when |
|---|---|
| Calendar opened | tasks created per entity from the template; owners notified with their day 1 tasks |
| Ledger tasks complete | a task closes itself when its ledger condition holds, for example 0 supplier invoices left to post |
| Journals posted | accruals and corrections posted from S02; document numbers attached |
| Entity signed | every task done or waived with a reason; accounting manager signs by working day 4 |
| Consolidation signed | group controller signs by working day 6; CFO signs by day 7 |
| Component | Trigger → action → outcome |
|---|---|
| chk_ledger_task | on schedule every 15 minutes → run the task's ledger check, for example the count of invoices left to post → mark the task complete and release the tasks that depend on it |
| btn_post_journal | on click → call the journal interface with the lines on S02 → store the document number, mark the task complete |
| btn_sign_entity | on click → check that every task is complete or waived → lock the entity, notify the group controller |
| grd_board | on open → read task status for every entity → show late tasks first with their blocking dependency |
| Step | Time limit and escalation |
|---|---|
| Task | its working day; then the owner is reminded and the task turns red on the board |
| Entity sign-off | working day 4, then the entity escalates to the group controller |
| Group close | working day 7, then the CFO sees the open items with the reason |
Names, places and figures are illustrative; the pattern is the catalogue's.
On the first working day of July, Kenji, an accountant for the Osaka entity, opened S01 at 08:30 and saw 14 tasks, 5 of them already complete because the ledger checks had passed overnight. He posted 3 accruals from the task screen before 11:00, and the document numbers appeared beside each one. The board showed the group controller in Frankfurt that 11 of 12 entities were on day 2 by 16:00 and that the Brazilian entity was waiting on 2 invoices, which were posted the next morning; the CFO signed on working day 6.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Journal line read from ACDOCA (universal journal); also on SAP ECC.
Open the S/4HANA page →Journal line read from General Ledger REST: journals · BICC GL journal lines extract; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Journal line read from Financial_Management: Get_Journals; HCM / finance.
Open the Workday page →Journal line read from CONFORMED.JOURNAL_LINE · HISTORY.JOURNAL_LINES; lakehouse.
Open the Snowflake page →Other systems connect through the same handlers; see how SmartApps connect.
About 30 minutes to a first running screen on your live rows, and 7 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.
Any of SAP S/4HANA, Oracle Fusion Cloud, Workday, Snowflake, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.
Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.