Payroll Software for Microsoft Dynamics 365 Business Central: The UK Buyer’s Guide

Business Central Has No Built-In UK Payroll Module

Microsoft Dynamics 365 Business Central does not include a native UK payroll module. The standard product ships without Real Time Information (RTI) submission capability, P11D processing, pension auto-enrolment, or Attachment of Earnings Order (AEO) handling. UK businesses running Business Central must therefore add payroll functionality through one of three routes: a native AL extension available on Microsoft AppSource, a third-party application connected via API, or a manual journal export to a standalone payroll system.

This gap is deliberate by design, Microsoft positions Business Central as a platform, not a payroll engine but it creates a critical evaluation decision for UK finance directors and ERP administrators. Choosing the wrong integration architecture can mean duplicated data entry, failed RTI submissions, and HMRC penalties.

What UK Businesses Should Look for When Choosing a Business Central Payroll Solution

HMRC Recognition

Any payroll solution processing UK employee data must appear on HMRC’s recognised payroll software list, published at gov.uk. HMRC recognition confirms the software can file RTI submissions (Full Payment Submission and Employer Payment Summary) in the correct format. Verify recognition status directly on the gov.uk list before shortlisting any product—do not rely solely on vendor marketing claims.

Integration Architecture

How payroll data moves between the payroll engine and Business Central determines data accuracy and audit integrity. Three architectures are common:

• AL Extension (native): Built directly inside Business Central using Microsoft’s AL programming language. Payroll runs within the Business Central environment; general ledger postings, employee records, and payroll journals are unified in a single database. This is the tightest integration and the lowest risk of reconciliation errors.
• API Integration: A separate payroll application pushes completed payroll results to Business Central via API after each pay run. Employee master data and cost-centre mapping must be synchronised in both systems. Suitable when the payroll application offers capabilities not available in an AL extension.
• Journal Export: Payroll is calulated in an entirely separate system; the operator exports a journal file and imports it manually into Business Central. This is the loosest coupling and carries the highest risk of keying errors and period-end mismatches.

Statutory Compliance Features

A Business Central payroll extension must cover the full UK statutory compliance set:

AppSource Availability and Deployment Type

Solutions listed on Microsoft AppSource have passed Microsoft’s technical validation process and can be installed directly from the Business Central administration panel. AppSource availability is a meaningful quality signal, though some specialist providers supply certified extensions outside AppSource. Confirm whether the solution is deployed as SaaS (hosted by the vendor) or supports on-premise Business Central environments if your organisation runs a local instance.

Comparison of UK Payroll Extensions for Dynamics 365 Business Central

The table below covers named extensions that have been identified as targeting the Business Central UK payroll market. HMRC recognition and feature support should be independently verified against the gov.uk recognised software list and each vendor’s current product documentation before purchase, as these details change with product releases.

P11D Processing, Court Orders, and Pension Auto-Enrolment Inside Business Central

P11D and Benefits-in-Kind

P11D processing covers the annual reporting of taxable benefits provided to employees—company cars, private medical insurance, interest-free loans, and similar items. Within a native AL extension, benefit values can be maintained against employee records in Business Central throughout the year and submitted to HMRC at year-end. When using an API-connected or journal-export solution, P11D data typically lives only in the external system, requiring manual reconciliation against the Business Central general ledger.

Verify that any solution you evaluate handles Class 1A National Insurance contributions (reported on the P11D(b)) as well as the individual P11D per employee, and that electronic submission to HMRC is supported.

Court Orders and Attachments of Earnings

Employers in England and Wales are legally required to operate Attachment of Earnings Orders issued by courts. Correct processing requires:

• Calculating protected earnings (the minimum take-home pay the employee must retain)
• Applying the correct deduction amount from net pay
• Handling priority ordering when an employee has more than one live order
• Remitting deductions to the relevant court or authority

A native AL extension handles these calculations inside Business Central, producing an auditable payroll journal. API-connected solutions handle the calculation externally, with results posted back to Business Central. Confirm that the solution you choose handles both priority and non-priority orders and produces the required remittance documentation.

Pension Auto-Enrolment

The Pensions Regulator requires employers to automatically enrol eligible workers into a qualifying workplace pension scheme. Payroll software must:

• Assess worker eligibility on each pay reference period
• Apply postponement periods where permitted
• Process opt-out requests within the statutory window
• Calculate contributions on qualifying earnings
• Export a correctly formatted contribution file to the pension provider (NEST, The People’s Pension, Smart Pension, and others each have their own file format)

Native AL extensions that handle auto-enrolment inside Business Central allow pension costs to be posted directly to the correct nominal accounts without a manual import step.

How to Verify HMRC Recognition

HMRC maintains a list of recognised payroll software at gov.uk/payroll-software. Recognition is granted per product and per tax year. When evaluating any solution:

1. Search the gov.uk list by product name before shortlisting.
2. Confirm the recognition covers the current and upcoming tax year.
3. Check whether recognition covers RTI submissions only, or also includes CIS, expenses and benefits filing.
4. Ask the vendor to provide their HMRC product reference number.

Recognition on the HMRC list is a necessary but not sufficient condition—it confirms filing format compliance, not the quality of integration with Business Central.

Integration Architecture Decision Summary

Key Takeaways for UK Buyers

Business Central ships with no UK payroll capability. An extension or integration is always required.

Verify HMRC recognition independently on the gov.uk recognised software list, do not rely on vendor claims alone.

Native AL extensions offer the tightest integration and eliminate the manual reconciliation step inherent in journal export approaches.

P11D, court orders, and pension auto-enrolment are all supported by the leading native BC extensions, but feature depth varies—request a demonstration of each statutory workflow before signing a contract.

AppSource listing signals Microsoft technical validation and simplifies installation and upgrade management within Business Central.