Form 5310-A Guide – IRS Notice for Plan Mergers and Spinoffs

Editorial Standards

How we research, review, and update this guide

Every Accountably guide is researched against primary IRS sources, reviewed by a U.S. CPA, and refreshed as guidance evolves. Read our Editorial Guidelines to see how we source, fact-check, and update our content.

A frequent mix-up sends a team straight to Pay.gov when the transaction in front of them is a plan merger or spinoff. Form 5310-A is not a determination letter request and is not filed electronically. It is a notice you mail to the Employee Plans address in Kentucky, and an IRS determination letter will not be issued in response to it. Do not confuse it with Form 5310 or Form 5300, which do route through Pay.gov with user fees.

Form 5310-A notifies the IRS of a plan merger, consolidation, spinoff, or transfer of plan assets or liabilities, and it also handles QSLOB elections, with authority at IRC §6058(b) for Part II and §414(r) for Part III. File at least 30 days before the transaction. The November 2010 revision remains current through tax year 2025, and multiemployer plans covered by PBGC insurance are excluded from filing it for reorganization events.

Key Takeaways

• You use Form 5310‑A to notify the IRS of a plan merger, consolidation, spinoff, or a transfer of plan assets or liabilities, and to elect, modify, or revoke Qualified Separate Lines of Business status. An IRS determination letter is not issued for this notice.
• File the notice at least 30 days before the merger, spinoff, consolidation, or transfer. For QSLOBs, follow the “notification date” rule tied to the testing year.
• Mail Form 5310‑A to the IRS Employee Plans address in Kentucky, or send by approved courier to the Florence, KY street address. These addresses reflect the October 11, 2019 update and remain in use.
• Do not confuse Form 5310‑A with Form 5310 or Form 5300. Determination letter applications for those forms are filed electronically on Pay.gov, include user fees, and follow a 15 MB upload plus fax‑overflow process. Form 5310‑A is a mailed notice.
• Multiemployer plans covered by PBGC insurance are excluded from filing 5310‑A for plan reorganization events.

What Form 5310‑A covers

Form 5310‑A is how you notify the IRS when you reorganize a qualified plan or make a QSLOB election.

Covered transactions

• Plan merger or consolidation, combining two or more plans into one plan.
• Plan spinoff, splitting a single plan into two or more successor plans.
• Transfer of plan assets or liabilities, moving a portion of assets or liabilities from a transferor plan with a concurrent assumption by a transferee plan.
• QSLOB elections, modifications, or revocations by the employer.

When a notice is not required

There are specific exceptions tied to the 1.414(l) regulations. For example, some defined contribution plan mergers, small spinoffs, or certain transfers that satisfy the regulation’s balance and value rules do not require filing a 5310‑A. The instructions detail scenarios and examples that fall under these exceptions.

Who files

• For mergers, consolidations, spinoffs, and transfers, the sponsor or plan administrator files a 5310‑A.
• For QSLOB matters, the employer files a single notice for the controlled group, as defined under sections 414(b), (c), and (m).

When to file

• Transactions, file at least 30 days before the merger, consolidation, spinoff, or transfer.
• QSLOBs, file by the “notification date” for the testing year. That date is the later of October 15 of the year following the testing year, or the 15th day of the 10th month after the earliest plan year start in the testing year.

Pro tip, treat the 30‑day clock like a closing checklist item. If your transaction date moves, re‑check your filing window so the notice still precedes the event.

Where to file

Mail Form 5310‑A to:

• Internal Revenue Service, TE/GE Stop 31A Team 105, P.O. Box 12192, Covington, KY 41012‑0192
• For express or courier, Internal Revenue Service, 7940 Kentucky Drive, Florence, KY 41042 (private delivery services like FedEx and UPS cannot deliver to a P.O. Box, so use this Florence street address for those carriers)

These addresses reflect the IRS’s employee plans submission update announced on October 11, 2019 and cited on the Form 5310‑A page.

Important, Form 5310‑A is not submitted on Pay.gov. Do not bundle it with determination letter applications.

Quick reference table, triggers and filer

