Workflows · FP&A · Tier 2 · the 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.
By hand: Quarterly or annual, eight to twenty hours · Municipalities, utilities, universities, any capital-heavy organization.
The card, as it runs by hand
- Input
- ERP capital actuals and the planning-system forecast, per project, with prior carry-forward and the exclusion list.
- What I do to it
- Apply the rules per project. Exclude amendments, inter-project transfers, and flagged postings. Fill missing organizations. Reconcile the report to the data form.
- Output
- Carry-forward by project with the rule trail, and a report-versus-form tie-out.
- Who checks
- The capital planning analyst confirms per project.
- How often
- Quarterly or annually.
- How long
- Eight to twenty hours by hand.
- How long now
- Measured in the course after the first governed run, per card. Not estimated here.
As a governed workflow
- Stays in code
- The rules. All of them.
- The AI does
- Explain each project's carry-forward in a sentence, flag rule exceptions, and reconcile report versus form in words.
- A person still
- The analyst confirms each project. Nothing writes back to the planning system without that.
- The log
- Rule version, projects processed, exceptions, confirmations.
AI does the preparation. A named person approves it. Nothing posts to the books without that approval, and every run is recorded.
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.