Your close checklist as code, evidence generated as you go.

The close checklist usually lives in a spreadsheet, and its reliability depends on the person driving it. If a step is skipped or run out of order, the error surfaces days later, and the evidence an auditor wants has to be reconstructed after the fact.

1. 1Schedule trigger runs each morning around period start.
2. 2Code block checks the business-day calendar and continues only on the first business day, so a weekend or holiday does not kick off the close early.
3. 3Sub-workflow blocks run each close task, reconciliations, accruals, checks, as its own reusable workflow.
4. 4Parallel block runs independent tasks at the same time so the close does not wait in a single line.
5. 5Condition block gates each dependent step on the prior one passing, enforcing the order.
6. 6Data Table block tracks the status and captures the evidence for each task as it completes.
7. 7Slack block gives the controller a live view of close readiness.

The close runs the same way every month, in the right order, with evidence captured as each step completes rather than reassembled later. The controller sees readiness in real time instead of chasing status.