29. May 2026
Financial Reporting in Business Central deserves a second look
There's a pattern we see often. A business goes live on Business Central, the finance team needs a balance sheet, an income statement, a departmental P&L, and within weeks the conversation has already moved to Power BI, Excel add-ins or Jet Reports. The built-in Financial Reporting feature gets skipped, sometimes without anyone opening it.
The reasons are understandable. Finance people know Excel, Power BI is everywhere and the feature carried a reputation from its old name, Account Schedules, which sounded like something you configured once and never enjoyed. We think that reputation is out of date, and for a large share of what finance teams actually need to produce, the native tool is the right one. It's also an area Microsoft has been steadily investing in across recent release waves, which is worth knowing before you commit budget to an external reporting stack you may not need.
What actually is Financial Reporting?
Financial Reporting is the feature formerly known as Account Schedules. It was renamed in the 2023 release wave 1, and the rename came with a tidier structure that's worth understanding because it explains how flexible the tool is.
A financial report is built from two reusable parts:
- A Row Definition describes what appears down the left-hand side: the accounts, totals, subtotals and headings. Rows can pull from G/L accounts directly, from account categories, or from other rows via formulas, so you can calculate things the chart of accounts can't hold on its own - gross margin, EBITDA, a ratio, a running subtotal across a group of accounts.
- A Column Definition describes what appears across the top: net change, balance at date, a budget column, a comparative period, a variance, a percentage of a base row, year to date, month to date. Columns can compare actuals to budget, this year to last, or one company's figures against a consolidated view.
A Financial Report is simply a Row Definition paired with a Column Definition. Both halves are reusable so you build a library of rows and columns once and then assemble reports from them. There's no practical limit on how many you create, and none of it needs a developer or an API guru.
Underpinning all of this are G/L Account Categories and Subcategories. If you assign these properly when you set up your chart of accounts, Business Central can generate the standard Balance Sheet, Income Statement, Cash Flow and Retained Earnings statements for you, and they restructure automatically when you change the categorisation. This is the single most undervalued setup step in the whole area. Teams that skip it end up hand-building reports that the system would have produced for them.
The part people underestimate
The reason finance teams reach for Excel or Power BI is usually analysis - slicing numbers by department, project, cost centre, customer group. The assumption is that Business Central can't do this natively. It can, through Dimensions.
Dimensions are tags applied to ledger entries and enforced through configured rules on accounts - for example, Department, Project, Region, whatever you define. In a Financial Report you can filter or break down any row or column by dimension, so a single income-statement row definition becomes a per-department P&L without building anything new. You can run a report across all values of a dimension at once, and analyse to a level of granularity that, in many other systems, would require a separate cube or data model. This is real reporting capability sitting inside the ERP, against live data, with no refresh lag and no second copy of the numbers to reconcile.
Alongside the formal reports there's also the Analyse mode on most list pages - an in-app pivot surface that lets you group, filter and summarise data on the fly without leaving Business Central or exporting anything. For the "I just need to check something quickly" requests that would otherwise trigger an Open in Excel export, it's frequently enough on its own.
When you do need to leave the system, you can. Financial Reports export cleanly to Excel and to PDF, and you can save Excel templates back into Business Central and re-run reports through them, which is useful for board packs and report packs that need a consistent house layout.
It is an area Microsoft is actively investing in
This is the part most relevant to anyone weighing native reporting against a third-party tool. Financial Reporting isn't in maintenance mode - it has had meaningful additions in three consecutive release waves.
In 2025 Release Wave 1, viewers gained the ability to hide empty rows and use an accounting format where negatives appear in brackets rather than with a minus sign. Authors got a month-to-date column type, the ability to document a report with an internal description and add introductory and closing paragraphs, and the option to save and run reports through Excel templates. Report runs could also be scheduled, and administrators were given visibility of the permissions and telemetry behind report usage.
In 2025 Release Wave 2, the scheduling went further: viewers can now have a report run on a schedule and delivered to an email inbox or the in-app report inbox, and run a report across every value of a dimension in one pass. For authors, row definitions can be edited directly in Excel, the No. and Description fields autofill, you get a notification when a G/L account name changes so definitions stay accurate, column headings support dynamic naming, and column definitions can handle both local currency and an additional reporting currency.
In 2026 Release Wave 1, the focus moved to distribution and governance. Reports can be scheduled to a whole distribution group, multiple reports can be combined into a single PDF - genuinely useful for assembling a board pack. You can place a company logo on PDF output. Administrators can set global defaults for things like negative-number format, reporting period and logo placement, override them per report where needed, and monitor report usage through a new audit log.
It's also worth seeing this in the wider context. Microsoft has been shipping ready-made Power BI apps for Business Central - Finance, Sales, Supply Chain and others at no additional licence cost, and has open-sourced them so they can be customised rather than rebuilt from scratch. Power BI visuals can now drill back into the underlying Business Central transaction. The point isn't that one tool is winning; it's that the whole reporting and analytics surface is a priority, and that native Financial Reporting and Power BI are being designed to complement each other rather than compete.
Where are its limits?
An honest assessment has to cover the limits, because they're real and they're where the external tools earn their place.
Financial Reporting is a financial statement engine. It's built around the general ledger, account categories and dimensions. It is not a visualisation tool - there are no charts and no interactive dashboards. If your audience wants to click into a figure and explore, or you want a polished visual dashboard for a leadership team, that's Power BI, and you should use it.
It also focuses on ledger data. The moment you need to blend financial figures with something that doesn't live in the G/L - operational metrics, CRM data, external benchmarks, anything non-financial - you're past what the native tool is for, and again that's Power BI or a proper data model. Microsoft have given us Statistical Accounts to help plug this gap but again, its pushing limits.
For genuinely ad-hoc throwaway modelling building out a one-off scenario, a quick what-if, a calculation that will never be run again - Excel is still faster and always will be. Jet Reports remains a strong choice for teams that want heavily Excel-native, refreshable reporting with a particular set of behaviours that suit their existing way of working.
The mistake isn't using Power BI, Excel or Jet Reports - it's reaching for them by default, before checking whether the structured financial statements and management reporting you actually need are already producible in the box.
How to get the most from Financial Reporting
A few things make the difference between a native reporting setup that quietly works and one that frustrates people into leaving.
- Get the G/L Account Categories and Subcategories right at implementation. This is the foundation the standard statements are generated from, and retrofitting it later is tedious.
- Be deliberate about Dimensions. They are your entire analytical layer, so decide early what you genuinely need to report on and apply them consistently. Dimensions that are inconsistently captured produce reports nobody trusts so Default Dimensions are important across Accounts and Account Types.
- Build a library of reusable Row Definitions and Column Definitions rather than one-off reports. The strength of the model is the recombination, and a small, well-named set of building blocks goes a long way.
- Set your defaults and report selections on the Reporting tab of General Ledger Setup, so the standard statements behave consistently for everyone and you're not re-specifying the same options each time.
- Make use of scheduling and distribution. If a report goes to the same people every month, the system can now run it and deliver it for you, which removes a recurring manual task that finance teams rarely enjoy.
Conclusion
Financial Reporting in Business Central won't replace Power BI for dashboards, or Excel for ad-hoc work, and it isn't trying to. For statutory and management financial statements, departmental and project P&Ls, budget comparatives and board packs (the bread and butter of finance reporting) it is more than capable - it works against live data, it needs no developer and no second copy of the numbers, and it's clearly on Microsoft's investment roadmap.
So the recommendation is simple: before you build a reporting stack around the external tools, open the one you already own and see how far it gets you. In our experience, for a lot of teams, that's further than they expect.