Transaction or election	What triggers filing	Who files	When
Plan merger or consolidation	Combining plans into one	Plan sponsor or administrator	At least 30 days before the event
Plan spinoff	Splitting one plan into successor plans	Plan sponsor or administrator	At least 30 days before the event
Transfer of assets or liabilities	Split of assets or liabilities and concurrent assumption by another plan	Plan sponsor or administrator	At least 30 days before the event
QSLOB election, modification, or revocation	Employer chooses to be treated as operating QSLOBs for testing purposes	Employer, one notice for the group	By the notification date for the testing year

Sources, Form 5310‑A instructions and “About” page.

A common mix‑up to avoid

It is easy to think 5310‑A is an online filing because so many Employee Plans submissions moved to Pay.gov. Here is the clean split:

• Form 5310‑A, mailed notice, no determination letter issued.
• Form 5310 and Form 5300, determination letter applications, must be filed on Pay.gov with user fees, 15 MB upload cap, and fax‑overflow to 844‑255‑4818. For status, call EP Customer Account Services at 877‑829‑5500 or use the listed fax line.

In other words, if you are notifying the IRS about a reorganization or QSLOBs, you are mailing 5310‑A. If you are asking the IRS to determine qualification for a terminating or ongoing plan, you are on Pay.gov with Form 5310 or 5300.

What the IRS expects in your 5310‑A package

When plans reorganize, the IRS wants to see that the receiving and sending plans stay qualified, that participants are protected, and that your math ties out. Think like a reviewer. Make it effortless for a specialist to follow your path from plan document, to transaction terms, to balances that move.

Core documents to gather

• Current plan document and adoption agreement for each plan involved.
• Trust agreement and any applicable custodial or pooled account agreements.
• All executed amendments in effect on the transaction date.
• Prior determination, opinion, or advisory letters, if available.
• Transaction documents, for example merger agreement or spinoff resolution.
• Asset and liability schedules that reconcile to the most recent valuation.
• Participant impact statement, for example how accounts map before and after.
• Any board minutes or consent actions that authorize the event.
• Contact authorization, for example Form 2848 or 8821, if you want your advisor to talk to the IRS on your behalf.

Make your exhibits self‑explanatory. Label each with a short description, plan name, and plan number. Use bookmarks in your PDF so an IRS reviewer can jump to what they need in seconds.

Smart file hygiene that speeds reviews

• Structured workpapers, one folder for each plan and a simple index at the top.
• Consistent file names, for example “PlanA_AdoptionAgreement_2019_Amend5.pdf.”
• A one‑page reconciliation that proves opening balance, outflow or inflow, and ending balance for each plan.
• A glossary of acronyms and a contact sheet with names and direct emails.

Who signs and how to route internally

• Plan administrator reviews and signs the 5310‑A notice for plan transactions.
• The employer signs for QSLOB elections or changes.
• Legal confirms the transaction documents, HR validates participant communications, payroll checks timing on payroll deferrals, and the recordkeeper confirms mapping and blackout timing.
• Set a single owner for the package. One person should control the document index, the checklist, and the mailing.

Line‑by‑line, what to prepare before you start typing

You can complete Form 5310‑A in one sitting if you collect the right facts first. Here is the short list I keep on my desk.

• Employer name, EIN, address, and contact info.
• Plan name and three‑digit plan number that match your Form 5500.
• Plan type, for example 401(k), money purchase, profit sharing, or 403(b).
• Original effective date and current plan year end.
• The exact reorganization event, for example merger into Plan B on a specific date.
• Names and plan numbers of all plans involved, sending and receiving.
• Whether the transfer affects all participants or only a group, with count and criteria.
• The participant communication date and method, for example mailed letter or portal notice.
• A short narrative that explains the transaction in plain English.

Keep the narrative simple, one paragraph that states the event, date, plans involved, and what moved. If a reviewer can explain your deal in one minute, your package is in good shape.

QSLOB elections in plain language

Qualified Separate Lines of Business are a testing framework. If your controlled group operates distinct lines that meet the qualification rules, you can test coverage and nondiscrimination by line, not as one aggregated company. The election, any modification, or a revocation is reported with Form 5310‑A, and it follows its own notification timeline. The employer, not the plan administrator, is the filer here.

