Build practical skill in reading plan provisions, classifying contributions, determining eligibility and vesting, calculating allocations and loans, and administering distributions. This free guide covers ASPPA's current QKA-1 Plan Management curriculum as of October 17, 2026, with twenty original multiple-choice questions and sixty substantive lessons. The nine-module allocations are editorial, not published examination weights. The actual QKA-1 examination has 75 multiple-choice questions and allows 150 minutes; this is a representative preview. Examples identify controlling provisions and use 2026 IRS limits where relevant. ASPPA citations establish curriculum relevance; IRS citations support the supplied limits and catch-up rules. QKA-2 testing detail and future curriculum versions remain outside this guide's scope.
What this guide covers
Practice QKA-1 decisions with 20 original questions and 60 lessons covering the nine current modules.
Plan Types
1. Defined contribution accounts versus benefit promises
A defined contribution plan establishes actual participant accounts. Contributions, investment experience, expenses, and distributions determine each account's value. A defined benefit plan instead promises a benefit under a formula, with funding calculated to support that promise. This distinction determines which records describe the benefit and who bears funding uncertainty. An individual statement or lump-sum payment option does not by itself establish the classification. Administrators should identify the governing promise before interpreting account statements, investment results, employer obligations, or participant payment elections.
Worked example: An employer contributes $4,000 to an employee's profit-sharing account, which subsequently loses $300 through investment performance. The account becomes $3,700 before other transactions. A pension promising a formula benefit does not automatically reduce that promised benefit by the same investment loss.
Common mistake: Assuming any plan that displays a dollar balance is defined contribution overlooks hypothetical accounts used to express defined benefits.
Official syllabus reference: [1]
2. Discretionary profit-sharing and required money purchase funding
A profit-sharing document can allow the employer to determine whether and how much to contribute annually. Its name does not require current business profits before contributions are possible. A money purchase pension document instead establishes a required employer contribution formula. Both can maintain actual participant accounts, making both defined contribution arrangements. The operational difference concerns the employer's funding commitment, rather than account ownership or investment allocation. An administrator must distinguish the annual decision to contribute from the document's separate rules for allocating an approved contribution.
Worked example: A company selects a $60,000 discretionary profit-sharing contribution after reviewing cash flow. Its administrator then allocates that amount under the document. A separate money purchase proposal requiring 6% of eligible compensation would create a formula-based commitment rather than the same annual discretion.
Common mistake: Treating a discretionary contribution decision as permission to improvise participant allocations ignores the binding allocation formula in the document.
Official syllabus reference: [1]
3. Cash balance pay credits and interest credits
A cash balance plan expresses a defined benefit through hypothetical accounts receiving pay credits and interest credits under its formula. Those balances measure the benefit promise; they are not simply shares of actual trust investments. Actual asset performance can differ from credited interest, affecting funding calculations without automatically changing participant credits. Administration therefore requires both benefit records and actuarial funding information. When reviewing a statement, identify whether its interest credit follows the document's specified method rather than assuming it equals the trust's investment return.
Worked example: A document credits an employee's hypothetical account with a pay credit and formula interest totaling $5,200. Trust investments produce a lower return. The benefit record still receives the promised formula credits, while the investment difference enters the plan's funding analysis.
Common mistake: Replacing a cash balance interest credit with actual portfolio earnings confuses the participant benefit formula with the trust's investment experience.
Official syllabus reference: [1]
4. The 401(k) feature inside a qualified plan
A 401(k) arrangement permits eligible employees to elect salary deferrals within a qualified defined contribution plan. The same plan may also contain matching, nonelective, profit-sharing, or employee after-tax sources. These sources can have different eligibility, allocation, vesting, and distribution provisions. Calling the entire arrangement a 401(k) plan does not make every contribution an elective deferral. Source classification is essential because individual deferral limits, annual-additions rules, participant ownership, and testing consequences do not apply identically to every dollar deposited into the trust.
Worked example: An employee defers $3,000, receives a $1,200 match, and receives a $2,000 profit-sharing allocation. The administrator records three sources. Only the $3,000 is the employee's elective deferral, even though all three amounts appear on the same participant statement.
Common mistake: Combining all deposits into one deferral total obscures employer contributions and can produce incorrect limit, vesting, and distribution decisions.
Official syllabus reference: [1]
5. 403(b) sponsorship and deferral coordination
A 403(b) arrangement is available to eligible types of employers, including public educational organizations and qualifying tax-exempt organizations. It is not interchangeable with a private company's qualified 401(k) plan merely because both accept salary deferrals. Employer eligibility, funding arrangements, and applicable participation rules require separate analysis. Nevertheless, an individual's 401(k) and 403(b) elective deferrals generally share the same basic individual deferral ceiling. Specialized 403(b) catch-up provisions require their own eligibility review and should not be assumed from age alone or applied automatically to a 401(k).
Worked example: A teacher makes elective deferrals to a school's 403(b) and later joins a business offering a 401(k). The administrator considers the teacher's earlier deferrals when evaluating remaining individual deferral capacity rather than treating the two labels as separate annual allowances.
Common mistake: Assuming different plan names always create separate elective deferral ceilings can allow an individual to exceed the shared limit.
6. SEP employer deposits versus SIMPLE salary reduction
SEP and SIMPLE IRA arrangements both use individual retirement accounts, but their contribution structures differ. An ordinary SEP is primarily an employer-contribution arrangement; a SIMPLE IRA generally combines employee salary reduction with required employer contributions under its applicable design. Neither should be administered by importing a qualified 401(k) document's elections. Contribution limits, employer eligibility, participant eligibility, and distribution restrictions need the correct arrangement-specific rules. Recognizing the funding mechanism helps an administrator interpret whether a payroll deduction is authorized or whether an employer contribution obligation exists.
Worked example: A small employer asks its bookkeeper to begin salary reduction under an ordinary SEP. The bookkeeper identifies that the selected arrangement does not provide that feature and distinguishes it from a SIMPLE IRA, which is designed to accept employee salary reduction contributions.
Common mistake: Treating every employer-sponsored IRA arrangement as permitting identical payroll deferrals overlooks the different contribution mechanisms of SEP and SIMPLE arrangements.
7. Governmental 457(b) limits remain a separate analysis
A governmental 457(b) arrangement is an eligible deferred compensation plan with its own contribution-limit framework. Its limit is generally separate from the individual elective deferral ceiling shared by 401(k) and 403(b) arrangements. That separation does not make contributions unlimited or justify importing 401(k) catch-up mechanics without checking the applicable 457(b) rules. Governmental and nongovernmental 457(b) arrangements also have important differences. Administrators should identify the sponsor and arrangement before coordinating contribution amounts, catch-up eligibility, portability, or participant communications about available savings capacity.
Worked example: A public employee participates in both a governmental 457(b) arrangement and a 403(b). Payroll reviews each arrangement's applicable limit separately instead of subtracting every 457(b) deposit from the 403(b) allowance. It still verifies compensation and catch-up conditions for each arrangement.
Common mistake: Extending the separate 457(b) limit to every deferred compensation arrangement ignores sponsor-specific rules and differences between governmental and nongovernmental plans.
Plan Qualification
8. Reading the complete governing document package
A plan's operational terms may be distributed across a basic document, adoption agreement, amendments, and incorporated provisions. Reading only one page can miss an election or later change. The administrator must establish which provisions apply to the transaction date and contribution source. Participant summaries and payroll worksheets help communicate or implement those terms but do not replace the governing package. Conflicting materials require separate analysis of document compliance and disclosure accuracy. Effective dates matter because a correctly adopted future amendment does not necessarily govern an earlier allocation.
Worked example: The basic document permits several entry schedules, the adoption agreement selects quarterly entry, and a later amendment changes only employer matching eligibility. The administrator retains quarterly deferral entry because the matching amendment does not alter that separate provision.
Common mistake: Reading an available option in the basic document as the employer's election can create operational terms the employer never adopted.
Official syllabus reference: [1]
9. Preapproved document reliance has boundaries
A preapproved plan uses a document framework reviewed through the IRS preapproval process. Employer adoption still requires valid elections, appropriate execution, and operation consistent with the adopted terms. Reliance associated with the document does not certify payroll accuracy, employee classifications, contribution calculations, or every employer modification. An administrator should distinguish document-form assurance from operational compliance. A favorable document review cannot resolve a failure caused by using the wrong compensation definition or allocation method. Employer-specific changes may also affect the scope of available reliance.
Worked example: A provider supplies a preapproved document allowing either an annual or payroll-period match. The employer elects the annual method, but payroll uses a payroll-period cap without reconciliation. The provider's document approval does not establish that payroll administered the employer's election correctly.
Common mistake: Treating a preapproved document as an annual operational audit overlooks employer elections, amendments, data errors, and implementation failures.
Official syllabus reference: [1]
10. IRS tax qualification and DOL fiduciary oversight
Retirement plan administration can involve overlapping federal responsibilities. The IRS administers tax-qualification rules and associated tax consequences. The Department of Labor administers applicable ERISA fiduciary, reporting, disclosure, and participant-contribution protections. A transaction may raise issues under more than one framework, so identifying one agency does not eliminate the other concern. For example, a contribution problem can require both account correction and review of handling plan assets. The administrator should classify the issue by the underlying obligation rather than assuming every retirement-plan matter belongs to one regulator.
Worked example: An employer delays transferring payroll deductions to the plan and also misallocates the deposits after transfer. Reviewing only the allocation formula misses the separate handling-of-assets issue. The administrator identifies both operational correction and applicable fiduciary compliance considerations.
Common mistake: Assuming IRS document approval establishes compliance with every ERISA fiduciary obligation confuses separate regulatory responsibilities and types of review.
Official syllabus reference: [1]
11. Qualification in form versus qualification in operation
Qualification in form concerns whether the document contains required provisions and valid adopted terms. Qualification in operation concerns whether actual administration follows the document and applicable requirements. Either dimension can fail independently. A compliant allocation formula does not help if payroll uses a different formula, while accurate payroll practice does not repair a missing required document provision. Separating these categories helps determine the evidence needed and the available correction approach. Administrators should reconstruct the required result before deciding whether a document amendment, account adjustment, or other corrective action is appropriate.
Worked example: The signed document promises an employer allocation based on compensation, but the administrator divides the contribution equally among participants. The written formula may be acceptable in form; the equal-dollar calculation creates an operational failure requiring participant-level analysis.
Common mistake: Describing every error as a document defect can lead to an amendment that leaves incorrect participant allocations uncorrected.
Official syllabus reference: [1]
12. Exclusive-benefit assets and administrative expenses
Plan assets are held for participants and beneficiaries and may pay permissible plan expenses under applicable rules. They are not an unrestricted employer operating account. An expense requires analysis of its purpose, reasonableness, authorization, and whether it is properly a plan rather than employer responsibility. Fiduciaries must also consider conflicts and prohibited-transaction concerns where relevant. The fact that a payment relates broadly to employee benefits does not establish that the retirement trust may pay it. Source documents and invoices should support the actual nature of the service.
Worked example: A service invoice combines participant account administration with work on the employer's unrelated business financing. The administrator separates the services before approving payment, rather than charging the entire invoice to the trust because one portion relates to the retirement plan.
Common mistake: Assuming every invoice mentioning the retirement plan is payable from plan assets overlooks the purpose and responsibility for each expense.
Official syllabus reference: [1]
13. Coverage, contribution testing, and top-heavy analysis
Coverage examines which employee groups benefit under a plan. ADP evaluates elective deferral percentages, while ACP generally evaluates matching and employee after-tax contribution percentages. Top-heavy analysis instead focuses on benefit or account concentration among key employees. HCE status and key-employee status are separate classifications serving different tests. Passing one analysis does not establish compliance with the others. Although detailed testing belongs chiefly to QKA-2, a QKA-1 administrator needs these distinctions to collect appropriate census, ownership, compensation, and contribution information and recognize when a plan design changes the required review.
Worked example: A plan includes many employees but has large balances belonging to owners. Broad participation may support coverage, yet it does not resolve top-heavy status. Likewise, acceptable elective deferral percentages do not establish that employee after-tax contributions satisfy ACP requirements.
Common mistake: Using HCE and key employee as interchangeable labels can corrupt classifications and produce conclusions about the wrong compliance test.
Official syllabus reference: [1]
14. Correction starts with the participant-level shortfall
A qualification failure should be defined precisely before selecting a correction approach. Identify the governing requirement, affected period, participants, contribution sources, and difference between required and actual treatment. Correction may involve contributions, earnings adjustments, distributions, document action, or other approved procedures depending on the failure. Available IRS correction pathways have conditions; discovering an error does not establish automatic eligibility for any particular route. Neither does it make immediate disqualification inevitable. A useful correction file explains the reconstruction, method selected, implementation evidence, and controls addressing the cause.
Worked example: Payroll excluded an eligible employee for several pay periods. The administrator reconstructs compensation, election opportunities, matching effects, and the affected dates before choosing a correction method. Simply enrolling the employee now would not determine whether the earlier missed opportunity also needs correction.
Common mistake: Fixing only future payroll can leave an existing participant shortfall unresolved even when the original administrative cause has been removed.
Official syllabus reference: [1]
Employee Contributions
15. Pretax and designated Roth deferrals share one ceiling
Pretax and designated Roth contributions are both elective deferrals when made through salary reduction elections. Pretax deferrals generally postpone federal income taxation, while designated Roth deferrals are included in current income and receive separate distribution tax treatment. Their different tax labels do not create separate elective deferral allowances. For 2026, the basic limit is $24,500 before an applicable catch-up. Administration must aggregate the two categories while maintaining separate source records for taxation. Roth treatment also does not remove ordinary eligibility, payroll-election, or applicable testing requirements.
Worked example: An employee directs $14,000 of 2026 deferrals to pretax and $8,000 to designated Roth. Total regular elective deferrals are $22,000, leaving $2,500 under the 2026 basic ceiling, assuming sufficient compensation and no other restriction or deferrals elsewhere.
Common mistake: Giving pretax and designated Roth elections separate annual allowances doubles a shared limit and can create an excess deferral.
16. Employee after-tax contributions are not Roth deferrals
Employee after-tax contributions come from compensation already subject to income tax, but they are not designated Roth elective deferrals. They generally do not consume the basic elective deferral limit, yet they count toward annual additions and can implicate ACP testing. Their earnings and distribution basis require separate accounting. A plan must actually authorize the contribution source before payroll accepts it. Calling any post-tax deduction Roth conceals these distinctions and can misstate both testing inputs and taxable amounts. Contribution classification begins with the governing election and source, not the paycheck label.
Worked example: A plan permits $5,000 of employee after-tax contributions after an employee has used regular elective deferral capacity. The administrator checks remaining annual-additions room and records after-tax basis separately, rather than treating the deposit as another designated Roth elective deferral.
Common mistake: Assuming all contributions taxed before deposit have identical limits and distribution treatment erases the distinction between after-tax contributions and Roth deferrals.
17. Individual elective deferrals follow the employee
The individual elective deferral ceiling generally aggregates applicable deferrals across employers, even when the employers are unrelated. A job change does not reset the calendar-year allowance. Payroll at one employer may not automatically know the employee's earlier deferrals, making accurate participant information important. This individual aggregation is distinct from employer aggregation rules governing annual additions or coverage. Administrators should identify the arrangement types involved because governmental 457(b) deferrals generally have a separate limit, while 401(k) and 403(b) deferrals generally share the basic individual ceiling.
Worked example: During 2026, an employee defers $10,000 at a former employer and then joins another 401(k) plan. With no catch-up eligibility or other restriction, the $24,500 basic limit leaves $14,500 rather than a fresh $24,500 at the new employer.
Common mistake: Relying solely on the new employer's year-to-date payroll total can overlook earlier deferrals subject to the same individual limit.
18. Age-specific catch-up capacity in 2026
Catch-up capacity is additional elective deferral capacity for eligible participants under applicable plan provisions. For 2026, the ordinary age-50 catch-up limit is $8,000, while participants turning 60, 61, 62, or 63 during the year can have an $11,250 limit in covered arrangements. The enhanced age-band provision began in 2025; it is not a future proposal. Catch-up classification requires exceeding an applicable regular, plan, or testing limit, rather than merely labeling the first payroll deposit catch-up. Compensation and the plan's actual catch-up provisions still matter.
Worked example: An eligible participant turns 61 in 2026 and can use the full enhanced catch-up. With sufficient compensation and no lower restriction, $24,500 of regular deferrals plus $11,250 of catch-up produces $35,750 of potential elective deferrals for that year.
Common mistake: Applying the enhanced catch-up to every participant older than 60 overlooks the specific age-60–63 band and the applicable year.
19. Roth catch-up uses prior-year sponsoring-employer FICA wages
Beginning in 2026, the Roth catch-up requirement applies to affected participants based on prior-year FICA wages from the sponsoring employer, using the applicable indexed threshold. The supplied IRS reference identifies a $150,000 threshold for determining 2026 treatment. Household income, investment income, and a spouse's wages are not substitutes for this criterion. The requirement concerns catch-up contributions rather than automatically converting all regular deferrals to Roth. Historical transition relief should not be treated as permanently exempting 2026, and later general applicability dates for regulations should not erase the statutory start.
Worked example: An employee's 2025 sponsoring-employer FICA wages were $152,000, and the employee makes catch-up contributions in 2026 under a plan with Roth features. The wage criterion triggers Roth catch-up treatment even if household taxable income is reduced substantially by unrelated deductions.
Common mistake: Using household adjusted gross income to classify mandatory Roth catch-ups substitutes a different income measure for the sponsoring-employer FICA wage criterion.
20. Annual additions capture more than elective deferrals
Annual additions generally include regular elective deferrals, employer contributions, employee after-tax contributions, and allocated forfeitures. Valid catch-up contributions are excluded. For 2026, the defined contribution dollar limit is $72,000, with a separate compensation-based limitation also requiring attention. This is not the same limit as the $24,500 basic elective deferral ceiling. A participant may have room for employer contributions after exhausting regular deferrals, or have insufficient annual-additions room for a proposed after-tax deposit. Accurate source classification and applicable employer aggregation are necessary before calculating remaining capacity.
Worked example: A participant has $24,500 of regular deferrals and $35,000 of employer contributions in 2026. Before considering any other additions and assuming sufficient compensation, $12,500 remains under the $72,000 dollar ceiling. A valid catch-up does not consume that remaining amount.
Common mistake: Subtracting only employee deferrals from the annual-additions ceiling ignores employer allocations, after-tax contributions, and other additions that may consume capacity.
21. Payroll deductions and prompt trust remittance
An employee's payroll deduction and the trust's receipt of that deduction are separate events. Applicable ERISA rules require participant contributions to be transmitted promptly based on when they can reasonably be segregated from employer assets, subject to any applicable safe harbor. An outer limit should not be treated as routine permission to delay when earlier segregation is feasible. Administration should reconcile payroll dates, withheld amounts, transfer dates, and trust receipts. A delay can create lost earnings and fiduciary concerns even when the contribution amount eventually reaches the correct participant account.
Worked example: Payroll withholds deferrals on Friday, routinely prepares accurate transfer data immediately, but leaves the funds with the employer for an unexplained extended period. The administrator reviews the actual segregation capability and affected earnings rather than concluding eventual deposit resolves the entire issue.
Common mistake: Measuring compliance only by whether the annual contribution total matches payroll overlooks the separate timing obligation for participant money.
Official syllabus reference: [1]
Distributions
22. A distributable event is source-specific
A participant request does not by itself establish that a plan may distribute every account source. The administrator must identify an applicable distributable event, confirm that the document permits the requested payment, and determine which sources are available. Severance, certain in-service events, hardship provisions, and other authorized events have different conditions. Fully vested status establishes ownership but does not necessarily establish immediate withdrawal access. Operational review should therefore separate vesting, event eligibility, source availability, and payment form before producing a distribution calculation or promising a payment date.
Worked example: A participant is fully vested in elective deferrals but remains employed and asks for an unrestricted withdrawal. The administrator examines the plan's in-service provisions and source restrictions; ownership alone does not establish that the requested payment can be made immediately.
Common mistake: Equating full vesting with unrestricted withdrawal access confuses nonforfeitable ownership with the separate legal and document conditions for payment.
Official syllabus reference: [1]
23. Payment forms, participant consent, and beneficiary rights
Distribution administration requires checking the forms offered by the document and any applicable consent protections. A lump sum, installment arrangement, or annuity can produce different payment mechanics, but availability depends on the plan and relevant rules. Some plans or benefits involve spousal protections that cannot be replaced by an ordinary beneficiary form. Participant notices and elections must address the actual benefit being paid. Death benefits also require review of the valid beneficiary designation, governing default provisions, and any controlling spousal rights rather than reliance on informal family instructions.
Worked example: A participant requests installments, but the document offers only a lump sum for that benefit. Before processing an alternative, the administrator verifies the permitted forms. If the participant dies before payment, the beneficiary and any applicable spousal protections require a separate review.
Common mistake: Assuming a signed request authorizes any payment form overlooks document limits and consent protections that can apply independently of participant preference.
Official syllabus reference: [1]
24. Direct rollovers prevent the withholding replacement gap
A direct rollover transfers an eligible rollover distribution to an eligible receiving arrangement rather than paying it to the participant. A payment made personally can involve mandatory withholding, leaving the participant with less cash than the gross distribution. Rolling over the full gross amount then requires replacing the withheld portion from other funds within the applicable rollover period. Withholding is a tax payment, not a receiving-account deposit. Administrators must also classify the distribution correctly because not every payment, including hardship distributions and required minimum distributions, is eligible for rollover.
Worked example: A gross eligible distribution of $10,000 produces an $8,000 check after the stated $2,000 withholding. To complete a full rollover, the participant deposits $10,000 using $2,000 from savings. Depositing only the check amount leaves part of the gross distribution unrolled.
Common mistake: Treating withheld tax as money automatically deposited into the receiving IRA overstates the rollover and understates the portion left outside it.
Official syllabus reference: [1]
25. Designated Roth distributions depend on qualification
Designated Roth contributions are taxed when contributed, but their earnings are not automatically tax-free whenever withdrawn. A qualified distribution requires satisfaction of the applicable holding-period condition and a qualifying event. A nonqualified payment generally requires distinguishing contribution basis from earnings under the applicable allocation rules. The administrator must preserve source and holding-period records rather than applying pretax-source taxation or assuming all Roth withdrawals are qualified. Rollover destination and treatment also require attention because a Roth plan account and a Roth IRA do not have identical administrative rules.
Worked example: A participant requests a designated Roth payment containing both contribution basis and investment earnings. The administrator checks the holding period and qualifying event before determining treatment. The fact that payroll previously taxed the contributions does not by itself make the earnings tax-free.
Common mistake: Calling every designated Roth withdrawal tax-free overlooks qualification conditions and the different treatment of basis and earnings in nonqualified payments.
Official syllabus reference: [1]
26. Hardship need and tax exceptions are separate
A hardship distribution addresses an immediate and heavy financial need under applicable plan and legal requirements. The document must authorize the feature and identify available sources and administrative conditions. Approval establishes permission to pay under hardship rules, not an income-tax exclusion or an automatic exception to additional tax on early distributions. Hardship payments are not eligible rollover distributions. Administrators should distinguish the evidence supporting the need, the amount available, and the payment's tax classification. A participant's serious financial circumstances do not merge these separate determinations into one approval.
Worked example: A participant receives an approved pretax hardship payment for a qualifying expense. The administrator explains that the payment is still taxable and cannot be rolled over. Any additional-tax exception must be evaluated separately rather than inferred from the hardship approval itself.
Common mistake: Assuming a qualifying hardship automatically eliminates early-distribution tax consequences confuses access to plan funds with the participant's separate tax treatment.
Official syllabus reference: [1]
27. Required minimum distributions require their own calculation
Required minimum distribution administration begins by identifying the participant, applicable starting rules, account source, employment and ownership circumstances, and whether the payment is a lifetime or beneficiary distribution. The required amount uses the applicable balance and distribution-period method rather than an arbitrary withdrawal percentage. A required minimum distribution cannot be rolled over. Current law also treats designated Roth plan accounts differently from pretax accounts for lifetime required distributions. Avoid assuming one starting age or one beneficiary schedule applies universally; the relevant birth year, death facts, and statutory category must be established.
Worked example: A distribution worksheet supplies an applicable prior-year balance of $260,000 and a distribution period of 26.0 for a pretax source. The calculated amount is $10,000. The administrator separates that required payment from any additional amount potentially eligible for rollover.
Common mistake: Processing an entire account withdrawal as rollover eligible can improperly include the portion that must first satisfy a required minimum distribution.
Official syllabus reference: [1]
28. Qualified domestic relations orders assign plan benefits
A domestic relations order does not become payable merely because a court issued it. The plan administrator determines whether it satisfies the requirements for a qualified domestic relations order under established procedures. Review includes the parties, assigned benefit, applicable period, and compatibility with available plan benefits. During review, applicable benefit-preservation procedures can matter. The administrator should distinguish an alternate payee's assigned benefit from the participant's remaining benefit and follow the qualified order's terms. Informal divorce instructions or beneficiary changes are not substitutes for this qualification process.
Worked example: A divorce order assigns part of a participant's account to a former spouse. The administrator reviews the order against qualification requirements and plan procedures before establishing the alternate payee's entitlement, rather than paying solely because the participant agrees with the assignment.
Common mistake: Treating every divorce decree as immediately payable bypasses the qualification determination and can misstate both the participant's and alternate payee's rights.
Official syllabus reference: [1]
Participant Loans
29. Loan availability comes from the plan and policy
Participant loans are optional plan features, not a universal participant entitlement. A plan offering loans needs governing provisions and operational procedures addressing availability, limits, security, repayment, interest, fees, and default. The administrator must apply those provisions consistently while satisfying applicable requirements. A participant's investment balance alone does not establish an available loan amount because vesting, existing loans, historical balances, and policy restrictions may reduce capacity. Loan approval should therefore follow a complete eligibility and calculation review rather than beginning with the amount the participant wants to receive.
Worked example: A participant has a large vested account and requests a second loan. The statutory calculation might permit additional borrowing, but the plan's policy allows only one outstanding loan. The administrator applies that restriction rather than treating the statutory ceiling as a guaranteed benefit.
Common mistake: Assuming the maximum amount permitted by tax rules must be offered ignores a plan's ability to impose narrower loan provisions.
Official syllabus reference: [1]
30. Loan ceilings limit total debt before new proceeds
A maximum-loan calculation compares the applicable dollar ceiling with the vested-benefit-based ceiling, incorporating any required historical adjustment. These ceilings generally constrain total outstanding borrowing rather than the new check alone. Existing debt must therefore be considered before determining additional proceeds. The plan may impose a smaller limit or decline an otherwise permissible loan under its policy. Vested account value, not total unvested assets, is the relevant account measure for the benefit-based calculation. Using a worksheet that separates total capacity from incremental proceeds prevents double counting.
Worked example: A supplied worksheet establishes a $40,000 maximum total outstanding balance. The participant already owes $15,000, and the policy permits another loan. Additional capacity is $25,000, not $40,000, because the existing debt continues to occupy part of the total allowance.
Common mistake: Paying the full calculated total ceiling as new proceeds ignores existing debt and can create a loan exceeding the permitted outstanding balance.
Official syllabus reference: [1]
31. The historical balance adjustment limits rapid reborrowing
The loan lookback adjustment considers the highest outstanding balance during the relevant preceding period in relation to the current balance. Its purpose is to prevent a recent repayment from automatically restoring the entire dollar allowance for immediate borrowing. A current-balance-only calculation can therefore overstate available proceeds. Administrators need reliable loan histories, including loans implicated by applicable aggregation rules, rather than just today's statement. Once the adjusted total dollar ceiling is calculated, compare it with the vested-benefit ceiling and then determine how much additional borrowing remains after existing debt.
Worked example: Under a supplied 2026 worksheet, the starting dollar ceiling is $50,000, the historical high is $24,000, and current debt is $10,000. The adjusted total ceiling is $36,000. Before other restrictions, only $26,000 of additional borrowing remains.
Common mistake: Assuming a recent repayment immediately restores equal new borrowing capacity overlooks the historical-balance adjustment built into the maximum-loan calculation.
Official syllabus reference: [1]
32. Level amortization repays principal and interest
A compliant participant loan generally requires a repayment schedule that amortizes principal and interest through substantially level payments at required intervals, subject to applicable exceptions. The document and policy also establish the permitted term and interest methodology. A payment is not entirely principal; interest changes the balance reduction produced by each installment. Administrators should reconcile scheduled payments with actual collections and loan accounting. Merely collecting a regular payroll deduction does not prove proper amortization if the payment amount, interest calculation, frequency, or maturity date was entered incorrectly.
Worked example: A supplied loan schedule calls for twelve equal monthly payments of $430, with the first payment including $30 of interest. That first installment reduces principal by $400. Crediting the full $430 against principal would understate the remaining loan balance.
Common mistake: Treating every payroll loan payment as principal repayment ignores interest and can cause balances to diverge from the approved amortization schedule.
Official syllabus reference: [1]
33. Refinancing preserves old debt's repayment boundary
Refinancing combines repayment of an existing loan with a replacement borrowing arrangement, sometimes including new cash. Compliance requires reviewing both maximum-loan calculations and repayment-term rules. Replacing the note does not automatically restart the permissible term for old debt. Depending on the applicable refinancing method, the old and new portions may need separate amortization or another structure satisfying overlapping-loan rules. Administrators should distinguish the amount used to retire existing principal from the participant's incremental proceeds and document how each portion meets its applicable payoff requirements.
Worked example: A policy requires $12,000 of existing debt to be repaid within eighteen months but permits new proceeds over forty-eight months. A refinancing schedule can separately preserve the old balance's deadline while amortizing the new money over the longer permitted period.
Common mistake: Restarting the entire loan term whenever new proceeds are added can improperly extend repayment of the participant's existing debt.
Official syllabus reference: [1]
34. Default and deemed distribution do not erase the loan
Missed loan payments require review under the policy and applicable default rules, including any permitted cure treatment. A resulting deemed distribution can create tax consequences without reducing the participant's account through an actual loan offset at that moment. The debt can remain on the plan's records, and later repayment or future borrowing may need special treatment. Administrators must distinguish collection status, tax reporting, account value, and offset events. Calling a loan taxable does not establish that the note has been cancelled or that the same amount can be borrowed again.
Worked example: A participant misses payments and the loan becomes a deemed distribution after the applicable review. The administrator records the tax event but continues tracking the outstanding obligation rather than deleting the loan asset and assuming the participant has regained borrowing capacity.
Common mistake: Deleting a loan merely because it became taxable confuses a deemed distribution with an actual account reduction and debt settlement.
Official syllabus reference: [1]
35. Loan offsets reduce accounts and may affect rollover options
A loan offset occurs when the plan reduces a participant's account to satisfy outstanding loan debt. Unlike a deemed distribution alone, an offset is an actual account reduction. Its tax and rollover treatment depends on the event and whether it qualifies for any special offset rules. The participant receives less cash because part of the benefit settles the debt. Administrators should identify the gross benefit, offset amount, cash payment, and applicable reporting separately. An extended rollover deadline should never be promised without establishing the facts required for that particular treatment.
Worked example: A participant has a $45,000 vested benefit including a $9,000 loan. An authorized full offset leaves $36,000 of cash before withholding. The gross settlement still involves $45,000 of benefit, with $9,000 used to satisfy the loan rather than paid in cash.
Common mistake: Reporting only the cash check as the entire benefit overlooks the loan offset and can misstate the participant's distribution and rollover analysis.
Official syllabus reference: [1]
Eligibility
36. Age and service requirements are cumulative conditions
A plan can require both an age condition and a service condition before participation, within applicable legal limits. The administrator must determine when each condition is satisfied and use the later satisfaction date before applying entry provisions. An employee's job title or payroll benefit code does not establish that result. Different contribution sources may have different eligibility conditions, so deferral participation should not automatically be copied to employer-source eligibility. The correct analysis uses date of birth, employment history, service method, document elections, and any applicable special participation rules.
Worked example: A document requires age 21 and one elapsed year of service. An employee completes the service year in March but reaches age 21 in May. The administrator begins the entry-date analysis from May because both conditions were not satisfied in March.
Common mistake: Entering an employee when the first condition is satisfied ignores a second required condition and can create premature participation.
Official syllabus reference: [1]
37. Entry dates follow eligibility satisfaction
The eligibility-satisfaction date identifies when the employee completes the relevant conditions. The entry date identifies when participation actually begins under the document's schedule. Monthly, quarterly, semiannual, and immediate-entry provisions can produce different results from the same service history, subject to applicable participation requirements. Read whether the document uses coincident, next-following, or other language; those distinctions matter when satisfaction occurs on a scheduled entry date. Administrators should maintain separate fields for condition completion and plan entry instead of treating an employment anniversary as the universal enrollment date.
Worked example: An employee satisfies all conditions on August 18 under a document providing the first monthly entry date afterward. Entry occurs September 1. If another employee satisfies conditions on September 1, the administrator checks the document's coincident-date language before assigning an entry date.
Common mistake: Automatically using the service anniversary as the entry date disregards the plan's separate schedule and its treatment of coincident dates.
Official syllabus reference: [1]
38. Hours-of-service methods depend on computation periods
Under an hours-based method, service credit depends on countable hours during the document's eligibility computation period. The initial period and later periods may differ, so calendar-year payroll totals are not always sufficient. Creditable hours can include categories beyond hours physically worked under applicable rules. A plan may also use an authorized equivalency method rather than exact recorded hours. Administrators should identify the period, crediting method, required service level, and source data before deciding whether an employee completed a service year or remains subject to special eligibility provisions.
Worked example: A document's initial computation period begins on the employee's hire date, and its supplied service requirement is 1,000 credited hours. The employee's calendar-year report shows 900 hours, but the complete hire-anniversary period shows 1,080. The administrator uses the governing period.
Common mistake: Using calendar-year hours for every eligibility determination can miss service earned across year-end within a hire-anniversary computation period.
Official syllabus reference: [1]
39. Elapsed time measures employment duration
An elapsed-time method measures service through periods of employment rather than requiring a specified hours total in each computation period. It can simplify administration for employees with irregular schedules, but it still requires correct employment, severance, absence, and reemployment dates. Applicable service-spanning provisions can affect which periods count. An administrator must not import an hours threshold from another source or another plan when the adopted method is elapsed time. Conversely, reaching an anniversary does not override a separate age condition or the plan's scheduled entry dates.
Worked example: A plan requires one elapsed year and quarterly entry. A continuously employed worker completes that year on November 12 despite a low weekly schedule. The administrator applies the quarterly entry provision rather than denying eligibility solely because recorded hours were below another plan's threshold.
Common mistake: Adding an unstated hours test to elapsed-time eligibility changes the adopted method and can improperly exclude continuously employed workers.
Official syllabus reference: [1]
40. Excluded classifications and service credit are different
A document may exclude an employee classification from participation, subject to applicable legal and coverage requirements. That exclusion does not necessarily mean employment in the classification is ignored for service credit. When an employee transfers into an eligible class, the administrator must examine prior service and the document's transition and entry provisions. Exclusions also must be supported by actual employment facts rather than informal payroll labels. Keeping class eligibility separate from age and service prevents the mistaken conclusion that every transfer starts a completely new waiting period.
Worked example: A document excludes a specified class but counts its service toward eligibility. An employee spends two years in that class and then transfers to an included position. The administrator evaluates already-earned service instead of automatically imposing another full service year after transfer.
Common mistake: Treating an excluded class as though the employee had never worked for the employer can improperly restart otherwise credited service.
Official syllabus reference: [1]
41. Long-term, part-time access needs separate source flags
Current long-term, part-time rules can require elective deferral access for certain employees who do not satisfy the plan's ordinary service requirement. They use a special consecutive-year service framework, with applicability depending on the arrangement and relevant years. Required deferral access does not automatically establish eligibility for every employer contribution. Permitted employer-source exclusions and special vesting or testing treatment require separate review. Administrators should preserve lower-hour service histories and distinguish special-rule entry from ordinary eligibility, then reevaluate the employee if regular service conditions are later satisfied.
Worked example: An administrator confirms that an employee qualifies for special deferral entry in 2026 but not regular matching eligibility. Payroll enables salary deferrals and retains a separate employer-source status, rather than using one enrollment switch that either blocks deferrals or grants every employer contribution.
Common mistake: Using a single participation flag for all sources can deny required deferral access or unintentionally allocate employer contributions to specially eligible employees.
Official syllabus reference: [1]
42. Rehire eligibility depends on preserved service
Reemployment does not automatically reset eligibility to the status of a new employee. The administrator must review prior participation, credited service, severance history, and applicable break-in-service or service-restoration provisions. Some returning employees can resume participation under reentry rules without completing another waiting period. Eligibility service and vesting service may require different analyses, so a result for one should not be assumed for the other. The document's rehire provisions should be applied to an accurate employment timeline, including transfers and periods that may receive special service treatment.
Worked example: A former participant returns after an absence. The document preserves the employee's earlier eligibility and provides reentry upon reemployment. Payroll therefore restores participation under that provision rather than imposing the waiting period used for newly hired employees without prior service.
Common mistake: Applying the new-hire checklist to every returning employee ignores preserved eligibility and can create an avoidable missed-deferral operational failure.
Official syllabus reference: [1]
Vesting
43. Vesting follows contribution sources and related earnings
Vesting determines the portion of an account that is nonforfeitable. Employee elective deferrals are fully vested, while eligible employer sources may follow document schedules unless special rules require full vesting. Earnings generally follow the source to which they are attributable. A single blended percentage can therefore misstate the vested benefit. Administrators should calculate each source separately and then combine vested amounts. Loan assets included in account values must not be added again, and a loan offset changes payment composition rather than the source's underlying vested percentage.
Worked example: An employee source contains $20,000 and is fully vested. An employer source contains $15,000, including earnings, and is 40% vested. The vested benefit is $20,000 plus $6,000, or $26,000, before considering any payment offsets or fees.
Common mistake: Applying the employer schedule to the entire account improperly reduces employee-owned deferrals and can understate the participant's nonforfeitable benefit.
Official syllabus reference: [1]
44. Cliff and graded schedules create different ownership paths
A cliff schedule moves an employer source from no vesting to full vesting when its specified service condition is reached. A graded schedule increases the vested percentage in steps. The applicable schedule must satisfy governing requirements and match the document's source-specific provisions. An administrator needs completed vesting service, not merely the employee's hire-date anniversary or eligibility status. Schedule amendments also require protection of accrued nonforfeitable benefits and review of applicable election rights. The permitted legal schedule and the employer's actual adopted schedule are separate questions.
Worked example: A supplied graded schedule provides 20% after two credited years and 40% after three. A participant with three credited years and a $25,000 employer source has $10,000 vested. A cliff schedule cannot be substituted simply because another employer uses one.
Common mistake: Using a familiar schedule from another plan substitutes an assumed design for the actual document and can alter participant ownership.
Official syllabus reference: [1]
45. Vesting service can differ from eligibility service
Eligibility service determines access to participation, while vesting service determines nonforfeitable ownership of applicable employer benefits. The document may use different computation periods, crediting methods, and permitted exclusions for these purposes. An employee's entry date therefore does not necessarily mark the beginning of vesting credit. Prior employment, service before plan adoption, transfers, and special statutory provisions may affect the calculation. Administrators should maintain distinct service records and apply the source's actual schedule only after determining credited vesting service under the relevant method.
Worked example: An employee joins the plan in July after satisfying eligibility, but the vesting computation uses the calendar year and counts qualifying service before entry. The administrator reviews the entire credited year rather than measuring vesting only from the July participation date.
Common mistake: Starting every vesting clock on the plan entry date can omit employment that the document requires to count toward ownership.
Official syllabus reference: [1]
46. Break-in-service rules determine preserved vesting credit
A break in service is determined under the applicable service-crediting rules, not simply by identifying any gap between paychecks. Its effect can depend on prior vested status, the pattern and length of breaks, and applicable document provisions. Some special absences affect break calculations without creating an ordinary year of service. Administrators should first establish whether a break occurred, then determine whether and when prior service must be counted after reemployment. Applying a blanket rule that all prior service disappears on termination disregards these separate steps.
Worked example: A participant leaves and later returns. Before assigning a vesting percentage, the administrator reconstructs prior credited years, break periods, and earlier vested status. The fact of termination alone does not answer whether the returning participant's previous service remains usable.
Common mistake: Treating every employment interruption as permanent loss of prior vesting service bypasses the document's break and restoration rules.
Official syllabus reference: [1]
47. Forfeiture timing and restoration after reemployment
The nonvested portion of an employer account is not necessarily forfeited immediately when employment ends. The document and applicable rules determine the forfeiture event and any later restoration requirements. A cash-out followed by reemployment can create repayment and restoration issues distinct from the employee's current vesting percentage. Administrators need records of the prior distribution, forfeited amount, repayment conditions, and restoration funding method. Forfeitures also remain plan assets until used as permitted; they do not become general employer funds merely because the former participant no longer owns them.
Worked example: Under supplied plan provisions, an employee receives a vested distribution and forfeits a nonvested employer amount. After rehire, a qualifying repayment requires restoration of that forfeited amount. The administrator reconstructs the original transaction instead of treating the new account as unrelated history.
Common mistake: Assuming a forfeiture is permanently irreversible can overlook restoration rights triggered by reemployment and satisfaction of applicable repayment conditions.
Official syllabus reference: [1]
48. Full-vesting events override ordinary schedules
Ordinary employer vesting schedules can be overridden by events requiring full vesting under law or the document. Plan termination, a qualifying partial termination for affected employees, and attainment of normal retirement age under applicable rules are important examples to evaluate. Documents may also grant accelerated vesting for specified death or disability events. These triggers are not interchangeable, and an isolated employee termination does not establish a partial termination by itself. Administrators should identify the event, affected population, relevant account sources, and any required factual analysis before applying an ordinary schedule.
Worked example: A plan is terminating, and an employee's ordinary employer-source schedule would otherwise show 40% vesting. The administrator evaluates the termination vesting requirement instead of paying only the scheduled percentage. A separate document provision may address disability under a different set of conditions.
Common mistake: Applying the ordinary schedule without checking full-vesting events can improperly forfeit benefits when a governing event makes them nonforfeitable.
Official syllabus reference: [1]
Employer Contributions
49. Allocation compensation is a defined calculation input
Employer allocations use the compensation definition applicable to that contribution source, not necessarily gross payroll, taxable wages, or the amount used for deferrals. The document may address bonuses, exclusions, participation-period compensation, and other adjustments. Applicable qualification requirements and compensation caps also constrain the calculation. For 2026, the supplied IRS annual compensation limit is $360,000. Administrators should reconcile the selected compensation base to payroll before applying any allocation percentage. A mathematically correct percentage applied to the wrong compensation amount still produces an incorrect participant allocation.
Worked example: A supplied document includes bonuses in profit-sharing compensation but excludes them from another payroll calculation. An employee has $70,000 of salary and a $10,000 included bonus. A 4% profit-sharing allocation uses $80,000 and equals $3,200, assuming all other conditions are met.
Common mistake: Copying one payroll compensation field into every employer formula overlooks source-specific definitions and can systematically misallocate contributions across participants.
50. Pro rata allocations divide a fixed contribution pool
A pro rata compensation allocation gives each eligible participant the same contribution percentage of the relevant compensation base. When the employer approves a fixed pool, divide each participant's eligible compensation by total eligible compensation and multiply by the pool. This differs from an equal-dollar allocation and from a formula promising a fixed percentage before the pool is known. Correctly identifying the eligible population is essential because adding or removing one participant changes every participant's share of a fixed pool. Rounding should be reconciled to the total authorized contribution.
Worked example: Three eligible employees have allocation compensation of $40,000, $60,000, and $100,000. A $20,000 contribution pool is allocated $4,000, $6,000, and $10,000. Each receives 10% of compensation, although the dollar amounts differ because their compensation amounts differ.
Common mistake: Dividing a compensation-based pool equally among employees changes the formula from pro rata compensation to equal-dollar allocation without authorization.
Official syllabus reference: [1]
51. Permitted disparity uses a defined integration formula
An integrated allocation uses permitted disparity to coordinate employer retirement contributions with the Social Security system under specific rules. It can allocate different effective percentages to compensation above and below an integration level, subject to limits and the adopted formula. This is not permission to choose arbitrary higher percentages for favored employees. The integration level, eligible compensation, allocation steps, and permitted disparity must be established before calculation. Administrators should use the document's actual method and year-appropriate inputs rather than assuming the Social Security taxable wage base always supplies every needed value.
Worked example: A supplied exercise formula allocates 3% of all eligible compensation plus 2% of compensation above an $80,000 integration level. An employee with $100,000 receives $3,000 plus $400. Those scenario percentages illustrate the calculation and do not establish a universally permissible integrated formula.
Common mistake: Treating any higher contribution rate above a chosen salary level as permitted disparity ignores the regulatory conditions and adopted integration method.
Official syllabus reference: [1]
52. Cross-testing evaluates benefits rather than equal contribution rates
A cross-tested allocation can assign different contribution rates to defined employee groups and evaluate nondiscrimination using benefits-based calculations when applicable requirements are met. Age and the period to retirement can influence the relationship between a current contribution and its projected retirement benefit. That does not make every group allocation acceptable. Gateway conditions, coverage, nondiscrimination methodology, and document provisions require separate evaluation. For plan management, the key decision is recognizing that an allocation worksheet is not approved merely because it matches the employer's desired group percentages.
Worked example: An employer proposes different profit-sharing percentages for two allocation groups. The administrator confirms the document permits those groups, then obtains the required benefits-based and gateway review. Matching the employer's spreadsheet does not alone demonstrate that the proposed allocation can be implemented.
Common mistake: Assuming cross-testing authorizes any age-related contribution pattern overlooks gateway, coverage, and nondiscrimination requirements that constrain the final allocation.
Official syllabus reference: [1]
53. Matching periods determine true-up obligations
A matching formula must specify both the contribution rate and the period over which compensation and deferrals are compared. An annual formula can require reconciliation when payroll-period deposits fail to deliver the annual entitlement. Front-loaded deferrals, bonuses, and midyear changes can create differences even when payroll applied its interim calculation correctly. A true-up is the difference between the required final match and amounts already credited, not a second full matching contribution. A payroll-period formula without an annual reconciliation provision can produce a different result, so the document controls.
Worked example: An annual formula matches 50% of deferrals up to 6% of $80,000 compensation. The employee defers $4,800, producing a $2,400 annual entitlement. If payroll credited $1,600, the required true-up is $800 rather than another $2,400.
Common mistake: Assuming every plan owes an annual true-up ignores the calculation period and reconciliation provisions actually selected in the governing document.
Official syllabus reference: [1]
54. Forfeitures require an authorized use and allocation
Forfeitures remain plan assets and must be used under the document and applicable requirements. Depending on the governing provisions, permitted uses can include paying qualifying plan expenses, reducing employer contributions, or reallocating amounts to participants. The employer cannot simply withdraw them as business cash. Reallocation can create participant annual additions, while using forfeitures to fund an employer obligation requires checking that the source and conditions permit it. Administrators should reconcile forfeiture balances, origin dates, authorized uses, and participant effects rather than allowing an unexplained balance to accumulate indefinitely.
Worked example: A plan has a $6,000 forfeiture balance and expressly permits its use to reduce the current profit-sharing contribution. If the required allocation is $30,000 and all conditions are satisfied, the employer supplies $24,000 in new cash while participants receive the full $30,000 allocation.
Common mistake: Reducing participant allocations by the forfeiture amount confuses funding an employer obligation with reducing the benefit promised by the formula.
Official syllabus reference: [1]
Safe Harbor 401(k) Plans
55. The traditional basic match has two tiers
A traditional basic safe harbor matching formula matches the first tier of deferrals at one rate and the next tier at a lower rate. A common basic formula provides a full match on the first 3% of compensation deferred and a half match on the next 2%. An employee deferring 5% therefore receives a 4% employer match under that formula. Administrators must apply tiers to eligible compensation rather than multiplying the entire deferral by the first-tier rate. Safe harbor status also depends on requirements beyond merely reproducing the formula.
Worked example: Under the stated basic formula, an employee earns $60,000 and defers 4%, or $2,400. The employer matches $1,800 on the first 3% plus $300 on the next 1%, producing $2,100 rather than a full match on every deferred dollar.
Common mistake: Applying a 100% match to all deferrals through 5% ignores the reduced second tier and overstates the basic formula's employer contribution.
Official syllabus reference: [1]
56. Nonelective safe harbor funding does not require deferrals
A safe harbor nonelective contribution is allocated under its compensation-based formula without requiring the employee to defer. It therefore serves nondeferrers differently from a matching design. The administrator must identify the employees entitled to the contribution and use the source's compensation definition and eligibility provisions. Traditional safe harbor nonelective arrangements also differ from matching arrangements in certain notice requirements, so one notice checklist should not be applied indiscriminately. The contribution promise must still be fulfilled, and safe harbor treatment does not eliminate other applicable qualification or operational obligations.
Worked example: A document promises a 3% safe harbor nonelective contribution to an eligible employee earning $45,000. The employee elects no salary deferral but still receives $1,350. A matching formula would instead require examining the employee's deferrals before determining the employer amount.
Common mistake: Denying a nonelective contribution because the employee opted out of deferrals incorrectly imports a matching condition into a different contribution design.
Official syllabus reference: [1]
57. Traditional safe harbor sources require immediate ownership
Required traditional safe harbor contributions are fully vested when allocated. They cannot simply be placed on the ordinary vesting schedule used for discretionary profit-sharing or another employer source. Source accounting therefore matters even when several employer contributions arrive in one deposit. Qualified automatic contribution arrangements have distinct permitted vesting treatment and should not be confused with the traditional design. Administrators should identify the specific safe harbor type before assigning percentages and distinguish required safe harbor dollars from additional employer contributions that may follow separate valid vesting provisions.
Worked example: An employee receives $2,000 of traditional safe harbor nonelective contributions and $1,000 of discretionary profit-sharing. The employee is 20% vested in profit-sharing. The vested employer benefit is $2,000 plus $200, rather than 20% of the combined $3,000 deposit.
Common mistake: Applying one employer vesting schedule to all employer deposits can improperly forfeit traditional safe harbor contributions that are immediately nonforfeitable.
Official syllabus reference: [1]
58. QACA combines automatic contributions with safe harbor conditions
A qualified automatic contribution arrangement, or QACA, is a specific safe harbor design combining automatic deferral provisions with required employer contributions and other conditions. Automatic enrollment alone does not establish QACA status. The arrangement must satisfy the applicable default contribution structure, election opportunities, notices, funding, and vesting requirements. QACA's permitted vesting treatment differs from immediate vesting under a traditional safe harbor arrangement. Administrators should distinguish QACA from other automatic-enrollment designs and preserve employee affirmative elections rather than treating the default percentage as mandatory for every employee.
Worked example: An employer automatically enrolls employees but uses an ordinary discretionary match and has not adopted QACA provisions. The administrator does not claim QACA testing relief merely because payroll uses a default rate. The complete design and operation must satisfy the relevant safe harbor conditions.
Common mistake: Equating automatic enrollment with QACA status overlooks the contribution, notice, election, and vesting conditions that define this particular safe harbor arrangement.
Official syllabus reference: [1]
59. Safe harbor testing relief has defined edges
A compliant safe harbor design can avoid ADP testing, and qualifying matching arrangements can receive ACP relief under applicable conditions. This does not waive coverage, annual-additions limits, compensation limits, document compliance, or every top-heavy obligation. Certain plans receiving only specified contributions can qualify for a top-heavy exemption, but additional contributions can change that analysis. Administrators should map each claimed exemption to its conditions rather than using safe harbor as a global compliance label. Additional profit-sharing and matching contributions need review even when required safe harbor funding remains correct.
Worked example: A plan adds discretionary profit-sharing after previously receiving only deferrals and required safe harbor contributions. The administrator retains the valid ADP safe harbor analysis but separately reevaluates top-heavy treatment and the qualification requirements affecting the new employer allocation.
Common mistake: Assuming safe harbor means no compliance testing of any kind extends specific relief to unrelated qualification requirements and contribution sources.
Official syllabus reference: [1]
60. Midyear changes require a safe harbor impact analysis
A midyear amendment to a safe harbor plan requires analysis of the specific change rather than a blanket assumption that every change is prohibited or unrestricted. The administrator should identify whether the change affects safe harbor contributions, required notices, participant election opportunities, or conditions for suspension or reduction. Some changes can be made while preserving treatment if applicable requirements are met; others can trigger testing or funding consequences. Effective dates and contributions already earned matter. Financial pressure alone does not authorize silently stopping a promised safe harbor contribution.
Worked example: An employer proposes changing its safe harbor match during the year. Before revising payroll, the administrator evaluates the amendment, applicable notice and election requirements, accrued contribution obligations, and testing consequences. The employer's desired effective date does not by itself establish that the change is permissible.
Common mistake: Stopping payroll funding before evaluating the amendment can create unpaid contribution obligations and undermine the safe harbor treatment the employer expected.
Official syllabus reference: [1]
Official syllabus sources
- ASPPA QKA current curriculum and examination format
- COLA increases for dollar limitations on benefits and contributions | Internal Revenue Service
- Retirement topics - Catch-up contributions | Internal Revenue Service