Business Central UK Payment Practices Reporting: 2024 Rules, Disputes and CSV Exports

Tracked under Microsoft’s AI at Work roadmap ID 576839 as part of the 2026 release wave 1 cycle, this update reached general availability on June 5, 2026, across Worldwide (Standard Multi-Tenant) cloud instances for the web client. Because the capability is enabled for end users automatically, UK finance teams do not need to wait on a complex feature-flag deployment to see the expanded reporting fields. Yet as any seasoned systems administrator will tell you, having a new button on an ERP page is not the same thing as achieving automatic legal compliance. Understanding what Business Central now tracks—and what UK statutory guidance still demands from human decision-makers—is essential before generating your next filing.

What Changed in the Business Central UK Localization​

Prior to this update, Business Central already included a baseline Payment Practices page in its British localization to help organizations track basic payment timing. However, when the UK amended its reporting legislation in 2024, the statutory requirements expanded beyond simple day-count averages and percentage buckets into monetary values and the root causes of payment delays.

According to Microsoft Learn’s 2026 release wave 1 documentation, the updated UK localization introduces three core functional additions to close that gap:

• Expanded Payment Practices Page Metrics: The existing Payment Practices page now captures additional data points required by the 2024 amendments, specifically the total value of payments made during the reporting period, late payments measured relative to agreed contractual terms, and the percentage of late payments caused by disputes.
• Purchase Invoice Dispute Mechanism: To calculate what share of late payments stemmed from genuine disagreements rather than slow processing, Business Central adds a dispute mechanism directly to purchase invoices. This allows accounts payable staff to link a delayed payment directly to a dispute status on the transaction record itself.
• CSV Export for Downstream Filing: Once the period data is compiled, users can export the Payment Practices report in CSV format so it can be used for submission or further processing.

Section Summary: Microsoft’s June 2026 update equips Business Central’s UK localization with native tracking for total payment values, overdue performance against agreed terms, and purchase invoice disputes, packaged with a CSV export option.

The Regulatory Backdrop: Why the 2024 Amendments Matter​

Why did Microsoft need to re-engineer purchase invoices to track arguments between buyers and suppliers? The answer lies in the UK government’s ongoing campaign to protect small and medium-sized suppliers from cash-flow crunches caused by larger corporate customers dragging their feet on bills.

According to official guidance published by the UK government on GOV.UK, the baseline duty to report stems from regulations made under the Small Business, Enterprise and Employment Act 2015 and the Limited Liability Partnerships Act 2000. Since April 2017, large qualifying UK companies and limited liability partnerships (LLPs) have been required to publish half-yearly reports on their payment practices, policies, and performance.

The Reporting on Payment Practices and Performance (Amendment) Regulations 2024 tightened that framework for company financial years beginning on or after January 1, 2025. Under the updated GOV.UK guidance, qualifying organizations must go beyond reporting the average number of days taken to pay and the volume proportions paid within 1–30 days, 31–60 days, and 61 or more days. They must also disclose value-based metrics and separate out how many late payments were held up because of a contractual dispute.

Who Actually Has to Report?​

Not every organization running the British version of Dynamics 365 Business Central is legally obligated to file these reports. As GOV.UK’s Duty to report guidance explains, the requirement applies only to "qualifying companies" (formed and registered under the Companies Act 2006 or prior legislation) and "qualifying LLPs" (registered under the Limited Liability Partnerships Act 2000) that exceed specific size criteria on their last two balance-sheet dates. Entities incorporated under foreign laws are excluded from this specific duty, even if they operate in the UK, though their UK-incorporated subsidiaries must report if they independently cross the size thresholds.

To fall into scope for a financial year, an individual company or LLP must exceed at least two of the three medium-sized company thresholds defined in section 465(3) of the Companies Act 2006 on its preceding two balance-sheet dates. Following the statutory threshold updates referenced in UK guidance, businesses must pay close attention to whether they cross two of the three markers (which rose to £54 million in annual turnover, £27 million in balance sheet total, and 250 employees from April 6, 2025, with parent companies subject to additional aggregate group tests). Crucially, GOV.UK stresses that reporting must be done at the individual legal entity level—submitting a single consolidated group report does not satisfy the law.

Furthermore, the UK government notes that separate 2025 regulatory amendments (Reporting on Payment Practices and Performance (Amendment) Regulations 2025) introduce retention-reporting rules specifically for qualifying construction contracts for financial years beginning on or after April 1, 2025. Administrators should note that Microsoft’s roadmap item 576839 specifically cites support for the 2024 amendment regulations, not the 2025 construction retention disclosures.

Section Summary: The 2024 UK regulations apply to financial years starting on or after January 1, 2025, requiring large UK-incorporated companies and LLPs at the individual entity level to disclose payment values and dispute percentages alongside traditional payment-timing statistics.

Where ERP Automation Meets Accounting Nuance​

It is tempting to read Microsoft’s business value statement—that Business Central "helps organizations stay compliant without manual data collection or spreadsheet work" —and assume the software handles the entire compliance lifecycle automatically. From an enterprise IT and financial governance perspective, however, software only knows what you tell it. When you compare Microsoft’s feature summary against the granular rules in GOV.UK’s statutory guidance, several critical operational boundaries emerge.

1. Paid Invoices vs. Overdue Invoices Are Separate Datasets​

One of the easiest traps in UK payment reporting is mixing up the population of invoices used for different statistics. According to GOV.UK’s reporting guidance:

