Payroll journal entries: examples, accruals, and reconciliation


Contents
Key takeaways
- A payroll journal entry is a summary of employee compensation recorded in the general ledger. The payroll register remains the detailed source: worker earnings, deductions, and net pay feed the balanced entry.
- Classify the worker relationship before choosing accounts. Employee compensation follows the payroll route with withholding liabilities; a documented contractor engagement follows a separate service-cost record. The contract label alone does not decide the treatment.
- Gross wages, employee deductions, employer contributions, and net pay have different accounting roles. In the illustrative example below, $10,000 of gross wages produces $8,000 of net pay and $2,000 of deduction liabilities; a separate $900 employer cost creates another expense and liability.
- The posting date and earned pay period are separate decisions. When wages are earned before the payroll run, an accrual can place the cost in the proper period, followed by a reversal or settlement when the actual payroll posts.
- A balanced entry is only the first check. Finance must trace the payroll register to the summary journal and general ledger, then match outstanding liabilities to cash, remittance, and payroll-report records.
- A correction to the books does not automatically correct a filed payroll report. The US Form 941-X and UK FPS/EPS routes apply to different filings, periods, and jurisdictions, so the team must review the original submission separately.
What is a payroll journal entry?
A payroll journal entry is the general-ledger posting that summarizes payroll activity for a reporting period. It records the expense, liabilities, and any settlement or clearing movements created by the payroll run. The supporting payroll register supplies the underlying earnings, deductions, and net pay.
Payroll journal, payroll register, and general ledger
The three records serve different purposes:
- The payroll register is the detailed payroll record. It normally identifies each worker and shows hours worked, earnings, deductions, and net pay. Its totals provide the basis for the summary journal entry.
- The payroll journal records the accounting effect of payroll in debit and credit form. It may contain the main payroll entry, employer-cost entries, accruals, reversals, adjustments, and settlement entries.
- The general ledger accumulates and classifies the transactions posted from journals. It shows the resulting expense and liability balances but does not preserve every worker-level payroll detail.
If the journal total does not agree with the register, finance needs to check the source totals, account mapping, and posting. A balanced journal proves only that debits equal credits; it does not prove agreement with the underlying payroll.
What a summary entry must retain
A summary posting should retain enough information to trace it back to the payroll register and forward to the resulting ledger balances. At minimum, that trail should identify:
- the payroll period and the chosen posting date;
- the gross wages charged to expense;
- each employee deduction recorded as a liability;
- employer contributions recorded as separate expense and liability amounts;
- net pay or other amounts payable to workers;
- the accounts credited or debited for later settlement; and
- the register, report, or other source record used to prepare the entry.
The summary entry need not repeat every worker’s name or deduction line. Keep that detail in the register or another controlled source record, with a reference that lets finance trace the posted totals.
Worker-level detail should remain available to authorized reviewers through controlled access. Reviewers can then trace an exception without giving every general-ledger user access to personal payroll information.
Does the cost belong in employee payroll?
Classify the working relationship before choosing payroll accounts. Employee compensation and contractor service costs follow different record routes because their tax, liability, and documentation treatment differs. The label on a contract or invoice is not enough to decide the accounting route.
Classify the relationship before choosing accounts
Start with the facts of the relationship and the applicable jurisdiction. In the US federal context, the IRS examines the relationship between the worker and the business, including evidence of control and independence. A document describing someone as an independent contractor does not by itself determine the treatment.
The classification changes what the finance team should document and post:
- For an employee relationship, the payroll route normally includes gross wages, employee deductions, net pay, employer payroll costs, and the related liabilities.
- For a contractor relationship, the business generally records the service cost under its applicable accounting policy and follows the contract, invoice, approval, and payment trail. Employee withholding accounts do not belong in that record.
This US federal distinction is not a universal classification test. State and local rules, statutory categories, and other jurisdictions can produce different requirements. The finance team therefore needs a documented determination under the rules that apply to the specific engagement before using either route.

