Version 29 removes SOAP on Microsoft pages and the old custom report layouts, switches on features you can no longer turn off, and starts the countdown to bigger removals in version 30. A plain-English checklist for end users: what is affected, how to check, and what to do before your update date.
Most Business Central updates arrive quietly. Version 29 (2026 release wave 2) is one to plan for, because it removes two things that real businesses still depend on, makes several features compulsory, and sets up some bigger removals in version 30 next April. None of it is difficult to deal with if you know about it in advance. All of it is awkward if you find out on the morning after your update.
This is the checklist we are working through with customers. For the new features, see Business Central version 29: what matters for a UK business.
Online customers can choose when their environment moves to version 29, up to the end of February 2027. In the Business Central admin centre, open the environment, check the scheduled date and move it away from month-end or your busiest week. Then work back from that date: everything below should be checked in a sandbox on version 29 before production moves.
What has changed: you can no longer publish one of Microsoft's own pages (customers, items, sales orders and so on) as a SOAP web service. Anything that connected to Business Central that way stops working on the update, and there is no switch to turn it back on.
Who is affected: businesses with older integrations, typically ones built years ago for NAV or early Business Central: EDI links, web shops, warehouse or transport systems, and in-house tools.
How to check: open the Web Services page and look for entries of type Page with SOAP published that point at standard Microsoft pages. Then ask every integration supplier, in writing, whether they use SOAP.
What to do: move the integration to the standard Business Central APIs, or to a copy of the page in your own extension. Do not move it to OData on the same Microsoft page, because that goes in version 30 (see below).
What has changed: the old page that NAV-era invoice, statement and remittance layouts were built on has been retired.
How to check and what to do: look in Report Layout Selection for reports using a custom layout, export them, and run Migrate to System Layouts. Full steps in Will your invoices still print?
These features were optional in Feature Management. In version 29 they are switched on for everyone and cannot be turned off.
| Feature | What changes | What to check |
|---|---|---|
| Masking of sensitive data | Sensitive fields are masked on screen. | Users can still see what they need, and any automation, robotic process automation (RPA) or test scripts that read values from the screen still work. |
| Manual flushing without a pick | Component consumption with manual flushing no longer needs a warehouse pick. | Production and warehouse teams: consumption still posts the way your process expects. |
| Default values for financial reports | Financial reports pick up new default settings. | Run your month-end pack in the sandbox and compare figures and layout with last month. |
| New reminder terms texts | The wording on reminders changes. | Print a reminder of each level and check what your customers will read. |
These are announced for removal in 2027 release wave 1. They are not in version 29, but if they affect you, the work belongs in the same project.
| Item | Who it affects | How to check | What to do |
|---|---|---|---|
| OData on Microsoft pages | Integrations, Excel workbooks and Power BI reports built on standard pages published from the Web Services page | Web Services page: OData published on standard Microsoft pages | Move to the standard APIs or the Analytics API, or a page in your own extension |
| Uploading extensions from Extension Management | Admins and partners who upload per-tenant extensions that way | How your partner deploys your customisations | Use the Business Central admin centre (or its API) instead |
| Finance reports API (beta) | Reporting tools built on it | Ask your reporting or BI supplier | Move to the Analytics API |
| Peppol BIS 2.0 and 2.1 | Anyone sending or receiving e-invoices in the older Peppol formats | E-document and Peppol setup, and your e-invoicing provider | Move to Peppol BIS 3.0 |
| AMC Fundamentals app | Customers using AMC banking for payment and bank files | Extension Management: is AMC Fundamentals installed? | Talk to AMC about moving to their own app |
If your system is still on version 27 or earlier, note that version 28 removed a set of legacy reports, such as the legacy aged accounts receivable and trial balance reports, along with the old Excel finance reports on the Business Manager and Accountant role centres. If your team still runs any report with "(legacy)" in its name, find its replacement now.
Version 29 breaks old SOAP integrations on Microsoft pages and retires the old custom report layouts, makes four features compulsory, and gives you until April 2027 to deal with OData on Microsoft pages, old Peppol formats, the finance reports API and AMC Fundamentals. Check the Web Services page and Report Layout Selection this week, test in a sandbox, and you will have nothing to worry about on update day.
Want a second pair of eyes? Our health check covers update readiness, or book a 30-minute call and we will go through the list with you.