Business Central ADP integration from pay run to ledger
A Business Central ADP integration moves the accounting result of every ADP pay run into the general ledger. Each line lands on the correct account, department and project. Payroll stays in ADP, where tax filing and pay rules belong. We build the bridge, so finance no longer rekeys a payroll register into a journal after each cycle.
Last updated
What a Business Central ADP integration carries over
ADP produces a general ledger interface after each payroll. It holds totals for wages, employer taxes, benefits, deductions and net pay. These are split by whatever cost allocation you keep in ADP. That output is the core of the integration. It becomes a general journal in Business Central, ready to check and post.
A second flow is optional. It carries employee master data in one direction or both. New hires, terminations and department changes can then update the employee card. As a result, expense reports, time sheets and resource records point at current people. Leavers are blocked the same way.
Map your payroll data →
- ✓Gross wages by department
- ✓Employer tax liabilities
- ✓Benefit and deduction totals
- ✓Net pay clearing amount
- ✓Employee record changes
Which ADP product you run changes the design
ADP sells several payroll products for different company sizes, and they do not share data the same way. Some offer an API through the ADP marketplace. Others rely on a scheduled export file. The fields in the ledger output also differ. So we confirm what your edition and contract allow before we propose anything.
That check decides the method for your Business Central ADP integration. With API access, we can pull the payroll result on a schedule. With file output, we set up a secure drop location. An import then reads the file as soon as it lands. Both routes end in the same journal.
Check your ADP edition →- ✓ADP product in use
- ✓API access available
- ✓Ledger file format
- ✓Cost allocation fields
- ✓Pay frequency and groups
Mapping pay codes to accounts and dimensions
The heart of the work is a mapping table inside Business Central. Each ADP earning, tax and deduction code points at a ledger account. Each ADP department or location code points at a dimension value. Finance owns that table. A new pay code can be added without calling a developer.
Where labor has to reach projects, we map ADP allocation codes to job and job task numbers. Then wages post as project cost. For month end, a reversing journal handles accrued payroll. It uses the same mapping, so accrual and actual stay consistent.
Design the mapping together →- ✓Earning codes to expense accounts
- ✓Tax codes to liabilities
- ✓Departments to dimension values
- ✓Labor to jobs and tasks
- ✓Month-end accrual logic
How we deliver the Business Central ADP integration
We build the import as an AL extension. If an AppSource connector matches your ADP product, we configure that instead. The journal arrives unposted. It carries a balance check and a list of any code without a mapping. So nothing reaches the ledger until a person in finance has looked at it.
Testing uses real past pay runs in a sandbox. First, we import them. Next, we compare the journal to what staff posted by hand at the time. Then we explain every difference. Your payroll administrator and controller both sign off before the first live cycle runs through the new route.
Test on a past payroll →- ✓Working import in production
- ✓Editable mapping table
- ✓Unmapped code warnings
- ✓Short user instructions
- ✓Test results on past runs
Keeping payroll detail private
Most companies do not want individual pay visible in the ERP. So we import summary totals by account and dimension, not one line per person. Project costing may need employee detail. In that case, permission sets limit who can open those entries, and the journal batch is locked to named users.
The other risk to a Business Central ADP integration is drift. ADP adds a new deduction, or someone renames a department. The import then posts quietly to a suspense account. To prevent that, we add an alert on unmapped codes. We also add a simple monthly comparison between the ADP register total and the ledger. Both take minutes to read.
Discuss payroll data privacy →- ✓Summarized posting by default
- ✓Restricted journal batch
- ✓Permission sets for payroll
- ✓Suspense account alert
- ✓Register to ledger comparison
Business Central ADP integration questions
Does Business Central run payroll itself?
Not for the United States. Business Central has employee records and a way to post payroll results. Pay calculation and tax filing stay with a payroll provider such as ADP. So the integration connects the provider's output to your ledger. Your payroll team keeps working in ADP as before, and finance gets a journal that is ready to check instead of a register to retype.
Is there a ready-made Business Central ADP integration connector?
Third parties offer connectors on AppSource apps, and their coverage depends on the ADP product you use. We compare them with a custom import against your needs. Then we recommend whichever gives finance the cleanest journal with the least upkeep. If a connector fits, we set it up and test it. If not, we build the import ourselves.
Can wages post to projects?
Yes. ADP may hold a job or cost allocation on each pay line. Or time sheets in Business Central may supply the split. Either way, labor cost can post to jobs and job tasks. Project margins then include payroll without a manual reallocation. We test the split against a past pay run first, so the numbers match what your project managers expect.
Who maintains the Business Central ADP integration mapping?
Your finance team does. The mapping lives on a Business Central page with ordinary fields. So adding a pay code, or pointing a department at a new dimension value, is a routine edit. We stay available during US business hours for anything beyond that. We also leave a short written guide that explains each field and who may change it.
How is this different from a general payroll integration?
The principle is the same, but the details belong to ADP. File layouts, code structures and API access rules are specific to each ADP product. So is the way cost allocations are exported. The design has to follow them. A generic payroll template would miss those details, and the journal would need hand edits after each cycle.
Book a discovery call
Let's talk through your move to Business Central.
A focused call with a senior consultant. We learn how your business runs today, give you an honest view on whether Business Central fits, and outline scope and next steps before you commit to anything.
What happens after you send the form