Keep contractor service costs on a separate record trail
Keep contractor service costs separate from employee payroll. A recurring payment alone does not justify using employee deduction or employer payroll liability accounts.
The record trail can include:
- the agreement or statement of work;
- the invoice or other support for the service;
- evidence of approval and delivery;
- the amount payable to the supplier; and
- the settlement of that payable.
The exact account names and measurement rules depend on the entity’s accounting policy and jurisdiction. The supporting tax guidance establishes the US distinction between employee withholding and payments to independent contractors; it does not prescribe one universal contractor expense account for every business.
Before posting, ask two separate questions:
- Has the worker relationship been reviewed and documented under the applicable rules?
- Does the proposed entry follow the employee payroll route or the contractor service-cost route?
If the first answer is unresolved, finance should pause before selecting accounts. This prevents a mixed workforce from being forced into one template and keeps each cost tied to the relationship that produced it.
Which accounts and amounts appear in a payroll entry?
A payroll entry normally combines four distinct amounts: gross wages, employee deductions, employer contributions, and net pay. Each amount has a different role in the journal, and confusing them creates errors in both the income statement and liability accounts.
Gross wages and net pay
Gross wages are the employee compensation recorded as payroll expense before employee deductions. Net pay is the amount payable to the worker after the deductions withheld from gross wages.
The basic relationship is:
Gross wages = net pay + employee deductions
Suppose the payroll register shows gross wages of $10,000 and employee deductions of $2,000. Net pay is $8,000. The initial posting records $10,000 of wage expense, credits $2,000 to deduction liabilities, and credits $8,000 to net pay payable.
These figures are hypothetical and imply no tax rate. In a real entry, the amounts come from the payroll register, and the chart of accounts determines the exact expense and liability names.
Employee deductions and withholding liabilities
Employee deductions are amounts withheld from gross wages and owed to a third party, such as a tax authority or benefit provider. They do not create an additional payroll expense. The worker has already received the compensation; the business holds part of it on behalf of another party until settlement.
For each deduction category, the entry generally:
- credits the relevant deduction liability;
- reduces the amount payable to the worker; and
- leaves the gross wage expense unchanged.
When the liability is settled, the business debits that liability and credits cash. If several liabilities settle together, a payroll clearing account may collect the outflows temporarily, but the individual liability accounts still need to reconcile to their own remittance records.
The account labels and deduction categories depend on the payroll system and jurisdiction. The transferable rule is to keep employee deductions separate from both wage expense and employer contributions.
Employer contributions and benefits
Employer contributions and benefits are costs borne by the business in addition to gross wages. They create separate payroll expense and liability amounts without changing employee net pay.
Using the hypothetical example, a $900 employer contribution produces:
- a $900 debit to employer contribution expense; and
- a $900 credit to the related employer-cost liability.
The resulting employer cost is $10,900: $10,000 of gross wages plus $900 of employer contributions. The $900 does not reduce the $8,000 payable to the worker and does not belong in the employee deduction liability.
Benefit costs may require different accounts and treatment, depending on the plan and the accounting policy. Finance should therefore identify each component from the payroll register or related benefit record rather than combine every employer cost into one vague line.
Cash, payable, and clearing accounts
Payable accounts record amounts that the business owes but has not yet settled. Net pay payable covers the amount owed to workers. Employee deduction liabilities cover amounts withheld for third parties, while employer-cost liabilities cover employer contributions and related obligations.
Cash normally appears when the business settles those obligations:
- debit net pay payable and credit cash when paying workers;
- debit an employee deduction liability and credit cash when remitting the deduction; and
- debit an employer-cost liability and credit cash when paying the related amount.
A clearing account can connect payroll processing with the bank or another settlement system. It should not remain an unexplained balance after the related payroll activity clears. The reconciliation must connect each payable and clearing movement to the source payroll record, bank activity, and remittance evidence.
These relationships follow the accounting mechanics, but account names and the exact settlement sequence vary by entity. A generic payroll template should therefore define the roles of the accounts while leaving jurisdiction-specific labels and amounts to the entity’s chart of accounts and payroll records.
How to record an initial payroll journal entry
An initial payroll entry starts with the payroll register, translates its gross-to-net amounts into debit and credit lines, and adds employer costs as separate expense and liability amounts. The example below uses hypothetical figures and one posting date; it does not represent tax rates or a required posting schedule.
Gather the register and choose the posting date
Begin with the payroll register for the pay period. Confirm the gross wages, employee deductions, net pay, employer contributions, and any off-cycle or adjustment lines included in that run. Keep the earned pay period separate from the date on which the business posts the entry.
The accounting process and the payroll process may use different dates:
- the earned period identifies when the compensation relates to the business;
- the posting date identifies when the journal entry enters the ledger; and
- the payment date identifies when the resulting payable is settled.
For this example, assume wages earned from 1–31 October are included in a payroll processed on 5 November, with the journal posted on 5 November. These dates are illustrative. The actual posting date depends on the entity’s close calendar and payroll process.
Before preparing the entry, confirm that the register is complete and that no manual, bonus, off-cycle, or correction item requires separate treatment.
Turn gross pay and deductions into balanced lines
The hypothetical register contains:
- gross wages of $10,000;
- employee deductions of $2,000;
- net pay of $8,000; and
- a separate employer cost of $900.
The gross-to-net check is:
$10,000 gross wages = $2,000 employee deductions + $8,000 net pay
The initial journal entry dated 5 November is:
| Account | Debit | Credit |
|---|---|---|
| Wage expense | $10,000 | — |
| Employer contribution expense | $900 | — |
| Employee deduction liabilities | — | $2,000 |
| Net pay payable | — | $8,000 |
| Employer contribution liability | — | $900 |
| Total | $10,900 | $10,900 |
This is an illustrative grouping of employee deductions and employer costs. A real chart of accounts may require separate liability lines for each deduction, tax, or benefit category. Finance should use the register and the entity’s approved account mapping rather than copy these grouped account names blindly.
The entry records three separate relationships:
- Gross wages become the business’s wage expense.
- Amounts withheld from workers become liabilities owed to third parties.
- The remaining amount becomes net pay payable.
Record employer costs without changing net pay
Employer contributions belong in the entry, but they do not reduce the amount payable to workers. The separate $900 employer cost creates $900 of additional expense and a $900 liability:
Total employer cost = $10,000 gross wages + $900 employer contribution = $10,900
The $8,000 net pay payable remains unchanged. Treating the $900 as another employee deduction would misstate both the amount due to workers and the liability owed for the employer contribution.
The same distinction applies to employer-paid benefits. Each component needs an amount and an approved account treatment from the payroll or benefit record. Finance should not add an amount merely because it appears in a payroll report; the component must belong to the period and the entry being prepared.
Check the entry against the register
Perform the checks after preparing the entry but before posting it:
- Balance check: total debits equal total credits. The illustrative entry totals $10,900 on each side.
- Gross-to-net check: gross wages equal net pay plus employee deductions.
- Employer-cost check: employer costs agree with the register and remain separate from employee deductions.
- Account-mapping check: each line points to the correct expense, payable, and clearing account for the entity.
- Period and date check: the register period, posting date, earned period, and payment date are identified and recorded according to the entity’s accounting policy.
- Detail-trace check: the summary entry can be traced to the payroll register or payroll report from which it was prepared.
A balanced entry can still contain a wrong account, the wrong amount, or a duplicate posting. The register comparison is therefore a separate control from the debit-and-credit check. If gross pay, net pay, deductions, or employer costs do not agree, finance should resolve the difference before the entry reaches the general ledger.
Which entry fits each payroll event?
The right payroll entry depends on the event being recorded and when the related cost was earned. Separating accrual, settlement, adjustment, and correction events keeps each transaction traceable and prevents the same expense or liability from being recorded twice.
Earned wages before payroll is processed
When workers have earned wages that will be processed in a later payroll period, the business may need an accrual before the payroll run posts. The accrual recognizes the earned cost and related liability in the appropriate reporting period; it does not anticipate every deduction or employer cost by an invented amount.
A simplified accrual entry is:
| Account | Debit | Credit |
|---|---|---|
| Wage expense | $1,000 | — |
| Accrued wages payable | — | $1,000 |
The amount is hypothetical. The real entry must follow the entity’s accounting basis, pay period, and accrual policy. For entities applying IFRS, IAS 19 supports recognizing short-term employee benefits when the employee has rendered the service, measured at the undiscounted amount expected to be paid.
The key control is the later reversal or settlement. If November payroll posts the full actual expense, finance must remove the October estimate when that expense posts so the same wages do not appear in both periods.
Net pay settlement and liability remittance
Settlement closes the payable created by the payroll entry. It does not create a second payroll expense.
For net pay, the standard movement is:
| Account | Debit | Credit |
|---|---|---|
| Net pay payable | $8,000 | — |
| Cash | — | $8,000 |
Amounts withheld from workers follow a separate path. Settling an employee deduction liability requires debiting that liability and crediting cash. Employer contributions and benefits settle through their own liability accounts. In each case, the amount paid must agree with the payroll record and the remittance or settlement evidence.
A clearing account may be used when several payroll liabilities are paid through one operational account. It does not replace the underlying liability records. Finance still needs to trace each employee deduction and employer cost from the register to its settlement.
Manual, off-cycle, bonus, and advance adjustments
Manual and off-cycle payroll items require the same basic controls as a regular run: identify the affected period, prepare the supporting entry, and reconcile the posted amount to the payroll record.
For a manual or off-cycle item, the adjustment should point to the original transaction, affected period, original accounts, amount, and supporting payroll record. Brown University’s payroll procedure, for example, distinguishes an overpayment, underpayment, pay-component change, or on-demand check from a regular-cycle payroll result when finance locates a posted adjustment. That institutional procedure does not establish a universal off-cycle journal entry, but it shows why the source result must be identified before the books are changed.
A bonus requires the payroll record to identify the supplemental wage and its payment treatment. In the United States, the IRS treats bonuses as supplemental wages. The withholding method can depend on whether the bonus is identified separately from regular wages and on the worker’s regular-wage withholding history. The journal should use the gross bonus, deductions, and employer costs from the approved payroll record; finance should not copy a withholding rate into a generic entry.
An advance needs a different question: what does the advance represent under the entity’s policy and local law? Stony Brook University describes an advance against wages already earned in a delayed or erroneous-paycheck situation. Dartmouth College describes an advance received before the next regular paycheck and deducted from that paycheck, with taxes and other deductions applied when the advance check runs. California State University, Los Angeles uses a payroll accounts-receivable treatment for an unpaid advance under its own policy.
The review should therefore establish:
- whether the amount represents earned pay paid early, a recoverable advance, or another arrangement;
- which approval, payroll offset, tax treatment, and account classification the entity’s policy applies;
- the period in which the related compensation is recognized; and
- how the advance payment and any later payroll offset reconcile.
Finance must not record every advance as a receivable or expense the same wages twice. The source payroll record, approval, later offset, and applicable policy determine the treatment.
Reversals, voids, and correcting entries
A reversal removes an earlier posting. A void cancels an unsettled payroll instrument or payment. A correcting entry fixes a posted transaction that remains in the books. These actions may occur together, but they answer different questions.
Before drafting an adjustment, identify:
- the original payroll period and posting date;
- the account, amount, and direction of the original entry;
- whether the payment was made, reversed, or voided;
- whether the worker or payroll record was also corrected; and
- whether any tax or payroll report already submitted includes the affected amount.
For example, if a payroll check is voided before settlement, the voided amount should not remain as an outstanding payable. If a transaction was already posted to the general ledger, finance must make an adjusting entry that removes or corrects it. That bookkeeping adjustment does not automatically amend the worker record or a filed payroll report.
Recurring accruals, reversals, and correcting entries can all appear in the general journal. The entry description should state the event, affected period, amount, and original reference. This preserves the audit trail and helps the reviewer determine whether the correction belongs to the original run, a later payroll, or a separate adjustment cycle.
How to accrue payroll across a reporting period
Accrue employee compensation when it has been earned but the related payroll has not yet been processed, provided the entity’s accounting basis and policy require that treatment. The accrual places the cost in the period in which the service was rendered; a later reversal or settlement removes the estimate when actual payroll posts, so the expense is not counted twice.
Estimate earned but unpaid wages
Begin with the earned period, the payroll cycle, and the actual register. A pay period may cross a reporting-period boundary, leaving wages earned before month-end but processed in the next month.
For IFRS entities, IAS 19 supports recognizing short-term employee benefits when the employee has rendered the service. The benefits are measured at the undiscounted amount expected to be paid in exchange for that service. Entities applying another accounting framework need to follow their applicable policy.
Use the most reliable estimate available from the payroll records. A common method is to calculate the portion of the current pay period earned by the reporting date. An institutional process may use a workday fraction or another documented method, but that calculation belongs to the entity’s policy. Do not copy an institution’s divisor or accrual formula into another business without confirming the pay cycle, exclusions, and accounting basis.
For the example below, assume $1,000 of wages was earned by 31 October and will be included in a payroll processed in November. The amount is hypothetical.

