Leave and absence in Dynamics 365 Human Resources

Leave administration is one of HR's most reliably high-volume processes — every employee, multiple times per year, across multiple leave types, with country-specific policies. Dynamics 365 Human Resources provides the leave engine, the request workflow, and the integration with payroll and time tracking. The depth of configuration is what makes or breaks deployments.

Leave plans. A leave plan defines an allowance:

• Leave type — Vacation, Sick, Personal, Parental, Bereavement, Jury Duty, etc.
• Accrual method — fixed annual grant, monthly accrual, hourly accrual.
• Accrual frequency — monthly, per pay period, continuous.
• Maximum balance — cap.
• Carry-over rules — what rolls over between years.
• Probation — accrual restrictions for new hires.

Each country, sometimes each business unit, has different leave plans matching local employment law.

Accruals. The mechanism that grows the balance:

• Front-loaded — full year's allowance granted on day 1 of the leave year.
• Periodic accrual — equal amounts added each period (monthly accrual at 1.67 days/month for 20 days/year).
• Hours-worked accrual — leave earned per hours worked (common for hourly employees).
• Tenure-based — accrual rate increases with years of service.

The accrual engine runs periodically (typically monthly) calculating each employee's earned leave per plan.

Balance display. Employees see:

• Available balance — currently usable.
• Accrued to date — earned in current year.
• Used to date — taken in current year.
• Future scheduled — approved future leave.
• Carried over from prior year.

Leave request workflow.

1. Employee selects leave type, dates, hours per day.
2. System checks balance availability.
3. Manager approves (or rejects with comments).
4. Approved leave deducts from balance.
5. Calendar / Outlook integration shows the time off.

For longer or unusual leave (parental, sabbatical), additional approval levels and HR review.

Balance checks at request time. When an employee requests leave:

• Balance available ≥ requested.
• Date in valid range (no past-dated without retroactive approval).
• No overlap with existing approved leave.
• Within policy (max 10 consecutive days; can be overridden by HR).

Violations either block or require additional approval.

Carry-over policies.

• Use-it-or-lose-it — unused leave expires at year end.
• Capped carry-over — N days max roll over.
• Unlimited carry-over — full balance preserves.
• Cash-out — unused leave paid out at end of year.

Country and union agreements determine the policy; the system enforces.

Holiday calendars. Public holidays are configured per location:

• Country-specific calendars.
• Regional variations (US state holidays).
• Floating holidays (Easter, religious observances).
• Company-specific (founder's day).

Holidays aren't deducted from leave plans (typically); they're scheduled time off.

Time-off types beyond leave.

• Compensatory time — overtime banked as time off.
• Time-off in lieu (TOIL) — flex schedule trades.
• Unpaid leave — leave without pay arrangements.

The system models each separately with own accrual and tracking.

Integration with payroll. Leave drives payroll:

• Paid leave — paid at regular rate during absence.
• Unpaid leave — no pay during absence.
• Partial pay — disability, parental at reduced rate.

The integration pushes leave data to the payroll system. For organisations on D365 HR + a third-party payroll (the typical model in 2026 since Microsoft's payroll engine was sunset), the integration is a defined data export.

Time and attendance. For hourly employees, hours worked feed leave accrual. Integration:

• Time clock data → daily hours → leave accrual.
• Tracking against schedule.
• Overtime calculation.

D365 HR works with time and attendance ISVs (UKG, Replicon, etc.) where deeper T&A capability is needed.

Leave reports.

• Balances summary — by employee, department, plan.
• Accrual history.
• Usage trends — leave-day distribution by month, by reason.
• Liability — accrued unused leave (a balance sheet liability).

The liability report is auditor-critical — accrued PTO is real money that must be on the balance sheet.

Country-specific complexity.

• EU directives — minimum 4 weeks annual leave; carry-over rules; sick leave separation.
• US FMLA — federal family medical leave protections.
• California paid sick leave — separate accrual rules.
• Maternity / parental leave — country-specific durations and protections.

Localisation packs handle most of this; specific business policies layer on top.

Common pitfalls.

• Wrong accrual frequency. Monthly when it should be per-pay-period; balances drift.
• Carry-over not enforced. Year-end runs but doesn't truncate balances; liability explodes.
• Approval bottleneck. Manager on PTO; their approvals stall; team can't get vacation approved.
• Calendar integration miss. Approved leave doesn't reach Outlook; meetings scheduled during PTO.
• Manual overrides poorly tracked. HR adjusts balances manually; audit trail thin.
• Policy creep. Each year new exception added; complexity overwhelms.

Operational rhythm. Daily request approval; monthly accrual run; quarterly review of balances and accrual adjustments; annual carry-over execution. The cadence matters; mature HR operations build it into their calendar.

Strategic positioning. Leave administration is unglamorous but operational core HR. Get it right — the system supports the workflow, employees self-serve, managers approve quickly, balances are correct — and HR can focus on the work that matters. Get it wrong, and the HR team spends hours weekly fielding "where's my PTO?" tickets. Configuration investment upfront pays back for years.