payroll clearing account does not zero out after the pay run: one tax liability line remains each cycle

TL;DR

A payroll clearing account should end every cycle at zero: wages, deductions and employer taxes flow in from the payroll journal and out to bank payments and tax remittances. One tax liability line surviving every cycle means that tax's outflow is coded somewhere else - the tax payment posts to a different liability account than the payroll journal credits, or the payroll system's GL mapping for that tax type points at the clearing account while the payment template points at the tax authority account. Trace the residual amount to its tax type in the payroll register, follow that tax through the mapping table to the payment, and align the two sides on one account. Clear the accumulated residue with a reclassifying journal once the mapping is fixed, or it will keep masquerading as a live liability.

payroll clearing account does not zero out after the pay run: one tax liability line remains each cycle

Use this when

• The payroll clearing or payroll tax liability account retains one line's balance after every pay run.
• All other payroll elements clear fully through bank and tax payments.
• A new tax type, jurisdiction or payroll system mapping change appeared around when the residue started.

Not for this skill when

• The whole payroll journal fails to clear because the bank payment has not been recorded. Record the payment first.
• The residual is an employee deduction in dispute or garnishments awaiting remittance by court schedule. Those clear on their own calendar.

Steps

1. Identify the residual: list the clearing account's open lines after the latest run and match the survivor to a tax type and amount in the payroll register. Verify: the leftover is named as a specific tax and pay period
2. Open the payroll GL mapping for that tax type and note the account the payroll journal credits. Verify: the inbound mapping for the tax is confirmed from configuration
3. Find the tax payment or remittance posting for the same tax and period and note the account it debits. Verify: the outbound coding is confirmed and the account mismatch, if any, is visible
4. Align the mapping or the payment template so both sides use the same liability account, prospectively from the next run. Verify: the configuration change is saved and scheduled for the next cycle
5. Reclassify the accumulated residual to the correct liability account with a documented journal, then run the next payroll and confirm the account zeroes. Verify: the clearing account ends the next cycle at zero with no survivor line

Variant phrasings

payroll clearing account does not zero out tax liability line remains

The per-cycle residue symptom.

payroll tax mapping GL account payment coded different liability

The mapping mismatch phrasing.

payroll clearing reconciliation residual tax type trace fix

The trace procedure search.

Compatibility: Payroll integrations from ADP, Workday, Paychex, Gusto and in-house payroll into SAP, NetSuite, QuickBooks and Dynamics general ledgers.

Why it happens

Payroll is a mapping exercise: dozens of register elements are translated into GL accounts by a mapping table maintained separately from both the payroll system and the payment process. When a tax is added or a chart changes, the inbound mapping and the outbound payment coding are updated by different people at different times, and any element whose two sides land in different accounts leaves a permanent residue that grows by one line every cycle while looking, at a glance, like money still owed.

Edge cases / pitfalls

• Employer versus employee portions of the same tax often map differently; check both portions before concluding.
• A residue equal to one jurisdiction's tax after a site closure means the payment stopped, not the mapping; confirm the liability is genuinely still payable.
• Reconcile the clearing account every cycle, not quarterly: per-cycle residues are trivial to trace fresh and painful to trace in bulk.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_F-fSQS1H8ntW9Xrqs6UGkQ