Every payroll, the same chore. The run finishes, and then someone opens a spreadsheet and starts typing numbers into the accounting system by hand. Gross wages here, taxes there, and the employer's share of benefits somewhere else, all split across departments. It takes hours, it is easy to fat-finger, and by month-end the payroll total in your books never quite matches what actually went out the door. So you spend another afternoon hunting for the difference.
There is a better way, and you may already own it. ADP Workforce Now can post payroll to your general ledger with a mapping that runs the same way every time. Built well, it turns that manual chore into a file you review and import, with the debits and credits already sorted by department and by pay component. Built poorly, it posts garbage faster, so the setup is what matters.
This guide walks through how general ledger mapping works, how to handle cost centers and departments, how the debits and credits line up by pay component, how to treat accruals, how to reconcile payroll to the ledger, and the mapping mistakes that cause most of the mess. The goal is payroll that lands in your books clean, every period, with no retyping.
A payroll general ledger posting is just a translation. Payroll speaks in earnings, taxes, and deductions. Your accounting system speaks in accounts, debits, and credits. The GL integration is the dictionary between them. It takes each piece of a payroll run and says which account it belongs to and whether it increases or decreases that account.
The whole thing rests on one rule from accounting: every entry has to balance. Total debits equal total credits. In payroll terms, the cost of employing people, wages plus the employer's share of taxes and benefits, gets recorded as expense, while the cash you paid out and the amounts you still owe to tax agencies and vendors get recorded as reductions in cash and as liabilities. If your mapping is right, the file ADP Workforce Now produces already balances, and it drops into your ledger without a fight.
The mapping is the heart of the integration, and it deserves real thought before you turn it on. For each pay component in ADP Workforce Now, you decide which general ledger account it posts to. Regular wages might map to a wages expense account. The employer share of payroll taxes maps to a payroll tax expense account. Employer-paid benefits map to a benefits expense account. Employee deductions and the taxes you withhold map to liability accounts, because that money is owed to someone else until you remit it. Net pay maps to cash, because that is what left the bank
The single most important habit here is to match your mapping to your actual chart of accounts. Pull the current account list from your accounting system and map to those exact account numbers. A mapping built against a guessed or outdated chart is the number one reason postings land in the wrong place. Write the mapping down as a reference so anyone can see which pay component feeds which account, and so the logic survives a staff change.
Most organizations do not want payroll as one lump. They want to know what each department, location, or project cost. That is where cost centers come in. ADP Workforce Now can tag each employee's pay to a department or cost center and split the general ledger posting accordingly, so finance sees wages for sales separate from wages for operations without any manual sorting.
For this to work, the department structure in payroll has to line up with the cost center structure in your accounting system. If payroll calls it "Field Ops" and the ledger calls it "Operations 200," someone has to reconcile that by hand every period, which defeats the purpose. Decide once how departments map to cost centers, keep the two systems in step, and update the mapping whenever you add a department. When an employee splits time across departments, make sure the setup allocates their pay the way finance expects, rather than dumping the whole cost in one place.
It helps to picture the standard entry, because once you see the shape, mapping mistakes become obvious. A normal payroll posts something like this.
Wages expense is debited for gross pay, because employing people is a cost. Employer payroll tax expense is debited for the company's share of taxes. Employer benefit expense is debited for the company's share of benefits. On the other side, cash is credited for net pay, because that money left your bank. Tax withholdings, both the employee and employer portions you owe to agencies, are credited to liability accounts, because you are holding that money until you remit it. Employee deductions like their share of benefits or a retirement contribution are credited to the matching liability accounts for the same reason.
When it all posts, the debits, your total employment cost, equal the credits, the cash out plus everything you still owe. If your mapping ever produces an entry that does not balance, that is your signal that a component is mapped to the wrong side or missing entirely.
Payroll and pay periods rarely line up neatly with month-end. If a pay period straddles two months, or if employees earn wages in one month that are paid in the next, the expense belongs to the month the work happened, not the month the cash moved. That is what a payroll accrual does. It records the earned-but-unpaid wages as an expense and a liability at month-end, then reverses in the next period when the actual pay posts.
The same thinking applies to earned paid time off. When employees earn vacation they have not yet used, that future obligation can be accrued as a liability so your books reflect what you owe. ADP Workforce Now can supply the data behind these accruals, and your finance team decides the accounting treatment. The payoff is a P&L where labor cost sits in the period the work was done, which makes every month comparable and keeps your margins honest. Because accrual treatment depends on your accounting policy, confirm the approach with your licensed advisor.
Even with a clean integration, reconcile. Reconciling means proving that what posted to the ledger matches what actually happened in payroll. The quickest check is to tie the total payroll expense in your books for the period to the payroll register total from ADP Workforce Now. Then confirm that the liability accounts, taxes withheld, benefit deductions, retirement contributions, clear as you remit them, rather than growing month after month because something is mapped but never paid down.
A liability account that only climbs is a classic warning sign that a deduction is being recorded but not remitted, or that a remittance is not being coded back against the liability. Catch that early and it is a quick fix. Let it run and it becomes a painful year-end cleanup. Reconcile every period, keep the proof, and month-end stops being a mystery.
A client came to us doing payroll GL entry entirely by hand, retyping numbers into their accounting system twice a month and losing most of a day to it, plus more time chasing a total that never quite matched.
We built the mapping in ADP Workforce Now against their real chart of accounts and split it across their four departments. Using rounded, illustrative numbers for a single run, gross wages of about $200,000 posted as a debit to wages expense, split roughly $80,000 to sales, $70,000 to operations, $30,000 to admin, and $20,000 to warehouse. Employer taxes of about $15,000 posted to payroll tax expense. On the other side, net pay of about $150,000 credited cash, and the balance, roughly $65,000 of withheld taxes and deductions, credited the matching liability accounts. Debits equaled credits, and the file imported in minutes. We also set up a simple period reconciliation tying the ledger back to the payroll register. The manual entry disappeared, and month-end got shorter. The numbers are illustrative, but the outcome is the point: the same clean entry, every period, without retyping.
"Why does my payroll total in the books never match the payroll register?" Usually one of two reasons. Either a pay component is mapped to the wrong account or left out of the mapping, or a timing difference such as an accrual or a mid-period adjustment has not been accounted for. Tie the register total to the ledger for a single run and the gap almost always points straight at the cause.
"Can the integration split payroll across departments automatically?" Yes. When employees are tagged to departments or cost centers and those line up with your chart of accounts, ADP Workforce Now can split the posting so each department carries its own cost. The work is in keeping the payroll department structure and the accounting cost centers in step with each other.
"How often should we reconcile payroll to the GL?" Every pay period, or at least every month at close. Reconciling each period keeps errors small and easy to trace. Waiting until year-end turns a five-minute check into a multi-day investigation, usually right when everyone is busiest.
A healthy setup is quiet. Every pay component maps to a real account from your current chart. Departments in payroll match cost centers in the ledger, so the split happens on its own. The posting balances every time, debits equal credits, without anyone forcing it. Accruals put labor cost in the right month so your P&L is comparable period to period. Liability accounts rise when you withhold and fall when you remit, never just climbing. And a short reconciliation runs each period, proving the numbers tie and catching any drift while it is still small.
Get there and the manual entry goes away for good. Payroll posts itself, finance trusts the labor numbers, and month-end is a review instead of a rescue. The setup takes some care up front, and then it pays you back every single run.
We are former ADP service professionals, and we work with ADP exclusively. We have built these GL mappings from the inside, matched them to real charts of accounts, and untangled the postings that never balanced, so we know exactly where integrations go sideways. When your books and your payroll refuse to agree, you do not open a ticket and wait on hold. You get a dedicated consultant who knows ADP Workforce Now and your accounting logic, and who will get payroll posting cleanly the first time. No tickets, no hold queues. We've got you.
Tired of retyping payroll into your books every run? REQUEST A CONSULTATION (ignitehcm.com/solutions/optimization).
ADP and the ADP logo are registered trademarks of ADP, Inc. This article is general guidance only and is not accounting, tax, or legal advice. Accrual treatment and account structure depend on your accounting policy and applicable standards; confirm your approach with your licensed advisor or ADP representative.
