Fpa Monthly Close
Use when running a month-end close, refreshing a forecast with the latest actuals, computing plan-vs-actual variance, or producing a "how did the month go" analysis in openfpa.
Install
$ agentstack add skill-jeffbrines-openfpa-fpa-monthly-close ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jeffbrines-openfpa-fpa-monthly-close) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Monthly Close (Operate)
Overview
Fold the latest actuals into the model, refresh the forward forecast from the last closed position, and explain the variance. The output is a narrative, not just a variance table - what changed, why, and what it means forward.
Core principle: A close that only reports numbers isn't done. The value is the explanation.
When to use
- Month-end actuals are available
- "How did we do vs plan?" / reforecast requests
Workflow
- Discover the company command. Run
openfpa entrypoint-list --kind close. Use a registered close command when one exists; otherwise build the workflow from the approved company architecture.
- Ingest the closed month's actuals (see fpa-configure-actuals).
- Establish the freeze line: closed months use actuals; the forecast resumes from the last closed balance. Never let a not-yet-closed month drive conclusions (see fpa-cfo-judgment).
- Recompute the forecast:
pyfpa.cashflow_from_config(cfg)after updating config with the new closed position. - Variance: compare actual vs plan for revenue, gross margin, EBITDA, and ending cash. For each material variance, state the driver (volume, price, cost ratio, timing).
- Pick a reforecast posture and say which you used:
- Plan - frozen forecast unchanged
- Latest estimate - actuals for closed months, plan forward from the last closed balance
- Run-rate - project the YTD actual pace forward
- Write the narrative: the 3 things that moved, the 3 risks forward.
Judgment checks (always)
- Is the "closed" month actually closed, or are accruals/COGS still posting?
- Did any account move because of a one-time/timing item? Separate it from run-rate.
- Multi-entity: is intercompany eliminated before you total?
Next
Close done → fpa-cash-runway (near-term liquidity), fpa-board-briefing (the writeup), and fpa-backtest-learn (score the prior forecast). Persistent or material misses feed fpa-research-loop for bounded challenger epochs.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: JeffBrines
- Source: JeffBrines/openfpa
- License: MIT
- Homepage: https://www.guiderail.io
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.