Sequence the work by entity and period.
Close tasks carry a named owner, due date, status, and sequence so dependencies surface before they become late.
Feature · Month-End Close
Close the period with evidence, not status meetings.
Move from open tasks to reconciled balances and approved adjustments while every dependency stays linked to its period and entity.
Work sequencedOwner and due date made visible
Balance explainedDifference retained for review
Change approvedReason tied to journal evidence
Period governedLock follows the complete trail
The operating sequence.
Each stage produces evidence the next stage can inspect rather than another disconnected status.
Explain the account balance.
Each reconciliation retains its controlled account, reporting entity, fiscal period, owner, review status, and unresolved difference.
Propose the correction with support.
The adjustment reason and amount remain linked to the reconciliation and balanced journal that substantiate the change.
Complete the trail before the period closes.
The governed state changes only after tasks, balances, review, and approved corrections support the close decision.
Automation keeps its boundary.
Workflow graphs ship inactive so finance can inspect their trigger, mutation, and approval class before activation.
Escalate without moving the period.
An overdue blocked task creates an internal controller escalation and leaves balances and period state unchanged.
Route the evidence.
An In Review reconciliation moves to the accountable controller queue without changing the submitted difference.
Post only behind approval.
The consequential workflow validates the linked journal before marking the accounting change posted.