Connect UKG Ready to DualEntry so each payroll run posts to your ledger as consolidated journal entries. The connection runs through DualEntry’s payroll-data provider, which handles authentication with UKG on your behalf. Data flows one way: UKG Ready to DualEntry.
Prerequisites
Confirm the following before connecting UKG Ready:
- Admin access to both your DualEntry and UKG Ready accounts.
- Your chart of accounts includes the GL accounts you intend to use for payroll expense, tax expense, employee and employer benefit accounts, and a payroll clearing or accrued-payroll account.
- A vendor record in DualEntry to use as the payroll vendor, typically named for UKG itself.
- The DualEntry companies that UKG Ready data should post to already exist.
- A debit account decided for every earnings, tax, deduction, and contribution item you expect UKG Ready to send, since a missing debit account blocks the pay statements that reference it. Decide a credit account too where you have one, since UKG Ready’s pay statement items map both sides.
No classification setup is required in advance. DualEntry splits pay statement lines by Department and Location classifications, creating them on first sync if they do not already exist, so you can let the first sync establish them and tidy names afterwards.
How to connect
DualEntry connects through a hosted Connect widget, so you do not generate API keys or paste credentials into DualEntry.
- In DualEntry, navigate to Configuration → Company → Integrations.
- Choose UKG Ready, then choose Connect. DualEntry opens the Connect widget in a new window.
- Sign in with your UKG Ready administrator credentials and approve the data scopes requested on DualEntry’s behalf.
- After approval, the provider redirects back to DualEntry and the integration shows as Connected.
The first sync pulls only metadata (companies, the payroll vendor, pay statement items, and departments), so you can finish mapping before any journal entries are written. Pay statements sync once the required mappings are complete.
That ordering is deliberate and worth not rushing. Mapping before the first pay statement arrives means you never have to unpick an entry that posted to the wrong account.
If the connection later shows a reauth or permissions status, the UKG authorization needs renewing. Reconnect from the same screen rather than creating a second connection.
Map your UKG Ready data
After connecting, DualEntry pulls UKG Ready metadata and shows what needs mapping. Until every required mapping is filled in, pay statements do not post.
There are three pieces of work:
- Companies and the payroll vendor. Map each UKG company to the DualEntry company its payroll should post to, and map the payroll vendor that gets stamped on every payroll journal entry line.
- Pay statement items. Map every earnings, tax, employee deduction, and employer contribution item to a debit account, and to a credit account where one applies. A missing debit account blocks the pay statements that reference it.
- Departments. Optionally map departments to classification lines if you want journal entry lines split by department.
UKG Ready’s pay statement items map to both a debit and a credit account, since the mapping shape is driven by the item’s category rather than the connector. UKG Ready has no integration-level default accounts, so map both sides directly on each item. Only the debit account is required for an item to post — DualEntry balances a missing credit account against your default offset account, so an item mapped on debit alone still posts, just not to the credit account you’d otherwise choose.
Departments match an existing classification line by exact name, so a difference in punctuation or case creates a new line rather than reusing the one you intended.
How payroll runs become journal entries
A payroll run does not post one journal entry per employee. DualEntry consolidates every employee’s pay statement for a payment into a single journal entry per company, with lines for earnings, taxes, employee deductions, and employer contributions. Mapping companies is therefore what determines how a multi-company payroll splits in your ledger.
Lines are grouped by pay statement item and by the classifications resolved for each employee, so an earnings item spread across three departments produces three lines rather than one. That grouping is what keeps a payroll of any size readable in the ledger while still supporting departmental reporting.
A line count that jumps unexpectedly between runs usually means new department values arrived from UKG Ready rather than anything changing on your side.
Per-employee detail stays available on the underlying pay statement records, which sync alongside the payments but are not posted individually. That keeps the ledger readable at any headcount while leaving the detail reachable when someone questions a figure.
Optional: Consolidate payroll tax
Tax items can be consolidated by GL account into a single “Consolidated Payroll Tax” line per account, which keeps the entry compact when several tax types map to the same account. To change the behavior, open the integration’s settings and toggle Consolidate payroll tax.
The setting affects only how tax items are grouped on the journal entry. It does not change which records are pulled from UKG Ready, nor how earnings, deductions, or contributions are grouped.
Leave it on unless someone actually needs tax-type-level analysis in the ledger. Consolidated tax lines carry no classifications, so turning it off produces more lines without adding departmental detail to them, which is rarely the trade you want on a large payroll.
Changing the setting re-renders pay statements on the next sync rather than rewriting entries that have already posted, so decide it before your first payroll rather than partway through a year.
- Paycom - the other UKG-adjacent payroll connector, which maps pay statement items the same debit/credit way
- Managing syncs - retry, resync, and archive behavior shared by every integration
- Journal entries - reviewing what payroll posts to your ledger
Last modified on August 27, 2026
