Year-End Payroll Provider Switch: Reconcile YTD and Assign W-2 Filing
Updated: 2 days ago
A new payroll system can show the right year-to-date balance while two providers are preparing to report the same wages. It can also pay the first January run correctly while nobody owns the previous year's W-2s. The provider's start date does not settle either question.
Before a year-end payroll provider switch, assign the reporting work for each employer and tax year, then reconcile the history that the new system will use. Treat loading balances, paying wages, filing wage statements and furnishing employee copies as separate jobs. Each needs an instruction that the receiving party has actually accepted.
This guide is for U.S. employers changing ordinary payroll service providers while continuing the same employment relationship. Its Year-End Cutover Proof Sheet connects the filing assignment to an employee-level YTD bridge. The examples are fictional operating illustrations. An acquisition, employer-identity change or different third-party payer arrangement needs its own tax review before these operating steps are applied.
Table of contents
Who will file the year that is ending?
Write the answer for the specific employer EIN, tax year and employee population. Identify who prepares the forms, who approves their contents, who transmits them and who furnishes employee copies. The person coordinating implementation should obtain an acknowledged assignment from both providers, rather than treating a sales promise or termination notice as a filing instruction.
IRS guidance describes ordinary payroll service providers preparing and filing W-2s using the employer's EIN. Changing that service does not, by itself, change the employer named on the form. The employer also retains responsibility for correct and timely W-2 furnishing and filing when using a reporting agent or payroll service provider. Record the arrangement being used before deciding which responsibilities can be delegated.
Other arrangements can differ. IRS outsourcing guidance distinguishes payroll service providers, reporting agents, section 3504 agents and certified professional employer organizations. A purchase or sale of a business can introduce successor and predecessor rules. If the cutover includes one of those changes, have the responsible tax adviser establish the reporting treatment. A routine software-migration checklist cannot establish it.
Ask the departing provider whether ending payroll processing also ends year-end preparation, employee access or correction support. Obtain the answer with dates, scope and charges. Ask the incoming provider whether its service includes the closing year's forms, which historical fields it requires and what happens if the employer misses its intake deadline. An active account is not proof that a particular form job is included.
The expected deliverable is an agreed reporting map. For example, the departing provider may remain responsible for 2026 reporting while the new provider starts 2027 payroll. Another approved arrangement may give the incoming provider complete 2026 reporting after a validated historical load. State the selected arrangement and the other provider's corresponding instruction. Do not leave both preparing an overlapping annual wage submission by default.
Keep this assignment beside the wider year-end close plan. The switch adds a handoff between systems; it does not replace the employer's reconciliation, employee-copy and filing obligations. Name an internal owner who can obtain missing evidence even after the implementation consultant's work ends.
Use pay dates to separate the two reporting years
For ordinary wage reporting, Form W-2 follows wages paid during the calendar year. December work paid in January generally belongs on the following year's W-2. The IRS instructions illustrate this boundary explicitly. Build the migration population from the relevant payment records, rather than assigning wages to a year solely from the pay-period end date or accounting expense month.
List the last intended payment in the departing system and the first intended payment in the receiving system. Include off-cycle payments, reversals and replacement payments that can cross that boundary. Give every item a stable reference. A calendar showing only the regular biweekly dates can omit the final bonus or a manual check that changes the closing-year totals.
Separate two questions on the handoff: which system processes the payment, and which reporting job includes it. A January launch can leave the old provider doing December reporting. A December launch can require the new provider to report earlier payments that it did not disburse. Neither situation is resolved merely by renaming the implementation date as the year-end cutoff.
For 2026 Forms W-2, the general deadline to file with SSA and furnish employee copies is February 1, 2027. Put the year-specific date and any applicable exception or relief into the calendar. Set earlier internal dates for obtaining exports, reviewing drafts and resolving discrepancies. A provider's processing cutoff and the statutory deadline serve different purposes.
Choose the switch window after checking those actual dates with both providers. If historical data will arrive after the incoming provider's agreed reporting cutoff, the plan needs another supported filing arrangement or a different launch date. Do not convert an unresolved timetable into permission to miss employee pay or reporting requirements.
Build a field-by-field bridge from the last trusted export
Freeze a named baseline after confirming which completed payments it includes. Preserve the report, export time, tax year, employer, population and last included transaction. Obtain employee detail and control totals. A grand total without employee identifiers or field definitions cannot show whether the import assigned the right balance to the right person.
Define historical field mapping before uploading. Distinguish total compensation from federal taxable wages, Social Security wages, Medicare wages and withholding. Keep deductions, benefit amounts, reporting codes and state or local fields separately identified where relevant. Similar column labels are not enough to establish equivalent treatment. Ask what each destination field feeds: a paycheck, a tax calculation, a form box or a display-only history screen.
A useful bridge starts with the verified closing balance from the old provider, adds authorized changes not already included, and adds actual new-provider payments for that same tax year. Compare the result with the proposed reporting output. Track a historical load as the representation of earlier activity, so the same amount is not counted again as both an opening balance and a new payment.
Consider a fictional employee with $42,000 of verified federal taxable wages in the departing provider's final export. The new provider processes another $3,000 of federal taxable wages in the same year. There are no other adjustments in this illustration. The expected annual amount for that field is $45,000. Importing the $42,000 makes it available for reporting; it does not mean the employee should receive another $42,000.
If the old provider reports $42,000 and the new provider also reports the complete $45,000 as overlapping wage data, the two amounts total $87,000. The verified payments support $45,000. That is a filing-coverage problem even if the new provider's own annual preview looks correct. Compare the proposed submissions together under the reporting assignment, rather than approving each provider's forms independently.
The IRS permits multiple W-2s in some situations but says not to report the same federal tax data to SSA on more than one Copy A. The control objective is complete, nonduplicated reporting under the applicable rules, not a promise that every employee must always receive one physical sheet. Determine what each form actually contains before labeling it a duplicate.
Perform this bridge for each relevant reporting field. An exact federal wage total does not prove correct withholding, coded benefits or state allocation. Also compare the population: active employees, people who left earlier in the year, rehires and people with a payment but no current job record. Offset errors between employees can leave the grand total unchanged.
Reconcile employee detail to the aggregate control totals, then connect the payroll-to-ledger tie-out and tax reporting reconciliation. Keep valid differences explained by their actual cause. The IRS instructions call for reconciling W-3 amounts with employment tax returns and retaining explanations for valid discrepancies. A note saying rounding or timing without supporting transactions is not an explanation.
The bridge represents one fictional reporting field. Other wage, withholding and benefit fields require their own reconciliation. Imported history is not another payment.
Year-End Cutover Proof Sheet
Use this sheet for the reporting assignment and its supporting balance checks. Complete one filing-job record for each employer, tax year and reporting scope. Add employee bridge records for the tested population and every unresolved difference. In a larger migration, keep the fields in a controlled register with access to restricted evidence. Do not circulate full Social Security numbers in a general project document.
Record the filing job
Employer and reporting year: Legal employer, verified EIN reference, tax year, employee population and relevant reporting jurisdictions. Identify whether this is an ordinary provider change or a different arrangement requiring tax review. Record the person who approved that classification and where the decision can be retrieved.
Included payment boundary: Last payment and transaction version included in the old baseline, first payment processed in the new system, and the rule for items arriving between those events. Identify any off-cycle, reversal or manual-payment list. State separately which year's wage reporting includes each boundary payment.
Assigned preparation and transmission: Provider or internal team preparing the forms, authorized transmitter, internal approver and employee-copy owner. Include the acknowledged scope from the selected provider. Record the other provider's instruction for that same scope, with confirmation that an overlapping submission will not proceed independently.
Historical data and form source: Exact baseline file, export time, employee count, field map, import batch and draft-form version. State whether the incoming provider is using historical balances for the closing year's reporting, the new year's payroll calculations, reference access or another approved purpose. Those uses should not be assumed interchangeable.
Dates and missing evidence: Statutory deadline checked for the reporting year, provider intake cutoff, internal draft-review date and escalation owner. List any missing export, unconfirmed cancellation or rejected record with a deadline and a supported alternative. An unchecked box cannot silently become an instruction to file estimated data.
Delivery and closure proof: Approved final population, form control totals, filing reference, processing result, employee-copy evidence and correction contact. Record the next person who checks a pending result. Keep account-access and record-retrieval arrangements that remain usable after the old service agreement ends.
Reproduce an employee balance
Identity and source position: Restricted employee reference, employer, tax year, reporting field and baseline amount. Identify the exact old-provider record supporting the amount. Match the employee across systems through an approved identifier crosswalk, rather than assuming that two matching names represent the same person.
Changes after the baseline: Authorized additions, reversals or corrections, with transaction references and confirmation that they are not already included. State whether a newer export replaces the baseline or supplies incremental activity. Retain both versions with their status, so an operator cannot mistake a cumulative replacement for another set of wages.
New-period activity: Actual payments processed by the new provider for that same reporting year, with the field-level amounts and run references. Keep imported history outside this activity subtotal. For a January launch, distinguish previous-year reference history from current-year wage counters and current-year payment activity.
Expected and proposed result: Baseline plus authorized changes plus new-period activity, compared with the amount allocated to the relevant draft form or forms. Show the arithmetic and difference. Identify whether the discrepancy concerns employee identity, population, field definition, year, duplication, omission or a source calculation requiring separate correction.
Resolution and reviewer: Approved fix, affected import or form version, person making the change and a second person's verification. Record the downstream outputs that need another check. If a difference is accepted as valid, retain the specific explanation and the responsible reviewer's decision rather than deleting it from the register.
Employee and filing follow-through: Which draft or employee copy changed, whether anything was already furnished or filed, and the person assigned to the applicable correction route. Record the actual final evidence when available. A bridge can be approved for preparation while filing remains pending; give those two events separate statuses.
For the $42,000 and $3,000 example, the bridge's expected federal taxable wage field is $45,000. Its filing-job record must also show how the proposed submission covers those wages once. Passing the arithmetic while leaving both providers authorized to submit overlapping data is not a completed proof sheet. Likewise, a clear filing assignment cannot compensate for an unexplained employee difference.
Test a January launch without closing December reporting
Suppose a fictional employer starts its new system with a January 8, 2027 payday for work performed in late December. The approved arrangement leaves 2026 W-2 preparation with the departing provider. The new system needs employee records and ongoing payroll instructions for January, but its 2027 wage calculation should not treat the old system's 2026 wages as wages paid in 2027.
Test the two jobs separately. In the new payroll, inspect the first payment's year, earnings, deductions, tax treatment and reporting counters. In the old reporting job, obtain a closing-year employee population and draft-form control totals. Include a former employee paid during 2026 who has no January payment. A successful January payroll says nothing about whether that person's 2026 form is included.
Where prior-year payroll history is kept in the new service, ask for the exact storage and reporting behavior. A history screen, an opening current-year balance and a form-producing historical load can have different effects. Require a demonstration with fictional records. Retain the expected results and the observed outputs from the employer's actual validation; this guide does not claim to have tested a provider.
Do not reset or carry every balance merely because the calendar changes. Wage counters, leave balances, loan balances and continuing deduction obligations are different data sets. Have the relevant owner establish what transfers and how it affects January. Check the resulting instruction against the approved arrangement instead of applying a single import setting to everything.
Keep the departing provider's reporting contact active through draft approval, filing follow-up and agreed correction support. Define how a former employee obtains a copy after portal access changes. The project needs a retrieval route that an internal payroll owner can use, not only an implementation consultant's temporary login.
A January payroll launch and the previous year’s wage reporting are separate assignments. This ordinary-wage example follows payment dates, with special arrangements reviewed separately.
Give late changes one owner and a route back to the filer
A baseline is a version of the facts, not a prohibition on fixing an error. Establish late-change approval for a payment discovered after the export, a corrected employee identifier or an approved taxable adjustment. Identify who determines the underlying treatment, who revises the source and who tells the assigned filer. Keep the affected work in an exception queue until the outputs agree.
In a third fictional situation, the old provider confirms that a $500 wage payment made during the closing year was omitted from the $42,000 baseline. The approved source position is now $42,500. With the same $3,000 of new-provider wages and no other wage changes, the expected annual field becomes $45,500. Other affected reporting fields must be checked against the actual payment record; the wage amount alone does not determine withholding.
If a revised export contains the complete $42,500, it replaces the earlier $42,000 position for this purpose. Loading both as incremental wages would double count history. Preserve the earlier export as superseded evidence, identify the replacement batch and compare the revised preview with the approved $45,500 result. Confirm that correcting history did not issue another employee payment or create an unintended bank instruction.
Send the accepted change to the actual filing owner. Updating the incoming provider's display does not correct a draft still being prepared by the departing provider. Conversely, correcting the old source does not prove that a previously imported balance refreshed automatically. Obtain the downstream acknowledgment and review the resulting version.
If forms were already furnished or filed, determine the applicable W-2c correction process from the current instructions and actual submission status. Quarterly tax corrections may also require their own analysis. Do not treat a replacement annual file as a universal correction method or assume a corrected employee PDF changes an agency submission. Preserve the original filing evidence while the responsible tax owner resolves the route.
A completed payroll run does not prove completed filing
Review the actual draft forms using the approved population and bridges. Confirm the employer identity, reporting year, employee identifiers and relevant boxes. Have a reviewer trace selected employees from original payment records through the imported balances and final draft. Include unusual populations and every material unresolved category, rather than selecting only people with simple current salaries.
Require a list of what will be transmitted and what will be furnished. Obtain confirmation of the other provider's instructions before release. A contract saying year-end included may not identify the specific employee population or whether a previous automatic filing setting remains active. Make the accepted filing scope visible to the person approving the release decision.
After transmission, retain the filing reference and check the processing outcome. SSA's available electronic-filing handbook distinguishes Received, In Process, Complete, Return and other statuses. A receipt proves receipt; it does not establish every later outcome. Ask the authorized filer to supply the relevant submission and employer-report results, with an owner for returned or unresolved items.
The handbook also warns against changing completed reports while resubmitting returned reports because earnings can be added to data already filed under the EIN. Use the applicable SSA instructions and the actual status when resolving a returned file. Do not send another complete annual wage file simply because a provider dashboard still shows a warning.
Verify employee-copy delivery as a separate step. Keep evidence of the approved method, completion and handling of undeliverable or inaccessible copies. Give employees one clear support route and an explanation of which provider supplies which year. Investigate overlapping amounts before telling an employee to disregard a form or combine amounts without review.
Preserved payroll records must remain available after the service ends. IRS employment-tax recordkeeping guidance generally requires records for at least four years, with longer periods for some specified matters. Apply the organization's retention and legal-hold decisions to the full evidence set. Exporting a PDF form without the supporting payment detail can make a later discrepancy much harder to resolve.
Approve the switch with an exit plan for missing evidence
Choose a cutover window that leaves enough time for the actual data handoff, draft review and supported filing arrangement. Require provider demonstrations of historical loads, a year boundary, a former employee and a late source correction. Confirm the scope, intake dates, fees, retrieval access and correction responsibilities in the agreement. A feature named year-end support is not a complete operating plan.
If a required export or reporting acknowledgment is missing, state the consequence and the supported alternative. That may mean retaining the departing provider for the closing year's forms, changing the implementation window or assigning a qualified internal or external tax team. Keep employee pay and statutory obligations with their responsible owners while deciding the migration sequence.
Judge the handoff by whether another reviewer can reproduce the employee balances and identify the accepted reporting job. Close the implementation work only after assigning any pending filing result and correction support to an ongoing owner. The enduring control is a specific connection between wages already paid, the balances carried into the new system and the forms that report them once.
Explore the Decision Guides library.
See the Payroll Switching & Migration hub.
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.
