Dynamics 365 Human Resources: Features, Payroll and Fit

Many companies run finance in one system and keep people data in another. HR and finance leaders know the result: positions that do not match the org chart in the ERP, cost centers rekeyed by hand, approvals in email, and a payroll file rebuilt every pay period. When a company moves to Dynamics 365 Finance or Supply Chain Management, the natural question is whether HR should move onto the same platform.

This guide explains what Dynamics 365 Human Resources covers, how it shares data with Finance and Supply Chain Management, how payroll works with it in the US, and where reporting, automation and data privacy fit. It ends with a balanced view of when it fits better than a dedicated HCM suite, and a planning checklist. It is written for HR and finance leaders at mid-sized and larger companies.

What Dynamics 365 Human Resources covers

Dynamics 365 Human Resources is Microsoft's core HR application within the Dynamics 365 Finance and Operations apps. Its main areas are:

• Core HR records: workers, employment details, personal information, documents and history.
• Organization and positions: departments, jobs, positions, reporting lines and position hierarchies. Positions can exist before anyone fills them.
• Leave and absence: leave plans, accrual rules, balances, requests and approvals.
• Benefits: plans, eligibility rules, enrollment and life events.
• Compensation: fixed and variable compensation plans, pay grades or ranges, and compensation review processes.
• Performance and goals: goal setting, reviews and ongoing feedback.
• Training and certifications: courses, skills, certificates and expiration tracking.
• Onboarding: checklists and tasks for new hires, assigned to HR, managers, IT and the new hire.
• Employee and manager self-service: employees update their details, request leave and enroll in benefits. Managers approve requests and see their teams.

Microsoft moved Human Resources onto the same finance and operations platform as Finance and Supply Chain Management, and retired the earlier standalone version. Check Microsoft's documentation for the timing, especially if you are reading older material about the standalone product. Features also change with service updates, so confirm current scope against Microsoft's release plans.

One platform with Finance and Supply Chain Management

The strongest argument for Dynamics 365 Human Resources is that it is not a separate system. It shares the platform, the database and the security model with Dynamics 365 Finance and Supply Chain Management. That has practical effects.

One employee and position structure

There is one worker record and one position structure. When HR hires someone into a position, that worker is available to purchasing, expenses, projects and production without a second record. A department change is made once.

Approvals that follow the org chart

Workflow approvals in Finance and Supply Chain Management, such as purchase requisitions, vendor invoices and expense reports, can route by position hierarchy or reporting line. If HR keeps that hierarchy accurate, approvals reach the right manager after a reorganization, with no second hierarchy to keep in step.

Cost centers through financial dimensions

Positions and workers can carry financial dimensions, such as department, cost center or business unit. Payroll costs, expense reports and project costs can then post to the general ledger with the same dimensions that finance uses for reporting. For a finance leader, this is often the reason to care: labor cost reports reconcile to the ledger because they start from the same structure.

Project and production worker data

Project accounting and Project Operations use workers and roles for resourcing and timesheets. Production control uses workers for shop floor job registration. A manufacturer with two plants in different states, for example, can maintain shift workers once in HR and use them for time registration and labor costing at both plants.

The payroll question

This is the most common question from US buyers. Dynamics 365 Human Resources is not a full US payroll engine. It does not, as a general rule, calculate federal, state and local tax withholding, file payroll tax returns or produce W-2s the way a dedicated payroll product does. US companies usually run payroll in a third-party or partner payroll product and connect it through integration. Microsoft's payroll scope and partner options can change, so confirm the current position in Microsoft's documentation.

What Human Resources does well is act as the system of record for the data that payroll needs. A typical integration moves this information each pay period:

From Human Resources to payroll:

• New hires, rehires and terminations, with effective dates
• Changes to position, department, location, manager and pay rate
• Compensation changes and one-time earnings
• Benefit enrollments and the deductions they create
• Leave taken and leave balances, where payroll needs them
• Hours from time capture, if it comes from project timesheets or production registration

From payroll back to Finance:

• A payroll journal summarized by account and financial dimension, posted to the general ledger
• Employer taxes and benefit costs, allocated to cost centers or projects

The key design decisions are which system owns each field, how mid-period effective-dated changes are handled, and how errors are caught before a payroll run. Data moves through data entities, the Data management framework or APIs, often orchestrated by an integration platform. Plan a parallel payroll run during testing and reconcile it line by line before go-live.

