← ClaudeAtlas

multi-entity-forecast-dashboardlisted

Build an interactive, single-file cash forecast dashboard for a multi-entity business (several QuickBooks company files) in a fixed "quiet analytics" visual style, with per-entity and consolidated views, P10/P90 forecast band, accounts/receivables detail, and a paper-style report. Pulls live data through the MosoFin connector when the user agrees, or falls back to a manual CSV upload when they opt out or have no connector. Use this whenever the user asks for a cash flow forecast, runway, cash dashboard, multi-entity or group consolidation view, "how much cash will we have", or a forecast for their MosoFin / QuickBooks workspace — even if they don't say "dashboard". Also use it to refresh or restyle an existing forecast dashboard so it stays visually consistent.
MosoFin/mosofin-finance-skills · ★ 0 · Data & Documents · score 69
Install: claude install-skill MosoFin/mosofin-finance-skills
# Multi-entity forecast dashboard Produces one self-contained HTML file: Overview · Accounts · Forecast · Report tabs, an entity switcher (Group + each company file), scenario presets and sliders, and — on the MosoFin path — a live **Sync from QuickBooks** button and an **Ask** drawer that read the books through the connector. The look is fixed. Read `references/ui-spec.md` before touching any HTML and never restyle ad hoc; the template already implements the spec. ## Workflow ### 1. Choose the data path Ask one question first: *"Use your MosoFin connection to read the books, or supply the data yourself?"* Then: - **MosoFin** → follow `references/mosofin-workflow.md` (workspace confirm → company files → `get_cash_flow` per entity → `get_aged_receivables` → consolidate). - **Manual / opted out / no connector** → follow `references/manual-workflow.md` (CSV schema, validation, what the dashboard hides). Never mix: if a MosoFin read fails partway, tell the user what succeeded and offer the manual path for the rest rather than inventing figures. ### 2. Assemble the data object Write a JSON file matching `assets/example-data.json`. Required keys: `group`, `mode` (`"mosofin"` | `"manual"`), `source`, `fetched`, `year`, `months`, `order`, `entities`, `notes`. Each entity needs `label`, `short`, and equal-length `ocf`, `icf`, `fcf`, `ni` arrays, plus `ar`, `arIc`, `ap`, `inv`; `aging` and `customers` are optional (`null` when not pulled). `notes` drive every explanatory