Reverse or settle the accrual without a second expense
The October accrual is:
| Posting date | Account | Debit | Credit |
|---|---|---|---|
| 31 October | Wage expense | $1,000 | — |
| 31 October | Accrued wages payable | — | $1,000 |
When the November payroll posts the full actual amount, finance reverses the estimate alongside the actual payroll posting:
| Posting date | Account | Debit | Credit |
|---|---|---|---|
| 5 November | Accrued wages payable | $1,000 | — |
| 5 November | Wage expense | — | $1,000 |
The reversal clears the October liability and removes the $1,000 estimate from November’s gross payroll expense. Combined with the gross November payroll posting, it leaves only the portion belonging to November in November expense. October retains its $1,000 accrued expense, so the same wages are not recognized in both periods.
The accrued wages liability is then cleared. Any difference between the estimate and actual amount needs to follow the entity’s accounting policy.
A different policy may settle the accrual directly rather than reverse it. Finance must follow the entity’s documented method and ensure that whichever route is used, the original accrual and the actual payroll do not both remain as expense in the same period.
Check the effect on the balance sheet and income statement
An accrual changes both statements. On 31 October, wage expense increases by $1,000 and accrued wages payable increases by $1,000. The balance sheet recognizes compensation owed for services already rendered; the income statement recognizes the cost in the period that consumed the services.
After the November payroll and reversal:
- the wage expense recognized for October remains $1,000;
- the November period carries only the current-period portion of the payroll after the $1,000 credit reversal;
- the accrued wages payable is eliminated;
- cash and the other payroll liabilities reflect the actual payroll run; and
- any remaining difference between the estimate and actual amount follows the entity’s policy.
Review the effect as a complete sequence rather than as isolated entries. Check that:
- the accrual falls within the period in which the wages were earned;
- the estimate uses documented payroll inputs;
- the later payroll posts the actual amount;
- the reversal or settlement eliminates the accrued liability;
- no portion of the same compensation remains in both periods; and
- cash, employee deductions, and employer liabilities reconcile to the payroll and remittance records.
The exact dates and amounts depend on the accounting basis, pay cycle, close calendar, and actual payroll register. The control remains the same: recognize the earned cost once, then remove the estimate when the actual payroll is recorded.
How to reconcile payroll entries and liabilities
Reconcile payroll in two directions. Start at the source record and trace it into the summary journal and general ledger; then start with the ledger balances and trace them to cash, clearing, and remittance evidence. A balanced entry establishes only that its debits and credits agree.
Trace source records into the summary journal
The payroll register normally contains the detail that drives the journal: worker earnings, deductions, and net pay. Compare its totals with the summary entry before posting, then retain a trace between the register, journal, and ledger.
For the illustrative payroll, the review would begin with three controls:
- Gross pay: the register’s $10,000 agrees with the wage expense posted.
- Net pay: the register’s $8,000 agrees with the net pay payable posted.
- Deductions and employer costs: the register’s $2,000 employee deductions and $900 employer cost agree with their corresponding liabilities.
Nebraska’s payroll certification process uses gross-pay and net-pay comparisons between the register and journal entry, while the IRS examination manual describes tracing source documents and journals into the general ledger. These are scoped public-process examples, but the source-to-ledger trace is a practical control for private finance teams.
A mismatch can sit in several places. The source total may be wrong, the journal may omit a line, the account mapping may be incorrect, or the transaction may have been posted twice. Start from the register rather than adjusting the general-ledger balance until the difference disappears.
Match the register, general ledger, bank, and remittance records
The source comparison verifies the entry. The settlement comparison verifies that the resulting liabilities have cleared.
For each payroll period, match four records:
| Record | What it should establish |
|---|---|
| Payroll register | Gross wages, employee deductions, net pay, and employer costs recorded by the payroll process |
| General ledger | Expense and liability accounts posted from the payroll journal |
| Bank or clearing records | Cash movements associated with the payment run |
| Remittance records | Evidence that withheld amounts and employer obligations were paid to the relevant recipients |
The settlement path depends on the liability. Net pay payable should be cleared when workers are paid. Employee deduction liabilities should be matched to the relevant remittance. Employer contribution and benefit liabilities should follow their own settlement records. If a clearing account carries several payroll outflows, its movement should reconcile to those individual liabilities rather than remain an unexplained balance.
US employers retain records of wage payments, tax deposits and acknowledgments, and filed returns. UK PAYE employers keep employee pay and deduction records, reports submitted to HMRC, and payments made to HMRC. These are jurisdiction-specific record requirements supporting the same reconciliation principle: the ledger needs a trace to the underlying payroll and remittance evidence.
Investigate stale liabilities, duplicate entries, and clearing balances
A liability that remains after the expected settlement period needs an exception owner and a documented resolution. Check for:
- a deduction payable that does not match any remittance;
- a net pay payable left after the payment run;
- a clearing balance that persists after the payroll cycle closes;
- a ledger expense duplicated from the same register;
- a reversal posted without a corresponding original; and
- a corrected journal that leaves the worker record or filed report unchanged.
Work from the difference rather than posting a plug. Identify the exact period and amount, determine which record changed, and then select the correction supported by that evidence. Investigate the payment record for an unresolved remittance. Review the original posting before adjusting a stale liability or reversing a duplicate. The entry should identify the original transaction and preserve the path from the exception to its resolution.
A zero clearing balance is not a universal requirement for every entity or payroll design. The control is that the balance is explained, supported by source records, and reconciled under the entity’s policy.
Keep worker-level detail and review access appropriate
Worker-level payroll records support investigation, but the general ledger does not need to become a register. Keep the detail in the payroll system or another controlled record and retain a reference from the summary journal to that source.
Review access should follow the purpose:
- payroll and finance staff need the detail required to prepare, reconcile, and correct the entry;
- managers may receive summarized information needed for their approval duties; and
- personnel outside those workflows should not receive unrestricted access to worker pay and deduction data.
The reconciliation file should record who reviewed the entry, the period, the source records used, the differences found, and the disposition of each exception. This creates accountability without duplicating sensitive payroll data across the ledger.

