Business Central 2026 Release Wave 1: What Malaysian Finance Teams Need to Know

What a Business Central release wave actually is

Microsoft ships Dynamics 365 Business Central updates twice a year through a structured programme called a release wave. Each wave is a defined window — 2026 release wave 1 covers new functionality delivered to market from April 2026 through September 2026 — during which Microsoft rolls out a major version (this wave is version 28) followed by monthly minor updates that add features progressively rather than all at once.

For a Malaysian finance team, this matters for a practical reason: features do not all appear on day one. Some are enabled automatically for every user the moment the update reaches an environment; others must be turned on deliberately by an administrator, maker or business analyst. Microsoft tags each feature in its release plan accordingly, and that distinction should shape how a finance team prepares for the update rather than treating it as a single event to react to.

This article reviews what Microsoft has confirmed for 2026 release wave 1 on its official release plan documentation, and sets out what the genuinely notable changes mean for finance teams operating Business Central in Malaysia.

AI agents and Copilot: what is actually new

The centrepiece of 2026 release wave 1 is the continued build-out of AI-powered agents inside Business Central. These are not generic chatbots; each agent is scoped to a specific finance or operations process, and each still requires a human to review and approve its output before anything posts.

Payables Agent

The Payables Agent automates parts of the accounts payable workflow — reading incoming vendor invoices, drafting purchase invoice entries, and matching invoices to purchase orders. In this release wave, Microsoft has made the Payables Agent available with a free trial mode that processes up to 50 invoices without requiring an email inbox to be configured first, lowering the barrier for a finance team to test it before committing to a full rollout.

Sales Order Agent

The Sales Order Agent reads incoming sales order requests (for example, from customer emails) and drafts sales orders in Business Central. Wave 1 updates let a company run multiple Sales Order Agents at once with smarter item matching and clearer relevance filtering, and improve how the agent handles email attachments so it focuses on genuine order documents rather than signature images or tracking pixels.

Expense Agent (new)

New in this release wave, the Expense Agent automates the end-to-end expense claim process. Employees submit a receipt through a web app, email, or (from around July 2026) a mobile app, and the agent extracts the details, checks for duplicates, and drafts the expense report. A later addition in this wave allows the agent to validate submitted expense reports against approval policies written in plain language, flagging exceptions for a human approver rather than replacing that approval step.

What this means for a Malaysian finance team

The consistent design pattern across all three agents is assisted drafting with mandatory human review. For a Malaysian finance team, that is the detail worth anchoring on: these agents can meaningfully reduce data entry time on payables, sales order capture and expense processing, but they do not remove the need for a controller or finance manager to review and approve postings. Internal controls, segregation-of-duties policies and audit trail requirements should be mapped against how each agent is configured before it is switched on for production use.

Financial reporting and dimension analysis

Financial Reporting in Business Central has been rebuilt in this release wave, and the changes are aimed squarely at the people who prepare and consume management accounts.

• Report discovery: a new tile view on the report list shows status, category, name and last run date at a glance, making it easier to find the right report in a large report library.
• Formatting and branding control: report authors can display the company logo on PDF outputs and override formatting defaults such as negative number presentation and report period on individual reports.
• Scheduled distribution: reports can now be scheduled for a distribution group, with recipients receiving the output by email and in an in-app report inbox — useful for routine management reporting packs that currently rely on someone remembering to run and circulate them.
• Dimension-based analysis: users can run a report across all values of a dimension in a single execution, rather than repeating the same report for each department, project or cost centre.
• Governance: administrators gain a new audit log that tracks report usage, alongside the ability to set organisation-wide defaults for formatting.

Microsoft has also delivered faster reports for deferral schedules and trial balance analysis, and new APIs that let auditors and IT staff analyse approval workflows and user permissions programmatically — a detail relevant to any Malaysian entity preparing for statutory audit or internal control review, since it gives an auditor a more direct way to extract evidence of who approved what, and when.

Separately, Microsoft has deprecated a set of legacy finance and fixed asset reports (including the legacy Aged Accounts Receivable, Aged Accounts Payable, and Trial Balance reports) in this release wave, in favour of the newer reporting and Power BI-based alternatives. Finance teams still relying on any of the legacy report names should confirm a replacement report before the update reaches their environment, to avoid a gap in a routine month-end reporting pack.

Electronic documents: the framework behind e-invoicing

Business Central's e-documents framework is the underlying mechanism Microsoft uses worldwide to automate the exchange of e-invoices and other structured business documents with tax authorities and trading partners. In 2026 release wave 1, Microsoft has extended this framework in two directions that are worth understanding even though neither is a Malaysia-specific feature in this wave:

