Finance Workflow Examples · FP&A · Tier 2 · company-specific long tail
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.
Current effort: Annual plus forecast refreshes, about two person-weeks · Energy, retail, telecom, transport, real estate.
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.
Rebuild the lease budget strip from the lease sub-ledger each budget cycle, with renewals and additions confirmed by the business, so the corporate budget carries the right lease expense by segment and month. Starts when the budget calendar opens the lease schedule, and again at each forecast refresh.
- 02 · Inputs and permissionsWhat comes in, where it comes from, its sensitivity, and whether it may be used in the approved AI environment.
The lease master and amortization tables from the ERP, the list of leases expiring in the horizon, email confirmations from the business, FX rates, allocation percentages, and manual adjustments. Contract terms and counterparties; confidential. 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.
Wipe the prior budget. Rebuild schedules for renewals and additions. Tag manual rows versus system rows. Apply FX and allocations. Pivot into the budget strip by line, segment, and month. Produce budget-to-actual by lease, segment, and quarter. Write the assumption notes. Collect the two signatures on the approval block.
- 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): Amortization, FX, allocations, and the strip layout. All code, with the rule version recorded.
Needs judgment: Whether an expiring lease will renew, on what terms, and which manual adjustments are still valid this cycle.
AI prepares: Draft the confirmation requests to the business and track the replies, draft the assumption notes, reconcile manual rows against system rows and list what changed, and draft the variance explanations. It does not compute the schedules.
- 05 · Output and downstream useWhat is produced, who uses it, and whether it informs a decision or changes another system.
The strip for the planning manager, the schedules, the assumption notes, and the reconciliation of manual to system rows. Used to load the corporate budget after approval; the load itself is a separate, approved step.
- 06 · Checks, exceptions, and responsibilityWhat a person reviews, how errors are identified, what happens when something is wrong, and who remains accountable.
The corporate accounting supervisor and manager sign the approval block, exactly as today. Any lease without a confirmation is an exception carried on the notes. A manual row with no owner is removed, not assumed. The supervisor remains accountable for the strip.
- 07 · Evidence and next decisionCurrent effort, expected benefit, quality measure, test result, and the decision to continue, revise, decompose, or stop.
Current effort: about two person-weeks by hand each cycle. Expected benefit: the chasing, the notes, and the reconciliation are the weeks; a hypothesis until measured. Quality measure: the strip ties to the schedules, every expiring lease has a confirmed assumption, and the approval block is signed. Test result: illustrative example, not yet tested in your environment. Because this is annual, large, and signed, the usual recommendation is to test a reconciliation first. Next decision, continue, revise, decompose, or stop: to be established during evaluation.
Control in this example. The same two signatures on the same approval block. Nothing loads to the budget without them.
AI handles defined preparation. A person reviews. Your controls remain in place.
Where it goes wrong
Treating it as a first automation. It is annual, large, and signed. Do the reconciliation first; do this once the team trusts the pattern.
Why it lands in a room
Every IFRS 16 lessee has it, it lives in one person's head, and the sign-off block is already a control model.
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.