Why Payroll and Accounting Records Don't Match

When payroll and accounting records do not match, a small employer is left staring at two sets of numbers that should agree and do not. One journal entry posted to the wrong account, a payroll liability left unreconciled, or a net pay total that never reached the books can turn a clean month end into hours of hunting. The good news is that most mismatches follow the same small set of causes, which means a few steady habits catch them before the close.

This guide walks through why payroll and accounting records do not match, from the way payroll entries land in the books to the reconciliation that ties the two together. If you are newer to the records side of payroll, it helps to start with our guide on payroll records employers should keep before you dig into the reconciliation habits. For a fuller look at the errors that show up alongside a mismatch, see our guide on what to do when payroll is processed incorrectly.

What It Means When the Records Do Not Match

Payroll and accounting records are two views of the same activity. The payroll register shows the wages, the taxes, and the net pay for the run. The books show the journal entries that record those same wages, taxes, and net pay in the right accounts. When the two agree, the records are reconciled. When they do not, a payroll entry landed wrong, a liability was left unreconciled, or a total never reached the books.

The mismatch can run in either direction. The books can show more wages than the payroll register, which usually means an entry was posted twice. The books can show less than the register, which usually means an entry was missed or posted to the wrong account. Either way, the fix is the same, which is finding the gap, correcting the entry, and reconciling the two so the records agree and stay easy to trace.

Common Causes of a Payroll and Accounting Mismatch

Most mismatches come from a small set of causes. Knowing them helps you find the gap fast and fix the right thing instead of the symptom.

• Payroll posted to the wrong account. A wage total lands in a generic expense account instead of the wages account, or a tax liability lands in the wrong liability account, so the books and the register disagree even when the totals are right.
• A payroll liability left unreconciled. A payroll tax liability is recorded in the books but never tied to the payment that cleared the bank, so the liability balance drifts and the books stop matching the register.
• Net pay never reached the books. The net pay total is recorded in the payroll register but the bank withdrawal is not entered in the books, so the cash account and the payroll total disagree.
• A manual check cut outside the run. A bonus or a correction check is cut outside the payroll run and never journaled, so the books miss the entry and the register does not reflect it.
• Payroll posted in a batch at month end. Several runs are posted together at month end instead of every run, so an entry from one run is missed or doubled and the two sets drift apart before the close.

Each of these causes shares one root, which is a gap between the payroll register and the books. For a closer look at how the entries themselves can go wrong, see our guide on how to prevent payroll data entry errors.

How Payroll Lands in the Books

Every payroll run creates a set of journal entries. Gross wages hit the wages expense account. Employer taxes hit the payroll tax expense account. Employee taxes and other withholdings hit liability accounts. Net pay hits the cash account when the withdrawal clears the bank. When each entry lands in the right account and the right amount, the books and the register agree.

The trouble starts when an entry lands wrong. A wage total posted to a generic expense account instead of wages makes the books read high in one account and low in another. A liability posted but never reconciled to the payment leaves the balance growing instead of clearing. When you post payroll every run and confirm each entry against the register, a wrong account or a missed entry shows up before the close instead of after.

How to Find the Mismatch

Even with clean posting, a mismatch can still slip through, which is why the reconciliation matters. Pull the payroll register for the period and the payroll entries in the books side by side. Confirm the gross wages, the tax liabilities, and the net pay match between the two. Reconcile each payroll tax liability to the payment that cleared the bank, and tie the net pay total to the payroll withdrawal.

Watch the entries that go wrong most often. A liability balance that grows instead of clearing, a cash withdrawal that does not tie to the net pay, or a wage total that does not match the register are all signs the two sets have drifted apart. A mismatch caught before the close is fixed by correcting the entry and rerunning the reconciliation, which keeps the records clean from the start.

Example: A Cafe Catches a Wrong Account Mapping

Consider a small cafe with hourly employees paid biweekly. During the month end reconciliation, the owner notices the wages expense account is lower than the payroll register total for the period. The owner checks the books and finds one payroll run was posted to a generic expense account instead of the wages account, so the wage total landed in the wrong place.

The owner pulls the payroll register, confirms the right wage total, and reclasses the entry from the generic account to the wages account. Because the close has not finished, the owner fixes the entry before the books are locked, keeps the register and a short note about the wrong mapping with the payroll records, and reruns the reconciliation. The example shows how a wrong account mapping turns into a clean correction when you post every run and reconcile before the close.

Example: A Shop Catches an Unreconciled Liability

Take a small retail shop with a mix of hourly and salaried staff paid semimonthly. During the month end reconciliation, the owner notices a payroll tax liability balance is still sitting in the books even though the payment cleared the bank the prior week. The owner checks the books and finds the payment was recorded in the cash account but never tied to the liability, so the balance never cleared.

The owner ties the payment to the liability, clears the balance, and reruns the reconciliation. Because the close has not finished, the owner fixes the entry before the books are locked, keeps the bank record and a short note about the missed tie with the payroll records, and confirms the liability balance is now zero. The example shows how an unreconciled liability is caught by the month end reconciliation and corrected before the close.

How to Prevent the Next Mismatch

A correction is cleaner when the next close does not repeat the same mismatch. The habits below keep the payroll register and the books from drifting apart.

• Post payroll to the books every run, not in a batch at month end, so no entry is missed or doubled.
• Confirm each journal entry against the payroll register before the close, including gross wages, tax liabilities, and net pay.
• Reconcile each payroll tax liability to the payment that cleared the bank every period.
• Tie the net pay total to the payroll withdrawal in the cash account every run.
• Watch for manual checks cut outside the run, and journal them the same day so the books reflect them.

Payroll and Accounting Reconciliation Checklist

Use this checklist before each month end close so the payroll register and the books start from the same numbers and the reconciliation catches the gaps that slip through. Work through it in order so the two sets agree and the records stay easy to trace.

Getting Started

A payroll and accounting mismatch is preventable, and the prevention is cleaner when you post payroll every run, reconcile each liability, and tie the net pay to the bank before the close. Work through the steps above, and your next close starts from numbers that agree instead of two sets that do not.