Rolled out for the Web platform in the Worldwide (Standard Multi-Tenant) cloud instance, this update adds structured payment status tracking directly into Business Central’s E-Document framework. According to Microsoft's release plan documentation on Microsoft Learn and the AI at Work Roadmap, the capability hit general availability in August 2026—specifically listed as August 3, 2026 on the archived 2026 release wave 1 plan—after appearing as a public preview item in the Update 28.3 release notes published in July 2026. While the roadmap entry itself was updated in mid-October 2026 to reflect its launched status, finance administrators and ERP architects now have a clearer picture of what this framework expansion actually transmits—and where its boundaries lie.
What the New E-Document Payment Tracking Actually Does
At its core, the update allows users to mark an electronic document as fully paid, partially paid, or unpaid. Rather than keeping that status trapped inside an internal accounting note, Business Central can now communicate that payment state across external networks, depending on how an organization’s e-document pipeline is configured.
According to Microsoft’s feature documentation, the directional flow works across both sides of the ledger:
- Accounts Payable Access Points: The system sends payment status information outward through configured accounts payable access points.
- Accounts Receivable Access Points: The system receives incoming payment status information through configured accounts receivable access points.
When payment tracking data travels with an e-document, it isn't just a simple boolean flag. Microsoft specifies three core pieces of financial metadata included in the e-document payment tracking payload:
- Date of payment collection: When the funds were actually collected.
- Amount collected, including VAT: The gross payment figure.
- Base amount and VAT amount at the time of payment: The specific tax breakdown separating net principal from value-added tax at the moment the payment occurred.
Why does the tax breakdown at the time of payment matter so much? Based on general industry knowledge of international VAT regimes and continuous transaction controls (CTC), several tax authorities require businesses to report not just when an invoice was issued, but when cash actually changed hands and how much tax was realized in that specific remittance—especially during partial payments. Microsoft notes in its release documentation that beyond boosting productivity by letting teams quickly see whether an e-document is unpaid, partially paid, or settled, the feature is designed to help businesses meet legal requirements in certain countries.
Summary of Core Capabilities
- Supports three explicit states: fully paid, partially paid, and unpaid.
- Transmits outward via accounts payable access points and ingests inward via accounts receivable access points.
- Captures collection date, total amount with VAT, and the specific base-versus-VAT split at the time of payment.
- Enabled automatically for end users in Worldwide Standard Multi-Tenant web environments, though underlying e-document services still require proper setup.
E-Document Status vs. Ledger Accounting: Knowing the Boundary
If you have spent any time administering an ERP system, you know that "enabled automatically for end users" is one of the most misunderstood phrases in enterprise software. Does this update mean Business Central is suddenly wiring money or replacing your bank reconciliation routines? Not even close.
To appreciate what Microsoft is doing here, it helps to separate document status messaging from financial ledger posting. According to Microsoft Learn’s documentation on managing receivables in Business Central, closing out sales invoices and purchase credit memos in your actual books still relies on established accounting workflows: importing bank statement feeds into the Payment Reconciliation Journal, matching lines in Bank Account Reconciliations, logging checks or cash on the Payment Registration page, or posting directly through the Cash Receipt Journal to customer and vendor ledger entries.
The E-Document framework operates alongside those accounting mechanics as a standardized communication layer. As Microsoft Learn’s E-documents overview explains, electronic documents in Business Central cover invoices and receipts in both directions and add capabilities for document-status-related messaging between access points. Marking an e-document as paid, partially paid, or unpaid—and transmitting or receiving its VAT and base amounts via an access point—is about synchronizing transaction lifecycle metadata with trading partners, service providers, and regulatory clearinghouses.
| Workflow Layer | Primary Tool in Business Central | Core Purpose |
|---|---|---|
| Document Exchange & Status Messaging | E-Document Core App & Access Point Connectors | Sends and receives e-invoices, receipts, and payment status payloads (paid, partially paid, unpaid, collection date, VAT split) across external endpoints. |
| Ledger Application & Bank Reconciliation | Payment Reconciliation Journal, Cash Receipt Journal, Payment Registration | Posts actual financial receipts, applies payments to open customer or vendor ledger entries, and reconciles system bank accounts against bank statements. |
Microsoft’s release note does not claim that marking an e-document as paid automatically posts a journal entry, nor does it detail how the system calculates partial installment splits, foreign currency fluctuations, or credit notes within the e-document payload. Administrators should treat this capability strictly as e-document status tracking and exchange rather than an automated banking engine.
The Long Road from Wave Plans to General Availability
If you feel like you have seen this feature name before, your memory isn't playing tricks on you. Tracking the lifecycle of this specific capability across Microsoft Learn reveals how complex regulatory framework features mature over multiple release cycles.
The feature title "Use payments with the E-Document framework" appeared in Microsoft Learn's 2025 release wave 1 and 2025 release wave 2 planning cycles, before carrying into the 2026 release wave 1 plan (which spans April through October 2026). In the Microsoft Learn documentation for Business Central Update 28.3 (last updated July 8, 2026), Microsoft listed "Use payments with the E-Document framework" under the Electronic documents product area as entering Public preview. Less than a month later, on August 3, 2026, the feature crossed the finish line into General Availability, with the Microsoft 365 / AI at Work Roadmap entry (ID 576813) reflecting its "Launched" status in October 2026.
Interestingly, the 2026 wave 1 release plan page on Microsoft Learn carries an October 2026 archival notice, reminding administrators that standalone Release Plans are being retired in favor of the unified roadmap and core Microsoft Learn technical documentation.
Prerequisites and Practical Checks for Administrators
Even though Microsoft marks this feature as automatically enabled for end users, payment statuses cannot travel through thin air. They rely entirely on your tenant's underlying E-Document architecture. If your finance team wants to take advantage of payment status tracking in Business Central, what should you verify in your environment?
- Confirm the E-Document Core App Is Installed: According to Microsoft Learn's E-documents overview, you must install the E-Document Core app in your Business Central environment to use the platform's electronic document capabilities.
- Avoid Legacy E-Invoicing Conflicts: In its Set Up E-documents documentation on Microsoft Learn, Microsoft warns that enabling certain legacy e-invoicing options on the Post and Send Confirmation dialog will lock your environment into legacy functionality and prevent you from using the modern E-Document framework.
- Configure Services, Workflows, and Sending Profiles: The E-Document framework requires configured e-document services, workflows, document sending profiles, and external access-point connectors to automate delivery and receipt.
- Verify Localization and Access-Point Support: Microsoft’s E-Document framework is built to be extended for local or industry-specific regulations. In its general overview documentation, Microsoft lists built-in localization support across several standards—such as Peppol PINT A-NZ for Australia and New Zealand; Peppol BIS 3 and OIOUBL for Denmark; Peppol BIS 3, XRechnung (UBL only), and ZUGFeRD for Germany; Peppol BIS 3 for Norway; Factura-E for Spain; and French e-invoicing support slated for 2026, with India, Italy, and Mexico listed as TBD on the new framework. However, Microsoft's roadmap announcement does not specify which individual countries, e-invoicing standards, or third-party access-point connectors currently support the new payment status messages.
Before promising your controller or tax auditor that Business Central will automatically satisfy a local e-invoicing payment-reporting mandate, check directly with your access-point provider and verify your specific regional localization app. The plumbing is now officially part of the core E-Document framework in Dynamics 365 Business Central—giving finance teams a clean, standardized way to track collection dates, gross receipts, and payment-time VAT splits right where their digital invoices live.