Workflow Examples
Finance Workflow Examples
See how the 1113 Workflow Card can be used to examine recurring Finance work. Each example shows the task’s purpose, inputs, current steps, rules and judgment, appropriate role for AI, human checks, and the decision that follows a bounded test.
These examples illustrate the method. They are not production-ready workflows, software specifications, or substitutes for your organization’s policies, controls, and approved technology environment.
The 1113 Workflow Card
Seven fields that make the work, AI’s role, and human responsibility explicit.
The 1113 Workflow Card is a one-page, structured way to examine one recurring task before deciding where AI belongs. It documents the intended design and the next decision: continue, revise, decompose, or stop. It is not, by itself, a production specification, execution log, evidence that a review occurred, or control certification.
01
Purpose and trigger
Why the task exists, when it starts, and what business outcome it supports.
02
Inputs and permissions
What comes in, where it comes from, its sensitivity, and whether it may be used in the approved AI environment.
03
Current steps
What the person does today, in order.
04
Rules, judgment, and AI’s role
What must remain deterministic, where judgment is required, and exactly what AI prepares.
05
Output and downstream use
What is produced, who uses it, and whether it informs a decision or changes another system.
06
Checks, exceptions, and responsibility
What a person reviews, how errors are identified, what happens when something is wrong, and who remains accountable.
07
Evidence and next decision
Current effort, expected benefit, quality measure, test result, and the decision to continue, revise, decompose, or stop.
Task size
Start with a task—not an entire function.
A card-sized task has one recognizable trigger, one main input set, one main output, and one person or role responsible for reviewing the result.
Broad functions and end-to-end processes are too large for one Workflow Card. If a task has several triggers, unrelated outputs, or separate owners, decompose it before deciding where AI belongs. Learning to find the right boundary is part of the method.
If your task is still too large, that is not a failed exercise. “Decompose” is a valid and useful result.
Candidate work
The kinds of work the method is designed to examine
The strongest starting points are recurring tasks with recognizable inputs and outputs, repeated preparation, reviewable results, and a person who already understands the work. Common Finance and operations candidates include:
Prepare and explain
- Reconciliations and exception explanations
- Variance and flux commentary
- Reporting packages
- Forecast-workbook preparation
- Close-status summaries
Extract, restructure, and compare
- Data extraction and restructuring
- Document review
- Classification and mapping proposals
- Procedure and policy comparison
Track and communicate
- Vendor-document tracking
- Recurring correspondence and follow-up
These are starting points, not a promise that every example is appropriate in every organization. Data sensitivity, access, consequences, reviewability, and company policy still determine what should proceed.
GL and close
GL and close
- View the Workflow Card
Tier 1 · first governed workflows · Monthly, three to six hours
AP sub-ledger to GL control-account reconciliation
The reconciliation every ERP shop has: open payables by company and offset, tied to the trial balance, with every difference explained as timing or error. The approval email already exists in the process.
- View the Workflow Card
Tier 1 · first governed workflows · Monthly, three to six hours
AR sub-ledger reconciliation with aging buckets
The receivables twin of the AP rec, with aging buckets, credit memos and unapplied cash as negative open amounts, and receipts posted after the as-of date backed out.
- View the Workflow Card
Tier 1 · first governed workflows · Monthly, eight to sixteen hours
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.
- View the Workflow Card
Tier 2 · company-specific long tail · Daily during close, two to four hours a month
The close calendar as an eight a.m. status note
Tasks by month and quarter, owner, force-check flag, timing, responsibility, kept by hand. Vendors sell task managers; nobody sells the agent that reads yours and writes the morning note.
FP&A
FP&A
- View the Workflow Card
Tier 1 · first governed workflows · Monthly, four to eight hours per organization
Monthly forecasting and analysis workbook, one tab per cost centre
The purest 'same structure repeated by period' process: a parameters tab, fund or department summaries, and one tab per cost centre with lookups to the chart of accounts and variance commentary.
- View the Workflow Card
Tier 2 · company-specific long tail · Annual plus forecast refreshes, about two person-weeks
Annual lease budget built from the lease sub-ledger
Lease master and amortization tables from the ERP, expiries in the horizon, business confirmations by email, FX and allocations, all rebuilt into the corporate budget strip. No vendor sells an agent for this.
- View the Workflow Card
Tier 2 · company-specific long tail · Quarterly or annual, eight to twenty hours
Capital carry-forward with exclusion rules
Prior-year carry-forward plus in-year forecast, recalculated per project with exclusions by account type: amendments, inter-project transfers, flagged postings. The story every capital analyst has lived: the report shows one number and the form shows another.
Finance systems
Finance systems
- View the Workflow Card
Tier 1 · first governed workflows · Weekly, one to two hours, usually skipped
The data-change audit log, summarized weekly
Thousands of rows a month of who changed what: date, form, action, user, old value, new value. The trail is captured and nobody reads it. Summarizing it is low risk and high credibility.
- View the Workflow Card
Tier 1 · first governed workflows · Monthly, one to two hours
Missing-mapping report with proposed mappings for approval
A scheduled report already lists accounts in actuals that are not in planning. AI proposes the mapping from the descriptions; a person approves before the table changes.
- View the Workflow Card
Tier 3 · demonstrate carefully; automate last, if at all · Annual plus amendments, two to four hours
Budget write-back to the ERP, only after approval
Export by entity group, transform to the ERP layout, stage through the loader with logs and bad-row files, import. The purest illustration of the model: the approval is the trigger, the pipeline is deterministic, and no unattended agent touches the ledger.
Operations
Operations
- View the Workflow Card
Tier 2 · company-specific long tail · Annual per vendor, fifteen minutes each, hundreds of vendors
Vendor insurance and WCB clearance expiry tracking
Certificates of insurance, WCB clearance letters, and banking forms arrive as PDFs by email. Someone reads the expiry, updates a tracker, and sends the renewal request. Universally recognized, never automated.
What to examine first
Three tiers of recurring work.
Tier 1
High frequency, rule-bound, and the output is a check or a report. Nothing lands in a ledger. Reconciliations, lead sheets, load validation, the audit log. Start here.
Tier 2
The long tail no vendor ships software for, because it is specific to how your company works. Lease budgeting, capital carry-forward, vendor expiries, the close digest. Where a trained team earns its keep.
Tier 3
Touches the book of record or needs judgment. Journal preparation, reclass entries, budget write-back. Taught as the clearest picture of the rule, automated last if at all, and always with a named person as the trigger.
Choosing where to start is the last part of The Governed Workflow: the team scores its own recurring work and picks two tasks to test first.
Recognize this work? Learn the method in The Governed Workflow