NIPA APA common mistakes
NIPA APA · Understand the traps and how to avoid them.
Treating the plan year, the limitation year, and the calendar year as interchangeable when computing 415(c) annual additions or 401(a)(17) compensation, so the candidate applies the wrong 12-month period to a short plan year or a plan with a non-calendar limitation year.
Most plans default to the calendar year, so candidates memorize "calendar year" as a rule rather than as a default that the document can override. Short plan years and off-calendar limitation years appear in only a minority of questions, so the distinction is under-drilled.
What to do instead
Before computing any limit, write three labels on scratch paper: plan year, limitation year, compensation period. Check the document language quoted in the item for an override. For a short limitation year, prorate the dollar limit by months (multiply by months in the short period divided by 12, rounding up to the next $1,000 for 415(c) as applicable) and never prorate the compensation limit.
Applying the ADP/ACP tests to a safe harbor 401(k) plan that has lost its exemption (for example, by failing to give timely notice, or by imposing a last-day or hours requirement on the safe harbor nonelective), then still reporting the plan as exempt from testing.
Candidates learn "safe harbor means no ADP test" as a flat rule and do not connect the exemption to the notice and vesting conditions that create it. The failure conditions are tested less often than the basic exemption.
What to do instead
For every safe harbor item, run a three-item checklist: (1) was the required annual notice given within the permitted window, (2) does the contribution satisfy the applicable vesting and withdrawal conditions, (3) did the plan add any impermissible condition on the safe harbor contribution. If any answer is no, the plan is subject to ADP/ACP and top-heavy rules for the affected year.
Calculating a participant's top-heavy account balance using the current-year balance only, instead of the determination date balance plus the appropriate lookback (last day of the prior plan year, with distributions of the prior five years added back).
Top-heavy is taught as "more than 60% of assets for key employees," and the determination date and lookback rules get compressed into a single sentence. The five-year distribution add-back is a detail that rarely surfaces in practice.
What to do instead
Build the balance in three steps: determination date balance, plus in-service and other distributions during the lookback period, minus rollovers and unrelated amounts the plan is permitted to exclude. Compare the key employee total to the total of all accounts, not just to non-key accounts, and confirm whether the plan uses a different determination date for the first plan year.
Answering an ERISA fiduciary question by identifying the correct standard of care but ignoring the co-fiduciary and monitoring duties, so the candidate misses the second violation (failure to monitor a delegate) that the item is actually testing.
Candidates focus on the named fiduciary's own conduct under the prudence and loyalty duties and treat delegation as a complete transfer of responsibility. The concept that appointing and monitoring a delegate is itself a fiduciary act is easy to state and easy to forget under time pressure.
What to do instead
On any delegation fact pattern, ask two separate questions: did the delegating fiduciary prudently select and monitor the delegate, and did any co-fiduciary know of a breach and fail to act? Treat each as a distinct potential violation and check whether the plan document allocates the duty in a way that limits liability.
Confusing a prohibited transaction under ERISA section 406 with a breach of fiduciary duty, and answering that a party in interest transaction is permissible because the terms were fair or the plan benefited.
Fairness feels like it should cure a conflict, and the fiduciary duty standard (acting prudently and for the exclusive benefit of participants) sounds like the governing test. Section 406 is a per se prohibition with its own exemption structure, which candidates under-weight.
What to do instead
Separate the two analyses explicitly. First ask whether the party is a party in interest and whether the transaction falls in a 406(a) or 406(b) category; if yes, it is prohibited unless a specific statutory or administrative exemption (or an individual exemption) applies. Then, separately, ask whether the fiduciary duty was breached. Fairness of terms does not create an exemption.
Reporting a distribution on the wrong form or in the wrong box, for example treating a direct rollover as a taxable distribution on Form 1099-R, or failing to code an early distribution with the applicable exception code.
The tax treatment and the reporting treatment are learned separately, so a candidate who knows the distribution is nontaxable may still select a taxable reporting outcome. Form 1099-R box and code conventions are memorized as isolated facts.
What to do instead
Anchor each distribution type to a reporting outcome: direct rollover is reported with the rollover code and generally no taxable amount in the gross box; a distribution with an applicable exception carries the specific exception code; a defaulted cash-out has its own treatment. Practice by writing the distribution type, the taxable amount, and the code side by side before reading the answer choices.
Computing required minimum distributions using the participant's age in the year of distribution rather than the age attained in the distribution year under the applicable tables, and applying the wrong life expectancy table (Uniform Lifetime versus Single Life for a spousal beneficiary more than 10 years younger).
The RMD rules changed substantially and candidates mix pre- and post-SECURE Act frameworks, including the age threshold and the treatment of designated beneficiaries. The tables look similar and the divisor selection is a small step in a longer calculation.
What to do instead
For each RMD item, state four facts before calculating: the participant's age at the end of the distribution year, the account balance at the prior year end, whether a spousal beneficiary more than 10 years younger triggers the Joint and Last Survivor table, and which SECURE Act regime applies to the beneficiary. Then apply the divisor. If the item involves an inherited account, determine the beneficiary category first, since that drives the entire method.
Determining vesting percentage from total years of service without checking the plan's vesting computation period, the elapsed-time versus hour-counting method, and the break-in-service rules that can trigger a forfeiture or a restoration.
Vesting is taught as a simple schedule lookup, and the computation period and break rules are treated as administrative trivia. Items that test them are usually worded so the schedule answer is available and attractive.
What to do instead
Before selecting a vesting percentage, identify the computation period, the service-counting method, and whether any break in service occurred. Apply the plan's break rule and any restoration rule, then apply the schedule. If the plan uses elapsed time, count from date of hire to the applicable anniversary rather than summing hours.
Calculating a benefit or contribution for a participant whose compensation exceeds the annual compensation limit, or who is a highly compensated employee, without applying the 401(a)(17) limit before the benefit formula and the discrimination tests.
The compensation limit is applied at the end of the workflow in candidates' mental models, but it must be applied first because it changes the compensation on which the formula and the tests operate. The order of operations is rarely made explicit in study material.
What to do instead
Fix an order of operations and reuse it: determine includible compensation, apply the 401(a)(17) limit, apply any plan-imposed compensation definition, then run the formula, then run the nondiscrimination tests on the limited compensation. State the order at the top of any calculation scratch work so you do not reverse steps under time pressure.
Missing deadlines that are measured in days from a triggering event, such as the participant notice window for a blackout period, the timing of a summary of material modifications, or the deadline to deposit participant deferrals.
These are recall items with no calculation to anchor them, and the day counts are close enough to be confused with one another. Candidates often remember that a deadline exists but not its length or starting point.
What to do instead
Build a one-page deadline table organized by triggering event, not by rule name: event, number of days, who must act, and the consequence of missing it. Rehearse it by triggering event (for example, "plan amendment adopted" leads to the SMM timing) so the retrieval cue matches how items are written.