• Broader document coverage. The e-documents framework now supports additional document types beyond e-invoices, including shipments and transfer shipments, so the same structured-exchange mechanism can extend to more of a business's operational document flow over time.
• Country-specific e-invoicing mandates. This wave adds or extends e-invoicing compliance features for specific jurisdictions currently named on Microsoft's release plan — for example, expanded e-invoice format support in Germany, and a new France e-invoicing and e-reporting capability ahead of that country's September 2026 mandate.

Why this matters for a Malaysian finance team even without a Malaysia-specific feature this wave

Malaysia is not among the countries Microsoft has listed for a new e-invoicing feature in 2026 release wave 1 specifically. That said, the architecture matters directly to any Malaysian business running Business Central alongside its LHDN MyInvois e-invoicing obligations: the e-documents framework is the same structured-exchange layer that a Malaysian localisation or partner-built connector would use to automate MyInvois submission, validation and status tracking from within Business Central, rather than through a manual or bolt-on process. As Microsoft continues to broaden what the framework supports natively, it becomes a more capable foundation for that kind of local compliance automation over time.

For SST reporting, the relevant read-across is indirect but real: cleaner, more structured document capture through the e-documents framework reduces the manual re-keying that often introduces errors into SST-relevant transaction data, and the financial reporting and dimension-analysis improvements described above make it easier to isolate and review SST-relevant figures at return time. Malaysian finance teams should treat these as adjacent productivity gains rather than as a direct SST or MyInvois feature delivered in this specific wave, and should keep validating their MyInvois and SST processes against current LHDN and RMCD guidance rather than assuming Business Central changes alone satisfy those obligations.

Other changes worth knowing about

A few additional wave 1 items are less headline-grabbing but still relevant to day-to-day finance operations:

• Outlook integration has been updated to keep users in their flow of work when saving business contacts and documents from email.
• External storage support for document attachments is now generally available, letting organisations store large attachment volumes outside the Business Central database.
• An enhanced MCP (Model Context Protocol) server allows agentic and Copilot-style experiences to connect to Business Central from compatible external tools, extending how AI-assisted workflows can interact with the platform.
• Governance and administration improvements give administrators more control over multi-environment access, customer-managed encryption keys and extended update scheduling windows.

How to plan for the update

A release wave should not be treated as a single disruptive event. A structured approach works better for a finance team responsible for month-end close, statutory reporting and audit readiness:

1. Read the release plan for your environment's update schedule. Business Central online environments receive updates on a rolling monthly cadence within the wave; on-premises deployments follow a separate upgrade path. Confirm which minor update (28.0 through 28.3 and beyond) your environment is or will be running.
2. Separate "automatic" from "admin-enabled" features. Microsoft tags every feature as either enabled automatically for users or requiring an administrator, maker or analyst to switch it on. Review the automatic list first, since those changes affect users without any local decision being made.
3. Check for deprecated reports before the update lands. If a month-end or year-end reporting pack references a legacy report name that Microsoft has deprecated in this wave, identify and test the replacement report in advance.
4. Test AI agents in a sandbox before production rollout. Use trial modes where available (the Payables Agent trial, for example) to validate accuracy against real vendor and customer documents before extending an agent's role in a live approval workflow.
5. Re-confirm MyInvois and SST workflows independently. Platform-level e-documents improvements are a foundation, not a substitute for validating that MyInvois submission and SST return preparation still work as expected after an update.
6. Brief finance and audit stakeholders on new audit-log and API capabilities. The new approval-workflow and permissions APIs give internal or external auditors a more direct way to test controls; understanding what they expose before an audit starts avoids surprises during fieldwork.

How SCSB helps

SCSB supports Malaysian organisations through Dynamics 365 Business Central implementation, configuration and ongoing support, including planning for platform release waves like this one. Our team reviews Microsoft's release plan for each wave, helps finance teams assess which features are relevant to their processes, and works with clients to test and configure changes — including AI agent setup, financial reporting configuration, and e-documents framework configuration — before they reach a live environment. This work sits alongside SCSB's implementation services for Microsoft 365, Microsoft Power Platform and Microsoft Azure.

If your organisation is planning for the 2026 release wave 1 update, or wants an assessment of which new Business Central capabilities are relevant to your finance operations, discuss your requirements with SCSB.

Last updated: July 2026

Microsoft, Dynamics 365, Dynamics 365 Business Central, Microsoft 365, Microsoft Power Platform, Microsoft Azure, and other Microsoft products referenced are trademarks of the Microsoft group of companies.