Dynamics 365 Business Central HR & Payroll Module: AL Architecture & GCC WPS [2026] | DataDaur

In Microsoft Dynamics 365 Business Central, the finance, sales, inventory, and purchasing engines are mature and deeply integrated — but when it comes to Human Resources and Payroll, the platform leaves a deliberate gap.

This article covers two topics:

• The business benefits of managing HR and Payroll inside Business Central rather than in separate, disconnected systems.
• Why a complete, region-specific payroll capability is not part of standard Business Central, and how we closed that gap by building a custom HR & Payroll module.

Part 1 — Why HR and Payroll Belong Inside Business Central

Business Central acts as the financial system of record. When HR and payroll operate in isolated silos, every salary payment, deduction, and accrual must be re-keyed or pushed through fragile API middleware. Consolidating these functions natively eliminates integration overhead.

Benefits for Human Resources

• A single source of truth for employee data. Personal details, departments, grades, and compensation all live in one place, tied directly to the finance system that pays them.
• No dual data entry. A new hire, a promotion, or a salary change is entered once and is immediately available everywhere it is needed.
• Cleaner reporting. Headcount, cost-per-department, and compensation analysis run against live ERP data instead of exported spreadsheets.
• Auditability. Every change to an employee record sits inside the same controlled, permissioned environment as the rest of the business's financial data.

Benefits for Payroll

• Direct posting to the general ledger. Payroll runs produce journal entries that flow straight into Business Central's financials — no manual uploads, no reconciliation gaps.
• Accuracy and consistency. Earning codes, deductions, and pay amounts are calculated from the same master data that HR maintains, eliminating mismatches.
• Real-time financial visibility. Salary cost is reflected in the company's numbers the moment payroll is posted.
• Compliance and control. Approval workflows and bank-file generation build governance and statutory compliance directly into the pay process.

The value of native integration

The architectural value lies in the data pipeline. HR owns the master data; payroll consumes it. A department transfer updates the general ledger allocation. A mid-month termination triggers a prorated final settlement. When both engines share the same Dataverse/SQL backend, the data flows synchronously without manual reconciliation.

Part 2 — The Standard Architecture Gap

Business Central includes a lightweight Human Resources module. Out of the box, it stores employee master records, registers absences, and tracks qualifications. It serves as a rudimentary data repository.

Business Central does not include a payroll engine. This is not an oversight — it is a deliberate decision by Microsoft. Payroll is left to certified partners and third-party add-ons, for sound reasons:

• Payroll rules are intensely local and regional.
• Tax rates, contribution thresholds, and statutory calculations change constantly.
• Every country — and often every industry — has its own processing and reporting requirements.

Maintaining all of that, everywhere, is not something Microsoft chose to own. As a result, real payroll in Business Central comes from country-specific solutions or from custom development.

Part 3 — Inside the Custom Module

The module is organized around two pillars: Human Resources as the foundation that holds employee and organizational data, and Payroll as the engine that turns that data into accurate, approved, disbursable pay. Below are the ten capabilities the module delivers.

Human Resources — the foundation

1. Employee & department details. The module maintains employee master records organized by department, giving the business a clear organizational structure. Department assignment is more than a label — it drives reporting, cost allocation, and the grouping of payroll costs across the organization.
2. Salary details. Each employee carries their own salary configuration — the base figures and components that define what they are paid. Because this sits on the employee record inside Business Central, it is always in sync with the data payroll uses to calculate pay.
3. Compensation based on employee grades. Rather than defining pay in isolation for every person, compensation is structured by employee grade. Grades standardize pay bands and benefit entitlements across the organization, so compensation is consistent, easy to govern, and simple to update — a change at the grade level flows through to everyone it applies to.

Payroll — setup and structure

4. Payroll periods. Payroll periods define the calendar of pay cycles. Every run, calculation, and report is anchored to a period, giving the whole process a consistent time framework.
5. Earning codes. Earning codes are the configurable building blocks of an employee's pay — the individual components (basic, allowances, and other earnings) that combine to form total compensation. Defining pay as codes makes the structure flexible and transparent rather than hard-coded.

Payroll — calculation

6. Prorated amounts. When an employee joins, leaves, or changes status partway through a payroll period, they should be paid only for the portion worked. The module calculates prorated amounts automatically, ensuring mid-period changes are paid fairly and accurately without manual adjustment.
7. Loans. Employee loans are managed within the module and recovered directly through payroll as scheduled deductions. Loan balances and repayments are tracked over time, so recovery is automatic and visible rather than tracked on the side.

Payroll — approval, disbursement, and reporting

8. Salary approval workflow. Payroll does not move straight from calculation to payment. A salary approval workflow routes each run for the required sign-off, moving it from draft to approved only once authorized. This builds governance and accountability directly into the pay process and creates a clear audit trail.
9. Bank files. Once approved, the module generates bank files — the structured payment files used to disburse salaries through the banking system. For Saudi Arabia this is the mechanism that supports salary payment under the Wage Protection System (WPS), turning an approved payroll run into a file the bank can process.
10. Monthly salary reports. The module produces monthly salary reports that give HR, finance, and management clear visibility into pay for each period — supporting review, reconciliation, and record-keeping.

Part 4 — Extending to Employees: The ESS Portal

Beyond the core Business Central module, employee-facing functionality is delivered through an Employee Self-Service (ESS) portal built on the Microsoft Power Platform. This extends selected capabilities — such as loan requests, payslip visibility, and leave applications — out to employees directly, while Business Central remains the system of record behind it.

Employees interact with the portal via Microsoft Power Apps; the approved data is securely written back to Business Central using Dataverse and standard API endpoints.

Tayyab Mughal

Author

Principal Agentic AI Engineer & Enterprise ERP Solution Architect

Connect on LinkedIn

Tayyab Mughal is a Principal AI Engineer and Enterprise ERP Solution Architect specializing in autonomous Agentic AI frameworks (Vantura), multi-step ReAct reasoning loops, on-device SLMs, and mission-critical ERP implementations across Microsoft Dynamics 365 (F&O, Business Central) and Odoo 19. He leads technical architecture and consulting engagements globally across North America, the UAE, and Europe.

#AutonomousAI&ReActLoops#Dynamics365(F&O/BC)#Odoo19Enterprise#DataverseIntegration#Zero-DowntimeMigration