By Rajib Lochan Huzuri
From a minor release to a monthly conversation about ERP, automation and governance
Business Central 28.4: Why Should an Enterprise Care?
At first glance, Business Central 28.4 does not look like the kind of release that would normally make its way into a CIO’s agenda. It is a minor update, not a new major version. There is no single headline feature that changes the way every Business Central customer works.
But that is exactly what makes this release interesting.
Business Central is no longer an ERP product that organizations update only when a major upgrade project comes around. Microsoft now operates Business Central as a continuously evolving online service. There are two major update cycles each year, with monthly minor updates in between. Those minor updates can include new release-wave capabilities, regulatory changes, and important fixes and improvements.
For an enterprise, that changes the question. Instead of asking only, ‘Should we upgrade to the next version?’, IT and business teams increasingly need to ask, ‘What changed this month, does it affect us, and what do we need to do about it?’
What Is Actually New in Business Central 28.4?
Microsoft’s 28.4 documentation highlights three feature changes: Known Senders in Payables Agent, payments with the E-Document framework, and the ability to preview Peppol electronic invoices from the purchase draft page. The first two are generally available, while the Peppol capability is a public preview.
| Change | Why it matters | What enterprises should consider |
|---|---|---|
| Known Senders in Payables Agent — GA | Can reduce manual intervention for invoices received from trusted vendor senders and move AP closer to exception-oriented processing. | Define who owns trusted senders, how they are reviewed, and how exceptions are handled. |
| Payments with E-Document framework — GA | Adds payment-related information to the electronic-document process and can help connect invoice processing with payment information. | Assess how it fits with existing payment, bank reconciliation and reporting processes. |
| Purchase draft page to preview Peppol electronic invoices — Public Preview | Gives users a way to preview Peppol electronic invoice information from the purchasing process before completing the transaction. | Test it in a sandbox and assess the impact on current e-invoicing and localization processes. |
1. Payables Automation Is Becoming More Practical
The Known Senders capability is probably the most interesting change in 28.4 from an operational perspective.
Accounts payable teams spend a surprising amount of time dealing with routine invoices. The challenge is not always the invoice itself; it is the repeated checking, classification and review that surrounds it.
Known Senders gives organizations another way to apply trust rules to invoices received from known vendor senders. The important point is not that Business Central suddenly makes AP fully autonomous. It does not. The more realistic opportunity is to reduce unnecessary manual intervention for trusted scenarios while keeping exceptions and unfamiliar situations under review.
That distinction matters in an enterprise environment. Automation without controls can create a new risk. A sensible implementation should define who can add or manage trusted senders, how those decisions are reviewed, and what happens when an invoice does not meet the expected conditions.
2. Electronic Documents Are Moving Closer to the Payment Process
The E-Document framework update is less visible to end users, but it points to an important direction in digital finance.
Electronic invoicing is often discussed as a document-exchange problem: receive an invoice, validate it, and post it. In practice, finance teams also need to know what happened afterward. Was the invoice paid? When was it paid? What amount was settled?
By bringing payment-related information into the E-Document framework, Business Central is helping connect those stages more closely. The enterprise opportunity is better traceability across the invoice-to-payment lifecycle, rather than simply another electronic-document feature.
Organizations should still assess how this interacts with their existing payment processing, bank reconciliation and reporting processes. The new capability should complement a controlled finance process rather than be assumed to replace one.
3. Peppol Preview: Useful, but Treat It as a Preview
Business Central 28.4 also introduces the ability to preview Peppol electronic invoices from the purchase draft page. Microsoft currently lists this capability as Public Preview.
For organizations already working with Peppol-based electronic invoicing, the practical value is straightforward: users can get more visibility into the electronic invoice before completing the purchasing process.
Because it is a preview capability, however, organizations should test it carefully in a sandbox and evaluate how it fits with their existing e-invoicing, localization and operational processes.
4. A Related Business Central 28 Change: Where AI Requests Are Processed
There is another item worth discussing alongside 28.4, although it should not be described as a new 28.4 feature.
Microsoft has documented a change affecting Copilot and agent requests for applicable Business Central environments on version 28.0 or later. Starting July 1, 2026, some requests may be processed in a different Azure geography.
For many organizations this may have little practical impact. For organizations with strict data-residency, privacy or regulatory requirements, however, it deserves attention.
This is a good example of why ERP governance is becoming broader than application functionality. The conversation now includes not only what the ERP can do, but also how AI services interact with business data and what governance controls apply.
5. The Bigger Agentic ERP Story
It would be easy to look at a feature such as Known Senders and call it an ‘AI revolution.’ That would be overstating it.
A better way to look at it is as one small step in a much bigger direction.
Microsoft’s broader Business Central 2026 release wave 1 strategy is explicitly moving the product toward AI-driven ERP, including expanded AI-powered agents that can help with more complex business processes.
The interesting shift is in the way people may interact with ERP. Historically, the pattern has been simple: open a screen, find a record, enter information, run a process and review the result.
The emerging model is different: describe an intention, let an AI-assisted capability gather context and perform defined actions, and keep people involved where judgment, approval or control is required.
That does not mean enterprises should start planning for fully autonomous ERP operations. The more realistic near-term opportunity is controlled automation of well-defined processes. The broader agentic model will evolve over time, and organizations will need to balance productivity with governance.
6. Business Central Updates Are Becoming an Enterprise Governance Issue
One of the biggest changes in the Business Central operating model is easy to miss: the update itself is becoming routine.
Microsoft manages the application and platform updates for Business Central online. Administrators and partners can use the Business Central administration center to manage update timing, and Microsoft recommends using preview environments to prepare solutions and users for upcoming changes.
That means organizations need a lightweight but repeatable release-management process. It does not have to become another large IT project every month. But someone should own the review.
A practical monthly review should answer four questions:
- Does this update affect a business process?
- Does it affect an integration, extension or ISV application?
- Does it introduce a compliance, privacy or data-governance consideration?
- Do users need configuration changes, testing, training or communication?
7. What Should Organizations Do for 28.4?
There is no reason to turn Business Central 28.4 into a major upgrade project simply because a new minor version is available. The right response depends on what an organization actually uses.
- Review whether Payables Agent and Known Senders are relevant to your AP processes.
- Validate the E-Document payment functionality against existing finance processes.
- If using Peppol-based invoicing, test the preview capability in a non-production environment.
- Review the Copilot and agent data-processing implications if your organization has data-residency or privacy requirements.
- Check critical extensions and integrations in a preview or test environment.
- Run targeted regression testing for the business processes that matter most.
- Obtain business-owner sign-off before adopting changes that alter operational processes.
Who Should Pay Attention?
| Role | Why it matters |
|---|---|
| CFO / Finance leadership | AP automation, electronic documents and payment visibility. |
| CIO / IT leadership | Continuous updates, integrations, extensions and AI/data governance. |
| Business Central administrators | Update management, testing and configuration. |
| Accounts payable leaders | Trusted vendor processing and exception management. |
| Compliance and security teams | E-invoicing requirements and AI/data-processing considerations. |
| Business Central partners | Customer readiness, extension compatibility and change management. |
Business Central 28.4 Readiness Checklist
- Review the Microsoft 28.4 release documentation.
- Identify which changes are relevant to your organization.
- Check Payables Agent and trusted-sender governance where applicable.
- Validate E-Document and payment-related processes.
- Test the Peppol preview capability before using it in production.
- Review AI and agent data-processing requirements.
- Check critical extensions and integrations.
- Run focused regression testing.
- Get business-owner approval for process changes.
- Obtain business-owner approval for process changes.
What CIOs and Business Leaders Should Take Away
- ERP is becoming a continuously evolving service, so release governance needs to become a regular business practice.
- The most valuable feature is not always the most visible one; small automation changes can have a meaningful operational impact.
- AI and agents are becoming an additional interaction and automation layer for ERP, but today’s capabilities should be distinguished from longer-term possibilities.
- Extensions and integrations need continuous compatibility attention rather than a one-time check before a major upgrade.
- Finance, operations and compliance teams should have a voice in ERP release decisions—not just IT.
- Data residency and AI governance are becoming part of normal ERP governance.
- The real value of an update comes from adoption, process improvement and appropriate controls, not simply from enabling new functionality.
Conclusion: The Real Change Is the Pace of Change
Business Central 28.4 is not a release that every executive needs to study line by line. Most organizations will not need a major project because of it.
But it is a useful reminder of where ERP is heading.
The Business Central platform is changing continuously. Automation is becoming more practical. Electronic documents are becoming more connected to downstream financial processes. AI is moving closer to everyday ERP work. And decisions about data, integrations and governance are becoming part of the ERP conversation.
For businesses, the advantage will not necessarily go to the organizations that turn on every new feature first. It will go to the organizations that develop a simple discipline for understanding what changed, deciding what matters, testing it properly and turning useful capabilities into measurable business outcomes.
That is perhaps the most important lesson from Business Central 28.4: the future of ERP may not arrive as one dramatic upgrade. It may arrive quietly, month after month.
Official Microsoft References
- Business Central update cycles: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/update-rollout-timeline
- Business Central 28.4 — What’s New: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/whatsnew/whatsnew-update-28-4
- Managing updates in the Business Central administration center: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-update-management
- Business Central 2026 release wave 1: https://learn.microsoft.com/en-us/dynamics365/release-plan/2026wave1/smb/dynamics365-business-central/