+1 480 485 7373
Microsoft Teams
ADP stays the payroll engine; Business Central keeps the books
Companies moving to Business Central from Dynamics GP are sometimes surprised to find no payroll to migrate into. Microsoft's US version of Business Central does not calculate paychecks, withholding or payroll tax filings. So a payroll provider such as ADP carries that work. That is a sensible split: ADP handles changing tax tables and quarterly filings, and the ERP handles accounting.
So the integration is one-directional for money. ADP produces the numbers; Business Central receives a journal. A few reference lists can flow the other way. For example, payroll staff may need the department or project codes set up in Business Central when they assign employees or hours. Employee master data stays in ADP. We deliberately keep Social Security numbers, bank details and individual pay rates out of Business Central. We post totals per account and dimension, not per person, unless job costing truly needs employee detail.
Which ADP product you run matters. Most ADP payroll products can produce a general ledger report or export file, and some subscriptions offer API access. The format depends on your ADP product and plan, and so does code mapping before export. So in a Business Central ADP integration, confirm that with your ADP representative early.
Mapping ADP earnings, deductions and taxes to the ledger
Four ways to get the payroll journal into Business Central
Export file and journal import
We reshape ADP's general ledger export into a Business Central general journal through a configuration package or Edit in Excel. Low cost, but a person runs it every pay period.
Connector app on AppSource
Some vendors publish apps that import payroll files into journals with saved mappings. Check that the app reads your specific ADP export format before you buy.
Power Automate or iPaaS
A flow picks the export up from SharePoint or email and transforms it. Then it writes journal lines through the Business Central API and leaves them unposted for approval.
Custom API integration
Where your ADP plan exposes an API, a service pulls each finished run and builds the journal. Worth it with several companies, many pay groups or detailed job costing.
Payroll posting details controllers ask about
- ✓Pay periods that straddle month end, and whether you accrue the unpaid days with an automatic reversing entry
- ✓Several legal entities on one ADP account, each posting to its own Business Central company with an intercompany step
- ✓Voided checks and manual adjustments, which must arrive as their own journal lines rather than edits to a posted run
- ✓Labor charged to jobs, which needs hours by project from ADP timekeeping or from Business Central time sheets
- ✓Paid time off liabilities, if your policy requires accrued PTO on the balance sheet
- ✓ADP service fees, which arrive on a separate invoice and belong in purchasing, not in the payroll journal
Checking the first payroll journals before trusting them
- 1
Build the code map with payroll
Sit with whoever runs ADP and list every earning, deduction and tax code in use, including rarely used ones, with its account and dimension rule.
- 2
Replay past runs
Import two or three past payrolls into a sandbox. Compare totals to the ADP register and to what your old system posted.
- 3
Tie cash to the bank
Confirm that net pay, tax and benefit clearing accounts return to zero once you match the bank debits.
- 4
Stop unknown codes
Set the import to reject any line with an unmapped code. Then a new deduction added in ADP shows up as an error, not a mispost.
ADP payroll and Business Central questions
Can Business Central run our US payroll instead of ADP?
No, the US version of Business Central has no payroll calculation or tax filing module. Some partners sell payroll add-ons, but most US companies keep a dedicated provider. ADP already handles tax table changes, filings and year-end forms, so replacing it would add risk without much gain. The integration simply puts the accounting result where it belongs.
Should the journal post per employee or in summary?
Summary by account and dimension is the right default. It keeps pay data private, keeps the ledger short and still gives department and project reporting. Per-employee posting makes sense mainly when you cost labor to individual jobs and the job report must show who worked. Even then we avoid storing tax IDs or rates in Business Central.
How are department and project codes kept consistent?
Business Central is the owner of dimension values, and ADP uses the same codes. Whenever finance adds a department or project, payroll adds it in ADP before the next run. The import rejects any code that does not exist in Business Central, which catches mismatches on the first payroll rather than at quarter end. For projects, some companies send a list from Business Central to the payroll team on a schedule.
More Business Central ADP integration questions
What about ADP expense reimbursements or time tracking?
Yes, if they run through the same payroll, but they often suit a separate flow. Reimbursements paid through payroll need their own account so they do not inflate wage expense. Time tracking data matters when hours must reach Business Central projects for billing, which is a different integration from the payroll journal. We map each source on its own terms.
Is our payroll data safe going through an integration?
It can be, if the design keeps sensitive fields out and access narrow. Export files should land in a restricted location. Delete them once imported, and never send them by open email. The Business Central user or app registration that writes the journal gets permission for journals only. Posting totals rather than individual pay keeps most sensitive data inside ADP.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.