Recording historical payroll tax payments during a payroll setup

Setting up payroll partway through a year means the payroll module starts with history it did not create. One of the setup screens asks you to enter tax payments already made this year. What you put there determines whether year-to-date wages, liabilities and payments tie together, so it deserves care rather than a quick guess.

What belongs in the tax payments entry?

Enter every payroll tax payment the business has already sent to a tax agency this calendar year. That covers federal deposits and payments, such as federal income tax withheld, Social Security and Medicare, and federal unemployment. It also covers state and local items: state withholding, state unemployment insurance, disability insurance, and any local payroll tax where applicable.

The key test is simple. If money left the bank and landed at a tax agency in settlement of payroll liabilities, it belongs here. Do not enter payments for taxes the business owes on its own income, and do not enter payments from a prior calendar year.

Where does the detail come from?

The bank is the authority on what was paid and when. Work from the check register or the bank statement and list each payment's date and amount. Then match each payment to the liability detail behind it, which comes from payroll registers, prior payroll service reports, or the payment confirmation notices agencies send.

Suppose a $1,000 payment went to the state unemployment agency on 1 February. The register tells you the amount and date, but the agency notice shows it split $800 to state unemployment insurance and $200 to disability insurance. Enter the split, not just the lump. Combined payments are common, and the breakdown is what makes the liability accounts clear at year end.

Why the split matters to the ledger

Each payroll tax is tracked as its own liability. If you record a combined payment as a single amount against one tax, the other tax's liability balance stays open. At the close, that stale balance looks like an unpaid tax. Someone then wastes time chasing a payment that was made months ago.

Getting the split right at setup also keeps the quarterly filings reconcilable. The agency's own totals for each tax should agree with the liability cleared in the books, payment by payment.

What if payroll ran on another service?

When converting from another payroll service mid-year, pull the year-to-date payment reports from the old service before access ends. Those reports usually give the per-tax breakdown you need. Cross-check their totals against the bank, since the bank is the evidence that survives the conversion.

What if the numbers will not tie?

If the payments you enter do not reconcile against year-to-date liabilities, stop and resolve it before running the first new payroll. A gap usually means a missed payment, a misdated one, or a liability recorded but never paid. That is a bookkeeping question, and the working papers you build here are what let you answer it cleanly.