Skip to main content
401kROBSCheck eligibility
Plan document restatement

ROBS Plan Restatements

A ROBS plan restatement should leave the company with one current document package, a complete prior-document chain, a signed adoption agreement, and a practical operating map for deadlines, notices, filings, and reliance limits.

By Dennis Shirshikov · Accessed July 31, 2026 · Updated July 31, 2026 · Sources accessed July 31, 2026

Restatement rule

Consolidate the plan text without erasing the plan history. The signed new package governs current administration, while prior documents prove prior rights and operations.

Direct Answer: Restate the Document, Preserve the History

A restatement replaces the plan text for current use while prior documents remain evidence of prior operation.

Direct answer: restate when the current governing document package must be replaced. Keep amendment, notice, administration, testing, filing, correction, valuation and termination work in their own lanes because each answers a different compliance question. A Rollover as Business Startup, or ROBS, uses a C corporation's qualified plan to buy employer stock. The IRS identifies recurring ROBS issues involving plan documents, determination-letter limits, employee access, valuation, filings and operational failures.[15][16] A restatement should therefore prove two things at once: the current document is adopted and usable, and the superseded document chain remains available to explain earlier eligibility, allocations, distributions, loans, employer-stock rights, notices, Form 5500 reporting and corrections.[5][8][22][23][24]

Start with the amendment/restatement boundary: use an amendment for a targeted document change, use a restatement for a full replacement package, and use separate workflows for notices, annual administration, tests, filings, EPCRS corrections, valuations or termination events. The business decision is simple: sign only after the sponsor can show document type, cycle status, adoption authority, effective dates, election changes, reliance limits, implementation owners, participant handoffs and correction boundaries. A provider packet is useful support, but the employer still owns adoption and operation under the plan document.[1][5][25][29][36]

Technical Terms Before Use

Restatement work fails when the same word is used for three different document events.

Restatement

A full replacement document package adopted to bring the plan document current and consolidate prior amendments. It governs prospectively from its stated effective terms while the old documents remain evidence of prior rights and operations.[1][3][8]

Amendment

A signed change to selected provisions of the existing document. Amendments may be required, discretionary, interim, conforming or corrective depending on authority and timing.[8][9][12]

Adoption agreement

The employer election instrument used with many pre-approved plans. It must be compared against payroll, eligibility, contribution, distribution, loan and employer-stock operations.[1][5]

Basic plan document

The base language maintained by the pre-approved plan provider and approved for form by IRS when an opinion letter is issued.[1][5]

Pre-approved plan

A plan document sold by a pre-approved plan provider after IRS reviews the document's form under the pre-approved program.[1][5][6]

Individually designed plan

A plan drafted for one sponsor rather than adopted on a provider's pre-approved document. Current timing is driven by RAL, operation, discretionary amendments and limited determination-letter windows.[8][9][12]

Opinion letter

The IRS letter for a pre-approved plan document's form. ROBS capitalization, valuation, fiduciary process and plan administration require separate operational support.[5][13][14]

Determination letter

The IRS letter generally requested by an individually designed plan in allowed circumstances, such as initial qualification, termination or another IRS-announced exception.[12][13][14]

Cumulative List

A list of qualification changes historically used for plan cycles. IRS says post-2015 cumulative lists are for pre-approved plan cycles only.[8][9]

RAL

The Required Amendments List is the annual IRS list of qualification changes and amendment deadlines for individually designed plans.[9][11]

OC List

The Operational Compliance List helps identify qualification changes effective during a calendar year. Operation from the effective date still controls.[10][11]

Pre-Approved Cycle Rules and Individually Designed Plan Treatment

Use official cycle pages, not vendor folklore or projected dates.

For pre-approved plans, IRS describes a six-year remedial amendment cycle. The official cycle table shows the third defined-contribution timely submission period as October 2, 2017 to December 31, 2018 and the third RAC ending January 31, 2023. The IRS list page states that virtually all third-cycle pre-approved DC opinion letters were issued at the same time, June 30, 2020, and adopting employers who used those documents to restate for the 2017 Cumulative List were required to adopt by July 31, 2022.[3][4]