Reporting and people analytics with Power BI

Human Resources includes standard workspaces and reports for day-to-day work. For people analytics across headcount, turnover, leave usage, compensation and labor cost, most companies use Power BI.

Because HR and financial data share a platform, one Power BI model can combine headcount by position with labor cost by financial dimension. A services firm with 900 employees, for example, could track billable headcount, open positions and labor cost per department in one report, instead of joining an HCM export to a finance export in a spreadsheet.

Two points to plan for:

• Sensitive measures need sensitive handling. Salary, performance ratings and leave reasons should be in a restricted model or protected with row-level security, not in a general report everyone can open.
• Definitions matter more than visuals. Agree on what counts as headcount, a hire, a termination and turnover before building reports. Our article on Power BI dashboard best practices covers how to keep leadership reports focused.

Automating HR processes with Power Automate

Human Resources has its own workflow engine for approvals. Power Automate extends that to the rest of Microsoft 365 and to outside systems. Common examples:

• Onboarding tasks: when a hire is confirmed, create the account request for IT, order equipment, add the new hire to Teams channels and send the manager a first-week checklist.
• Leave approvals in Teams: managers receive leave requests as approval cards in Microsoft Teams and approve them without opening the HR system. Microsoft has offered Teams integration for leave in Human Resources; check current documentation for what is built in versus what you add with Power Automate.
• Certification reminders: notify a worker and their manager before a required certificate expires.
• Offboarding: trigger access removal and equipment return from a termination date.

Keep sensitive data out of flow notifications and email bodies, and give each production flow a named owner.

Security and privacy of employee data

Employee data is among the most sensitive information a company holds. Human Resources uses the platform's role-based security model: users get roles, roles grant duties and privileges, and access can be limited by legal entity. Plan these points early:

• Role design: separate HR administrators, HR generalists, managers, payroll staff and finance users. Finance users often need worker names and dimensions but not salary, medical leave reasons or personal contact details.
• Self-service scope: decide which fields employees can change themselves and which require HR approval.
• Retention and deletion: define how long you keep records for former employees and applicants, and how you remove them afterward.
• Integrations and analytics: every copy of HR data in a payroll system, data warehouse or Power BI model needs its own access controls.
• Audit: turn on the logging you need to show who changed sensitive records.

Privacy and employment record laws differ by state and country, and they change. The system can support compliance but does not guarantee it, so confirm your retention and privacy requirements with legal counsel.

When it fits and when a dedicated HCM suite fits better

Both approaches are reasonable. The right answer depends on what drives your HR needs.

A distributor with three warehouses, a few hundred employees and Dynamics 365 Supply Chain Management already in place will often find the shared platform worth more than extra HR features. A company whose main HR problem is recruiting at volume, or that wants payroll and HR from one provider, may be better served by a dedicated HCM suite integrated to the ERP. Some companies run both: a dedicated HCM for talent and recruiting, with core worker and position data flowing into Dynamics 365.

Licensing matters too. Human Resources is licensed per user, and attach licenses may apply when users already hold another Dynamics 365 base license. Rules change, so confirm current licensing and pricing with Microsoft or a partner.

Implementation checklist

• Map your current HR processes, systems and data owners, including payroll, benefits and time capture
• Decide which system owns workers, positions, compensation and benefits data
• Design the organization and position hierarchy with both HR and finance in the room
• Agree on financial dimensions for positions and labor cost posting
• Choose a payroll provider and define the integration fields, frequency and error handling
• Define leave plans, accrual rules and how balances will be migrated
• Design security roles, including what finance and managers can and cannot see
• Set retention rules for employee and applicant records and review them with counsel
• Plan data migration for active workers, history you need to keep and open balances
• Test self-service with real employees and managers
• Build key approvals and automations, such as onboarding and leave requests
• Run at least one parallel payroll and reconcile the results
• Train HR staff, managers and employees, and plan support for the first pay periods after go-live

Next steps

If you run, or plan to run, Dynamics 365 Finance or Supply Chain Management, start with a short assessment of your HR and payroll processes. Map where worker data lives, who owns it and what payroll needs each period. That usually shows whether Human Resources, a dedicated HCM suite or a mix is the better fit.

If you want help with that assessment, or with the payroll integration, reporting and automation around it, talk to our team.