Reconciled p.24
FY2025 budget vs. actual: Revenue
+28.5% vs. prior period
Use case
Budget planning & forecasting
Build driver-based budgets and rolling forecasts on top of actuals that are already reconciled to the ledger, so every variance you report traces back to a real, cited number instead of a re-keyed export.
Built on actuals already reconciled from
- PDF filings
- Bank statements
- ERP exports
- ZATCA e-invoices
- Excel schedules
The old cycle
Budget season shouldn't start from a blank workbook every year.
- Actuals still get re-keyed from a spreadsheet export before a budget can even start.
- Finance, sales, and ops plan in separate sheets that never reconcile with each other.
- A rolling reforecast means rebuilding formulas, not just changing one assumption.
- Every cycle starts from a blank workbook instead of a reconciled base case.
A more coherent cycle
One forecast, tied to the ledger the whole way through.
A guided walkthrough of a live model: every figure on screen still carries its own citation.
Insight, not re-keyed data
Variance narrative draws from the same cited figures already sitting in the board pack, nothing gets exported and retyped first.
React at reforecast speed
Change one driver in plain language and every dependent line recomputes across the model, deterministically.
Planning as one team
Finance and the functions it plans with work from the same governed definitions, not divergent spreadsheet copies.
Key features
What a reconciled budget cycle runs on
Branch a what-if without forking the plan
Test a hiring freeze, a price change, or a downturn in plain language: every dependent line recomputes against the same reconciled base case, never a detached copy.
58% Baseline
86% Best case
34% Downturn
Aligned across every planning surface
Budget owners, FP&A, and the functions finance plans with all read from one governed definitions layer, so a driver means the same thing in every forecast.
Granular access rights
Role-based access and per-organization isolation keep sensitive drivers scoped to the people who should see them.
Actuals and forecast, one line
Add a new actual period and the forecast months ahead of it recompute in place: no separate tab, no manual splice.
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Not a rating. A chain.
Every figure in this plan can show its own proof.
- 1 Filed
- 2 Extracted
- 3 Reconciled
- 4 Cited
- 5 Exported
Reconciled p.31
Hiring-freeze scenario: Payroll
−6.2% vs. prior period
Reconciled p.19
Rolling OPEX forecast: Q3
+4.1% vs. prior period
Keep exploring
Other plans built the same way
Financial consolidation
Multi-entity roll-up and intercompany elimination on one canonical model, with lineage intact through the roll-up.
Read the use caseHeadcount planning
Model roles, comp, and timing against the same actuals base, so hiring flows straight into the P&L forecast.
Read the use caseSales forecasting
Bookings and revenue forecasts run against actuals already reconciled to the ledger, never a side spreadsheet.
Read the use caseFrequently asked
Questions about budgeting and forecasting.
What makes a budget "reconciled" here, rather than just entered?
Every actual behind the budget has already been checked against the printed subtotal on its source document. The budget compares to that tied-out number, not a re-keyed one.
How is a rolling reforecast different from rebuilding the model?
A reforecast changes an assumption in plain language (hiring, pricing, a demand shift) and the deterministic engine recomputes every dependent line. The structure of the model never changes underneath you.
Can I test a hiring freeze or a downturn without breaking the live plan?
Yes. Scenarios stay tied to the underlying reconciled base case, so a what-if recomputes on its own branch and never overwrites the plan everyone else is working from.
Where does the variance narrative come from?
From the same cited figures already used in the board pack: the variance explanation and the reported number are never two different data pulls.
Can I just ask questions about the budget instead of building a report?
The Analyst agent answers plain-language questions over your model and its cited actuals: retrieving figures, running the calculation, and citing what it computed from.
What happens if a figure can't be reconciled yet?
It doesn't quietly enter the plan. Nothing exports (board pack or statement) until the reconciliation checks agree; an unverified number gets refused, not shipped.
Do we need a live ERP connection before we can start budgeting?
No. Excel, CSV, or PDF upload works standalone, so modeling can start before any live connection exists.
Get started
Plan the next forecast on evidence, not an export.
Book a walkthrough and we'll build a rolling forecast from a sample of your own actuals: reconciled, cited, and ready to reforecast on the spot.