Budgets and group reports on Business Central data
- 01Business Central
- 02API / Dataflow Gen2
- 03Fabric
- 04Management reporting · Budget and forecast
To compare Business Central companies against budget, shared report lines and dimensions must be agreed first. We review how Sparkle’s connection package fits your finance model and planning process.
Status: Sparkle package. Finance modelling and planning are scoped separately.
How does data reach Fabric?
Microsoft lists Business Central as a Dataflow Gen2 source. We compare it with Sparkle’s data-connection package. The choice depends on companies, history and required fields.
Which data will we use?
We plan mappings for ledger entries, accounts, dimensions and budget, and check that the chosen API exposes every required field.
What will the output look like?
For example, a management report by company and agreed dimension, with actuals alongside budget. Account mappings are approved before combining figures; forecast revisions use approved assumptions. Inspect the worked example.
What is checked before implementation?
We check your environment, companies, API permissions, dimensions and required refresh frequency. Any proposed mirroring route is assessed in your environment before it enters the agreed scope.
Your finance team approves account mappings and balances for a sample period. We agree the environment, access and processing boundaries with your IT team. No API keys are needed for the first call.
What needs a separate agreement?
Currency treatment, intercompany eliminations and statutory consolidation. ERP changes, unlimited history and writeback to the source also require separate scope. A management view is not automatically a consolidation solution.
How will you accept the work?
We check balances for the agreed period and entities, report-line mappings and refresh logs. Gaps are recorded before you decide on the next stage. Planning and ongoing management have separately agreed scope.
Sparkle’s package and Future Finance
Sparkle’s data-connection package and Future Finance’s modelling and planning serve different needs. Sparkle’s published analysis describes the package in Estonian. One quote separates connection, model, planning and managed-service scope without overlapping charges. Microsoft costs remain separate.
First step
Finance review: options, cost assumptions and implementation scope. Price on request. View services.
Technical source, checked 9 October 2026: Microsoft Fabric: connector overview. The source describes vendor capabilities, not the readiness of a Future Finance connection.