Payroll Liabilities Keep Growing: Reconcile the Balance Before Year-End

A growing liability is a question that needs evidence

A payroll liability account may increase because amounts are not yet due, deposits are missing, entries are duplicated, or the ledger mapping is wrong. Start by obtaining payroll registers, provider cash-requirement reports, bank records, and relevant payment confirmations. Do not clear the balance to expense merely because it has remained on the balance sheet for several months. The balance represents a reconciliation problem until the underlying movements are explained.

Separate federal taxes, state and local obligations, benefits, retirement amounts, garnishments, and other payroll-related items. A combined account can conceal an overdue obligation behind an unrelated credit. Identify the responsible provider for each category. Publication 15 provides federal employer-tax guidance, while other obligations need their own current review. The owner should know which part of the balance belongs to which system and payment process.

Build a rollforward for each material liability

Show beginning balance, payroll-generated amounts, cash deposits or remittances, corrections, and ending balance. Match dates carefully because payroll, bank withdrawals, and authority posting may occur on different days. Explain timing differences with evidence and a resolution date. A permanent item labeled timing is not a completed reconciliation if it never clears in the following period.

Compare the provider's reports with the ledger mapping. A payroll journal may record gross wages, employer costs, and liabilities while a separate bank-feed rule also expenses the withdrawal. That can distort both profit and the liability. Ask the accountant to trace a single payroll end to end, then apply the findings to the remaining periods. A sample trace often reveals the repeated configuration error more clearly than a year-end balancing entry.

An example of a duplicate posting

Suppose payroll creates $15,000 of tax liabilities during a month, and bank withdrawals for those taxes total $15,000. The ledger nevertheless shows an additional $15,000 liability because the payment import was posted to payroll tax expense instead of the liability account. The company may have paid correctly while reporting an incorrect balance and expense. This arithmetic example illustrates mapping; it does not establish that every unexplained liability is harmless.

Now consider a different month where a bank withdrawal failed. The ledger may show the same apparent balance, but the operational response is different. Verify actual acceptance and settlement rather than assuming the prior mapping explanation applies again. The owner needs to distinguish a bookkeeping correction from an unpaid obligation, because correcting the ledger does not send money to the recipient.

Resolve discrepancies with the right provider

Give payroll support a concise issue file: pay period, report, expected amount, actual withdrawal, confirmation, and ledger entry. Ask for an explanation and any required correction steps. Preserve case references and written responses. If a payment or filing issue requires an advisor's review, escalate it instead of allowing the bookkeeper to improvise a classification that makes the balance disappear.

Check whether ownership changes, payroll-provider transitions, or multiple employer accounts created duplicate or missing records. Confirm the taxpayer and period associated with each payment. A related company's deposit cannot simply be assumed to satisfy another company's obligation. If accounts were combined in internal reporting, maintain enough detail to reconcile each actual employer separately.

Use the corrected balance in the cash and tax forecasts

Once reconciled, update the operating cash plan for any amounts still payable and ask the advisor how corrections affect the tax projection. Do not distribute cash that is needed for an unresolved payroll obligation merely because management believes the issue is probably accounting. Conversely, remove duplicated expense from the forecast when the accountant confirms the error, so the owner does not make decisions using understated profit.

Add the rollforward to monthly close and require evidence for old items. Name a reviewer and a deadline for resolving exceptions. This workflow does not determine penalties, filing corrections, or payment schedules for a particular employer. It gives the owner a reliable explanation of the balance and separates actual funding needs from posting errors. That clarity makes year-end planning safer and keeps the company from carrying an unexplained payroll account indefinitely.

Review access and authorization when the provider changes a payment setting. A correct reconciliation this month does not prevent a later configuration change from recreating the problem. Keep a short log of material mapping changes and have the controller review the first affected payroll.