Cycle 4 is more limited as of the accessed sources. IRS states that providers applying during the fourth defined-contribution pre-approved plan cycle could use revised LRMs for the February 1, 2024 through January 31, 2025 submission period. The IRS list page identifies a fourth remedial amendment cycle list for DC plans submitted from February 1, 2024 to August 25, 2025, covering the 2023 Cumulative List. The six-year cycle table accessed here leaves the fourth DC RAC end blank, so the supported reader takeaway is to track official IRS announcements before using an adopting-employer Cycle 4 restatement deadline.[1][3][4][5]

Individually designed plans use a different current framework. IRS explains that the former five-year remedial amendment cycle ended January 1, 2017. Required amendments are tied to the RAL unless legislation or guidance states otherwise, operational compliance applies from the effective date, and determination-letter applications are limited to stated circumstances such as initial qualification, termination or IRS exceptions.[8][9][10][11][12][13]

Document Type, Standardized or Nonstandardized Status, and Reliance

Reliance depends on document form, employer elections, and operation.

A pre-approved plan is sold by a provider that requests IRS approval of the document's form. IRS now recognizes standardized and nonstandardized pre-approved plans, with standardized plans described by IRS as safe harbor plans and nonstandardized plans reflecting the flexibility of the predecessor Volume Submitter program.[1][6][7] The employer's adoption agreement matters because it chooses provisions within the approved document. Changes outside permitted options, customized language, or mismatched operation can affect reliance and may require a determination-letter analysis if current procedures allow it.[2][5][6][14]

In a ROBS plan, reliance language must be narrower than marketing language. An opinion letter can support the document's form. The founder's stock purchase, adequacy of consideration, private-company valuation, eligibility practices, later employee access, Form 5500 choice, payroll coding, fiduciary process and EPCRS result require separate evidence and analysis.[14][15][16][25][26][30]

Pre-Signature Comparison Workflow, Adoption Package and Implementation Crosswalk

The restatement is ready only when the signed terms can be operated without guessing.

1. Freeze the current file

Collect current plan, adoption agreement, trust, amendments, SPDs, SMMs, opinion or determination letters, board authority, payroll rules, recordkeeper specifications, census and Form 5500 identifiers.[5][22][23][24][34]

2. Identify document type

Classify the plan as pre-approved standardized, pre-approved nonstandardized, or individually designed before applying a deadline or reliance rule.[1][5][6][12]

3. Build a redline and election inventory

Compare old and new adoption agreements line by line across eligibility, compensation, deferrals, match, nonelective contributions, vesting, loans, distributions, QDRO, claims, safe harbor, employer stock and trustee provisions.[5][17][18][21][22]

4. Run legal and operational screens

Check anti-cutback, benefits-rights-features, coverage, nondiscrimination, top-heavy, employee-stock access, controlled-group, merger, acquisition, spinoff, provider-change, valuation and notice effects before signature.[15][18][19][20][21][25][26]

5. Approve and sign

Confirm corporate authority, plan sponsor action, trustee signature if required, provider or counsel packet, stated effective dates, and no unsigned attachment governs operation.[5][25][29]

6. Implement with a crosswalk

Translate signed elections into payroll codes, recordkeeper settings, participant materials, testing specifications, Form 5500 identifiers, valuation procedures and correction logs.[10][22][23][32][33][34]

Decision tree

Use these questions before signature:

  1. Is the plan pre-approved or individually designed?
  2. If pre-approved, is the provider's document on the relevant official list and within the announced adoption window?
  3. If individually designed, which RAL, OC List, discretionary amendment or determination-letter rule controls?
  4. Do any elections change eligibility, compensation, contributions, vesting, distributions, loans, safe harbor terms or employer-stock access?
  5. Do anti-cutback, benefits-rights-features, coverage, nondiscrimination, top-heavy, notice, Form 5500, valuation or correction issues require counsel review before signature?
  6. Can payroll, recordkeeper, trustee, TPA, CPA and participant communications operate the signed document on the stated dates?

Adoption, Signature, Effective and Operational Dates

One date field cannot carry a restatement file.

The adoption date records corporate or sponsor action. The signature date proves the authorized signer executed the package. The restatement effective date states when the document terms apply. The operational implementation date shows when payroll, recordkeeper, trustee, participant materials, testing and filings began using those terms. A retroactive effective date needs authority from the document, statute, guidance, RAL framework, pre-approved cycle instruction or correction analysis.[5][8][9][10][11][12][30][31]

