ADP TotalSource
One journal entry per pay run, per company — every mapped employee summed into a single consolidated entry, not one line each.
Overview
Payroll from ADP TotalSource arrives in DualEntry already summarised. Instead of a journal entry per employee, DualEntry creates one entry per pay run, per company, summing every employee mapped to that company into a single consolidated entry.
DualEntry pulls entities, companies, employees, payments and pay statements from ADP, maps each pay statement item to a GL account, and posts the result against your payroll vendor. Locations come across as their own mappable company rows, so a multi-company group posts to the right books without anyone sorting rows by hand.
The connection is read-only. Approvals stay in ADP; DualEntry takes the financial result.
Provider entities
Companies
Payroll vendor
Pay statement items
Employees
Departments
Payments
Pay statements
Data synced
The integration syncs the following data types:
Key Features
- Consolidated by company, not by employee
Pay statements are grouped by payment and split by each employee's mapped company, producing one journal entry that sums lines across every employee in that company.
- Locations map to their own companies
ADP locations arrive as separate mappable rows, so multi-entity groups post each location's payroll to the correct set of books.
- Pay statement items drive the GL
Every earnings line, tax, deduction and employer contribution maps once to a GL account and reuses that mapping on each run.
- Choose how entries are dated
Date journal entries by payment date or by period end, whichever matches how you close.
- Optional tax consolidation
Collapse payroll tax lines into a single consolidated line, or leave each tax type on its own line.
- Read-only by design
Data flows one way. DualEntry never pushes your chart of accounts or journal entries back into ADP.
.avif)