Quick QSLOB readiness check

• Do you have clear organizational charts that map to lines of business.
• Can you produce headcount and participation by line for the testing year.
• Are the benefit, rights, and features consistent within each line.
• Do payroll and HR systems tag employees to the correct line.
• Do you have a written policy that defines and maintains your lines, with dates.

If you struggle to answer those, pause before you elect QSLOB treatment. Clean data and consistent definitions matter more than anything else in this section.

Timeline planning, so you do not miss the window

Working backward is the easiest way to hit the 30‑day advance notice rule for plan reorganizations. Here is a simple timeline you can clip into your project plan.

• T‑60 to T‑45 days, kick off with legal, HR, payroll, recordkeeper, and auditor. Assign the 5310‑A owner and start the exhibit index.
• T‑45 to T‑35 days, finalize all plan documents and transaction terms, draft your participant communication, prepare asset and liability schedules, and draft the one‑paragraph narrative.
• T‑35 to T‑32 days, internal review by benefits, finance, and outside counsel. Collect signatures.
• T‑31 days, print, bind, and prepare the mailing with tracking and proof of mailing.
• T‑30 or earlier, mail the 5310‑A package.
• T‑10 to T day, complete the asset transfer or spinoff. Confirm the first payroll cycle after the event is mapped correctly.

Always attach proof of mailing to your index. A clean audit trail is your safety net if questions come up later.

Avoid the 7 most common errors we see

• Filing after the event date. Set a calendar alert tied to your definitive agreement so the clock starts automatically.
• Mismatch between plan names and plan numbers across documents. Match the 5500 exactly.
• Missing executed amendments. Use a gap list to confirm no amendments are missing between the last restatement and the transaction date.
• No reconciliation of money that moved. One clean schedule solves half of the back‑and‑forth.
• Ambiguous participant mapping. Spell it out, for example “active, terminated, and QDRO alternate payees with balance on date X.”
• Unclear contact path. Always include a direct contact who can answer questions quickly.
• Confusing or unlabeled exhibits. Bookmark and label everything.

How to assemble a clean, reviewer‑friendly 5310‑A package

You want a package that any IRS specialist can follow without a single email. Think of it like a short story with exhibits.

Cover letter blueprint

Your cover letter does the heavy lifting. Keep it to one page.

• Opening, state that you are filing Form 5310‑A for a merger, consolidation, spinoff, transfer of assets or liabilities, or a QSLOB action.
• Event summary, list the plans involved, the event date, and a one‑sentence description of what is moving.
• Exhibits, include a numbered list with short labels, for example Exhibit 3, Executed Amendment 2023‑02.
• Contact, provide a direct name, phone, and email for questions.
• Signature block, the plan administrator or employer officer signs, with title and date.

If you can hand the cover letter to someone outside benefits and they understand the transaction in a minute, you nailed it.

Exhibit index to keep everything straight

Put an index as page two, right behind the cover letter. It should list each exhibit, the plan name, the plan number, and a nine‑word description or fewer. Use bookmarks in the PDF that mirror the index. Reviewers can jump straight to your proof.

Narrative example you can adapt

Here is a short narrative you can tailor.

On February 28, 2026, Sponsor A will merge the Sponsor A 401(k) Plan, Plan 001, into the Sponsor B 401(k) Plan, Plan 003. All active and terminated participants with balances on the event date will be mapped to comparable investment options in the receiving plan based on a like‑for‑like mapping grid included as Exhibit 8. No protected benefits are eliminated. All plan documents and executed amendments in effect on the event date are attached.

Reconciling money that moves

A one‑page reconciliation prevents most follow‑up calls.

• Show period start balances, the gross transfer, fees if any, and ending balances for each plan.
• Tie those amounts to valuation statements or trustee reports.
• Include headcount by status, for example active, terminated, alternate payees.
• If you exclude anyone, say why, for example frozen account under QDRO hold.

Participant communication, keep it simple and dated

Attach the participant notice and the date you sent it. If you used multiple methods, list each method, for example mail, email, or portal banner. Add a brief summary of blackout dates and mapping. If your recordkeeper provides a final communication packet, include the table of contents.

