Business Central 29 Reporting: What Changes in 2026

Business Central 29.0 in one paragraph

Business Central 2026 release wave 2, version 29.0, reaches general availability in the first week of October, and the financial reporting section of the release notes is longer than it has been in several waves. The short version for a controller: 29.0 is a real improvement to the governance and packaging of financial reports, it does not add consolidation, and it does not change the shape of the data you can report on. If your month-end pain is assembling and controlling a set of financial statements, several of these features will help you in October. If your pain is that the numbers you need span sub-ledgers and companies, 29.0 leaves that where it was.

Everything named below is quoted from Microsoft's own what's new page for 29.0, which was last updated on 7 September 2026.

What genuinely improves in 29.0

Three changes stand out, and they happen to be the three that touch the monthly close rather than the developer's workflow.

Report packs replace the manual PDF assembly job

The feature Microsoft calls "Run multiple financial reports and get a single PDF output" lets you define a pack containing several financial reports, then run it immediately or schedule delivery to report inboxes or by email. If you have ever produced a board pack by running the P&L, then the balance sheet, then the cash flow, exporting each to PDF and stitching them together in the right order, this removes that job. It is not glamorous and it will quietly save somebody two hours every month.

Financial report definitions are now always logged

Under "Financial report changes are now always logged", changes to financial row, column and report definitions are automatically recorded in the change log. Anyone who has spent a morning working out why the current-year column suddenly included an extra account, with no record of who changed the row definition or when, will understand why this matters more than its position in the release notes suggests. It is an audit feature that pays for itself the first time a number moves unexpectedly.

You can trace where a G/L account is used before you publish

"Trace G/L account usage in finance reports" lets report authors identify uncategorised accounts, trace account usage and calculations, and preview definitions before publishing. The uncategorised-account finder is the useful half. A new account gets created during the year, nobody adds it to a row definition, and the P&L quietly stops adding up to the trial balance. Until now you found that by reconciling. Now you can ask the system.

The governance features nobody asked for and everybody needed

A second cluster is about control rather than speed. "Control the lifecycle of all report layouts" lets you set a status on every layout type, so end users only see the layouts you want them to see. "Brand document reports with report themes" and "Reuse header/footer layouts across document reports" let you set defaults globally, per company, per report or per layout, which in a group with several legal entities is the difference between consistent output and twenty slightly different invoice templates. The updated Word add-in adds a HideIf control under "Use conditional visibility in the updated Word add-in", so a layout can suppress a block rather than needing a separate layout for the variant.

None of this will appear in a business case. All of it reduces the number of small requests that reach your partner, which is where a surprising share of a finance team's external spend goes.

There is also one item aimed squarely at automation. "Automate report outputs" adds new APIs on the report inbox so that Power Automate, or an MCP client, can pick up report output programmatically. If you have been scripting around the lack of a clean handoff, that gets easier.

What 29.0 does not change

Being straight about the limits is more useful than listing features, so here they are.

There is no consolidation feature in 29.0. There was none in 28.5 either. Group consolidation in Business Central still runs the way it always has, through a separate consolidated company that imports each business unit's data. If you need intercompany eliminations or currency translation, 29.0 gives you nothing new, and that is the gap Exsion Corporate is built for. There is also a longer walkthrough of the Excel route to consolidating multiple companies in Excel.

Financial Reporting is still shaped around the general ledger. Row and column definitions work on G/L balances. That is exactly right for a statutory P&L or balance sheet, and it is why report packs are a good fit for the statement pack. It is not the tool for a margin report that has to join item ledger entries to customer ledger entries, or for a cost-to-complete view that sits across job ledger entries. Those questions were never in scope for Financial Reporting, and they still are not.

A PDF is an output, not a model. Report packs and scheduled delivery produce a document. That is the right format for the version you file and circulate. It is the wrong format for the version somebody wants to re-cut by cost centre during the meeting, because a PDF cannot be pivoted, filtered or drilled.

Cross-company ad hoc reporting is unchanged. If you want one table covering fifteen companies so you can pivot it, 29.0 does not offer that. The consolidated-company route remains the built-in answer, and it is built for formal statements rather than for a Tuesday afternoon question.

The telling detail: Microsoft is now measuring Open in Excel

The most interesting line in the release notes is not a reporting feature at all. Under "Monitor usage of Open in Excel with telemetry", Microsoft now logs Open in Excel actions to telemetry, describing it as making data export events auditable and as critical for compliance, security investigations and understanding customer usage patterns.

