Finance Workflow Examples · FP&A · Tier 2 · company-specific long tail
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.
Current effort: Quarterly or annual, eight to twenty hours · Municipalities, utilities, universities, any capital-heavy organization.
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.
Calculate each project's capital carry-forward under the exclusion rules and reconcile it to the planning form, so the capital plan carries a defensible number per project. Starts at quarter end and at the annual plan.
- 02 · Inputs and permissionsWhat comes in, where it comes from, its sensitivity, and whether it may be used in the approved AI environment.
ERP capital actuals and the planning-system forecast per project, the prior carry-forward, and the exclusion list (amendments, inter-project transfers, flagged postings). Internal project data. 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.
Apply the rules per project. Exclude amendments, inter-project transfers, and flagged postings. Fill missing organizations. Reconcile the report to the data form. Explain each project's number to its analyst.
- 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 exclusion rules and the carry-forward arithmetic. All of them, in code, with a version number.
Needs judgment: Whether a flagged posting really belongs in the exclusion, and whether a project's number is plausible given its status.
AI prepares: Explain each project's carry-forward in a sentence from the rule trail, flag rule exceptions, and reconcile report versus form in words. It does not apply the rules.
- 05 · Output and downstream useWhat is produced, who uses it, and whether it informs a decision or changes another system.
Carry-forward by project with the rule trail, and a report-versus-form tie-out. Used by the capital planning analyst to confirm each project before the plan is loaded; it informs the load and does not perform it.
- 06 · Checks, exceptions, and responsibilityWhat a person reviews, how errors are identified, what happens when something is wrong, and who remains accountable.
The capital planning analyst confirms per project. A project whose report and form disagree is an exception until explained. A rule change is versioned before it is used. The analyst remains accountable for the plan numbers.
- 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 twenty hours by hand per cycle. Expected benefit: the per-project explanation and the tie-out narrative stop being hand-written; a hypothesis until measured. Quality measure: every project reconciles or carries an explained exception, and the rule version is recorded on the output. 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. Nothing writes back to the planning system without the analyst's confirmation per project.
AI handles defined preparation. A person reviews. Your controls remain in place.
Where it goes wrong
Rules that live in a spreadsheet nobody versions. Put them in code with a version number.
Why it lands in a room
Long-tail and painful, with a rule set that is obviously code.
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.