401(k) Contribution Types Explained: Deferrals, Match, Nonelective, QNEC, and QMAC
Practical guidance for 401(k) contribution types explained: deferrals, match, nonelective, qnec, and qmac, including controls, records, and review steps.
401(k) contribution types are different payroll and employer funding commitments, so they should be named, tracked, and reconciled separately even when they arrive in the same trust account.
“Contribution” is too broad for operational work. Employee deferrals, employer match, nonelective contributions, QNECs, and QMACs can follow different formulas, timing, vesting, and correction rules. Clear labels make reports easier to review and reduce the chance that one type is mistaken for another.
At a glance
- Core question: Does the recorded operation match the plan’s written terms?
- Best evidence: Dated source reports, not a reconstructed summary.
- Reading path: Define the rule, compare records, then document action.
Define the operating question
Employee elective deferrals are amounts withheld from a participant’s pay under an election. Employer match is generally tied to deferrals under the plan formula. A nonelective contribution is an employer contribution not conditioned on a participant deferral. QNEC and QMAC are technical contribution categories often used in testing or correction contexts; their treatment must follow the plan terms and applicable rules. The IRS fix-it guide emphasizes reviewing plan terms and correcting failures to operate accordingly.[1]
Before reviewing individual transactions, write the question in a way that can be tested: which people, pay periods, contribution source, and plan provisions are in scope? Use source-system extracts with an “as of” date and preserve the version of the plan materials used. That discipline separates a defensible finding from a report that merely looks complete.
Compare records before drawing a conclusion
The useful comparison is not “employee money versus employer money” alone. Ask what triggers the contribution, how its amount is calculated, when it is funded, whether it vests, and whether it is designated for a correction or testing purpose. These attributes drive payroll coding and the review evidence needed later.
| Record set | What to test | Useful outcome |
|---|---|---|
| Plan materials | Rule, formula, eligibility, and timing | Control standard |
| Payroll and HR data | Dates, pay, status, and withholding | Expected result |
| Trust or recordkeeper data | Funding and allocation | Confirmed variance |
Use a variance log that records the participant or payroll population, source records, initial explanation, owner, due date, and disposition. Do not silently overwrite a difference to make totals agree. A documented “not an error” conclusion is valuable because it shows why the reviewer rejected the exception.
Make the comparison reproducible. Save the original extract names, filters, report dates, and calculation version, then have another reviewer rerun a small sample from the same evidence. This is especially important when a payroll code, job classification, or plan amendment changes during the review period. A control is more reliable when it can explain both a matched item and an exception. Where information is incomplete, label the item as pending rather than guessing an effective date or contribution source. The resulting file gives the sponsor a practical audit trail and a clearer handoff if outside counsel or a plan specialist needs to evaluate a potential correction.
Implement a controlled response
Once a variance is confirmed, contain the issue first. Stop the faulty configuration or manual process, preserve the records, and identify whether additional payrolls or populations use the same rule. Then use a consistent case file: facts, governing terms, analysis, professional advice, corrective amounts if applicable, approvals, funding evidence, participant communications, and prevention steps. The right sequence depends on the plan and facts, so administrators should involve ERISA counsel, a qualified TPA, or other appropriate advisers before selecting a correction method.
- Build a contribution dictionary with the exact plan label, trigger, formula, funding cadence, payroll code, and reviewer.
- Keep deferral, match, nonelective, QNEC, and QMAC files distinct through calculation, approval, and posting.
- Recalculate a sample of each type using the plan definition of compensation and any applicable caps or exclusions.
- Require documented approval for manual journals and correction-related contributions.
- Reconcile the payroll register, funding report, trust receipt, and participant allocation by contribution type.
Assign one owner for the case, but do not make that person the only reviewer. Payroll can validate source data, HR can validate employment events, and the recordkeeper can validate posting. The plan administrator should retain the final decision trail. This division makes it easier to distinguish a data correction from a plan-operation correction and reduces the risk that a fix in one system is never reflected in another.
Review the control, not only the case
Review the dictionary after every amendment, vendor change, or testing cycle. When an unfamiliar contribution label appears, pause before posting it and obtain the governing instruction. A clean audit trail should let a reviewer identify why an amount exists without inferring its purpose from a general ledger description.
Decision flow
- Set scope: define the requirement, scope, timing, and decision owner.
- Check evidence: check documents, reports, controls, and open exceptions.
- Assign action: assign the approved action, deadline, and accountable owner.
- Revisit: revisit evidence, changes, and unresolved exposure.
Move forward only when the evidence supports the prior step; retain the record of each decision.
Practical review table
| Review point | Evidence to retain | Escalate when |
|---|---|---|
| Population | Dated HR and eligibility extracts | People appear in one system but not another |
| Calculation or election | Plan terms and calculation detail | Expected and actual results differ |
| Funding or posting | Bank, trust, and allocation confirmations | Timing or allocation cannot be explained |
| Prevention | Test result and owner sign-off | The root cause remains active |
Planning resource
Takeaway
The strongest operating practice is a short, repeatable reconciliation tied to the plan document, with dated evidence and an exception path that stays open until both the participant impact and root cause are addressed. That approach turns a difficult review into a manageable routine.[1]
Close the review by asking whether the control would detect the same failure next month. If the answer depends on a person remembering a special step, convert that step into an owned report, a documented approval, or a system validation. Retain both the original exception and the proof of the changed process. Periodic samples should confirm that the control is operating in practice, not merely written into a procedure.
Editorial disclaimer: This article is general educational information, not legal, tax, investment, actuarial, or compliance advice. Plan documents, facts, and current guidance can change the result; consult qualified advisers before acting.
References
- [1] https://www.irs.gov/retirement-plans/401k-plan-fix-it-guide