Task Completion Burndown
Follow completed, submitted, blocked and remaining work, with drill-through to assignments and authorized exceptions.
Task management
Keep close work, evidence and handoffs in one place.
YouStatusNotStartedInProgressSubmittedBlocked
| Task Code | Close Period | Name | Category | Due Date | Status |
|---|---|---|---|---|---|
| TC-199 | CP-66563 | Task 460 | Cash | 29 Sep | NotStarted |
| TC-587 | CP-11438 | Task 694 | AR | 11 Sep | InProgress |
| TC-705 | CP-87825 | Task 657 | AP | 06 Sep | Submitted |
| TC-375 | CP-94439 | Task 550 | Inventory | 16 Sep | Blocked |
| TC-568 | CP-84543 | Task 624 | FixedAssets | 06 Sep | NotStarted |
| TC-606 | CP-65037 | Task 155 | Payroll | 19 Sep | InProgress |
Work from an assigned checklist
My Closing Tasks focuses on the authenticated owner’s unfinished work. The task includes its category, due date, status, related reconciliation or journal review and any blocking reason. Accountant starts the assignment, prepares supporting work and submits the current revision. Another person’s task is not writable merely because its URL is known. An inactive assignee remains visible in history while Close Manager arranges a replacement for outstanding work.
Review the evidence before completion
The assigned reviewer inspects the submitted evidence and records the decision against the task revision. Owner and reviewer must be distinct authenticated people. Evidence can link to an approved reconciliation, a reviewed journal or an immutable supporting file. A dependency remains a real condition: downstream completion cannot bypass unfinished predecessor work. When the underlying evidence changes after review, retain the earlier decision and request the affected review again.
Resolve blockers and authorized exceptions
Late Tasks and Open Issues Log help Close Manager distinguish an overdue assignment from work that cannot proceed. A blocked task retains its reason and owner. Skipping required work needs a documented policy basis, a distinct Close Manager decision and Controller / CFO authorization; changing the status alone is insufficient. A permitted exception remains visible in the close evidence. Due-date changes and reassignments preserve their own audit trail without erasing the original handoff.
Statusnot Done or Skippedoverdue
| Task Code | Close Period | Name | Owner | Due Date |
|---|---|---|---|---|
| TC-704 | CP-17962 | Task 931 | JL | 08 Sep |
| TC-980 | CP-88656 | Task 237 | MA | 05 Sep |
| TC-663 | CP-12874 | Task 231 | EM | 05 Sep |
| TC-307 | CP-73716 | Task 265 | YZ | 12 Sep |
| TC-131 | CP-10711 | Task 853 | BW | 07 Sep |
| TC-670 | CP-18142 | Task 349 | JM | 29 Sep |
Rollout checks
Walk a task from assignment through submission and independent review, then change its evidence and verify that the affected decision cannot be reused. Test both dependency types and an attempted self-review. Exercise a required skip with and without the Controller authorization. Confirm that reminders identify the responsible person and do not mark work complete when an email is delivered.
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.
Prepare assigned reconciliations and independently review other assignments. Review journal entries within the effective threshold policy.
Prepare assigned close tasks and account reconciliations with supporting evidence.
Read the retained evidence independently. Concurrence is an explicitly scoped attestation, not management approval.
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
Test controls and resolve findings
Collect test evidence and document the actual disposition of findings.
4 stages · 2 approvals