Restatement files should also preserve provider version dates, opinion-letter dates, adoption-agreement version numbers, SPD or SMM dates, safe harbor notice dates if applicable, 204(h) analysis dates, blackout notice dates if rights are suspended, valuation dates, Form 5500 plan-year identifiers and any amended filing conclusion.[22][23][27][28][32][33][34]

Business Events, Design Elections, and ROBS Employer-Stock Risk

Review the restatement when provider changes, document-vendor changes, payroll or recordkeeper conversions, corporate transactions, ownership changes, or employer-stock elections affect plan terms or operation.

Provider changes, document-vendor changes, payroll conversions and recordkeeper conversions can require new adoption packets, mapping, notices, blackout review, fee disclosures and identifier reconciliation. Corporate events such as merger, acquisition, spinoff, controlled-group change, outside equity, share redemption, stock sale, asset sale, plan merger or termination can change the employer, participants, plan assets, reporting and fiduciary issues.[5][15][25][27][28][32][33][35]

The adoption agreement review should inventory eligibility, age and service, entry dates, exclusions, compensation definitions, elective deferrals, match, nonelective contributions, safe harbor status, vesting, distributions, hardship, loans, QDRO, claims, beneficiary, rollover, trustee, fiduciary, investment direction and employer-stock provisions. ROBS-specific review should flag founder-favorable elections, private employer-stock liquidity, valuation, share class, redemption rights, transfer restrictions and employee access to employer stock.[15][16][17][18][19][20][21][25][26]

Board, Sponsor, Trustee, Administrator, TPA, Recordkeeper, Payroll and Counsel Map

A restatement with unclear ownership becomes an operational failure.

Board or corporate officer

Approves corporate authority, sponsor resolutions, provider contracts, share transactions and authorized signer identity.[15][25][29]

Plan sponsor

Selects document type, signs adoption package, confirms elections, and owns business decisions embedded in the restatement.[1][5][13]

Plan administrator

Maintains documents, participant communications, request response, Form 5500 handoffs and record retention.[22][23][24][34]

Trustee or custodian

Signs or acknowledges trust changes when required and confirms authority before plan asset movement.[5][17][25]

TPA or document provider

Supplies document package, cycle instructions, election support, adoption checklist and operational specifications within engagement scope.[1][5][6]

Recordkeeper

Maps elections into account, loan, distribution, investment and statement systems and keeps conversion proof.[23][28][34]

Payroll owner

Implements eligibility, compensation, deferral, match, loan and vesting rules only from signed terms.[10][18][30]

ERISA counsel

Reviews anti-cutback, reliance, individually designed status, correction, corporate event, employer-stock and notice issues.[12][14][19][20][30][31]

Participant Handoffs, Form 5500 Consistency, Records and Correction Boundaries

Restatement work closes only after people, filings and records match the signed document.

ERISA SPD and SMM rules require participant-facing summaries and modification summaries under specified timing rules. Other rules can trigger earlier or different communications, including 204(h) for applicable pension plan amendments that significantly reduce future accruals, blackout notices for certain suspensions of rights, safe harbor notices, fee disclosures, QDRO procedures, claims procedures and distribution notices. The restatement owner should map each changed provision to a communication decision rather than assuming one generic notice covers all changes.[22][23][27][28]

Form 5500 consistency should be checked after every restatement: plan name, sponsor EIN, plan number, plan year, plan characteristics, signer, trustee or custodian, employer securities, participant counts, final or amended return status and attachments. Keep superseded documents, signed amendments, restatements, election inventories, operational proof and disclosure records at least through the statutory six-year floor for report and disclosure support, and longer while rights, valuations, claims, taxes or corrections can depend on them.[24][32][33][34]

Correction should be classified before promises are made. A missed restatement, wrong election, unsigned package, operation-before-signature, employee exclusion, valuation mismatch or notice failure may implicate IRS EPCRS, DOL fiduciary or disclosure issues, Form 5500 amendments, participant corrections and counsel review. VCP availability and outcome depend on current facts and procedures.[29][30][31]

Fourteen Operational Controls for Restatement Files

These controls are intentionally operational, because restatement failure usually shows up in payroll, statements, notices or filings.

