App catalogue Finance

Month-end close checklist

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.

HIERARCHY · MONTH-END CLOSE CHECKLISTAccountingL1: accountantsscreen · usersL2: accounting managerscreen · usersControllingL1: business controllersscreen · usersL2: group controllerscreen · usersFinance leadershipL1: CFOscreen · usersa person created at a level is assigned their parent-level and child-level users at the same timeTrigger and flow criteriaThe close calendar starts on the last working day of each month for every entity, or when the accounting manag…
The hierarchy: functions, levels, and the criterion that starts the flow. Each level carries a screen and its people.
7 days
of configuration to a production-grade version
estimate
6
screens, desktop and mobile
catalogue
4
data handlers, read in place
catalogue
4
systems with a page for this app
catalogue
3
clocks with escalation
catalogue
What it does

Today, and with the app

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.

Who takes part

Collaborative app: levels first, then screens per level, then people, then the flow and trigger criteria

FunctionLevelDoes
AccountingLevel 1: accountantscomplete tasks, post journals, attach evidence
AccountingLevel 2: accounting managerreviews and signs each entity
ControllingLevel 1: business controllersreview results by cost center and confirm allocations
ControllingLevel 2: group controllersigns the consolidation
Finance leadershipLevel 1: CFOsigns the close
Screens

6 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 My tasksthe owner's tasks for today and overdue, with entity, dependency status and the ledger check result; complete button
S02 Task detaildescription, evidence upload, journal preview with account, cost center and amount; post button; comment thread
S03 Entity sign-offtask list for the entity by day with status and evidence; sign or return
S04 Cost center reviewresults by cost center against plan, items still to post, allocations run; confirm
S05 Close boardentities by working day, tasks done, blocked and late; drill to the dependency
S06 Calendar setuptask templates, owners, days and dependencies per entity; copy to next period
Data handlers

4 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
Journal linejournal lines and posting status by entity, period and userS/4HANA · Oracle Fusion · Workday · Snowflake
Supplier invoicesupplier invoices still to be posted for the periodS/4HANA · Oracle Fusion · Workday · Snowflake
Capital requestassets under construction to settleS/4HANA · Oracle Fusion · Workday · Snowflake
Cost centerthe cost centers each entity closesS/4HANA · Oracle Fusion · Workday · Snowflake

Written back

ObjectWhat changes
Journal lineaccrual, reclassification and correction journals posted from a task through the released journal interface; the document number stored on the task
The flow

From the trigger to the last write

THE FLOW · MONTH-END CLOSE CHECKLIST1Calendar openedtasks created per entityfrom the template; ownersnotified with their day 1tasks2Ledger taskscompletea task closes itself whenits ledger condition holds,for example 0 supplierinvoices left to post3Journals postedaccruals and correctionsposted from S02; documentnumbers attached4Entity signedevery task done or waivedwith a reason; accountingmanager signs by workingday 45Consolidation signedgroup controller signs byworking day 6; CFO signs byday 7
Each step and the criterion that moves it.

Start: The close calendar starts on the last working day of each month for every entity, or when the accounting manager opens it early.

StepMoves when
Calendar openedtasks created per entity from the template; owners notified with their day 1 tasks
Ledger tasks completea task closes itself when its ledger condition holds, for example 0 supplier invoices left to post
Journals postedaccruals and corrections posted from S02; document numbers attached
Entity signedevery task done or waived with a reason; accounting manager signs by working day 4
Consolidation signedgroup controller signs by working day 6; CFO signs by day 7
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
chk_ledger_taskon 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_journalon click → call the journal interface with the lines on S02 → store the document number, mark the task complete
btn_sign_entityon click → check that every task is complete or waived → lock the entity, notify the group controller
grd_boardon open → read task status for every entity → show late tasks first with their blocking dependency

Clocks

StepTime limit and escalation
Taskits working day; then the owner is reminded and the task turns red on the board
Entity sign-offworking day 4, then the entity escalates to the group controller
Group closeworking day 7, then the CFO sees the open items with the reason

Measures

working days to close per entitytasks completed by the ledger checktasks late by ownerjournals posted after day 3
A day with the app

Illustrative

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.

illustrative scenario · Month-end close checklist
On your systems

One page per system

The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.

Other systems connect through the same handlers; see how SmartApps connect.

Terms on this page

Working dayA counted day of the close calendar, starting at 1 on the first working day after period end.
Ledger checkA criterion on live ledger data that decides whether a task is complete, for example 0 supplier invoices left to post.
Waived taskA task closed by the accounting manager with a reason, for example because the entity had zero activity of that kind this period.
Questions

How long does it take to have this running?

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.

Which system does it run on?

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.

Who takes part from outside the company?

Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

See this app on your data

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.