What changes across jurisdictions and after a correction?
Double-entry mechanics remain consistent, but account names, withholding categories, reporting forms, remittance records, and correction procedures vary by jurisdiction. A corrected journal entry fixes the books; it does not automatically correct a payroll report that has already been submitted.
Separate accounting mechanics from local payroll rules
The recurring accounting relationships do not depend on the country:
- gross wages are recorded as compensation expense;
- employee deductions reduce the amount payable to the worker and create liabilities;
- employer contributions create separate expense and liability amounts; and
- settlement removes the relevant payable or clearing balance.
Local rules determine which amounts populate those relationships, which accounts hold them, when they must be reported, and how errors are corrected. The employer’s tax residence, the worker’s location, the type of engagement, and the applicable reporting regime can all affect the result.
Finance should therefore separate three questions:
- Accounting question: which period recognizes the cost, and which expense, liability, and cash accounts record it?
- Payroll question: which deductions and employer amounts apply, and what supporting payroll record documents them?
- Reporting question: which authority receives a report, what was submitted, and which correction route applies to that filing?
A generic example can demonstrate debit and credit logic. It cannot establish tax rates, filing deadlines, or the correct correction form for an actual engagement.
US withholding and amended return example
In the United States, an employer that withholds employment taxes from employee wages records those withheld amounts as liabilities and later settles them according to the applicable federal, state, and local requirements. Employer payroll taxes create separate expense and payable accounts.
Suppose a payroll register contains a wrong withholding amount, and the business has already posted the payroll entry. The first correction belongs in the accounting records:
- correct the payroll or worker record when appropriate;
- post a correcting journal entry against the affected expense, liability, and payable accounts; and
- identify the original posting and the reason for the change.
If the same error appears on a previously filed US Form 941, a separate reporting step is required. The IRS instructs employers to use Form 941-X to correct errors on a Form 941 they previously filed. Form 941-X does not apply to every employment-tax form; its instructions specifically exclude corrections to Forms CT-1, 943, 944, and 945.
A journal correction does not necessarily trigger a Form 941-X. If the reported wages and deductions were correct and finance only changed the general-ledger account used to classify an amount, the evidence does not establish an error on Form 941. The team must inspect the filed return rather than amend every report whenever a book entry changes.
UK PAYE records and correction example
UK PAYE employers keep records of what they pay workers, deductions made, reports submitted to HMRC, and payments made to HMRC. These records support the payroll-to-report reconciliation and identify which submission contains an error.
The correction route depends on the document and period:
- For an error in the current tax year’s FPS, HMRC directs the employer to update the year-to-date figures in the next regular FPS.
- An error in the final FPS of the year follows a different route, so the final-submission instructions must be reviewed.
- For an erroneous EPS, HMRC directs the employer to submit an EPS with corrected year-to-date figures for the affected tax year.
FPS and EPS therefore serve different correction purposes. The team should identify the original submission, the affected tax year, and whether the error changed reported pay or deductions before acting.
The same cross-record review applies to both examples:
| Record affected | Required review |
|---|---|
| Payroll register or worker record | Correct the underlying calculation or detail |
| General ledger | Post an entry against the correct expense and liability accounts |
| Bank or remittance record | Confirm whether cash or a third-party settlement already occurred |
| Filed payroll report | Use the correction route for that specific form, jurisdiction, and period |
This sequence prevents a team from treating a corrected journal as the end of the correction. A report remains wrong until the appropriate filing process addresses it, while an unchanged report may remain correct when only the book classification changed.
Manual entry, import, or integrated posting?
Choose the posting workflow from the controls the finance team can sustain. Manual entry, report import, and integrated posting can all produce a balanced journal; the practical differences lie in traceability, account mapping, review effort, and exception handling. Available source processes do not establish that one method produces fewer errors or a faster close.
Compare source traceability and control needs
The first question is whether each workflow leaves a clear route from the payroll source to the posted journal and back to the supporting record.
Manual entry gives the preparer direct control over each line, but it depends on disciplined copying, reconciliation, and review. The reviewer must compare the posted totals with the payroll register rather than accept a balanced entry as sufficient evidence.
Imported posting uses a payroll report as the source for the journal. It reduces manual transcription, but the team still needs to confirm that the report covers the correct period, the mapped accounts are valid, and the import has not omitted or duplicated lines.
Integrated posting creates the journal from a connected system. This can preserve a direct link to the payroll process, but the accounting team still needs to verify the account configuration, the approval path, and the treatment of exceptional payments. An integration does not remove the need for review.
Compare the options against the finance team’s actual environment:
| Control need | Manual entry | Imported posting | Integrated posting |
|---|---|---|---|
| Trace to the payroll source | Direct but dependent on accurate preparation | Requires report retention and version control | Depends on the integration and source-system history |
| Account mapping | Prepared and checked line by line | Defined in import mapping | Maintained in system configuration |
| Review of exceptions | Separate from posting | Requires an exception queue or report | Requires ownership of configuration and exceptions |
| Protection against duplicate posting | Process control and posting review | Import control and duplicate detection | System controls plus monitoring of reruns |
| Separation of preparation and approval | Important because one person may perform both | Important when import preparation can be automated | Important because system roles can still be misconfigured |
The selection should reflect payroll volume, system access, account complexity, and the reviewers available to investigate exceptions. Available institutional sources describe controls for reconciliation and mapped journals, but they do not provide transferable error-rate or close-time comparisons among these three workflows.
Review mapped accounts, approvals, and exceptions
Account mapping determines what the journal actually says. Review each payroll code, deduction, employer cost, and adjustment against the chart of accounts before the transaction posts.
Washington’s college payroll process illustrates the risk: an invalid chartstring can enter a finance journal and require correction before posting. The account codes belong to that institution, but the control transfers: a balanced entry can still contain an invalid or inappropriate account. Review the mapping rather than checking only whether debits equal credits.
Define the approval workflow for each posting type:
- The preparer confirms the source period, register totals, and posting date.
- A reviewer checks gross wages, net pay, employee deductions, employer costs, and the account mapping.
- The approver authorizes the posting and records the source reference.
- Finance reconciles the posted balances to cash, remittance, and payroll-report evidence.
Exception handling should state who owns each difference and when it must be resolved. The exception queue should distinguish:
- missing or invalid account mappings;
- unmatched employee deductions;
- off-cycle or manual adjustments;
- duplicate imports or repeated integrated runs;
- reversals with no original entry;
- payroll-register and journal differences; and
- liabilities that did not settle as expected.
An automated workflow can flag mapped-account errors, repeated source files, and amount differences, but it still needs human validation for the cases that affect the classification of a cost, an exceptional payroll item, or a prior-period correction. Finance needs a posting it can trace, review, reconcile, and correct without reconstructing the payroll run from scratch.
Common payroll journal entry mistakes
Employee deductions, balanced journals, and copied examples each create a different risk. Check the expense treatment, source agreement, and local context separately.
Treating employee deductions as another expense
Employee deductions are already part of gross wages. Withholding $2,000 from an employee does not create $2,000 of additional compensation expense; it changes the amount payable to the worker and creates a $2,000 liability to the relevant third party.
For the hypothetical $10,000 gross-pay entry:
- debit wage expense for $10,000;
- credit employee deduction liabilities for $2,000;
- credit net pay payable for $8,000; and
- record the separate $900 employer cost through its own expense and liability accounts.
The resulting employer cost is $10,900. If the $2,000 deduction were added again as an expense, the books would incorrectly show $12,900.
A related error is to treat employer contributions as employee deductions. Employer contributions increase the business’s cost and liabilities but do not reduce net pay. Keep these amounts on separate lines even when the payroll report groups them in one total.
Confusing a balanced entry with a reconciled entry
A balanced entry proves that total debits equal total credits. It does not prove that the journal agrees with the payroll register or that its liabilities have settled.
Check three layers separately:
- Source agreement: gross pay, net pay, deductions, and employer costs in the journal agree with the payroll register or report.
- Ledger agreement: the posted amounts reached the intended expense and liability accounts.
- Settlement agreement: cash, clearing, and remittance records explain how the resulting liabilities cleared.
Washington’s payroll process shows why the first two checks matter separately: an invalid chartstring can enter a finance journal and require correction even when the entry balances. Nebraska’s certification process combines the balance check with separate gross-pay and net-pay comparisons against the payroll register.
A payroll entry can therefore pass the debit-and-credit test while still containing an invalid account, the wrong period, a duplicated transaction, or an unsettled liability. Reconciliation continues after posting.
Copying an example without checking period or jurisdiction
A worked payroll entry is a model, not a universal template. Before using it, verify:
- the worker relationship and documented classification;
- the earned pay period, posting date, and payment date;
- the accounting framework and entity policy;
- the deduction and employer-cost categories in the actual register;
- the jurisdiction-specific withholding, reporting, and remittance rules;
- the chart of accounts and settlement process; and
- any original payroll report, filed report, or prior posting affected by an adjustment.
The US federal treatment of employee wages and independent-contractor payments differs from UK PAYE records and reporting. A US withholding label such as FICA or Form 941 cannot be translated directly into a UK entry, and a UK correction through FPS or EPS cannot be applied to a US filing. These are separate filing systems, not interchangeable account names.
The same caution applies to entity-specific practice. Washington’s college accounts, Nebraska’s certification steps, and UCSF’s accrual method illustrate particular processes. They can help finance identify a control, but their account codes, dates, formulas, and approval steps require verification before reuse.
Before posting a copied example, replace every placeholder with evidence from the current payroll and confirm that the entry answers three questions: which period receives the cost, which obligations remain outstanding, and which records will prove that the liabilities later cleared.
Frequently asked questions
What is the double entry for payroll?
The double entry records payroll expense as a debit and the related amounts owed as credits. For a hypothetical payroll with $10,000 of gross wages, $2,000 of employee deductions, $8,000 of net pay, and a separate $900 employer cost:
| Account | Debit | Credit |
|---|---|---|
| Wage expense | $10,000 | — |
| Employer contribution expense | $900 | — |
| Employee deduction liabilities | — | $2,000 |
| Net pay payable | — | $8,000 |
| Employer contribution liability | — | $900 |
| Total | $10,900 | $10,900 |
These amounts are illustrative and imply no tax rates. A real entry follows the payroll register and the entity’s chart of accounts.
Is payroll expense a debit or credit?
Payroll expense is normally a debit. The debit records compensation cost in the reporting period. The related credits create liabilities for net pay, employee deductions, and employer contributions.
When finance later pays workers, it debits net pay payable and credits cash. That settlement entry does not create a second debit to payroll expense.
What is the difference between a payroll journal and a payroll ledger?
A payroll journal records the debit and credit effects of payroll activity. A payroll ledger, often represented by the payroll register, retains the detailed underlying records used to prepare that journal, including worker earnings, deductions, and net pay.
The general ledger receives the summarized journal entry. The payroll source record remains the trace for investigating individual amounts. Terminology can vary by accounting system, so finance should confirm whether “payroll ledger” means the register, a subsidiary ledger, or the journal itself.
How often should payroll journal entries be recorded and reconciled?
Record payroll entries at the frequency of the payroll runs and the entity’s reporting requirements. At minimum, each run creates a trace from the payroll source to the journal and general ledger. Each reporting close requires a reconciliation of the register, ledger balances, cash or clearing movements, and remittance records.
A payment alone does not determine the posting frequency. Off-cycle payroll, bonuses, adjustments, accruals, and corrections create separate events that must be recorded when they occur. The review calendar should cover every reporting period in which payroll liabilities or clearing balances remain outstanding.
What is the entry when salaries are paid in cash?
The payment of salaries in cash settles an existing net pay liability:
| Account | Debit | Credit |
|---|---|---|
| Net pay payable | $8,000 | — |
| Cash | — | $8,000 |
The $8,000 is the hypothetical net pay amount from the earlier example. If salaries are paid directly without first recording a payable, the business records the full payroll expense, deductions, employer costs, and cash movement in one combined entry. The register still supports the gross-to-net calculation.
Do outsourced payroll runs still need a journal entry?
Yes. Outsourcing the payroll calculation and processing does not remove the business’s need to record the resulting accounting entries. Finance still needs to identify the payroll expense, liabilities, payment, and any employer costs in the general ledger.
In the US, an employer that outsources payroll and related tax duties to a third-party payer generally remains responsible for those duties, including liability for the taxes, subject to specific third-party arrangements and exceptions. The outsourcing agreement therefore does not replace the finance team’s review of the payroll report, journal entry, and subsequent reconciliation.
The outsourcing provider may supply the journal or a report that feeds it. The business remains accountable for the entries and supporting records in its own accounting system.
A payroll entry close check
Before you approve a payroll journal entry for posting, confirm the following. The check should be completed for the pay period and the entries being posted, not treated as a one-time form.
- Worker relationship: the employee or contractor classification is documented, and the cost follows the appropriate record route.
- Source record: the payroll register or report for the period is identified and attached to the review trail.
- Earned period: the period in which the compensation was earned is recorded separately from the posting date.
- Gross-to-net check: gross wages equal employee deductions plus net pay.
- Employer-cost check: employer contributions and benefits are recorded separately and do not change employee net pay.
- Balance check: total debits equal total credits.
- Account mapping: every line points to the correct expense, payable, and clearing accounts under the entity’s chart of accounts.
- Manual items: bonuses, advances, off-cycle payments, corrections, and reversals are identified and supported by their own source records.
- Adjustment link: each correcting entry refers to the original payroll period, amount, account, and reason for correction.
- Settlement path: net pay, employee deductions, employer contributions, and benefits each have a defined cash or remittance path.
- Reconciliation: register totals agree with the journal, ledger balances agree with the posting, and cash or remittance records support the settlement.
- Exception ownership: stale liabilities, duplicate postings, invalid mappings, and uncleared balances have a named reviewer and resolution status.
- Reporting check: the team has determined whether any affected payroll report was already filed and needs a separate correction.
- Audit trail: the reviewer, approval, source references, exceptions, and final posting are recorded.
Approve the entry after checking it against the source, the entity’s accounting policy, and the settlement trail. Equal debits and credits alone cannot reveal a wrong account, period, duplicate transaction, or unsettled liability.
Sources
- IRS Publication 15-A (2026): Employee or Independent Contractor
- IRS Publication 15 (2026): Employer's Tax Guide
- IFRS Foundation: IAS 19 Employee Benefits
- IRS Internal Revenue Manual §4.10.3: Examination Techniques
- Washington State Board for Community and Technical Colleges: Payroll Accounting
- Nebraska Department of Administrative Services: Payroll Certification Mini-Manual
- UCSF Controller's Office: Understanding Biweekly Payroll Accruals
- IRS: Employment Tax Recordkeeping
- HMRC: PAYE for Employers — Keeping Records
- IRS Instructions for Form 941-X (2026)
- HMRC: Correcting Your FPS or EPS
- New Mexico Public Education Department: Manual of Procedures, PSAB Supplement 14 — Payroll
- Brown University Controller: Payroll Accounting Adjustments FAQs
- Stony Brook University: Salary Advances Against Payroll Policy
- Dartmouth College: Pay Advance Policy
- California State University, Los Angeles: Salary Advance and Payroll Accounts Receivable Management Policy P015