Keep a restatement inventory with provider, cycle, opinion-letter date, document version and signer date
Require one owner for the master evidence file
Separate basic plan document, adoption agreement, trust, board authority and SPD
Use a redline for every restated election
Map old elections to new elections before signature
Block payroll and recordkeeper changes until the signed package is final
Require cited authority for each retroactive effective date
Screen employer-stock provisions for employee access, valuation and liquidity risk
Run anti-cutback and benefits-rights-features review before removing rights
Tie the restatement to SMM, SPD, 204(h), safe harbor, blackout, 404a-5 and QDRO handoffs
Reconcile plan name, EIN, plan number and sponsor identity to Form 5500 records
Keep superseded documents permanently with amendments and operational evidence
Log provider, TPA, recordkeeper, payroll, trustee and counsel responsibilities in writing
Escalate missed signatures or operation-before-signature to correction analysis

Nine Reproducible Date and Version Scenarios

Each scenario states its official-source basis and avoids unsupported cycle projection.

Cycle 3 DC adoption history

Facts: the IRS list page says virtually all third-cycle pre-approved DC opinion letters were issued at the same time, June 30, 2020, and adopting employers using those documents to restate for the 2017 Cumulative List were required to adopt by July 31, 2022. Arithmetic: IRS announced the end date rather than requiring the reader to add a period. Result: use July 31, 2022 only for the historical Cycle 3 conclusion.[3][4]

Cycle 4 provider submission window

Facts: IRS cycle table shows the fourth defined-contribution timely submission period as February 1, 2024 to January 31, 2025. Result: treat that period as the document provider submission window rather than the adopting-employer signature deadline.[1][4][5]

Cycle 4 public submission list

Facts: IRS list page says the fourth RAC list is for defined contribution plans submitted from February 1, 2024 to August 25, 2025 and covers the 2023 Cumulative List. Result: the list establishes current submission status rather than a final restatement deadline for adopting employers.[3]

No invented Cycle 4 RAC end

Facts: the IRS six-year cycle table accessed July 31, 2026 has a blank fourth DC RAC end cell. Result: identify Cycle 4 as in provider submission or listing status and wait for official text before using an employer adoption deadline.[3][4]

2025 RAL item for individually designed plan

Facts: IRS table shows the 2025 RAL general plan amendment deadline as December 31, 2027. Arithmetic: issuance year 2025 plus two following calendar years reaches 2027. Result: use the table date unless the specific list states another date.[9][11]

2024 RAL item

Facts: IRS table shows the 2024 RAL general plan amendment deadline as December 31, 2026. Arithmetic: issuance year 2024 plus two following calendar years reaches 2026. Result: keep the RAL item separate from any pre-approved restatement cycle.[9][11]

SMM after restatement adoption

Facts: a calendar-year retirement plan adopts a material restatement change on November 15, 2026. ERISA's general retirement-plan SMM rule uses 210 days after the plan-year end. Arithmetic: December 31, 2026 plus 210 days equals July 29, 2027. Result: use earlier special notice rules if they apply.[22][23][27]

204(h) handoff check

Facts: a covered applicable pension plan amendment significantly reduces future accruals effective July 1, 2026. Arithmetic: July 1, 2026 minus 45 days equals May 17, 2026. Result: first decide whether the plan is an applicable pension plan under the regulation before treating 204(h) as required or inapplicable.[19][27]

Provider change and plan number consistency

Facts: a restatement changes recordkeeper and document provider for the 2026 plan year. Result: reconcile plan name, sponsor EIN, plan number, trust accounts, signer and final prior-year reporting before the next Form 5500-series filing or amended filing conclusion.[32][33][34]

When to Revisit a ROBS Plan Restatement

Some changes require the sponsor to review the restated package before the next routine administration cycle.

Official-source changes

Recheck the restatement file when official sources change in these ways:

  • IRS announces Cycle 4 defined-contribution opinion letters, an adopting-employer adoption period, or a fourth RAC end date.
  • IRS updates the pre-approved plan list, RAL, OC List, EPCRS page, Revenue Procedure program, Form 5500 instructions, or ROBS compliance materials.
  • DOL updates SPD, SMM, furnishing, fiduciary, blackout, fee-disclosure, annual-reporting or record-retention guidance.
  • eCFR, OLRC, IRS or DOL links fail, redirect to materially different authority, or show a newer controlling date.

Company or plan changes

