Connect Paycom payroll and post journal entries

Connect Paycom 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 Paycom on your behalf. Data flows one way: Paycom to DualEntry. Paycom pay statement items carry both a debit and a credit account rather than a single GL account. This mapping shape is driven by the item’s category, not by Paycom specifically, so other connectors sending the same kind of pay statement item data map it the same way. Read Map pay statement items before you start mapping.

​

Prerequisites

Confirm the following before connecting Paycom:

• Admin access to both your DualEntry and Paycom accounts, since the connection is authorized by an administrator on each side.
• 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 Paycom itself.
• The DualEntry companies that Paycom data should post to already exist.
• The two integration-level default accounts described below are decided in advance and set up by DualEntry, since Paycom doesn’t expose a self-service field for them.

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.

1. In DualEntry, navigate to Configuration → Company → Integrations.
2. Choose Paycom, then choose Connect. DualEntry opens the Connect widget in a new window.
3. Sign in with your Paycom administrator credentials and approve the data scopes requested on DualEntry’s behalf.
4. After approval, the provider redirects back to DualEntry and the integration shows as Connected.

If the connection later shows a reauth or permissions status, the Paycom authorization needs renewing. Reconnect from the same screen rather than creating a second connection, which would leave you mapping the same data twice. 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.

​

Map pay statement items

Every pay statement item resolves to a debit account and a credit account, and where each side comes from depends on the item’s category: The two defaults apply once to the integration rather than per item, but neither has a self-service control in DualEntry today — ask DualEntry to set them for you before your first payroll sync:

• Earnings credit account - the offset every earnings line credits, typically your payroll clearing or accrued-payroll account.
• Employee contributions debit account - the offset every employee deduction line debits.

An earnings item with no credit account, on either the item or the integration default, does not block the pay statement from posting. DualEntry balances the entry by sending the difference to your default offset account instead, so get the defaults set first if you want earnings and deductions landing on the accounts you intend rather than the generic offset. Employer contributions and taxes take both sides from your mapping, so those are the categories where you decide the expense account and the corresponding liability account explicitly.

​

Map companies, the vendor, and departments

Beyond pay statement items, three mappings complete the setup:

• Companies. Map each Paycom company to the DualEntry company its payroll should post to. Journal entries are consolidated per company, so this mapping determines how a multi-company payroll splits.
• Payroll vendor. Map the payroll vendor stamped on every payroll journal entry line. This is what makes payroll traceable in vendor-level reporting rather than appearing as unattributed journal activity.
• Departments. Optionally map departments to classification lines if you want journal entry lines split by department.

Departments match an existing classification line by exact name. If the Paycom name and the DualEntry name differ at all, including by punctuation or case, DualEntry creates a new line rather than reusing the one you meant, so check the names before the first sync rather than merging duplicates afterwards. Department mapping is the one piece here you can safely defer. Companies and the vendor block posting; departments only change how finely the lines are split.

​

How payroll runs become journal entries

A payroll run does not post one journal entry per employee. DualEntry consolidates every employee’s pay statement into a single journal entry per payment and company, with lines for earnings, taxes, employee deductions, and employer contributions. Each entry is dated from the payment’s pay date rather than the date the sync ran, so a payroll imported late still lands in the period it belongs to. If a payment arrives from Paycom with no pay date, DualEntry falls back to the sync date instead of blocking the entry. Check that the target period is open before syncing a backdated run, since a locked period rejects the entry. 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. 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 are consolidated by GL account into a single “Consolidated Payroll Tax” line per account by default. This keeps the entry compact when several tax types map to the same account, for example when state income taxes across several states all post to one expense account. If you would rather see one line per tax item, open the integration’s settings and toggle Consolidate payroll tax off. The next sync re-renders pay statements with one line per tax item and account pair. The setting affects only how tax items are grouped. It does not change which records are pulled from Paycom, 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.

​

Related reading

• UKG Ready - the sibling 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