Leaving a Payroll Provider: Secure the Exit Before You Cancel
Updated: 5 days ago
Leaving a payroll provider requires agreement on what stops, what continues and what the employer will still be able to retrieve. Before sending an instruction that ends service, identify the applicable notice process, the last payroll the provider will handle, the remaining work it has accepted and the records your organization will hold independently.
Treat cancellation as a set of service decisions. The subscription, payroll processing, tax support, employee portal and historical archive may have different end conditions. A replacement provider's successful first payment does not establish that those arrangements have been settled.
U.S. payroll owners, HR leaders and finance managers can use this guide after they have decided to leave, or while establishing the conditions under which leaving is possible. The Payroll Provider Exit Docket below helps organize the decision before anyone closes access. Contract interpretation, disputed charges and jurisdiction-specific obligations need the appropriate legal or tax adviser; the operating controls here do not create cancellation rights.
Planning the replacement as well as the exit?
Use the free advisor conversation at SelectSoftware Reviews to discuss providers against your exit requirements. Ask each candidate how it returns historical records and supports work that remains after its service ends.
Contents
Which contract and services will the notice end?
Find the signed order, service agreement, renewals, amendments and applicable service schedules. Identify the customer legal entity and the party supplying each service. An account branded with a payroll company's name may be purchased through an accountant, reseller or another service organization. Confirm who can receive an effective instruction and who can approve a change to the agreement.
Build a short service inventory from actual invoices and use, rather than assuming the payroll subscription is the entire relationship. Include payroll calculation and payment, tax deposits and returns, timekeeping, benefits administration, carrier files, retirement contributions, accounting exports and historical access where applicable. Give each item its agreement reference, supplier and internal owner.
Then describe the intended outcome in ordinary language. For example: end new payroll processing after the December 18 check date, obtain the historical records, and retain only the specifically agreed work for the closing year. That description is a request for confirmation. It becomes an operating instruction only after the affected parties have acknowledged the actual scope and dates.
Distinguish a commercial decision to leave from a dispute about performance. Preserve unresolved cases and the relevant commitments before cancellation. If a party believes a contractual breach permits a particular exit route, have counsel assess the provision, evidence and required process. A missed support response does not, by itself, establish a universal right to cancel without charges.
This preparation also reveals dependencies that need separate arrangements. Ending a payroll integration might affect the way a retirement file reaches its recipient while leaving the retirement plan itself in place. Ask the responsible plan, benefit or service owner what must change. Do not use a payroll cancellation instruction as a substitute for confirming the status of those other relationships.
The notice clause sets the first deadline
Write down the provisions that govern notice, renewal, minimum terms and early termination. Record the permitted delivery method, recipient, information required and any rule about when notice is received or effective. Distinguish a deadline to prevent renewal from the date service ends. Have procurement or counsel resolve unclear wording before an operator calculates a deadline from it.
For each important date, keep the source beside the interpretation. A useful entry says which agreement version and section were reviewed, what date the reviewer derived, who checked it and what remains uncertain. “Thirty days” copied into a spreadsheet without its context cannot tell a successor whether calendar days, a billing period or another condition was intended.
Send a proposed service schedule with the notice when the approved process permits it. Ask the provider to confirm receipt, the resulting service-end date, any separate processing cutoff and the treatment of remaining services. Keep both the sent instruction and the acknowledgement in the restricted exit file. A ticket marked received is evidence of receipt; inspect the response for what the provider actually agreed to do.
If notice must be sent before the migration can be fully tested, assign that uncertainty explicitly. Ask whether notice can be withdrawn, dates amended or a limited extension agreed, and on what terms. Do not describe an unconfirmed option as a fallback. The migration owner needs to know when continuation would require a fresh commercial agreement or a different supported payroll route.
Avoid using account closure as a negotiating tactic during a live payroll problem. First establish whether employees' payments, funding or required filings are at risk and obtain a supported response. Preserve the commercial dispute separately. An exit deadline cannot make an unfinished payroll obligation disappear.
Four dates belong on the exit schedule
The exit schedule should answer four different questions: when an effective notice is due, which payroll is the last one to be processed, how long agreed follow-up services remain available, and when each form of account access ends. Add dates for billing and data delivery when they differ. Label a date as proposed, acknowledged or completed so a plan cannot be mistaken for an achieved result.
For the last old-provider run, name the employer, pay date, payment population and any separate off-cycle activity. Identify the processing and funding cutoffs that apply to that run. Ask what happens to a correction discovered after it: can the provider process it, will the new provider handle it, or is another authorized route required? The answer needs an owner and an agreed channel, not an assumption that the old account can be reactivated.
For residual services, describe the actual work. “Tax support continues” is too broad to establish who will prepare a particular return, handle a rejected transmission, answer a notice or make a later amendment. Separate those services and specify their intake deadlines, expected outputs, charges and escalation contacts. The purpose is to prevent work from falling between providers, rather than to recreate the entire tax review inside the exit plan.
For access, distinguish administrator, employee, accountant and support-assisted retrieval. Read-only access may expose reports while excluding configuration history or a previously available export. Employee portal access does not demonstrate that the employer can retrieve the records required for an inquiry. Test the particular route your organization plans to rely on.
Make service dependencies visible in the handoff. If a carrier file or accounting feed will stop with payroll processing, give its receiving team the last expected delivery and the replacement route. If an interface stays active for a residual task, restrict its purpose and identify who will retire it later. Keeping every connection open indefinitely is not an exit control.
Keep the agreement clause, sent notice and provider acknowledgement with the corresponding date entry.
Obtain records in a form your organization can use
Turn “we own our data” into a list of deliverables and retrieval arrangements. Ask which records can be exported, by whom, in what format and at what cost. Establish the periods and employee populations included, whether former employees are covered, and how much lead time a provider-assisted request requires. Ownership language alone does not describe the export or the continuing service available to retrieve it.
Separate the records needed to run the replacement system from those needed to explain past payroll. An implementation import may contain current employee setup and year-to-date balances without preserving historical approvals, pay statements or filing acknowledgements. The archive owner needs a package suited to historical questions, even when the new system does not import those records.
Use a proportionate acceptance check before access ends. Have an authorized reviewer open a retained report outside the provider portal, identify the employer and period, locate a selected former employee and follow a selected historical transaction to its supporting record. Record what was checked and what was missing. This is a retrieval check on the exit package, not a claim that every historical calculation has been audited.
Keep the source files, explanatory report definitions and an index that connects them. If a report uses different date bases, currencies or employee identifiers from another export, preserve that explanation with the files. Give cumulative extracts a visible version and coverage statement so they cannot later be mistaken for additional transactions to import.
Have privacy, security and records owners approve the storage location and access. Payroll files can contain sensitive identifiers, banking information and compensation. Use the approved secure transfer route and avoid scattering archives across personal inboxes or unmanaged folders. The exit coordinator should record a restricted location reference in the docket, without copying sensitive employee details into a broadly shared project tracker.
Agree how later records will be delivered. A package downloaded after the last payroll may still be missing a return filed in January or a corrected statement produced later. Give those expected additions an owner, due date and receipt check. Closing the initial export task should not close a future deliverable that has yet to exist.
Keep employer obligations separate from the vendor relationship
The employer generally keeps its employment-tax duties when it uses an ordinary payroll-service or reporting-agent arrangement, as the IRS explains. Different third-party arrangements, including qualifying CPEO situations, require separate analysis. Replacing a vendor does not establish that a deposit was made or that a return was accepted.
Assign each outstanding obligation to a named preparer and employer reviewer for the specific EIN, jurisdiction and period. Obtain the departing provider's description of the work it will complete and the incoming provider's acknowledgement of the work it is accepting. Ask the employer's tax adviser to resolve gaps, overlapping instructions and arrangement-specific responsibility. Do not let both providers infer that the other will file the same return.
Carry evidence of actual payments, transmissions and acceptance into the retained records. A tax balance refunded to the employer needs a documented destination and follow-up action where payment remains due. An invoice for a filing service is commercial evidence, not proof that the agency accepted the filing. Unresolved notices and corrections should remain in the responsible team's queue after the subscription closes.
Retention also has its own timetable. The IRS's employment-tax recordkeeping page calls for at least four years after filing the fourth quarter for the year, and longer periods for certain credit-related records. For covered records, federal wage-and-hour guidance generally distinguishes three-year payroll records from two-year wage-calculation records. State rules, benefit records and preservation obligations can require other treatment. Have the records owner apply the relevant schedule rather than turning a provider's access window into the retention rule.
Ask about the provider's remaining copies and applicable retention or deletion process. An immediate deletion request may conflict with records that must still be preserved or work that remains authorized. Resolve the scope with legal, privacy and records owners before giving the instruction. Obtain the appropriate confirmation when disposition is permitted; do not infer that closing a login removed every copy.
Attach each preparer’s acceptance and the eventual result to the obligation entry in the exit docket.
Read the cancellation workflow for the specific product
Public help pages show why product-specific confirmation matters. Gusto's current cancellation guidance says an account cannot be canceled while a payroll is in progress and describes continued access to historical records after cancellation. It also gives different tax-handling instructions according to the cancellation choice. Verify the current instructions for the account and obtain a clear acknowledgement of remaining work before proceeding.
Intuit's current payroll cancellation guidance distinguishes products: it describes one year of payroll-data access for QuickBooks Workforce and a separate twelve-month tax-return access route for Desktop Payroll Assisted. Other Desktop payroll options have different limitations. Its full-service instructions also say to keep the bank account open until the remaining liabilities have been debited and paid. Confirm the product and service arrangement rather than borrowing another customer's timeline.
These examples are not recommendations to use either product or promises about every account sold under those brands. The customer's agreement, product, purchasing channel and selected cancellation options must be checked. Save the applicable instructions and confirmation with the exit file, including the date reviewed. If the public page and the provider's account-specific answer differ, resolve the conflict before relying on either for a consequential action.
Price the remaining relationship, including the work after exit
Request a written closing estimate that separates subscription charges through the effective end date, any applicable early-termination amount, data retrieval, historical access, tax or year-end work and later corrections. Include only charges that the provider identifies as applicable, and mark estimates as estimates. Ask what event creates each charge and whether the figure depends on employee count, jurisdiction, timing or another variable.
Compare those amounts with the proposed schedule. A nominally cheaper immediate cancellation may leave the employer buying a separate archive retrieval or filing service. A short paid extension might be useful when it supplies a defined missing capability, but it needs a confirmed scope and ending condition. Do not buy an extension solely because nobody has assigned the remaining work.
Keep disputed amounts visible alongside agreed payment arrangements. Finance should know which invoices are expected, which charges require review and which funds relate to payroll or taxes rather than subscription fees. Route any proposal to revoke banking authority through the people responsible for pending payments and the applicable agreement. Preventing an unwanted subscription debit and interrupting an authorized payroll or tax payment have different consequences.
Record expected credits and refunds as items to reconcile, not reductions already received. Identify the original charge or tax balance, the expected return route and the owner who will confirm receipt. A final invoice does not necessarily settle every financial movement associated with the account.
Payroll Provider Exit Docket
Create one docket for the employer and service arrangement being ended. Repeat a service or obligation entry when its dates, supplier or responsibilities differ. Copy the fields into an approved workspace and link to restricted evidence; the docket itself should not contain employee bank numbers, Social Security numbers or raw payroll files.
Complete the factual fields first. Then ask the accountable business owner to choose whether to send notice, amend the planned dates, continue a limited service or pause a particular closure instruction. A missing acknowledgement is an unresolved condition, not an implied approval.
Agreement and authority
Employer and account: Legal entity, EIN reference, account and service arrangement: ____.
Agreement evidence: Signed version, amendments and reviewed notice or renewal clauses: ____.
Authorized instruction: Sender, required recipient, permitted delivery method and internal approver: ____.
Service boundary: Services ending, services continuing and separate suppliers affected: ____.
Open interpretation: Question for counsel or procurement, decision owner and answer due: ____.
Keep the clause reference distinct from the business interpretation. Attach the acknowledgement when it arrives.
Dates and acknowledgement
Notice milestone: Required notice event, checked deadline, delivery evidence and receipt status: ____.
Last processing: Employer, last pay date, included runs and applicable submission or funding cutoffs: ____.
Residual service: Each remaining service, ending condition, intake cutoff and provider acknowledgement: ____.
Access sunset: Administrator, employee and assisted-retrieval routes, with each confirmed end condition: ____.
Change route: Procedure, contact and terms for an extension or revised exit date, or explicitly unconfirmed: ____.
Label each date proposed, acknowledged or completed.
Records and remaining work
Archive delivery: Record classes, periods, populations, formats, delivery dates and restricted location: ____.
Retrieval evidence: Reviewer, selected records, access route, check date, result and missing items: ____.
Obligation entry: EIN, jurisdiction, period, required output, preparer, employer reviewer and deadline: ____.
Future addition: Expected later form or correction, delivery owner, due date and receipt check: ____.
Connected service: Last expected feed, receiving owner, replacement route and access-retirement task: ____.
Repeat the obligation entry for each distinct responsibility. Preserve original confirmations and record where they can be found.
Commercial close and decision
Closing charges: Applicable charges, basis, estimate or invoice status, disputed items and finance owner: ____.
Money still moving: Pending payroll or tax debits, credits, refunds, expected dates and reconciliation owner: ____.
Preservation and access: Approved retention schedule, any hold, archive custodian and authorized users: ____.
Unresolved condition: Missing evidence or agreement, affected closure action, owner and escalation date: ____.
Decision and follow-through: Authorized action, approver, date, conditions and next verification: ____.
Sending notice, stopping processing and retiring access can be separate decisions. A condition remains open until its evidence or approved alternative is recorded.
Turn the exit docket into buying questions
Your completed docket can guide a free conversation with SelectSoftware Reviews about replacement options. Take the records you were unable to obtain from the old service and ask candidates to show how their own archive and post-exit support would cover them.
A December exit with a January service still open
Alder Works, a fictional employer, has reviewed an agreement that permits notice by October 31 to end the subscribed processing service on December 31. Those are invented terms for this example. The parties acknowledge December 18 as the final scheduled old-provider payday, while a separate written arrangement covers specified year-end filing work through January. Administrator report access is confirmed through March 31.
On December 19, the migration coordinator sees the final scheduled payroll complete and proposes closing all old access. The docket shows why that instruction is premature: the archive has payroll registers but lacks a selected former employee's statement, the January work has not produced its final records, and finance is still expecting a refund. The subscribed processing service can end as agreed while those tasks retain named owners.
The archive custodian obtains the missing statement through the agreed route and records a successful retrieval outside the portal. Payroll and the tax adviser confirm the January deliverables and the employer reviewer responsible for checking acceptance evidence. Finance records the expected refund separately from the closing invoice. The team schedules a February archive addition and an access-retirement review before March 31.
An authorized correction discovered on December 22 requires another payment. The December 18 boundary no longer describes all activity that needs handling. The payroll owner establishes which provider can make the correction through a supported route, records its pay date and updates the history and reporting assignments. Nobody sends the same payment to both providers or treats a previously downloaded cumulative export as the final version.
If the departing provider cannot supply a required record before access expires, the docket needs an active exception. Request the missing record by name, period and required delivery date through the provider’s retrieval or extension process. Escalate an unresolved delivery gap to the business owner and appropriate adviser, and record what any agreed alternative actually supplies. “We can probably call support later” is not an accepted archive arrangement.
The example's outcome is a sequence of documented actions, rather than a single cancellation checkbox. Notice was delivered, payroll processing ended on the agreed boundary, remaining work was checked and the archive became independently usable. Access retirement follows the evidence and approved terms, with unfinished items transferred to an enduring owner.
Finish access retirement and preserve the follow-up contact
Before the final account instruction, reconcile the docket against the migration plan and the provider's acknowledgement. Confirm that a late change has not altered the last included payroll, archive coverage or remaining filing assignment. Have the relevant owners report the status of their own work; the project coordinator should not certify an agency acceptance or archive check they have not seen.
Give employees the specific information they need: where to obtain old statements or tax forms, where future records will appear, and the employer contact for a missing document. Describe only the access documented for that account. If a portal will end, provide a supported alternative and sufficient internal lead time to handle questions. Keep sensitive documents out of broad announcements.
Retire administrator accounts, integrations and payment permissions according to the approved sequence. Preserve the ability to complete authorized residual tasks through appropriately restricted access. Confirm the effect of each removal with the responsible team, particularly where a shared identity, accountant connection or automated feed serves more than one employer or service.
Keep a durable employer contact for post-exit questions. Transfer unresolved notices, refunds, record requests and corrections into the normal operating queues, with their evidence references and next deadlines. A departed project manager or expired support mailbox should not be the only route to the remaining file. Store the closing acknowledgement, final service schedule and commercial reconciliation with the retained agreement.
Questions about ending the provider relationship
Will the new provider cancel the old service for us?
Rely on the specific authorized arrangement agreed in writing by the parties. Obtain evidence of the actual notice and departing provider's acknowledgement. A new provider's onboarding completion message does not establish that the old agreement, billing or access arrangements have ended.
Is continued read-only access enough?
It can support retrieval when its scope, duration and authorized users are documented, but check the actual records available and preserve an independent archive under your organization's requirements. A portal that displays a pay statement may not expose the approval or filing confirmation needed to answer a later question.
Should we wait until year-end to leave?
Choose the date from the applicable contract, payroll readiness and remaining-service responsibilities. A year boundary can help describe reporting work, but it does not automatically assign that work or repair missing history. Coordinate the exit schedule with the migration owner and tax adviser before committing to a date.
What if we cannot agree on an exit charge or data request?
Preserve the request, response, agreement provisions and affected deadline. Ask the appropriate commercial or legal owner to resolve the dispute, while payroll and tax owners protect the obligations that still exist. Specify which processing, filing or retrieval task needs an interim agreement while the dispute is resolved. Withholding an instruction or a payment does not create that agreement.
What changes if the business is closing?
Business closure needs its own final-payment, filing and account-closure review. The IRS lists final returns, employee tax responsibilities, business-account closure and record retention among the steps to address. Have the tax adviser determine the applicable federal, state and local actions and confirm which ones the provider will perform. Canceling the subscription does not document completion of those steps. Preserve a responsible contact and a usable archive after the operating business stops using the payroll system.
What if the account has already been canceled?
Establish which access and services remain available now, then request the missing records through the supported route. List unfinished payments, returns, corrections and refunds with their current owners. Ask for a confirmed extension or retrieval arrangement where needed, including its cost and delivery conditions. If a required record or deadline cannot be covered, escalate the specific gap promptly. Reconstruct the exit docket from the retained agreement, messages and actual results rather than assuming the cancellation confirmation settled every item.
Choose the next relationship with its ending in view
Include the next provider’s eventual exit in your buying discussion. SelectSoftware Reviews offers a free advisor consultation; obtain the candidate’s own written terms for record delivery and remaining work before signing.
Continue with the guide library:
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.