Recheck the signed package when the company or plan changes in these ways:

  • The sponsor changes document provider, TPA, recordkeeper, payroll system, trustee or counsel.
  • The company hires employees, changes ownership, adds outside equity, redeems shares, buys or sells a business, or prepares to terminate the plan.
  • Plan operation does not match the signed adoption agreement, including eligibility, contributions, loans, distributions, employer-stock access or notice timing.
  • A missed signature, late adoption, unsupported effective date, valuation issue, Form 5500 inconsistency or participant complaint points to correction analysis.

Frequently Asked Questions

Common restatement questions, with the same answers used for structured search results.

What is a ROBS plan restatement?

A ROBS plan restatement is a newly adopted full plan document package for future administration. Prior documents, amendments, elections, operations and records remain part of the evidence chain for earlier plan rights and operations.[1][3][8][15][24]

How is a restatement different from an amendment?

An amendment changes selected provisions of an existing plan document. A restatement replaces the full document set, commonly including the basic plan document, adoption agreement, trust or custodial references, and incorporated amendments. Both require signature authority, effective-date control, operational implementation and participant handoffs.[5][8][22][23]

What is an adoption agreement?

An adoption agreement is the election document used with many pre-approved plans. The basic plan document contains common language, while the adoption agreement records employer elections such as eligibility, compensation, contributions, vesting, distributions, loans and employer-stock features.[1][5][6]

What is a basic plan document?

A basic plan document is the pre-approved provider's base plan language. The adopting employer usually uses it with an adoption agreement and must keep the complete package, opinion letter and signed elections together.[1][5][6]

What does an IRS opinion letter cover?

For a pre-approved plan, the IRS opinion letter addresses the form of the approved document. Adopting employer elections, operation, a ROBS stock purchase, valuation, correction, notices, fiduciary decisions and business outcomes require separate review.[5][13][14][15]

Do pre-approved defined-contribution plans have a mandatory six-year cycle?

Yes. IRS describes six-year remedial amendment cycles for pre-approved plans. The current official cycle table shows the third defined-contribution timely submission period and the fourth defined-contribution timely submission period, while the IRS list page states the third-cycle employer adoption deadline was July 31, 2022.[3][4]

What was the Cycle 3 defined-contribution restatement deadline?

IRS states that adopting employers using third-cycle pre-approved defined-contribution documents to restate for the 2017 Cumulative List were required to adopt the plan by July 31, 2022. That historical deadline applies to Cycle 3 rather than the current Cycle 4 employer-adoption question.[3][4]

Has the IRS announced a Cycle 4 adopting-employer restatement deadline?

The official pages accessed for this article identify Cycle 4 defined-contribution provider submissions from February 1, 2024 to January 31, 2025 and a public list of submissions through August 25, 2025. The six-year cycle table leaves the fourth RAC end date blank, so the supported conclusion is provider submission and listing status rather than an adopting-employer deadline.[1][3][4][5]

Do individually designed plans follow a six-year restatement cycle?

Individually designed plans follow the RAL, operational compliance requirements, discretionary amendment timing and available determination-letter windows under the current official framework. IRS states the former five-year cycle ended January 1, 2017.[8][9][11][12]

Can a ROBS company rely on the provider's opinion letter after changing elections?

Reliance depends on staying within the pre-approved document and employer-reliance rules. IRS cautions that adopting employers generally rely on the pre-approved plan's opinion letter, but changes to the plan may affect that reliance and can require a determination-letter analysis if current procedures allow an application.[2][5][6][14]

What dates must the restatement file track?

Track provider cycle dates, adoption package date, signer date, restatement effective date, operational implementation date, participant-communication date, recordkeeper conversion date, payroll conversion date, Form 5500 plan-year reporting date and any correction date. Each date answers a different evidence question.[5][8][10][22][23][34]

Can a restatement remove employer-stock access for later employees?

A restatement should treat removal of employer-stock access for later employees as a high-risk ROBS change requiring review before signature. IRS ROBS materials identify post-setup amendments that prevent other participants from purchasing employer stock or participating as recurring concerns tied to coverage, discrimination and benefits-rights-features failures.[15][16][18][21]

Does a restatement require an SMM or updated SPD?

The participant handoff depends on what changed and what communication rule is triggered. ERISA requires SPD and SMM furnishing under specified timing rules, and special notices such as 204(h), safe harbor, blackout or fee notices may apply to particular facts.[22][23][27][28]

