Payroll & 1099
Payroll Tax Payable: Definition and Reconciliation
Payroll tax payable is the balance-sheet liability for employee taxes withheld and employer payroll taxes incurred but not yet deposited or paid to the agency.
Each payroll creates both compensation expense and liabilities. The business withholds federal income tax, employee Social Security and Medicare taxes, and applicable state or local taxes from gross wages. It also incurs employer Social Security, Medicare, FUTA, state unemployment, and other payroll taxes. Until those amounts are deposited, they remain payroll tax payable. A clean balance reconciles from payroll registers to tax returns, electronic deposits, bank activity, and agency accounts by tax type and period. The account should not be forced to zero merely because a payroll company withdrew cash.
This guide is part of Steady’s Payroll, W-2 & 1099 library. It explains the federal workflow in practical terms, but the correct result still depends on the payment year, entity, worker relationship, filing method, and state rules.
The answer in context
Withheld taxes are not employer revenue
Amounts withheld from employees are trust-fund liabilities held for deposit and reporting.
Employer taxes are separate costs
The employer share of Social Security and Medicare and unemployment taxes increase payroll expense and create their own liabilities.
One control account can hide errors
Separate federal withholding, FICA, FUTA, state withholding, unemployment, and local taxes by jurisdiction or use a detailed subledger.
Liability dates follow payroll
Tax liability generally arises when wages are paid, even when the bank debit or agency deposit occurs later.
Deposit schedules differ from return frequency
Monthly and semiweekly deposit rules do not mean Form 941 is filed monthly. The $100,000 next-day rule can accelerate a federal deposit.
Provider withdrawals need allocation
A combined debit can contain net pay, taxes, benefits, garnishments, and service fees. Reconcile each component instead of clearing the liability to one total.
Step-by-step workflow
- Map payroll codes. Assign every tax and deduction to an expense, liability, cash, or clearing account with a documented jurisdiction and form.
- Record the payroll. Post gross wages and employer taxes to expense, employee and employer taxes to payables, deductions to their liabilities, and net pay to cash or clearing.
- Tie the register. Compare employee totals, taxable wages, current tax, year-to-date amounts, and employer taxes with the approved payroll register.
- Match deposits. Record each payment by agency, tax type, period, amount, settlement date, and trace number.
- Reconcile returns. Tie Forms 941, 940, W-2 and W-3, and state returns to payroll and the liability subledger.
- Investigate the ending balance. Separate deposits in transit, future-due liabilities, rejected payments, notices, prior-period adjustments, and posting errors.
- Close only supported items. Clear a payable when the payment and reporting are matched to the correct period, not when cash merely leaves the bank.
Worked example
A company records a biweekly payroll with $42,000 of gross wages, $9,800 of employee taxes, $3,400 of benefit deductions, $3,200 of employer payroll taxes, and $28,800 of net pay. The entry creates separate employee-tax, employer-tax, and benefit liabilities. Later bank debits are matched to the net-pay file, federal deposit, state deposit, and benefit vendors. A $650 remaining federal balance is traced to a deposit scheduled after month-end rather than written off.
The example is intentionally a workflow illustration, not a conclusion for every taxpayer. A strong file connects each number on the return to a source report and records why an exception, exclusion, or classification was applied.
Records to keep
Keep the source form or worksheet, contracts or engagement records, payer and recipient identity support, the detailed payment or payroll ledger, bank and processor reconciliation, calculations, correspondence about corrections, filed copies, recipient-delivery evidence, and federal and state acceptance confirmations. Store the records by tax year and keep superseded versions when they explain a correction.
A reviewer should be able to begin with the final reported amount and trace it back to transactions without rebuilding the year. Add a short review memo for judgments such as worker status, corporate exemption, payment-method exclusion, state filing, or unusual timing. That memo is often more useful than another unlabeled spreadsheet.
Common mistakes
- Posting only net pay. Gross wages, taxes, deductions, employer costs, and liabilities disappear from the books.
- Combining every liability. Separate agencies and tax types so missed deposits can be found.
- Clearing from the bank total. Allocate provider debits to the payroll detail and actual agency payments.
- Ignoring rejected deposits. A debit reversal or agency reject leaves the liability unpaid.
- Using Form 941 as the only support. Reconcile the return to every payroll run and deposit.
- Leaving old balances unexplained. Age liabilities by period and resolve notices, duplicates, and corrections.
Final review before filing
Confirm the form and revision year, taxpayer identities, dollar fields, payment categories, withholding, filing channel, recipient statement, state obligations, due dates, and approval. Compare the final output with the source reconciliation rather than reviewing the form in isolation. If software recalculates an amount after an edit, rerun the tie-out.
Keep preparation, filing, and acceptance as three separate statuses. A draft can be complete but unfiled; a transmission can be sent but rejected; a federal return can be accepted while a state return is still missing. This status discipline prevents a polished PDF from being mistaken for finished compliance work.
How to handle a discrepancy
When a source form, ledger, payroll report, or software preview disagrees with another record, stop before filing and identify which amount represents the underlying transactions. Trace the difference by vendor or employee, date, invoice or payroll run, payment channel, and account. Common causes include a payment posted to the wrong year, a void recorded after a report was generated, a card payment included with checks, a duplicate import, an incorrect taxpayer name, or a late adjustment. Record the explanation and the correcting entry or form request.
Do not erase the trail by overwriting the original report. Save the first version, the reconciliation, the corrected version, and the approval. If a third party supplied an incorrect information return, request a formal correction and retain the correspondence. If a return was already transmitted, use the current correction procedure for that form and channel. A corrected recipient copy without a corresponding agency correction can leave the records inconsistent.
Federal filing is only one layer
Federal acceptance does not settle state or local obligations. A state may use a different threshold, worker test, filing portal, account number, transmittal, or due date. Some states receive eligible information through a combined program, while others require a direct submission. Verify the jurisdictions connected with the payer, recipient, employee, work location, withholding, and business activity. Save state confirmations separately so they are not hidden behind the federal acceptance.
Make next year easier
Turn the year-end work into a monthly control. Collect identity forms during onboarding, code payment methods consistently, reconcile payroll and vendor activity each month, and flag vendors or income streams that need special treatment. Schedule a fall review of missing forms, classification questions, state registrations, and electronic-filing access. By year-end, the team should be validating a maintained file instead of reconstructing twelve months of transactions under a deadline.
Practical implementation notes
Liability rollforward
Beginning balance plus current payroll liabilities minus deposits and adjustments should equal the ending balance by agency and period.
Aging report
Label every open amount as not yet due, in transit, rejected, disputed, corrected, overpaid, or unexplained.
Approval control
Separate payroll preparation, final approval, bank release, journal posting, and reconciliation where staffing allows.
For the next layer of context, see this related guide, the companion reporting article, and the connected workflow.
If the form, books, and filing status do not agree, Steady can help reconcile the source data and prepare a clean filing package through its specialist service.
Frequently asked questions
Is payroll tax payable an expense?
The payable is a liability. Employer payroll taxes are expenses, while employee withholdings reduce net pay and create liabilities.
Why does the account have a credit balance?
A normal credit balance generally represents taxes incurred or withheld that have not yet been deposited.
Can payroll tax payable be negative?
A debit balance can signal an overpayment, duplicate posting, refund, timing issue, or an incorrectly cleared liability and should be investigated.
When is the liability cleared?
Clear it when a supported payment is applied to the correct agency, tax type, and liability period.
Does a payroll service own the liability?
No. A provider may submit deposits and returns, but the employer remains responsible for oversight and accurate records.
What should it reconcile to?
Tie the account to payroll registers, tax returns, agency payment histories, bank activity, notices, and year-end wage statements.
Turn this guide into action