Use Flow Pages when the page should be a single full-page statement or KPI page instead of a mixed dashboard. Use this when the page should be read top to bottom.
Flow Pages work best for:
- Income Statement
- Balance Sheet
- Cash Flow
- Trial Balance
- Drivers
- KPI Dashboard
Start with a Flow Page
Create the Flow Page before adding the widget; building a full-page statement on a Grid Page usually means rebuilding it.
Choose the widget that fits the page
- Use Income Statement, Balance Sheet, Cash Flow, or Trial Balance when the page needs accounting structure.
- Use Drivers when the page should explain the operating inputs behind the numbers.
- Use KPI Dashboard when the page should start with high-level metrics before deeper detail.
Set the data first
For Flow widgets, start with the data controls:
- period scope
- source type
- forecast version or scenario when applicable
- statement template when the statement should use a specific layout
Confirm the time range and source before polishing the layout, so the page is built around the right numbers.
Use breakout and period-column controls carefully
Flow widgets include settings that change how the page is organized:
- Breakout controls whether the page is grouped by period, comparison set, dimension, or entity
- Period columns control whether the page shows monthly, quarterly, annual, and total columns where those modes apply
- Income Statement and Cash Flow widgets can show multiple period levels at once, such as M + Q + Total
Use statement structure tools where they belong
If the statement needs different row ordering, labels, or hidden lines, fix that in Statement Format Editor first. Then come back and finish the report page here.
Use Manage KPIs before you build the page if the KPI Dashboard needs metrics that are not already set up.
Finish with display controls
After the data and structure are correct, use the display controls to clean up the finished page:
- decimals and display units
- show account numbers when the audience needs them
- hide zero rows where blank detail adds noise
- variance color treatment when comparison columns should be easy to scan
- statement title or TOC row label when the page needs better navigation
Watch out for
- Report display controls — decimals, colors — won't fix a structural problem. If a statement looks structurally wrong, fix it in the statement template or Statement Format Editor first.
- If the numbers do not match what you expected, confirm source type, forecast version, scenario, and period scope in that order.