Can EPCRS fix a missed restatement?

EPCRS can correct a missed restatement only when the failure and facts fit current IRS correction rules. SCP, VCP and Audit CAP are correction lanes with fact-specific eligibility, procedure, evidence and agency-review consequences, and DOL fiduciary or disclosure issues may need separate handling.[30][31]

What should be kept after signing a restatement?

Keep the signed restatement, adoption agreement, basic plan document, trust or custodial documents, opinion letter, prior documents, all interim and discretionary amendments, board authority, redlines, election inventory, implementation crosswalk, participant communications, payroll and recordkeeper proof, Form 5500 handoff, valuation records and correction analysis.[5][15][24][25][29][34]

Official Sources, Currency and Limits

Every material cycle, reliance, date, notice, correction and responsibility claim cites official sources nearby.

Access date for all listed sources: July 31, 2026. The source list contains 36 official IRS, DOL, OLRC and dated eCFR API sources; no commercial, forum or AI source is used. OLRC pages state laws in effect on July 31, 2026 for cited Code and ERISA sections. eCFR API URLs use the latest verified reachable July 21, 2026 dated snapshots because ordinary HTML access can be unreliable. IRS and DOL page update dates vary and are disclosed in the source notes. This guide provides general education only; a specific ROBS transaction, plan qualification, restatement deadline beyond cited official text, determination-letter reliance, correction outcome, notice package, Form 5500 conclusion, valuation or participant result requires fact-specific professional review.

  1. [1] IRS pre-approved retirement plans

    Accessed July 31, 2026. IRS page last updated April 3, 2026. Used for pre-approved plan definition, provider role, fourth-cycle LRM context, standardized and nonstandardized plan language, trust document limits, and adopting-employer framing.

  2. [2] IRS pre-approved plan adopting employer

    Accessed July 31, 2026. Used for adopting employer adoption obligations, two-year adoption period framing, reliance cautions, and when employer action may affect reliance.

  3. [3] IRS list of pre-approved plans

    Accessed July 31, 2026. IRS page last updated June 28, 2026. Used for Cycle 3 defined-contribution list, virtually all June 30, 2020 opinion-letter issuance, July 31, 2022 adoption deadline, and Cycle 4 submission-list status through August 25, 2025.

  4. [4] IRS six-year cycle for pre-approved plans

    Accessed July 31, 2026. IRS page last updated April 3, 2026. Used for mandatory pre-approved remedial amendment cycle table and current fourth defined-contribution submission period, with no fourth RAC end listed.

  5. [5] IRS pre-approved plan submission procedures

    Accessed July 31, 2026. IRS page last updated November 27, 2025. Used for Form 4461 packet content, redline encouragement, adoption agreement, interim amendment certification, official opinion letter, non-reliance on interim notifications, and adopting-employer reliance limits.

  6. [6] Rev. Proc. 2023-37

    Accessed July 31, 2026. Used for the current pre-approved plan opinion-letter program, fourth DC cycle, standardized and nonstandardized pre-approved plan framework, employer reliance, and cycle procedures.

  7. [7] Rev. Proc. 2017-41

    Accessed July 31, 2026. Used for prior pre-approved program changes and the merger of M&P and VS concepts into the single opinion-letter program.

  8. [8] IRS amend or update a plan

    Accessed July 31, 2026. IRS page last updated July 23, 2026. Used for amendment and restatement resources, cumulative list, RAL, OC List, LRMs, pre-approved cycles, and individually designed cycle history.

  9. [9] IRS Required Amendments List

    Accessed July 31, 2026. IRS page last updated July 21, 2026. Used for individually designed RAL deadlines, 2024 and 2025 RAL dates, and the statement that post-2015 cumulative lists are for pre-approved plan cycles.

  10. [10] IRS Operational Compliance List

    Accessed July 31, 2026. Used for operational effective-date controls and OC List limits.

  11. [11] Rev. Proc. 2022-40

    Accessed July 31, 2026. Used for the current RAL and OC List remedial amendment framework.

  12. [12] Rev. Proc. 2016-37

    Accessed July 31, 2026. IRS page last updated July 23, 2026. Used for the end of the five-year individually designed plan cycle, RAL framework, no interim amendments for individually designed plans under that procedure, discretionary amendment timing, and determination-letter availability.

  13. [13] IRS determination, opinion and advisory letters

    Accessed July 31, 2026. IRS page last updated July 23, 2026. Used for letter-type distinctions and application paths.

  14. [14] IRS scope and benefit of a favorable letter

    Accessed July 31, 2026. Used for scope of letter reliance and document-versus-operation limits.

  15. [15] IRS ROBS compliance project

    Accessed July 31, 2026. IRS page last updated November 16, 2025. Used for ROBS transaction structure, recurring failures, determination-letter limits, employee access, valuation, Form 5500, Form 1120, and Form 1099-R concerns.

  16. [16] IRS ROBS examination guidelines

    Accessed July 31, 2026. IRS memorandum dated October 1, 2008. Used as examination context for plan document, stock, valuation, adequate consideration, records, promoter fees, discrimination and prohibited transactions, not as current approval.

  17. [17] 26 USC 401

    OLRC text contains laws in effect on July 31, 2026. Used for qualified trust, 401(k), exclusive benefit, safe harbor and employer-security context.

  18. [18] 26 USC 410

    OLRC text contains laws in effect on July 31, 2026. Used for participation and coverage boundaries.

  19. [19] 26 USC 411(d)(6)

    OLRC text contains laws in effect on July 31, 2026. Used for anti-cutback protection.

  20. [20] 26 CFR 1.411(d)-4

    Dated eCFR API snapshot July 21, 2026; accessed July 31, 2026. Used for protected benefit and optional form rules.

  21. [21] 26 CFR 1.401(a)(4)-4

    Dated eCFR API snapshot July 21, 2026; accessed July 31, 2026. Used for benefits, rights and features nondiscrimination analysis.

  22. [22] 29 USC 1022

    OLRC text contains laws in effect on July 31, 2026. Used for SPD and SMM content standards.

  23. [23] 29 USC 1024

    OLRC text contains laws in effect on July 31, 2026. Used for SMM, SPD, annual report and furnishing timing.

  24. [24] 29 USC 1027

    OLRC text contains laws in effect on July 31, 2026. Used for six-year report and disclosure record retention floor.

  25. [25] 29 USC 1104

    OLRC text contains laws in effect on July 31, 2026. Used for fiduciary prudence, following documents, diversification and service-provider monitoring.

  26. [26] 29 USC 1108(e)

    OLRC text contains laws in effect on July 31, 2026. Used for qualifying employer-security acquisition or sale conditions.

  27. [27] 26 CFR 54.4980F-1

    Dated eCFR API snapshot July 21, 2026; accessed July 31, 2026. Used for 204(h) notice recipient and timing handoff when applicable.

  28. [28] 29 CFR 2520.104b-1

    Dated eCFR API snapshot July 21, 2026; accessed July 31, 2026. Used for ERISA document furnishing and electronic-delivery framework.

  29. [29] DOL Meeting Your Fiduciary Responsibilities

    Accessed July 31, 2026. DOL publication dated September 2021. Used for fiduciary process, service-provider monitoring, plan documents, records and disclosures.

  30. [30] IRS EPCRS overview

    Accessed July 31, 2026. IRS page last updated July 31, 2026. Used for SCP, VCP, Audit CAP and correction boundaries.

  31. [31] Rev. Proc. 2021-30

    Accessed July 31, 2026. Used as the governing EPCRS procedure identified by IRS for correction method and VCP boundaries.

  32. [32] IRS Form 5500 Corner

    Accessed July 31, 2026. Used for Form 5500-series coordination and extension handoff.

  33. [33] DOL Form 5500 Series

    Accessed July 31, 2026. Used for EFAST2 annual reporting coordination.

  34. [34] 2025 Instructions for Form 5500

    Accessed July 31, 2026. Used for amended return, plan name, EIN, plan number, signatures, final return and records in annual reporting.

  35. [35] IRS plan amendments before termination

    Accessed July 31, 2026. Used for termination amendment handoff and the rule that a terminating plan must be updated for applicable law.

  36. [36] IRS plan sponsor responsibilities

    Accessed July 31, 2026. Used for plan sponsor operating responsibility, written plan, employee information, notices, records and ongoing compliance controls.

Keep the restated document and the superseded chain together

The signed restatement answers today's administration question. The historical chain answers audit, claim, valuation, filing and correction questions.

Amendment controls Annual checklist