Special cases you should flag early

Certain transactions deserve a quick chat with counsel or your recordkeeper before you finalize the notice.

Defined benefit plans

If you are carving out liabilities or merging defined benefit plans, make sure your actuarial schedules line up with the transaction terms. Cross‑reference the plan’s funding and lump sum rules to confirm protected benefits are handled correctly. A short actuarial memo saved with your exhibits helps reviewers.

403(b) plans

Confirm custodial and annuity contract assignments are permitted and documented. If contracts cannot be pooled, spell out how you will handle accounts that stay behind or move on different dates.

Plans with safe harbor features

If you have safe harbor matching or nonelective provisions, confirm they remain intact through the transaction. Note any timing adjustments to notices or funding.

Partial transfers tied to acquisitions

When only some employees move, show the criteria. Examples include business unit, job code, or location. Add a simple count by group so the reviewer can see that the selection is objective and consistent.

Internal controls that keep you out of trouble

You do not need a giant operations manual. You need a few habits that never slip.

• One owner for the 5310‑A package, responsible for the index and mailing proof.
• A two‑person check on plan names and plan numbers across every document.
• A final tie‑out meeting with legal, HR, payroll, and the recordkeeper.
• A policy to archive the package, the tracking receipt, and the participant communication for not less than seven years.

If you partner with an external team, set expectations in writing. Ask for structured workpapers, consistent file names, and a standard review pass that catches missing signatures and mismatched plan numbers.

Clear ownership, a single source of truth for documents, and a simple checklist solve most filing risks.

Where an operations partner actually helps

Most filing issues are not legal questions. They are delivery problems, missing files, and messy exhibits. If you need extra hands, a disciplined delivery partner can standardize workpapers, control versioning, and move the package across the finish line. On complex events with tight calendars, that kind of structure protects your timeline and your audit trail.

• Standard operating procedures keep file names, folders, and versions predictable.
• Layered reviews, preparer to senior to quality, reduce rework.
• Continuity plans prevent disruption if someone is out during a critical week.

If you work with Accountably, we focus on that operational discipline. We set up clear SOPs, structured exhibit lists, and a clean review path so your team can stay focused on strategy while we keep the package precise and on time.

Choosing the right form, a quick comparison

Many teams mix up 5310‑A with determination forms. Use this table to pick the right path.

Purpose	Use this form	Typical filer	Submission path	User fee
Notify IRS of plan merger, consolidation, spinoff, or asset or liability transfer	Form 5310‑A	Plan administrator or sponsor	Mail to IRS Employee Plans	None
Request determination on plan termination	Form 5310	Plan sponsor	Pay.gov with exhibits and cover letter	Yes
Request determination on individually designed plan qualification	Form 5300	Plan sponsor	Pay.gov with exhibits	Yes
Adopt or change QSLOB status	Form 5310‑A	Employer for the controlled group	Mail to IRS Employee Plans	None
Request determination for adopters of pre‑approved plans	Form 5307	Plan sponsor	Pay.gov	Yes

If you are sending 5310 or 5300, expect an online upload limit and potential fax overflow. Keep the receipt and document locator. For 5310‑A, your proof of mailing is what matters.

Step‑by‑step mailing checklist

• Print the signed Form 5310‑A and cover letter on company letterhead.
• Place the exhibit index behind the cover letter.
• Assemble exhibits in the same order as the index and add bookmarks.
• Use a trackable mailing method. Keep the receipt with the index.
• Save a complete PDF set in your plan compliance archive.

Add a calendar reminder ten days after mailing. If tracking does not show delivery, follow up with the carrier and re‑send as needed.

Working with auditors and recordkeepers

Loop in your auditor if you expect the transfer to cross a plan year end or if the transaction affects audit timing. Share your reconciliation and mapping grids early. For recordkeepers, confirm blackout timing, fund mapping, and any fee implications. Ask for a final transaction report that reconciles to your schedules. Save that report with your exhibits.

Data privacy and security

Treat your package like financial statements. Limit access to those who need it, and use a role‑based folder with audit logs. Avoid local storage. Encrypt files you send to outside counsel or advisors. If you engage outside support, request background‑verified staff and a written confidentiality agreement.

