Payroll Journal Entry Review: Approve the Batch Before Posting
Updated: Nov 3
An approval to post a payroll journal should name the entry it authorizes: the ledger batch, its source run and version, the accounting period, and the evidence used to review its amounts. A message saying “payroll looks fine” leaves the poster to decide which file, date and accounts that approval covers.
Use a payroll journal entry review checklist to make that authorization specific. Confirm the final run's financial effects, the treatment of each account group, the period and entity, the absence of a duplicate, and the route by which payroll funding will clear. Then approve that exact batch or return it with a reason that the preparer can resolve.
This guide is for U.S. payroll and finance teams reviewing an accrual-basis accounting entry before it reaches the general ledger. The examples are fictional, with assumed approved payroll totals rather than calculated tax rates. Your controller or accounting adviser must approve recognition policies, account classifications, thresholds and correction entries for your organization.
If you are comparing payroll services because finance repeatedly rebuilds the journal, bring a sample export and your chart of accounts to a free SelectSoftware Reviews advisor consultation. Ask prospective providers to show the posting detail, correction process and work your team will retain.
Contents
Define what the posting approval covers
Separate payroll approval from journal approval. Payroll approval addresses the pay result and release. Journal approval addresses how a particular result will be recorded in a particular set of books. A payroll run can be correct while its export uses an obsolete account map.
The reviewer needs the final register or accounting summary, the proposed journal, the mapping version, a list of included runs, and the relevant adjustment and funding reports. Use access-controlled links to source records. A summary without employee names may be enough for the accounting review, while restricted detail remains available to investigate an exception.
Record the legal entity, ledger, currency, pay date, earned period, run identifier, export time and journal batch identifier. If one export combines several runs, attach its run list. If one run creates several accounting batches, list all of them and explain the split. File names alone are weak identifiers when files can be overwritten.
Decide which route creates the entry: an automatic integration, an uploaded file or manual preparation. Check the ledger and interface history for an existing batch before authorizing another route. A failed screen message can follow a successful import, so an uncertain response requires a status check before a retry.
Name the boundary of approval. For example: “Approve batch J-431 version 2 for Entity A's November ledger, covering runs R-118 and R-119; no other run included.” Posting access should support that boundary. If a file changes afterward, the original approval does not establish that the revised amounts were reviewed.
Follow the amounts through a reviewable journal
Start with source totals that distinguish gross wages, employee withholdings, employee deductions, employer costs and net pay. OpenStax's payroll accounting examples distinguish employee deductions from additional employer costs and show liabilities followed by settlement. Use those accounting relationships, while obtaining current tax calculations from your payroll process and applicable official guidance.
Consider a fictional approved run with $48,000 gross wages, $9,000 employee tax withholding and $3,000 employee benefit deductions. Net pay is $36,000. Employer payroll taxes are an assumed $4,000, and the employer benefit cost recorded through this entry is $2,000. No other earnings, reimbursements, noncash compensation or employer costs are included.
For this illustration, no related cost or obligation has already been booked, and no payment has yet settled. The approved account map uses separate payables. Actual employers may use more detailed accounts or an approved clearing arrangement.
Expense debits:
Wages expense: $48,000.
Employer payroll-tax expense: $4,000.
Employer benefit expense: $2,000.
Total debits: $54,000.
Liability credits:
Net wages payable: $36,000.
Payroll taxes payable, employee and employer combined: $13,000.
Employee benefit deductions payable: $3,000.
Employer benefits payable: $2,000.
Total credits: $54,000.
The arithmetic gives two useful checks: $48,000 minus $9,000 minus $3,000 equals $36,000 net pay; $36,000 plus $13,000 plus $3,000 plus $2,000 equals $54,000 liabilities. The $9,000 withheld from employees is part of their gross wages, not an additional employer expense.
Before approving, tie each amount to its source report and trace the actual account numbers. The combined tax payable is an explanatory total, not a recommendation to merge all agencies in one operational account. Keep the detail needed to identify each obligation, tax period and recipient.
Now change the draft so it debits wages expense $39,000 and employer payroll-tax expense $13,000, retaining $2,000 benefits. Total debits still equal $54,000. The journal balances, but $9,000 of employee withholding has moved out of wage expense into employer tax expense.
That draft needs correction before posting. Confirm the intended classification with the accountant and regenerate the affected accounts. If this exact error has already posted, an approved reclassification would debit wages expense $9,000 and credit employer payroll-tax expense $9,000, with no cash or employee pay change. That is an illustration of this isolated error, not permission to use the same entry for a different discrepancy.
The equality of debits and credits is one test. The posting decision also needs the correct source, accounts, period and batch history.
Explain the difference between payroll cost and provider funding
A bank debit is evidence of a cash movement. Its amount need not equal wage expense, total payroll cost or the journal's debit total.
In the same example, suppose the provider requests $36,000 for net pay, $13,000 for taxes and a $250 service fee. Its total debit is $49,250. The $5,000 of employee and employer benefit obligations is paid separately. The example's $54,000 payroll cost therefore does not reconcile directly to the $49,250 provider debit.
Build the funding explanation from the provider's breakdown: $49,250 equals $36,000 plus $13,000 plus $250. Keep the fee outside wage and employer-tax expense. Identify whether benefit contributions, manual checks, reserve movements or earlier corrections are outside that debit.
Check whether the accounting feed already records the cash side. If it does, accepting a bank-feed transaction as another payroll expense can record the same economic event twice. Match the bank item to the approved accounting route, rather than creating a second expense because the bank description says payroll.
A provider's collection of tax money also does not establish that the agency received it. IRS guidance on outsourcing payroll duties warns that employers generally remain responsible for federal tax payment when using an ordinary payroll service provider. Confirm the legal arrangement and obtain payment evidence; special third-party-payer arrangements need their own analysis.
Your accountant should define the entries between the bank debit and confirmed disbursement. Where money is held pending payment, the route may use an approved provider-funding or clearing account. Do not automatically reduce every tax liability merely because funds left the bank, or assume that a clearing balance must be zero while supported payments remain in transit.
For each settlement, identify the obligation reduced, the amount, the payment reference and the evidence that permits that accounting treatment. A returned payment needs an explicit restoration or correction under the approved procedure. Preserve its connection to the original payment so a replacement does not look like a second payroll expense.
Fictional amounts: payroll cost is $54,000; total cash for those obligations plus the separate $250 fee is $54,250. Payment timing and the approved clearing method determine the intervening balances.
Review the accounts below the balanced total
Use the current chart of accounts and approved mapping, including account numbers, entity, department, location and project dimensions that your ledger requires. An account name that looks familiar can conceal a changed number or posting restriction.
Inspect every new earning or deduction code in the batch. Determine whether it creates expense, a payable, a reimbursement, a recovery or a noncash record under the approved policy. Do not copy the treatment of a similarly named code without checking what the transaction represents.
Employee deductions normally direct part of gross pay to another recipient. Employer contributions create additional cost where required by the arrangement and recognized under the accounting policy. Combining the two without retaining their distinction makes a plausible total harder to explain.
Check benefit costs against entries outside payroll. If accounts payable already recognized an insurer invoice, booking the full benefit expense again through payroll may duplicate cost. Determine whether the payroll deduction should offset an existing receivable or payable, or use another accountant-approved treatment. The illustrative journal above deliberately assumes no earlier entry.
Review allocations at the level that affects decisions. If wages move between two departments while the total stays constant, compare the approved worker or labor-allocation records and the effective mapping dates. For multiple entities, prove each entity's balanced entry and any approved intercompany treatment; a consolidated balance can conceal opposite errors in separate books.
Examine suspense and default accounts individually. A system-generated default does not establish the right classification. Identify the source code, intended destination and correction owner. A temporary account should have an approved purpose, support and clearing date, rather than serve as an unexplained plug that allows an import to balance.
Also inspect the exported signs. A reversal, refund or deduction recovery can be valid, but a negative amount in a credit column may be interpreted differently by the import format. Compare the resulting ledger preview with the intended debit and credit. Never rely solely on the spreadsheet's appearance.
Keep earned dates, pay dates and posting periods distinct
The work period explains when employees earned the compensation. The pay date identifies when wages were paid. The journal date determines where an accounting entry lands under the chosen posting method. The bank date identifies a cash movement. Record these separately even when several happen on the same day.
For an accrual-basis close, costs incurred but not yet recorded may require a period-end adjustment. OpenStax's discussion of accrued salaries illustrates this distinction. A platform's operational instruction to use the paycheck date for a payroll entry does not, by itself, resolve every month-end recognition question.
Suppose a run pays for October 26 through November 8 and is paid November 13. If the payroll entry posts in November, finance must determine whether October's books already include the appropriate unpaid service-period cost under its policy. Check the related accrual and reversal references, rather than moving the whole payroll journal into October.
Do not rebuild the accrual inside the journal checklist. Obtain the approved estimate and its settlement or reversal instruction. Confirm that the payroll posting and related adjustment will recognize the service cost once. An unexplained carryover should stay visible to the person approving close.
Check the actual ledger period, not just a date printed on the file. A closed-period import may be rejected or redirected by a system's configuration. Obtain evidence of the selected period and approval for any permitted exception before release.
A general-ledger correction does not automatically correct payroll wage records or tax returns. Intuit's manual-payroll guidance, for example, explains that recording outside-service payroll payments in QuickBooks Online does not create employee W-2 information. Establish which source records are wrong before deciding whether the fix belongs only in accounting.
Likewise, changing a posting date does not change a legal payday or tax-deposit deadline. IRS Publication 15 bases federal deposit obligations on the applicable tax rules, including payment timing and the employer's deposit schedule. Keep those obligations with their own calendar and evidence while finance resolves the ledger treatment.
Control replacements and entries outside the regular run
A corrected export must identify whether it replaces the earlier journal in full or supplies only the difference. The reviewer needs both the earlier posting status and the correction's intended effect.
Assume the $48,000 gross run is revised to $48,600. For this separate hypothetical change, approved employee tax withholding rises by $180, net pay by $420, and all other amounts remain unchanged. The full revised journal has $54,600 debits and credits. In this simplified example, the delta journal has a $600 wage debit, $180 tax-payable credit and $420 net-payable credit. In an actual revision, recalculate employer payroll taxes and any wage-based benefit costs; include every changed amount in the full or delta journal.
If the earlier $54,000 journal has not posted, withdraw it and approve one replacement. If it has posted, follow an approved delta or reversal-and-replacement procedure. Posting the full $54,600 without addressing the original would record both versions. Posting a $600 delta after reversing the original would leave most of the run missing.
Inspect the register, interface history and ledger batch status together. “Sent” can mean transmitted, imported, validated or posted depending on the system. Resolve an uncertain status before another attempt. Record the batch IDs that establish what happened.
Manual checks and off-cycle payments need the same population discipline. Identify whether they are included in the regular export, arrive through a separate batch or have already been booked through another process. A check issued outside the provider may appear later in payroll for wage reporting without representing another cash payment.
A void also needs more than a negative line. Determine whether the original wages were reversed, the payment stopped or recovered, the tax result changed, and a replacement issued. Different answers can require different records. Obtain payroll's approved correction result and finance's posting instruction before treating the entire event as canceled.
Noncash benefits and equity events deserve explicit treatment because wage reporting, employee withholding and cash pay can move differently. The journal reviewer should obtain the approved accounting instruction, including any compensation cost already recognized elsewhere. A gross wage addition is not automatically an instruction to debit wage expense again or pay the employee cash.
Compare providers against the records you need
If journal exports or correction histories are driving a provider search, describe those requirements to SelectSoftware Reviews. Ask prospective systems to produce a reviewable journal and show how replacement entries are identified.
Choose the review depth from the change and exposure
Review the full batch's control totals and completeness, then investigate the parts whose treatment or evidence changed. A stable mapping does not require someone to recalculate every paycheck, but it does require proof that the reviewed report covers the batch being approved.
Compare current and prior runs only after adjusting for population and events. A higher total may reflect an extra run, new employees, a bonus or a different earned period. A flat total may conceal offsetting changes. Record the explanation by affected account or population instead of accepting “similar to last month” as the evidence.
Give additional attention to new accounts, manual edits after export, unusual users, entries near period close and items routed outside the normal interface. PCAOB staff guidance discusses both automated and manual journals when addressing fraud risks in audits. That is guidance for auditors under PCAOB standards, not a universal employer checklist or a requirement that every small business perform an audit.
For your operating review, require the preparer to identify what changed and retain the supporting instruction. Where possible, have a suitably authorized person other than the preparer review the entry. A small team can arrange a documented controller or owner review, restricted posting access and review of subsequent changes. Decide the compensating procedure explicitly when duties cannot be fully separated.
Set dollar and percentage investigation triggers around your own account risks and reporting needs. A threshold can prioritize investigation; it does not prove a difference is harmless. An employee underpayment, wrong tax result, unauthorized account or unknown cause needs its relevant correction route regardless of whether the journal's net difference is small.
Measure the procedure with observable records: approvals attached to the correct batch, preventable duplicate attempts, replacements after approval, and exceptions discovered after posting. Do not claim improved accuracy from a checklist's existence. Review actual outcomes and change the weak step when the evidence shows a recurring problem.
Document a hold that someone can clear
A useful hold identifies the batch, failed test, evidence, affected amount or population, responsible person and decision deadline. “Please check payroll” gives the preparer no reliable completion test.
For the misclassified example, the hold could say: “Batch J-431 contains $39,000 wages expense and $13,000 employer payroll-tax expense. Approved reports support $48,000 and $4,000. Regenerate using mapping M-7 and return a ledger preview with unchanged $54,000 totals.” That names the remedy without authorizing a change to employee pay.
Distinguish a posting hold from a payroll-payment hold. A ledger mapping defect does not itself authorize delaying wages or tax payments. Route a suspected pay or tax error to the responsible team immediately, including the applicable deadline and an authorized alternative processing path when needed.
The federal overtime rule generally calls for payment on the regular payday for the period in which the workweek ends, with a limited delay rule when the amount cannot be determined in time. That delay must be no longer than reasonably necessary and cannot extend beyond the next payday after the amount can be computed. Check other applicable wage and state requirements separately, rather than allowing the month-end accounting queue to decide when employees are paid.
A hold on one batch need not stop an independently supported batch if the authorized reviewer confirms they can be separated. Conversely, dividing one unexplained entry into smaller batches does not resolve its missing support.
If a deadline requires an estimate or temporary classification, the controller must approve the accounting basis, amount, affected period, follow-up owner and reversal or clearing instruction. Keep the exception open until the promised evidence arrives. Do not let an informal “post for now” instruction become the permanent record of the decision.
Payroll Journal Posting Review Sheet
Use one sheet for each journal batch or clearly defined group reviewed together. Copy the fields into your close workbook or document and retain links to the actual evidence. Enter a result and reference, not merely a tick beside an unperformed test.
Batch and source
1. Entry identity: Ledger batch ID, journal version, legal entity, ledger and currency: ______.
2. Source coverage: Final run IDs and versions, pay date, earned dates and included off-cycle or manual items: ______.
3. Export authority: Approved register or summary, export time, preparer and mapping version: ______.
4. Prior-entry search: Ledger and interface locations checked, search time, matching IDs and resolved duplicate or uncertain-status results: ______.
Source note: if the coverage or prior posting state is unknown, identify what must be resolved before this batch can be authorized.
Amount and treatment tests
5. Gross-to-net proof: Gross wages ______ minus employee taxes ______ minus employee deductions ______, with separately explained other items ______, equals net pay ______; source reference ______.
6. Journal proof: Debit total ______; credit total ______; difference ______; matching source totals and account-level exceptions ______.
7. Employer costs: Tax and benefit cost sources, amounts, existing invoice or accrual entries checked and treatment approved: ______.
8. Account review: New or changed codes, account numbers, dimensions, signs, suspense balances and supporting approval: ______.
9. Period bridge: Journal date and ledger period, related accrual or reversal IDs, policy and evidence that cost is recognized once: ______.
10. Funding bridge: Bank or provider amount, net pay, taxes, fees and excluded payments; clearing method, settlement evidence and remaining obligations: ______.
Amount note: keep related values in each compact calculation together. A balanced journal or matched bank debit does not substitute for the account and obligation checks.
Authorization and completion
11. Changes and corrections: Full replacement or delta, original batch status, manual changes after export and linked approvals: ______.
12. Review result: Approve this exact batch or hold; specify the failed test, amount or population, remedy and required evidence: ______.
13. Open work: Owner, deadline, escalation contact and any separately authorized temporary treatment: ______.
14. Approval: Reviewer, role, timestamp and exact batch version authorized; any changes requiring renewed review: ______.
15. Posting result: Poster, timestamp, ledger journal ID, actual period, import totals, rejected lines and final status: ______.
16. Follow-through: Settlement or reconciliation owner, remaining evidence due, replacement history and date the open work was resolved: ______.
Completion note: posting approval, successful posting and later settlement are separate results. Complete the posting fields from the ledger response and retain unresolved obligations for follow-through.
Connect the approval to the posted result
The poster should compare the authorized version with the version being released. If they differ, determine whether renewed review is needed under the approved policy before continuing. Preserve an immutable copy or version history so later reviewers can reconstruct the authorization.
After posting, capture the ledger journal ID, actual period, amounts and import result. Check for rejected lines, partial batches and automatic remapping. A successful upload without a posted ledger reference is not evidence that the intended entry reached the books.
Compare the posted account totals with the approved preview. Resolve a difference through a documented correction; do not silently edit the review sheet to match the ledger. Keep the old and new approvals when the posting changed.
Retain the review record with the source reports, mapping, adjustment instructions and posting evidence. IRS employment-tax recordkeeping guidance includes wage-payment details, deposit confirmations and returns, and calls for at least four years after filing the fourth quarter for the year. Some listed credit records require longer retention; other legal requirements and holds may also extend the period.
Apply the organization's retention schedule and access controls across the package. The journal sheet need not repeat Social Security numbers or bank details that are already held in restricted source records. A broken permission link is also a missing piece of practical evidence, so confirm the reviewer and later reconciliation owner can retrieve what their roles require.
Give the completed sheet to the person reconciling payroll liabilities and cash. Their work can then start with identified entries and explicit outstanding items. The journal review ends with a defensible posting record; it does not certify that every downstream payment, return or balance has been completed.
Questions at the posting desk
Can we approve before the provider finishes tax payments?
Yes, where the supported journal correctly recognizes the obligations and the approved accounting method permits it. Record what remains payable or in transit and who will verify settlement. Do not mark a tax as paid solely because the provider collected funding.
Do we need an employee-level journal?
Not always. Use the detail needed for accurate accounts, entities, allocations and later investigation. A summary journal can be reviewable if it traces to complete restricted payroll support. Avoid distributing sensitive employee data merely to make a summary look more detailed.
What if the exported journal has no batch identifier?
Assign a controlled reference in your review process and retain the exact file or immutable version. Record the provider run identifiers, export timestamp and ledger reference after posting. Confirm the system's duplicate-prevention behavior rather than assuming your reference enforces uniqueness.
Should a rounding difference go to suspense?
Only under an approved, supported accounting treatment. Investigate the source and cumulative effect first. A repeat difference can signal a sign, allocation or file-processing problem; a small amount does not establish that rounding caused it. Document the actual cause and correction route.
What should we try when every run needs manual rebuilding?
Take one representative run and one correction through the existing export, import and posting process. Record the exact unsupported accounts, dimensions or version controls and the work required to compensate. Use that evidence to decide whether configuration, process repair or a different integration is appropriate before committing to a provider change.
A next step if you are comparing payroll services
Bring your posting review requirements to an optional SelectSoftware Reviews advisor conversation. Confirm the export, correction and audit evidence in a provider demonstration before choosing.
Explore related payroll resources:
About the author
Ben Scott writes and maintains payroll decision guides for founders and operators. His work focuses on execution realities and how decisions hold up under growth, complexity, and controls and documentation pressure. He works hands-on in HR and leave-management roles that intersect with payroll-adjacent workflows such as benefits coordination, cutovers, and compliance-driven process controls.
