Immutable budget versions
An approved number cannot move. A change is a new version with a trail.
Plan budgets, drivers and workforce, then explain every variance against actuals.
Build budgets by entity, account, cost centre and project in versions that cannot be quietly changed. Drive plans from headcount and volumes, read actuals from the ledger, and let AI draft the variance story for a person to edit and publish. Purchasing checks availability against the same active budget.
An approved number cannot move. A change is a new version with a trail.
Plans built from headcount, rates and volumes, not typed numbers.
Variances are drilled to journals and explained in plain language that a person edits and publishes.
Spend is checked against the active budget before it is committed.
The pipeline forecast and quotas arrive as a starting plan.
Search or filter. Planned items are labelled; everything else is available now.
Build the budget in a spreadsheet-style grid and keep every approved number safe behind a version.
11 featuresPlan from headcount, rates and volumes instead of typing numbers.
5 featuresPlan people cost from real positions with salary data protected.
4 featuresCompare plan, forecast and actuals from the ledger and explain the differences.
8 featuresSee the money already spoken for and check availability before spend is committed.
3 featuresSeed the revenue plan from sales forecasts and quotas instead of retyping them.
3 featuresPlanning behaves the way your finance policy says.
5 featuresNamed so you know where Planning stops today.
3 featuresIt prepares the work. A person confirms it.
The same four building blocks, specific to Budgeting & Planning.
Version approvals use the shared authority matrix. The preparer never approves, and a second step applies above a tenant threshold.
Three datasets and seven reports power CFO, FP&A analyst and budget owner dashboards. Variance can be grouped by account, cost centre, department, project or month.
Datasets
Dashboards
Budget lines and driver values flow through public resources and feeds. Planning reads published data from other hubs, never their tables.
/v1 versions, budget lines, drivers
Events
Connectors
There is no dedicated migrate pack for budgets or planning tools. Budgets can be loaded by spreadsheet import with a dry run.
Variance, commitments, a budget version and the approvals queue have phone screens. Grid editing is a desktop task.
Actuals come from the ledger, refreshed on request, with drill to journals.
The pipeline forecast seeds the revenue plan.
Quota totals seed the revenue plan.
Positions seed the workforce plan, with salary data role-gated.
Requisitions and purchase orders are checked against the active budget and their commitments are read back.
Expense spend shows against the budget.
Forecast figures can inform cash planning.
Yes. Original, revised and forecast versions are kept, and an approved version never changes.
It drafts it, citing journals and drivers. A person edits and publishes.
Yes. Requisitions and purchase orders are checked against the active approved version, with warn or block as a setting.
Yes. CSV and XLSX with a dry run and control totals, and you can export both.
Salary data needs a specific right and is never given to the assistant.
Not yet. Scenarios, zero-based and capital planning and cross-entity plan consolidation are planned.
A plan can be shown in a presentation currency at the stored rate.