Finance Workflow Examples · GL and close · Tier 1 · first governed workflows
Balance sheet lead sheet pack with flux commentary
Thirty-plus account-group tabs, current versus prior month by company, each tied to a summary and initialled by a reviewer. The hours are large and the AI's job is bounded by the tie-outs.
Current effort: Monthly, eight to sixteen hours · Any consolidating group.
On the one-page 1113 Workflow Card
The 1113 Workflow Card is a structured way to examine one recurring task before deciding where AI belongs: seven fields, one page. It is not, by itself, a production specification, execution log, evidence that a review occurred, or control certification.
- 01 · Purpose and triggerWhy the task exists, when it starts, and what business outcome it supports.
Give the reviewer a balance-sheet lead sheet per account group, tied to the summary, with the month's movements explained, so every sheet can be initialled before the close is signed off. Starts when the period is closed in the consolidation system.
- 02 · Inputs and permissionsWhat comes in, where it comes from, its sensitivity, and whether it may be used in the approved AI environment.
A live retrieval from the consolidation system driven by a year and month parameter block, plus last month's pack for the prior-period comparison. Consolidated financial data, confidential until reported. Whether the extract may enter the approved AI environment depends on the organization's policy; practice or sanitized files are used until that is confirmed.
- 03 · Current stepsWhat the person does today, in order.
Roll the period, refresh every tab, tie each tab to the summary, run the validation tab, write the movement commentary per account group, and assemble the 'what changed' summary for the reviewer.
- 04 · Rules, judgment, and AI’s roleWhat must remain deterministic, where judgment is required, and exactly what AI prepares.
Deterministic (computed in code, the same answer every time): The retrieval, the roll-forward, the tie of each tab to the summary, and the validation tab. They either tie or they do not.
Needs judgment: Whether a movement is expected given what happened in the business, and which movements deserve a sentence in the summary.
AI prepares: Draft the flux commentary per tab from the movements and the prior commentary, flag movements outside the usual range, and draft the one-page 'what changed' summary. It does not touch the tie-outs.
- 05 · Output and downstream useWhat is produced, who uses it, and whether it informs a decision or changes another system.
The pack, with a validation tab, draft movement commentary per tab, and a 'what changed' summary. Used by the reviewer to initial each lead sheet and by the controller for the close sign-off; it informs the sign-off and changes no system.
- 06 · Checks, exceptions, and responsibilityWhat a person reviews, how errors are identified, what happens when something is wrong, and who remains accountable.
The reviewer initials each lead sheet, looking for unexplained movements and tabs that do not tie. Commentary is a draft until they do. A tab that fails validation stops the pack until it is fixed. The controller remains accountable for the close.
- 07 · Evidence and next decisionCurrent effort, expected benefit, quality measure, test result, and the decision to continue, revise, decompose, or stop.
Current effort: eight to sixteen hours by hand each month. Expected benefit: the commentary and summary drafting shrink, with the tie-outs unchanged; a hypothesis until measured. Quality measure: every tab ties, every initialled sheet has commentary the reviewer accepted, and no accepted commentary explains a movement the tie-out should have caught. Test result: illustrative example, not yet tested in your environment. Next decision, continue, revise, decompose, or stop: to be established during evaluation.
Control in this example. The pack informs the close sign-off. Nothing is posted or adjusted from it.
AI handles defined preparation. A person reviews. Your controls remain in place.
Where it goes wrong
Commentary that explains a movement the tie-out should have caught. Tie first, explain second.
Why it lands in a room
Very visual. A controller sees their own pack on the screen and knows the hours.
This example illustrates the method. It is not a production-ready workflow, a software specification, or a substitute for your organization’s policies, controls, and approved technology environment.