Close Cycle Time
Compare target and confirmed close dates by entity, with period-by-period trends.
Close planning
Give every close a clear calendar, scope and owner.
not Locked
- CC-1608: CP-55279, 15 Sep to 21 Sep, NotStarted
- CC-3963: CP-41570, 12 Sep to 20 Sep, InProgress
- CC-9851: CP-24149, 24 Sep to 01 Oct, Reviewed
- CC-8589: CP-14873, 16 Sep to 18 Sep, LockPending
- CC-2301: CP-64563, 24 Sep to 26 Sep, LockFailed
- CC-8538: CP-97418, 09 Sep to 12 Sep, ReopenPending
Set the calendar around the business
Period Close Calendar shows the start, end and target close date for each period. Admin configures the fiscal calendar, holiday source, timezone and workday rules with Controller / CFO. Resolve dates before launch and retain the calendar snapshot. An entity’s ledger-period key supplies its stable identity; a familiar period code is only the display label. Monthly, quarterly and annual scopes must be explicit so their evidence and downstream requests cannot be confused.
Assign work and dependencies
Snapshot the effective task descriptions, required flags, owners, reviewers and dependency edges. ClosingTaskDependencies distinguishes a predecessor needed before work starts from one needed before work finishes. Reject circular dependencies and missing people before the checklist is released. Close Manager can reassign work with a recorded reason, while the prior assignment stays attributable. My Closing Tasks then shows each person the work they can act on, with due dates and related reconciliation or journal evidence.
YouStatusNotStartedInProgressSubmittedBlocked
| Task Code | Close Period | Name | Category | Due Date |
|---|---|---|---|---|
| TC-199 | CP-66563 | Task 460 | Cash | 29 Sep |
| TC-587 | CP-11438 | Task 694 | AR | 11 Sep |
| TC-705 | CP-87825 | Task 657 | AP | 06 Sep |
| TC-375 | CP-94439 | Task 550 | Inventory | 16 Sep |
| TC-568 | CP-84543 | Task 624 | FixedAssets | 06 Sep |
| TC-606 | CP-65037 | Task 155 | Payroll | 19 Sep |
Track readiness across entities
Close Status Heat-Map brings period status, task completion, reconciliations and open issues together. Read those totals as a way to find the remaining work; a high completion count does not itself authorize a lock. Reviewed, LockPending and Locked describe different outcomes. Keep an entity with a connector failure visible alongside one with unfinished accounting work. The close manager can explain the next action from the underlying records instead of interpreting an ambiguous green status.
StatusNotStartedInProgressReviewedLockPendingLockFailedReopenPendingReopenFailedReopened
| Period Code | Entity | Status | Target Close Date | Task Count |
|---|---|---|---|---|
| PC-511 | ENT-103 | NotStarted | 13 Sep | 31 |
| PC-895 | ENT-511 | InProgress | 17 Sep | 34 |
| PC-620 | ENT-472 | Reviewed | 06 Sep | 22 |
| PC-795 | ENT-737 | LockPending | 09 Sep | 14 |
| PC-548 | ENT-986 | LockFailed | 18 Sep | 28 |
| PC-901 | ENT-830 | ReopenPending | 23 Sep | 31 |
Rollout checks
Pilot the calendar across a holiday and a weekend, including a task due after period end. Create the same launch request twice and confirm that it produces one checklist population. Try a missing reviewer, a circular dependency and a template from another entity. Each invalid case should stop the affected launch before incomplete work is published. Compare the retained source snapshot with the assignments shown to the team.
Before rollout, agree the entity and period population, source-system ownership and the people assigned to each decision. Preserve existing accounting identifiers during migration and reconcile imported totals to the owning system. A preview on this website does not provision a live connector or grant a user financial authority. In Proto, configure the corresponding records and actions, test permitted and rejected operations through the API as well as the interface, and retain the implementation evidence before releasing the application.
Record the accepted pilot evidence with the exact configuration revision so subsequent changes can be compared to the behavior Finance reviewed.
Modules
-
Close planning
Give every close a clear calendar, scope and owner.
-
Task management
Keep close work, evidence and handoffs in one place.
-
Reconciliations
Connect every account balance to evidence and independent review.
-
Journal and variance review
Review accounting entries and explain the movements that matter.
-
Control testing
Keep control tests, findings and follow-up connected to the close.
-
Sign-off and audit
Keep final decisions separate from confirmed ledger locks.
Reports
All reportsRoles and permissions
Coordinate the close, resolve assignments and monitor readiness before requesting financial sign-off.
Read only explicitly granted entity-period evidence through an active, unexpired, unrevoked grant.
Related processes
Launch and run the close
Turn the close calendar into assigned, independently reviewed work.
5 stages · 1 approval
Review journals and variance
Resolve entry reviews and explain required balance movements.
4 stages · 2 approvals
Sign off, lock and reopen
Approve a stable close basis and verify the ledger outcome.
6 stages · 3 approvals