How to Record Payroll From Bank Statements

To record payroll from bank statements, start from the payroll register, not the bank lines. Post gross wages and employer taxes as expenses, withholdings as liabilities, and net pay as the cash that left. Then match each bank debit (net pay, tax deposits, provider fees) to that entry so the liability accounts clear to zero.

Which payroll lines show up on a client's bank statement?

One pay run usually creates several bank lines, and none of them is the gross payroll figure. A typical run shows a net pay debit, one or more tax debits and a provider fee. How they are grouped depends on the payroll provider and on whether the client pays taxes through the provider or directly.

The common patterns are:

• Separate debits. One debit for total net pay, one for federal taxes, one for state taxes and one for the provider's fee. This is the easiest layout to record.
• One combined debit. The provider pulls net pay plus all taxes in a single amount and pays everyone from its own account. The bank line then has to be split against the register.
• Per-employee lines. Direct deposits listed one by one, or paper checks clearing on different days. A small client with three paper checks may show three check numbers clearing over two weeks.
• Tax debits on a schedule. If the client deposits federal tax itself, the debit follows the deposit schedule, not the pay date. The IRS page on depositing and reporting employment taxes explains that employers deposit on either a monthly or a semiweekly schedule, electronically, for example through EFTPS.

None of these lines tells you gross wages, which taxes were withheld from employees or what the employer owes on top. That is why payroll cannot be coded from the bank statement alone.

The payroll register behind every payroll bank line

The payroll register is the report the payroll system produces for each pay run. It lists, per employee and in total, gross pay, each withholding, net pay and the employer's tax amounts. It is the source document for the payroll entry. The bank statement is only the proof that the cash moved.

Ask the client for read access to the payroll system, or for the register and the tax liability report each period. A summary for the whole run is enough for the books. Keep the per-employee detail in the payroll system, where it belongs, rather than in the general ledger.

Check three totals on every register before posting:

1. Gross pay minus total employee withholdings equals net pay.
2. Net pay equals the net pay debit, or the sum of direct deposits and checks, on the bank statement.
3. The employee and employer taxes the provider says it will collect equal the tax debits on the statement for that run or deposit period.

If any of the three fails, stop and find out why before posting. A failed match usually means a manual check, a voided payment or a correction run that the register does not show.

A worked pay run entry from gross wages to net pay

A pay run entry records the full cost of payroll, not just the cash. The example below uses made-up figures for a fictional client's semi-monthly run of $10,000 gross wages. The Social Security and Medicare amounts use the familiar 6.2% and 1.45% employee and employer shares; the income tax, state and unemployment figures are illustrative only.

The entry for the pay date:

• Debit wages expense 10,000.00.
• Debit payroll tax expense 1,095.00 (the employer column).
• Credit federal withholding payable 1,100.00.
• Credit Social Security and Medicare payable 1,530.00 (both shares).
• Credit state withholding payable 400.00.
• Credit federal unemployment payable 60.00.
• Credit state unemployment payable 270.00.
• Credit checking 7,735.00 (the net pay debit).

The entry balances: 11,095.00 of debits against 11,095.00 of credits. The checking credit is the only part that matches a bank line on the pay date. Everything else sits in liability accounts until the tax debits arrive.

When the provider takes one combined debit

If the provider pulls 10,765.00 in one line (net pay of 7,735.00, the federal deposit of 2,630.00 and state withholding of 400.00), code that line to a payroll clearing account instead of checking. Post the register entry with net pay credited to clearing, and record the taxes the provider remits as debits to their liability accounts and credits to clearing. Clearing then returns to zero, and any leftover balance in clearing points to a run you have not posted or a debit you have not matched.

Payroll tax deposits and the liabilities they clear

A payroll tax deposit is a payment of money already owed, so it reduces liability accounts and never touches an expense. The expense was recorded on the pay date. Coding the deposit to payroll tax expense counts those taxes twice.

For the example run, a federal deposit of 2,630.00 clears federal withholding payable (1,100.00) and Social Security and Medicare payable (1,530.00). A later state debit of 400.00 clears state withholding payable, and the unemployment amounts clear when the quarterly or annual payments go out.

Withheld taxes behave much like sales tax: the client collects the money on someone else's behalf and passes it on. The guide to recording sales tax payments uses the same liability-then-payment pattern, and the two are easy to confuse when a state agency handles both. Check the payee description and the agency account number on the bank line before applying a rule.

Federal unemployment is handled on its own timing. The same IRS page notes that FUTA deposits are required for a quarter once the tax due exceeds $500, so small employers can carry the liability across quarters before a debit appears.

Payroll provider fees, refunds and other stray lines

Payroll provider fees are a service cost, not wages or taxes. Code them to a payroll processing fees or professional services account. They often arrive as a separate small debit on the pay date or once a month, with the provider's name and words like "FEE" or "INVOICE."

Other lines turn up less often and need their own treatment:

• Garnishments and benefit deductions. Withheld from employees and paid to a court, an insurer or a retirement plan. Post them to their own liability accounts from the register, then clear them with the payment.
• Employer benefit contributions. The employer's share of health premiums or retirement matches is an expense, separate from wages.
• Reimbursements paid through payroll. Expense reimbursements added to a paycheck are not wages if the register shows them as non-taxable. Code them to the underlying expense accounts.
• Tax agency refunds. When a deposit was overpaid, the agency may send money back. The refund reduces payroll tax expense or the liability it overpaid. If the refund includes interest, that part is income; see recording interest income for how to separate it.
• Voided payroll checks. A check that never clears needs a reversal in the books, or it sits outstanding in the bank reconciliation forever.

Once the provider's lines follow the same descriptions each run, client rules take over most of this work. In AutoBankConvert, rules written for a client's net pay, tax and fee debits code those lines each month, and approving a new debit once teaches the rule for the next run.

Why do payroll liability accounts stop balancing?

Payroll liability accounts stop balancing when an entry on one side is missing or posted twice. In clean books, each liability returns to zero once that period's taxes are paid. A balance that grows month after month is almost always a bookkeeping error, not real unpaid tax, though it is worth confirming with the provider's tax report.

The usual causes:

• The deposit coded to expense. The liability was created but never cleared, so it grows by every deposit amount.
• Net pay coded as wages from the bank line, plus the register posted. Wages are counted twice, and the net pay credit shows up as an unmatched item.
• A missed pay run. An off-cycle bonus or correction run had no register entry, so its tax debit has no liability to clear.
• Quarterly timing confused with an error. Unemployment taxes paid quarterly will show a legitimate balance between payments.
• Provider and books using different periods. A run paid on the 1st for work in the prior month can land in either month. Pick one rule, usually the pay date, and keep to it.

Run a payroll liability report at each month end. Any account with a balance that does not match the provider's open tax report gets traced back to the run that caused it.

When payroll cleanup is outside the bookkeeping engagement

Payroll cleanup moves outside a normal bookkeeping engagement when the problem is in the payroll system itself rather than in the books. Filing amended payroll returns, correcting W-2s, setting up a new state account or reworking a year of mis-coded runs are separate pieces of work.

Recording pay runs from the register and matching bank debits each month is routine bookkeeping. Rebuilding twelve months of payroll entries for a client who never sent a register is not. Agree with the client in writing what is covered, and quote the cleanup separately. The post on billing for out-of-scope bookkeeping work suggests how to raise the conversation before the hours pile up.

Where payroll tax filings are wrong, bring in whoever runs the client's payroll or the CPA. The books can show that a liability is off; fixing what was filed with a tax agency is a different responsibility.