Month-end close orchestration
Run the sequence of entries, reconciliations and reviews that produce a final set of books, against a fixed calendar and owner list.
varies by archetype
1The task exists in this business archetype but behaves differently. The note is the point of the edge: it must say how it differs, not merely that it does.
Credit loss provisioning sits on the critical path and cannot run until loan-level data is final, so the long pole of the close is a model run rather than a reconciliation. Close duration is bounded by model execution and review, and compressing it means changing the model, not the calendar.
consumes
3A canonical data object the task needs as input.
owned by
1The business-partner org unit accountable for the task.
runs in
1The end-to-end shared-services process the task sits inside.
serves
1The verb-level intent the task exists to satisfy.
performed in
2Software the task is actually carried out in.
Relationships pointing at this node.
performed by
2A job title someone actually holds does this work.
Unresolved from the source registry
not yet modelledFree-text strings from the source spreadsheet that have not been resolved to a node. Preserved verbatim so nothing is silently dropped — these are backlog, not content.
Produces: Close calendar · Close checklist