Read that as a signal rather than a feature. Microsoft is instrumenting Open in Excel because it is used constantly, and because an unlogged export of ledger data is a governance gap. Both things are true, and both are worth sitting with.

What the telemetry does is record that an export happened. What it does not do is change what the export is. The file that lands on somebody's desktop is still a copy: accurate at the moment it was created, stale at the next posting, and living outside Business Central's permission model from the second it is saved. Logging the event tells your compliance officer that a copy was made. It does not tell them where the copy went.

That distinction is the whole argument for reporting on live data rather than on exports, and it is a distinction Microsoft has just made easier to see.

Where the Excel layer still earns its place

The honest position is that 29.0 and a live Excel layer solve different problems, and a finance team that understands the split will get more out of both.

Use Financial Reporting and report packs for the statement pack: the P&L, the balance sheet, the cash flow, the things whose structure is agreed and whose output is a document. In October those get easier to produce, easier to brand and easier to audit.

Use a live Excel connection for everything that is still a question rather than a statement. With Exsion Reporting, the workbook holds the query definition rather than the numbers, so the same file answers the same question every month. Pressing refresh asks Business Central again through OData web services and drops current figures into the layout you already built, leaving formulas and pivots where they are. A refresh of 700,000 G/L Entry rows takes under five seconds, and a single PivotTable can hold up to 25 million Business Central rows when the data loads straight into the data model, which is well past the point where most teams assume Excel gives out.

Three properties matter here and none of them changes in 29.0. The query can span tables, so a margin report can join what it needs to join. It can span companies, so ticking fifteen companies returns one table with a company column. And it runs as the signed-in user, using that user's Business Central rights, so a site administrator who can see one company sees one company in Excel too, and there is no second security model to maintain. That last point is the direct answer to the governance question the Open in Excel telemetry raises: a live query inherits the permissions, where a saved export does not.

Exsion installs from AppSource in about five minutes with a 30-day trial, works against Business Central online and on-premises, and publishes its pricing. It reads from Business Central and stores no data of its own. If your close is slow before any of this, the Business Central reporting performance guide is the better starting point.

What to do in the first month after GA

Four things, in order, and none of them takes long.

1. List your statement pack and check what a report pack would replace. If you assemble PDFs by hand, this is the fastest win in the release.

2. Turn on the change log review habit for financial report definitions. The logging is automatic now, so the only new work is looking at it when a number surprises you.

3. Run the G/L account usage trace once, before your first close on 29.0. The uncategorised-account finder will either reassure you or catch something, and both outcomes are worth an hour.

4. Separate your statements from your questions. Write down which recurring reports are fixed documents and which get re-cut on request. The first list belongs in Financial Reporting. The second list is the one to test against a live Excel connection.

Business Central 29.0 is a good release for finance, and the governance items in particular have been a long time coming. It is also a release that makes the boundary clearer than before: Microsoft has improved how you produce and control a statement, and has started measuring how often you leave the application to answer everything else. The second number is the one worth watching in your own telemetry.

Frequently asked questions

[[FAQ_START]]

When is Business Central 29.0 generally available? | Business Central 2026 release wave 2, version 29.0, reaches general availability in the first week of October 2026. Microsoft's what's new page for the release was last updated on 7 September 2026.

Does Business Central 29.0 add financial consolidation? | No. There is no consolidation feature in 29.0, and there was none in 28.5. Group consolidation still runs through a separate consolidated company that imports each business unit's data, and intercompany eliminations and currency translation are unchanged.

What are report packs in Business Central 29.0? | A report pack is a defined set of several financial reports that you can run as a single PDF output. You can run a pack immediately or schedule its delivery to report inboxes or by email, which removes the manual job of exporting each statement and stitching them together.

Are changes to financial report definitions logged in 29.0? | Yes. Changes to financial row, column and report definitions are now automatically recorded in the change log, so you can see who changed a definition and when without reconstructing it by reconciliation.

What does the Open in Excel telemetry in 29.0 actually do? | It logs Open in Excel actions to telemetry so that data export events become auditable. It records that an export happened; it does not change what the export is, so the resulting file is still a copy that goes stale at the next posting and sits outside the Business Central permission model.

Does 29.0 remove the need for an Excel reporting add-in? | Not for the reporting that spans sub-ledgers or companies. Financial Reporting works on general ledger balances and produces documents, which suits the statement pack. Reports that join tables such as item ledger and customer ledger entries, or that need one live table across several companies, still need a live Excel connection.

[[FAQ_END]]