• Payments Made in the Period: Metrics covering the average time taken to pay and the 30/60/61+ day buckets include only payments actually made during the reporting period under qualifying contracts. If an invoice arrives mid-period and remains unpaid when the period closes, it is excluded from these figures and waits until the period in which it is finally paid.
• Payments Due but Not Paid Within Agreed Terms: Conversely, the metrics measuring late payments—including the total value of payments not paid within the agreed period, the percentage of late payments, and the percentage of late payments caused by disputes—examine payments that were contractually due within the reporting period, regardless of whether they were paid late during the period or remained unpaid at the end of it. (Invoices that were already overdue before the reporting period began are excluded so they are not double-counted across consecutive reports.)

2. How Disputed Invoices Behave Across Metrics​

Business Central’s new purchase invoice dispute mechanism lets AP teams flag delayed payments as disputed. How does UK law treat those flagged transactions? According to GOV.UK, marking an invoice as disputed does not erase it from your late-payment statistics.

Consider a practical example drawn directly from the GOV.UK framework: suppose a company has 4 payments under qualifying contracts that fall due within the reporting period and are paid outside the agreed contractual terms. Only 1 of those 4 was held up because of a genuine contractual dispute, while the other 3 were simply paid late without a dispute. Under the regulations:

1. All 4 invoices count toward the proportion and value of payments due in the period that were not paid within agreed terms.
2. Because 1 out of the 4 late payments resulted from a dispute, the company reports that 25% of its late payments were not paid within agreed terms due to a dispute.
3. Once that disputed invoice is eventually paid, it is also included in the standard payment-time statistics (average days to pay and the 30/60/61+ day buckets) for the period in which the payment clears.

3. Qualifying Contracts vs. Everything in the Purchase Ledger​

An ERP purchase ledger typically contains every bill a company receives: utility bills, business rates, intercompany recharges, financial services fees, and overseas vendor invoices. However, GOV.UK explicitly instructs businesses to report only on "qualifying contracts"—broadly defined as business-to-business contracts for goods, services, or intangible property that have a significant connection to the UK, while excluding contracts for financial services and non-contractual statutory charges like business rates. Similarly, invoices fully settled via credit notes or 100% offsetting do not count as "payments made" in the timing statistics.

Because Microsoft’s public release-plan documentation does not detail the exact filtering logic, field names, or setup steps used by the Payment Practices page, finance teams cannot blindly export the CSV and upload the numbers. You must verify how your Business Central chart of accounts, vendor posting groups, and purchase invoices distinguish qualifying B2B contracts from out-of-scope transactions.

Section Summary: While Business Central automates the tracking of dispute flags and payment values, finance teams must ensure their underlying ERP data respects UK statutory rules on qualifying contracts, credit notes, and the distinct calculation rules for paid versus due-and-late invoices.

Architectural Context and Documentation Caveats​

For IT administrators managing Dynamics 365 Business Central tenants in the UK, this feature arrives during a broader architectural transition. According to Microsoft Learn’s United Kingdom local functionality documentation, starting with Business Central 2025 release wave 2 (version 27), Microsoft began transitioning the UK localization to operate as a set of extensions built on top of the international W1 Base App. Microsoft gave customers a three-release window to choose whether to enable the new extension-based features before the legacy localization features are deprecated and the new architecture becomes mandatory. While Microsoft’s release notes do not state that the 2026 wave 1 Payment Practices update requires a specific localization migration step, administrators maintaining customized UK environments should keep this extension architecture in mind when testing updates.

There is also an important documentation caveat to note. As of October 2026, Microsoft Learn’s 2026 release wave 1 plan page for Use Payment Practices in the UK localization (last updated August 27, 2026) carries an archive notice stating that the release-plan entry is no longer maintained and directs administrators to live product documentation for authoritative guidance. Because the archived release-plan page outlines the high-level capabilities without providing click-by-click setup instructions or exact CSV schema mappings, administrators should inspect the live Payment Practices page directly inside their Business Central sandbox environment before relying on it for a statutory filing.

Practical Checklist for UK Finance and ERP Teams​

If your organization falls within the UK’s payment practices reporting thresholds—or if you submit reports voluntarily—here is how to put Business Central’s updated localization to work safely:

1. Inspect the Payment Practices Page in a Sandbox: Because the feature rolled out automatically in June 2026 for Worldwide Standard Multi-Tenant web environments, open the Payment Practices page in a copy of your production company to review the new columns for total payment value, late payments against agreed terms, and dispute percentages.
2. Establish a Clear AP Workflow for the Dispute Mechanism: Train accounts payable staff on when to use the new dispute mechanism on purchase invoices. Ensure your internal policy aligns with the UK government’s definition of a contractual dispute so clerks do not casually flag routine administrative delays as "disputes" just to make the department’s metrics look better.
3. Audit Contract Scope and Payment Terms: Verify that vendor payment terms on purchase invoices accurately reflect agreed contractual terms (since GOV.UK rules measure lateness against the agreed contract period, not internal payment-run schedules). Confirm how you will exclude non-qualifying items such as business rates, financial services, or fully credited invoices.
4. Reconcile the CSV Export Before Director Sign-Off: Export the report to CSV and spot-check a sample of paid, overdue, and disputed invoices against the calculation formulas in GOV.UK’s guidance. Remember that the CSV export does not automatically transmit your filing to Whitehall: a named company director or designated LLP member must formally approve the figures, and the report must be published on the UK government’s web-based service within 30 days of the end of the six-month reporting period.

Section Summary: Administrators should validate the automatically enabled Payment Practices page and purchase invoice dispute controls in a sandbox, align AP dispute-flagging habits with statutory definitions, and reconcile the exported CSV data prior to director approval and online submission.