Paylocity Integration | DualEntry
Paylocity
Overview
Payroll is one of the largest recurring entries in the ledger and one of the least rewarding to type twice. Without a connection, every Paylocity pay run means rekeying earnings, taxes, deductions and employer contributions into the general ledger, then reconciling whatever does not tie out.
DualEntry connects to Paylocity through a hosted widget, using Paylocity administrator credentials and the data scopes you approve, and data flows "one way: Paylocity to DualEntry". The initial sync deliberately retrieves metadata only — companies, vendors, pay items and departments — so the required mappings can be finished before a single pay statement posts. After that, DualEntry syncs Paylocity every 24 hours by default, on an interval you can set anywhere from 30 minutes to 30 days, with on-demand syncs available during close.
One thing to settle before connecting: Paylocity "posts one journal entry per employee pay statement", so a 40-person pay run generates 40 separate entries. Ledger volume scales with headcount, and per-employee compensation lands in the GL — which the documentation advises handling by tightening "roles and permissions before connecting Paylocity rather than after the first pay run posts".
Data synced
The integration syncs the following data types:
No items found.
Key Features
- One-way authenticated sync
Data flows one way, Paylocity to DualEntry. You authenticate with Paylocity administrator credentials through a hosted widget and approve the requested data scopes. - Metadata-first initial sync
The first sync retrieves companies, vendors, pay items and departments only, so the required mappings can be completed before any pay statement posts. - Configurable sync schedule
DualEntry syncs Paylocity every 24 hours by default, on an interval you can set from 30 minutes to 30 days, with on-demand syncs when you need them during close. - Pay statement item mapping
Earnings, taxes, deductions and contributions each map to debit accounts, and each sync refreshes that metadata alongside the payroll data. - One entry per employee pay statement
Unlike consolidated connectors, Paylocity posts a separate journal entry for each employee pay statement — a 40-person pay run produces 40 entries, so ledger volume scales with headcount. - Optional department mapping
Paylocity departments can be mapped to classification lines. Employee work locations are not available from the integration.
FAQ
No items found.