Financial Statements Workflow
Use this page as the map for Financial Statements in Mission Control. It tells you which screen to open for each job, in what order, and which detailed guide to follow next.
Audience: Controllers, CFOs, ERP leads, and financial analysts who design and run statements in Mission Control.
Where: Mission Control → Financial Statements
What each area owns
Financial Statements splits work into five pages. Templates and trees are design-time assets. Saved statements and schedules are how you run and deliver them.
| Domain | What you define | Where you configure it |
|---|---|---|
| Statement design | Templates: rows, columns, criteria, styles, shared row/column sets | Financial Builder |
| Access | Which team members can view or edit each template | Financial Security |
| Multi-company navigation | Trees (nodes + company/part scope); assign a tree to a template | Financial Trees (assign from Builder) |
| Interactive run | Named saved statements, parameters or tree scope, Execute, export/print | Financial Viewer |
| Scheduled delivery | Cron rules + email of PDF/XLSX for a statement | Financial Scheduler |
Financial Extraction appears in the same nav group but is not covered in this guide set yet.
Recommended order
Stand up statements for a team in this order:
- Design templates — create or AI-generate templates in Financial Builder, then edit rows/columns and Save.
- Build trees (if multi-company) — create trees in Financial Trees, then Assign Tree on templates that should lock to tree navigation.
- Grant access — set template view/edit permissions in Financial Security.
- Run interactively — create a saved financial statement in Financial Viewer, set Parameters or Trees, Execute, export or print.
- Schedule delivery (optional) — create schedules in Financial Scheduler for recurring PDF/XLSX email.
You can skip trees if every run uses company/part parameters only. You can skip the scheduler if people only run statements interactively. You should not skip security if more than one person needs controlled access to designs.
Mission Control page map
| Nav item | Route | Use it to… |
|---|---|---|
| Financial Builder | /missioncontrol/financials/builder | Design View: manage Financial Templates, edit the design canvas, Generate with AI, Assign Tree. Draft edits; persist with Save. |
| Financial Security | /missioncontrol/financials/security | Template Permissions matrix. View/edit toggles save immediately; use Apply To for bulk changes. |
| Financial Trees | /missioncontrol/financials/trees | Build and Save multi-company trees; Quick Tree from GL structure. |
| Financial Viewer | /missioncontrol/financials/viewer | Report View: create/select a saved financial statement, set Parameters or Trees, Execute, Export to Excel, or Print. |
| Financial Scheduler | /missioncontrol/financials/scheduler | Schedule a statement with Config, Rules, Email, and review Executions. |
Builder vs Viewer
| Financial Builder | Financial Viewer | |
|---|---|---|
| Mode | Design View | Report View |
| Object | Template (layout definition) | Saved financial statement (named run bound to a template) |
| Best for | Rows, columns, formulas, filters, styles, AI generation | End month, companies/parts or tree scope, Execute, export/print |
| Save model | Working draft on the canvas → Save | Parameters/tree selection → Save; Execute runs without requiring a prior save |
Design the layout in Builder. Run numbers in Viewer. Do not treat Viewer as the place to redesign row and column structure.
Templates vs saved statements
| Concept | Owned in | Job |
|---|---|---|
| Template | Financial Builder | The reusable statement design (and optional assigned tree) |
| Saved financial statement | Financial Viewer | A named instance that points at a template and stores run parameters / tree selection |
Create the template first. Then use Create Financial Statement in Viewer and pick that template. Scheduler schedules a statement (the run target), not a bare design canvas.
When to use trees
Use Financial Trees when you need a reusable multi-company navigation structure:
- Build the tree (nodes + company/part scope) and Save.
- Optionally Assign Tree on a template in Builder so Viewer runs through that tree.
- In Viewer, open the Trees panel to pick a tree/node and Execute.
- In Scheduler, set Scope Mode to Trees when the schedule should follow tree scope instead of flat Parameters.
If every run is a simple company/part list for one End Month, stay on the Viewer Parameters panel and skip trees.
Guides in this set
| Guide | Status |
|---|---|
| Create and design financial templates | Drafted |
| Generate a financial template with AI | Drafted |
| Build financial trees | Drafted |
| Run a financial statement | Drafted |
| Assign template permissions | Drafted |
| Schedule financial statement delivery | Drafted |
Start with the Builder guide if you are defining statements from scratch. Start with Viewer if templates already exist and you need to run or export results.