Unreconciled Payroll Items: Resolve the Difference and Prove Closure
Updated: 2 days ago
A payroll liability comparison starts with a $480 difference. The preparer finds a missing $300 entry and posts the approved correction. The remaining $180 still needs an explanation. Calling the case resolved because the largest part was fixed would remove the very question the next reviewer needs to see.
An unreconciled payroll item is a defined difference between records that has not yet been supported, corrected or matched to its expected outcome. Keep its identity, original amount and discovery date while recording what has actually been resolved. The item can change explanation, owner or accounting period without losing that history.
Use this SOP for U.S. payroll and finance teams handling open payroll-to-ledger, liability, payment and deduction comparisons. It provides an Open Difference Resolution Card, three fictional cases and two visual checks. It does not select a tax correction, authorize recovery from an employee or establish a universal aging deadline. Those decisions require the appropriate facts, authority and current rules.
Contents
Define the comparison before naming the difference
Write the comparison as a statement another person can reproduce. Identify the employer entity, obligation or account, payroll run and version, covered dates, currency and two record sources. State what agreement is expected between them. “Payroll is out by $480” is insufficient if the reviewer cannot tell which totals produced it.
For example, compare a specific payroll liability from the final run with the corresponding posted ledger movement. Do not compare an employee net-pay total with a provider withdrawal that also contains taxes, fees or other amounts. A legitimate difference in scope needs a bridge between the totals, rather than a journal designed to force them to match.
Record both source amounts and a consistent sign convention. You might use expected amount minus observed amount for that comparison. State whether the amount represents wages, employer cost, a deduction, a liability or cash. A positive $480 is meaningful only after the reader knows which side is short and what that side represents.
Save the actual source versions or reproducible references. A later payroll rerun can change an exported total without changing the bank or ledger record already used. Preserve the original comparison and identify the replacement version separately. Otherwise, an apparently disappearing difference may be a changed input rather than a resolved item.
Check the scope before opening multiple cases. Two people may have reported the same missing ledger batch from different screens. Link their observations to one controlled item when they describe the same difference. Conversely, one report total can contain several unrelated questions that need separate evidence and owners.
A zero account balance does not establish that each underlying transaction is explained. Review the individual movements and the obligations they represent before treating the balance as complete.
Classify the explanation the evidence supports
Use a short classification to direct the next task. Keep it provisional until the evidence supports the explanation. The following categories describe operating work, not legal conclusions or an assertion that a person has done something wrong.
Expected event still pending. The records concern the same population and amount, and a specific event is expected to complete the comparison. Name that event, its expected date and the evidence that will show it happened. A scheduled payment file can support an expectation; it does not establish receipt.
Missing or inaccessible evidence. The team cannot yet reproduce the result because an approved source, transaction detail or confirmation is absent. Identify exactly what is missing and who can supply it. “Awaiting support” should lead to a document request, not a generic request for someone to explain payroll.
Incorrect or duplicate record. A calculation, posting, allocation or imported transaction appears inconsistent with its approved source. Preserve the original record and describe the proposed correction. An accounting correction and an employee-pay correction have different approval and verification paths.
Unmatched settlement or allocation. Money or a credit is visible, but its destination, period, participant or liability has not been established. Keep the settlement reference and determine where it belongs. Do not allocate a convenient amount to the oldest open item merely because the numbers fit.
Obligation or treatment needs specialist review. The difference raises an unresolved wage, tax, benefit, employment or accounting question. State the question and the reviewer needed. Continue safe fact gathering while the decision is obtained; an unsupported assumption should not become the default treatment.
Record a reason when the classification changes. A bank return may turn a pending settlement into a payment exception. Evidence of a duplicate journal may turn an unexplained balance into a defined posting correction. Preserve the original discovery date through both changes.
Show what remains without hiding what happened
Keep three amounts visible: the original identified difference, the portions supported as resolved and the amount still unresolved. Attach the evidence to each resolved portion. This gives the next reviewer a way to verify progress without reconstructing every earlier spreadsheet.
For a simple item with no newly discovered components, the remaining difference equals the original difference less the portions verified as resolved. Use signed amounts consistently. If the original item was $480 and a supported correction resolves $300, the remainder is $180. Keep the case partly resolved until the rest has an accepted explanation or correction.
A proposed entry is not a resolved portion. Wait until the authorized change reaches the intended record and the reviewer verifies its effect. Similarly, a requested payment or a provider's promise of a credit should stay in the action history until the required outcome is supported.
Separate newly discovered amounts from progress on the original item. If a later review finds another $20 error, identify whether it belongs to the same original transaction population. Add a dated component or open a linked item, with its own origin and amount. Do not silently rewrite the original $480 as $500 and make the earlier reconciliation impossible to follow.
Preserve gross differences when unrelated amounts offset. An unexplained $900 tax comparison and an unexplained negative $900 benefit comparison produce a net zero, but they still contain two unresolved questions. Their destinations, approvals and possible consequences differ. Track each through its own evidence.
Illustration: adding unrelated differences to zero does not explain either comparison. Resolve each underlying item against its own records.
An approved reclassification can resolve a comparison when it puts an amount in the correct account and the reviewer verifies that treatment. It does not prove a payment, filing or employee obligation is complete. Keep any surviving task connected to the resolution record instead of erasing it behind an accounting entry.
Age the item against its expected event
Track time since discovery and time past the expected event separately. The first shows how long the difference has been known. The second shows whether the current explanation is still behaving as expected. A large new item and a small item repeatedly missing its clearing date can demand different responses.
Choose and state the counting convention. A calendar-day age includes weekends; a business-day commitment depends on the relevant working calendar. Use the correct time zone and cutoff when those affect the task. An internal review date is not a substitute for a wage, tax, plan or contractual deadline.
In a calendar-day illustration, an item discovered on day 0 has an expected clearing event on day 2. At the day 7 review, it has been open for seven days and is five days past that expectation. Both figures remain useful. The next payroll's arrival does not turn the original discovery into a new day 0.
Calendar-day illustration. Keep the original discovery date and the original expected event when a later commitment is added.
Changing the owner, moving the item to next month's tab or replacing a provider ticket number should not restart its age. If the original expectation was wrong, retain it and record why it was replaced. Show the revised date alongside the earlier missed commitment so the reviewer can distinguish a justified change from repeated postponement.
Use age to ask a question, not to declare a result automatically. Which expected event failed? Does the evidence still support the timing explanation? Has the consequence changed? Who can authorize the next step? Those questions make an aging review useful without inventing one deadline that supposedly applies to every payroll difference.
Give the next task an acceptance test
Assign one person to coordinate each item, even when several functions must contribute. That person keeps the comparison, requests, decisions and next review connected. Task responsibility can change as work moves from payroll to finance, systems, a bank or a provider.
Write the next action as an observable task. “Obtain the posted journal batch for run P17, including its account detail” is more useful than “finance to investigate.” Include a due date, the expected evidence and a named route if the task cannot be completed. A provider ticket belongs in that trail; it does not replace the employer's coordinating owner.
Specify the acceptance test before making the change. A missing journal correction needs proof that the authorized entry was posted once, to the intended entity and period, and that the comparison now agrees. A payment question needs evidence appropriate to the actual payment outcome. A spreadsheet total changing is not an adequate test for either.
Keep preparation and acceptance distinguishable. A small team may have one person gathering records and proposing entries, but a designated reviewer should assess consequential decisions within the company's approval structure. If independent review is limited, document the limitation and arrange a proportionate second check rather than describing an approval that did not occur.
Federal tax responsibility also depends on the actual outsourcing arrangement. The IRS explains that an ordinary payroll service provider's default does not remove the employer's federal deposit and filing responsibilities; other third-party arrangements can have different liability treatment. Identify the arrangement before assuming that a provider's involvement transfers the obligation.
Escalate when the consequence or commitment changes
Review urgency as soon as the item is identified. Potentially unpaid employees, an uncertain tax deposit, an unexplained benefit deduction or suspected unauthorized activity may require action before the next ordinary close meeting. The amount and age help describe the case; they do not determine the applicable payment or reporting rule.
Give the decision maker the affected population, supported amount, uncertainty, deadline requiring review and action already taken. If the exact amount is not known, state the basis for the estimate and who will refine it. Avoid presenting an unverified worst-case total as a confirmed loss.
Use missed commitments as an escalation trigger. When the named event passes without its expected evidence, ask the owner to reclassify or support the explanation and set a specific next action. Escalate a missing response to the role that can obtain the record or make the decision. Extending a ticket's date alone does not satisfy that review.
For employee retirement contributions, use the plan's actual deposit requirements and appropriate specialist advice. The IRS's 401(k) fix-it guidance explains that elective deferrals must be deposited as soon as the employer can and that delayed deposits may require correction. A tracker label such as “under 30 days” does not provide permission to wait.
Differentiate operating priority from authority to leave an amount uncorrected. A small internal allocation question may receive a different review from an employee payment concern. Define who may approve a correction, monitoring or temporary accounting treatment and record the reason. Do not let a general dollar threshold silently decide every category.
A suspicious record needs an appropriate incident or fraud-review route, with restricted access to sensitive details. Keep a neutral description in the open-item card. The ordinary reconciliation owner should not delete source history, accuse an employee or improvise a recovery while trying to make the account balance.
Follow three differences to different outcomes
The following fictional cases illustrate the method. The amounts are operating examples, not tax calculations, required tolerances or deadlines.
A missing entry resolves only part of the comparison
The final payroll output supports a $12,480 movement in a particular liability. The posted ledger contains $12,000 for the same entity, run and period. Finance reproduces the positive $480 difference using retained versions of both reports.
The team identifies a $300 item in a separately approved payroll adjustment that did not reach the ledger. After review, the missing entry is posted once and its batch reference retained. The ledger movement becomes $12,300, leaving $180 unresolved. The original payroll output remains $12,480.
The coordinating owner records $300 as verified resolution and retains $180 as open. An explanation for the remainder is still being obtained from the payroll detail. If it concerns a tax, wage or benefit obligation, the appropriate deadline and responsible specialist must also be identified. No one assumes that the remaining amount is a rounding difference.
At the next review, the item appears as partly resolved with its original discovery date, the verified $300 component and a dated action for the $180. That is useful progress. Replacing the original card with a new $180 item would hide how the team reached that position unless both records remained explicitly linked.
A provider withdrawal does not establish the tax destination
The employer's bank shows a withdrawal matching the provider's funding request. The payroll liability remains open because the reviewer has not obtained evidence connecting the tax component to the correct employer account and period.
The next task is to obtain and check deposit detail, not to post a second payment merely because the liability is still visible. Identify what the provider withdrew, what portion represented the tax and which tax-payment record supports the proposed clearing. Coordinate any suspected missed deposit promptly with the responsible tax reviewer.
If the payroll tax return itself was wrong, a ledger entry does not correct that filed return. The current Form 941-X instructions describe correction of a previously filed Form 941 and distinguish the available processes and conditions. Have the tax reviewer establish the proper filing and payment response, while the card tracks that response and its evidence.
The item can be split into supported components if only some deposits are established. Keep the unverified portion open and retain the link between employer funding, the reported liability and the destination evidence. Do not send a replacement deposit or amendment solely to obtain a cleaner tracker.
Two offsetting differences need separate answers
A tax comparison has an unexplained positive $900 and a benefit comparison an unexplained negative $900. The consolidated spreadsheet shows zero. The preparer has not established that the amounts involve the same transactions, the same recipient or an authorized offset.
The reviewer keeps two items open. One owner obtains tax detail; another obtains the benefit allocation and settlement records. Each item has its own acceptance test and urgency assessment. The net zero remains a mathematical observation, not a disposition.
If later evidence proves the amounts were two sides of one misclassified entry, finance can propose a supported correction and cross-reference both cards. Verification must establish that the corrected accounts and any remaining obligations are right. Matching numbers alone do not establish that explanation.
Copy an Open Difference Resolution Card
Create one card for a defined comparison. Use restricted source references rather than bank account numbers, Social Security numbers or an unrestricted employee export. Repeat amount-component rows when part of an item is resolved; keep dated history instead of overwriting earlier decisions.
Identify the comparison
Reference and boundary: Item ID, employer entity, account or obligation, currency, payroll run/version and covered dates: ____________________.
Expected record: Source name/version, source amount and evidence reference: ____________________.
Observed record: Source name/version, observed amount and evidence reference: ____________________.
Original difference: Signed amount, sign convention and the exact comparison performed: ____________________.
Discovery: First identified date, person identifying it and any linked earlier observation: ____________________.
Explain the remaining amount
Classification: Current explanation, evidence supporting it and unresolved question: ____________________.
Verified resolution: Amount component, completed action, evidence and verification date; repeat for each portion: ____________________.
Remaining difference: Signed unresolved amount and its relationship to the original difference and verified portions: ____________________.
Expected event: Event that should clear or explain the remainder, original expected date and required confirmation: ____________________.
Age and missed expectation: Days since discovery, counting convention, days past the expected event and any revised commitment: ____________________.
Act and check
Consequence and deadline: Affected people or obligations, applicable deadline requiring review and decision owner: ____________________.
Next task: Specific action, responsible person, due date and escalation route: ____________________.
Acceptance test: What the verifier will compare and which result permits this task to finish: ____________________.
Correction and handoff: Authorized transaction or filing references, provider/bank case IDs and linked work still outstanding: ____________________.
Reviewer: Person accepting the evidence, review date and any independence limitation: ____________________.
Record the disposition
Current decision: Open, waiting for a dated event, correction in progress, partly resolved or closed with evidence; reason and approver: ____________________.
Resolution support: Final explanation, accepted evidence and any separate obligation that remains tracked elsewhere: ____________________.
Retained record: Restricted storage reference, record category, retention owner and access arrangement: ____________________.
Closing a card confirms the stated comparison has been resolved with accepted evidence. If a related payment, filing or other obligation survives, identify it explicitly and keep an active linked record. A transfer to another owner should not make an unverified obligation disappear.
Filled card for the partly resolved $480 item
Comparison: Item P17-L1; one entity and liability account; final run P17-v2 shows $12,480 against the original posted $12,000.
Movement: Original difference +$480; verified missing-entry correction +$300; current ledger movement $12,300; remainder +$180.
Time: Identified on day 0, original clearing expectation day 2, reviewed day 7; seven calendar days open and five past expectation.
Explanation: The $300 has a verified posting batch. The $180 is not yet explained; the original timing label is being reconsidered.
Action: Payroll owner to obtain the run's detailed liability breakdown by the stated next review; finance coordinates any tax or benefit deadline assessment.
Test: Reviewer will match the remaining $180 to an authorized source or approved correction and verify the resulting liability comparison.
Disposition: Partly resolved; $180 remains open. Retain the original sources, the $300 posting and the new evidence request under the same item.
This filled card illustrates an unfinished case. Replace its generic owner and next-review wording with named people and actual dates when using the template. The day counts describe calendar-day aging, not a recommended wait before addressing an obligation.
Close the item against evidence from the affected records
Ask the verifier to reproduce the final comparison. Show which source was corrected, which difference was explained and where the accepted outcome appears. Record the actual evidence reference and acceptance date. “Discussed with provider” is action history unless the discussion supplied evidence sufficient for the stated conclusion.
For a corrected journal, retain the authorization, posted entry and before-and-after comparison. For a supported timing difference, retain the later event's confirmation and the match to the original item. For an incorrectly scoped comparison, preserve the bridge that explains why the original totals were not comparable and obtain approval for the revised method.
For tax evidence, the IRS recordkeeping page specifically lists deposit dates and amounts, EFTPS acknowledgment numbers, copies of returns and confirmation numbers among the records to keep. Select evidence that answers the actual question. An acknowledgment for one period or employer does not resolve another period's open item.
Do not require one universal document for every outcome. A settlement, a participant credit, a posted correction and a return acknowledgment establish different facts. Identify which facts the card needs and whether the evidence has limits. If the evidence proves only part of the conclusion, preserve the unresolved portion.
Retain the reviewer's decision when a completed comparison has linked work elsewhere. For example, the accounting correction may be complete while a tax correction is still in progress. Show both states in the close support. Use “accounting comparison resolved; filing correction pending in case T4” instead of an unqualified label that invites the next reader to assume everything is finished.
Carry the item through close and provider changes
Roll unresolved items forward with their original IDs, amounts, discovery dates and evidence history. At each review, reconcile the opening list, newly identified items, verified resolutions and closing list. Distinguish a change in the open amount from removal of the whole item.
Keep a snapshot of the reviewed population and the decisions made for that close. Later discoveries should create a dated revision or linked observation. Changing last month's list to match today's knowledge would make it difficult to establish what the controller actually knew when the close was accepted.
When providers or accounting systems change, assign each surviving item to a named party and test access to its source records. Identify whether the old or new provider will supply a correction, deposit detail or historical report. Keep commercial exit dates separate from the completion of those obligations.
Do not let the new system's opening balance become the only evidence for an old difference. Retain the supported starting position, the unresolved components and the route to the old records. Otherwise, a migration can make an aged question harder to investigate while making its age appear to disappear.
Include unresolved items in the controller's close support at the right level of detail. The working card can remain restricted while the summary identifies the amount, consequence, accepted temporary treatment and outstanding decision. A completed close checklist should not obscure an unfinished payroll question.
Retain the proof and use recurrence to improve the process
Apply the retention schedule for the underlying record types, including any longer claim, investigation or preservation requirement. Closing the operating item is not a deletion event. Keep the original sources, accepted changes and final comparison connected so a later reviewer can understand the outcome.
The IRS employment-tax recordkeeping guidance includes wage and payment details, deposits and returns, and specifies different retention treatment for some credit-related records. Use that current guidance alongside the employer's other applicable retention duties. A single aging report's disposal date cannot determine the life of every record attached to it.
Review patterns after the immediate items have owners. Count repeated causes, missed expectations, items reopened after premature closure and resolution portions awaiting verification. Compare those measures with the work performed and the affected payroll population. A lower outstanding dollar total can reflect an offset or transfer instead of a better process.
Change one upstream control when the evidence supports it. Duplicate imports may need a batch-identity check. Missing detail may require a report-access or provider-support change. Late approvals may require an input cutoff decision. Specify the changed step, its owner and the next payroll on which it will be checked.
For the first use of this SOP, select a real carried-forward item and complete its comparison, remaining amount and acceptance test. Have the reviewer attempt to reproduce those three points from the retained evidence. Any missing source or undefined responsibility becomes a specific next task, while the original difference remains visible.
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.
