Resource Center Home
Resource Center Home

HR and Payroll for Business Central

HR and Payroll for Business Central

How to restore benefit deductions syncing from HR to Business Central in Full Lifecycle for BC – PEPM

Benefit Deductions Not Flowing from HR to Payroll NOW for Business Central

Applies to: Integrity HR with Payroll NOW for Business Central (HR-to-Payroll benefit deduction integration)

Last reviewed: June 2026

Summary

Benefit deductions configured in HR for an employee fail to appear in Payroll NOW, forcing payroll staff to enter those deductions manually every pay cycle. This article explains why this happens, how to identify the misconfigured benefit plan that causes it, and how to correct it so the deductions flow automatically again.

Symptom

  • One or more benefit deductions set up in HR (for example, medical, life, flexible spending, or retirement) do not appear in Payroll NOW for an affected employee.
  • Payroll staff must manually add the missing benefit deductions to the affected employees on every payroll run.
  • Several otherwise-unrelated deductions for the same employee may all be missing at once.
  • Newly hired employees typically sync correctly; the problem is concentrated on certain existing employees.

How the Integration Works

The HR-to-Payroll integration transmits each employee’s benefit deduction data to Payroll NOW. All of an employee’s benefit deduction lines are sent together as a single employee-deduction record. Payroll NOW validates that record as a whole: every line must reference a payroll deduction code that exists, and is not blocked, in Payroll NOW. If the record passes validation, the employee’s deductions are created or updated; if any part of it fails validation, the entire update is rejected.

Cause

The root cause is a benefit plan in HR that is missing its employee deduction code. When a plan is set up — or later changed — with only the employer contribution code populated and the employee deduction code left blank, the integration emits a deduction line with a blank (empty) deduction code for every employee enrolled in that plan.

Because the employee-deduction record is validated as a single unit, that one invalid line causes Payroll NOW to reject the whole record, typically with an error indicating that a payroll code does not exist (for example, “The Payroll Code does not exist, Code=””). As a result, none of that employee’s benefit deductions post — including correctly configured, unrelated plans such as retirement or flexible-spending deductions.

New hires often sync without issue because their enrollments were created after the plan was configured correctly, or their records simply do not carry the problematic line. The failure concentrates on existing employees whose records include the incomplete plan line.

Diagnosing the Affected Benefit Plan

  1. Identify the affected employees — those whose benefit deductions are missing in Payroll NOW and require manual entry each cycle.
  2. Review the benefit plans assigned to an affected employee in HR. Look for any plan that has an employer contribution code but no employee deduction code (a blank deduction-code mapping).
  3. Check whether the same plan is shared by the other affected employees. A single misconfigured plan commonly affects everyone enrolled in it.
  4. In Payroll NOW, verify the deduction code the plan should reference: Full Payroll Menu >> Setup >> Payroll Codes. Confirm the intended code exists as a Deduction-type payroll code and that its Blocked field is not set to Yes.

Resolution and Workaround

  1. Correct the benefit plan mapping in HR. Open the affected plan and populate the employee deduction code (and confirm the employer contribution code if the plan has an employer-paid portion). Both codes referenced by the plan must correspond to existing, unblocked payroll codes in Payroll NOW.
  2. If the required deduction code does not yet exist in Payroll NOW, create it first (see Related Resources below), then map it on the plan.
  3. Re-apply the corrected plan to each affected existing employee and trigger a re-sync of their benefit data so the corrected mapping is transmitted to Payroll NOW.
  4. To keep payroll on schedule while corrections are in progress, the affected deductions may be entered manually on the impacted employees for the current cycle. This is an interim measure only — once the plan mapping is corrected and re-synced, the deductions will flow automatically.
  5. If, after correcting the plan and re-syncing, an existing employee’s deductions still fail to post, the integration record for that employee may still contain a leftover line from the original incomplete setup. Re-adding the plan deduction code to the EE’s deduction view card can correctly code the line and remove the original blank-code line, so the record continues successfully. If you encounter this, contact Integrity Support — clearing the leftover line may require assistance beyond the HR benefits screens.

Verification

  1. After the corrected sync, open the affected employee in Payroll NOW (Full Payroll Menu >> Employees >> Payroll Employees) and confirm the expected benefit deduction lines now appear.
  2. Confirm that the previously failing, unrelated deductions for that employee (for example, retirement or flexible-spending deductions) are now present as well.
  3. Run a trial or preview payroll for an affected employee and verify all expected benefit deductions calculate correctly before processing the live batch.

Key Points to Remember

  • A single invalid benefit line blocks all of an employee’s benefit deductions, not just the misconfigured one. When several deductions disappear for the same employee at once, suspect one bad line rather than multiple separate problems. Update the deduction code on the deduction view card in HR to fix.
  • The issue is configuration-based and tends to cluster on a shared plan; correcting the plan mapping resolves it for everyone enrolled.
  • Always confirm that referenced codes exist and are unblocked in Payroll NOW before re-syncing.

Related Resources

Questions / Resources

If you have questions or comments please email support@integrity-data.com.

Last Review: June 2026

Was this article helpful?
Views: 15

Leave A Comment