Mini case study

We helped a mid‑market manufacturer spin off a closed division’s employees to the buyer’s plan. Their risk was timing. Payroll needed the transfer to complete between pay cycles. We built a three‑week sprint, set the 5310‑A owner, and created a single workbook that tied headcount, balances, and mapping. The notice went out thirty‑two days before the transfer. On the event date, funds moved, payroll hit on schedule, and the auditor cleared the tie‑out in one pass. Nothing fancy, just disciplined prep.

Common Mistakes We See Every Season

Plan-event notices fail in predictable ways. The same five or six mistakes recur every season we touch a Form 5310-A package, and almost every one starts with skipping the Who Must File instructions before mailing.

Reusable Checklists

These checklists are copy-paste ready for firm SOPs. Drop them into your engagement folder and use them as gates before the 5310-A package leaves the office.

Keep 5310-A Season From Stalling

Form 5310-A work clusters around plan-level events. A merger, a spinoff, a transfer of plan assets or liabilities, or a QSLOB election lands on a stakeholder map that includes plan sponsors, recordkeepers, payroll, outside counsel, and the reviewer waiting for a clean package. When the transaction date moves, the notice window moves with it, and a Part II filing that was on schedule last Tuesday can stall the entire deal by Friday.

The fix is operational. Once we build a standard 5310-A workflow that owns the line-by-line prep, the exhibit index, and the mailing routing, the package stops being a fire drill and starts being a one-pass review. We see fewer reroutes from the TE/GE team and faster auditor sign-off on the post-event reconciliation.

• Stand up a single 5310-A workbook that ties line 4a plan name, line 4b plan number, line 5a plan type, and the line 6 other-plan inventory to the source plan documents – so the same data is not retyped across exhibits.
• Build branching logic into the Part III worksheet: line 7a controls 7b and 7c, line 9 controls whether lines 11 and 12 stay live or go blank, and line 10 boxes are gated on actual coverage and participation tests.
• Maintain two pre-addressed shipping labels in every engagement folder – one USPS (Covington P.O. Box) and one PDS (Florence street address) – and pick at the moment of mailing, not at the moment of drafting.
• Gate the actuarial statement of valuation attachment on line 5a = 1; defined contribution plans skip the IRC §401(a)(12) and Treas. Reg. §1.414(l) schedule entirely.
• Lock the advance-notice window required under Treas. Reg. §1.414(l) into the project plan, so a slipped close date does not pull the notice mailing inside the IRS guidance window.

That is the kind of disciplined offshore execution we deliver at Accountably. Our trained teams sit inside your plan-event workflow, run the line-by-line prep and exhibit index on our side, and hand the reviewer a single PDF that ties back to the source documents. See our tax outsourcing services for how we structure the engagement.

FAQs

Is there a user fee for Form 5310‑A

No. Form 5310‑A is a notice filing. You mail it with your exhibits and cover letter. Keep proof of mailing with your plan records.

How far in advance must I file

For mergers, consolidations, spinoffs, and transfers, file at least 30 days before the event date. For QSLOBs, follow the testing‑year notification timing. If your transaction date slips, recheck your 30‑day window.

Do I get a determination letter after filing Form 5310‑A

No. The IRS does not issue a determination letter in response to a 5310‑A notice. If you need a determination, you submit the appropriate application, often Form 5310 for terminations or Form 5300 for individually designed plans.

What if only some employees move in a transfer

Describe the selection criteria in plain English and include counts by group. Attach a reconciliation that ties to the valuation for the assets and liabilities that move.

What should my exhibit list include

Plan documents, trust agreements, executed amendments, transaction terms, reconciliation schedules, participant communications, prior letters if available, and any contact authorization. Label each exhibit and add PDF bookmarks.

Do 403(b) mergers and spinoffs use Form 5310‑A

Yes, when the transaction is within scope. Confirm contract rules and documentation. Include custodial or annuity contract references so reviewers can follow your path.

What happens if I miss the 30‑day deadline

Talk with counsel quickly. File as soon as possible, document the reasons, and keep precise proof of mailing. Then verify payroll and recordkeeper timing so participants are protected.