Payroll journal preparation controls: source-to-ledger research guide

This guide addresses the source-to-journal stage for a U.S. employer: converting a finalized, approved payroll output into a general ledger entry and a reviewer-ready evidence packet. It uses U.S. federal payroll tax and wage-record sources. It does not determine worker classification, calculate an employee's lawful pay, select a state or local tax treatment, interpret a benefit plan, or prescribe financial-statement classification under a specific accounting framework.

The federal sources establish useful record categories and control concepts, but they do not provide one universal payroll journal template. An employer must adapt the method to its payroll provider, legal entities, chart of accounts, reporting framework, state and local rules, plan documents, collective bargaining terms, contracts, and retention schedule.

Step 1: Freeze the source packet. Obtain the payroll register marked final, the payroll approval, payroll tax and deduction summaries, employer-tax detail, change report, and any off-cycle or void report for the same payroll run. Record the legal employer, payroll-run identifier, pay-period dates, pay date, extraction timestamp, report name, and report version. A bank file is not a substitute for the register because it normally does not explain gross earnings, deductions, or liabilities.

Step 2: Test source completeness. Confirm that the packet covers the expected legal entities and payroll runs, including off-cycle payrolls, reversals, and manual checks. Tie the register's employee-level detail to its summary totals when both are available. Do not silently combine different pay dates or revised outputs. If the provider regenerates a report, preserve the earlier version and document what changed.

Step 3: Apply the approved mapping. Map every payroll code to its journal treatment: debit or credit, account, legal entity, cost center or other required dimension, effective date, and mapping owner. Distinguish gross earnings, employer payroll taxes, employee tax withholdings, voluntary and involuntary deductions, reimbursements, net pay, and clearing activity. A new or unmapped code is an exception, not permission to use a suspense account without review.

Step 4: Build the journal from control totals. Prepare debits for compensation and employer costs and credits for net-pay clearing, taxes payable, deductions payable, and other mapped liabilities, subject to the employer's accounting policy. Show the register total used for each journal line or grouped line. Confirm that debits equal credits and that grouped journal amounts can be recomputed from the payroll source.

Step 5: Perform source-to-journal checks. Compare journal totals with the register for gross pay, net pay, employee taxes, employer taxes, and deductions. Check legal entity, accounting period, pay date, duplicate journal identifiers, reversal settings, and allocation dimensions. Compare with a relevant prior payroll only as an exception-finding procedure. A variance from a prior period is not itself an error, and a small variance is not automatically acceptable.

Step 6: Review and post. Give the reviewer the journal, source packet, mapping version, tie-out, variance explanations, and exception log. The reviewer should reperform selected control-total ties, inspect changes and unusual manual lines, confirm the period and entities, and record approval before posting. Capture the posted journal identifier and posting timestamp afterward so the packet proves what entered the ledger, not merely what was proposed.

The cover sheet should identify the legal employer, payroll-run ID, pay-period start and end, pay date, accounting period, payroll system, source extraction timestamp, source version, journal ID, journal date, currency, and any reversal date. It should also name the preparer, reviewer, payroll approver, and posting approver with dated status fields.

The control-total section should separately show gross earnings, employee taxes, employer taxes, employee deductions by material payee or class, reimbursements where relevant, net pay, total journal debits, and total journal credits. For each total, record the source report and field, mapped journal lines, result of the tie-out, and any explained difference.

The mapping evidence should retain payroll code, code description, effective date, account and dimension treatment, debit or credit direction, mapping owner, approval reference, and superseded version. The exception record should carry an exception ID, amount, affected employees or accounts where access permits, cause, owner, required action, due date, disposition, linked correction, reviewer, and closure date.

Journal preparation is not payroll authorization. A preparer can collect approved outputs, apply an authorized mapping, produce the entry, and document discrepancies. The preparer should not approve their own payroll changes, create or alter employee bank instructions, decide an uncertain tax treatment, approve a new mapping, release payroll funds, or approve their own journal.

A payroll owner should confirm that the register is final and authorized. An accounting owner should approve mapping policy and unusual classifications. A separate authorized reviewer should approve the journal, and an authorized user should post it under the organization's access model. When a small team cannot fully separate these roles, document the conflict and add a named compensating review of the source, mapping, posted journal, and subsequent cash settlement.

Limit the packet to data needed for accounting and review. Employee bank details, government identifiers, and other sensitive fields generally are not needed in a journal workpaper. Use stable payroll-run and employee identifiers where detail is required, and grant access according to role.

Stop or escalate when the approved register is missing, totals do not foot, an earning or deduction code is unmapped, the legal entity or period is uncertain, a source version changes, a duplicate journal may exist, a manual line lacks support, or the journal does not balance. Also flag retroactive pay, voids, reversals, off-cycle runs, terminated-employee payments, negative deductions, and entries proposed after the close cutoff.

Do not force-balance with an unexplained plug or erase a difference by changing the source total. Record the gross difference, isolate it by category and entity, identify whether the source, mapping, calculation, or posting is wrong, and assign resolution to the owner of that layer. A correction should reference the original payroll run and journal, preserve the audit trail, and receive approval under the same or stronger boundary as the original entry.

The IRS employment-tax record period and the Department of Labor wage-record periods described in the evidence map cover different records and use different rules. Neither should be read as a single destruction date for the complete journal packet. State and local law, benefit-plan rules, litigation holds, contracts, financial-reporting support, insurance requirements, and company policy may require other records or longer retention.

Maintain a schedule that identifies each record class, controlling requirement, retention trigger, owner, approved repository, access class, hold process, and disposal authority. Preserve source versions, approvals, mapping history, posted-entry evidence, and correction lineage for the applicable period. Obtain payroll, tax, employment-law, records-management, and accounting advice for requirements outside this bounded federal-source review.

The frontmatter evidence map connects each listed URL to a claim used in this guide. Operational steps such as versioning, mapping approval, journal tie-outs, and exception routing are control recommendations derived from the cited record categories and control concepts, not claims that the agencies prescribe this exact workflow or that it produces a stated error-rate reduction.