There is a special kind of dread that arrives with a 401(k) question. An employee says her deferral looks wrong. The recordkeeper's report does not match the payroll register. Finance asks whether the match used the right definition of compensation, and nobody in the room is completely sure. Retirement money is the most emotionally loaded number on a pay stub after the net check, and mistakes here erode trust fast.
The frustrating part is that most 401(k) payroll problems are not complicated. They come from setup decisions made once, sometimes years ago, that nobody has revisited: how deferrals are coded, how the match formula is entered, whether limits are enforced, and whether payroll and the recordkeeper are actually talking to each other. Get those four right and the plan mostly runs itself. Get one wrong and you are hand-fixing contributions every quarter.
This post walks through the 401(k) mechanics that live inside ADP: deferrals, match formulas, limits, catch-ups, recordkeeper integrations, and the year-end true-up. We've got you.
Every 401(k) deduction starts with two choices per employee: how much, and what tax treatment. On the "how much" side, deferrals are set either as a percentage of pay or as a flat dollar amount per pay period. Percentages scale automatically with raises, bonuses, and overtime, which is usually what employees intend. Flat dollar amounts stay fixed no matter what the paycheck does, which some people prefer for budgeting but which quietly falls behind as pay grows.
The tax treatment side is pre-tax versus Roth. Pre-tax deferrals reduce taxable income now and are taxed at withdrawal. Roth deferrals are taxed now and, if the rules are met, come out tax-free later. In payroll terms, these are two different deduction codes with different tax handling, and an employee can often split between them if the plan allows. The classic error is entering a Roth election under the pre-tax code or vice versa: the money moves, the W-2 is wrong, and the fix involves amended reporting. When elections change, verify the code, not just the amount.
Two more setup details worth checking. First, which earnings the deferral applies to: does the plan document include bonuses, commissions, and overtime in deferrable compensation? Payroll must match the document, not someone's memory of it. Second, effective dating: elections should start with the correct pay period, especially for new hires in plans with automatic enrollment, where a missed start date becomes a correction with lost-earnings implications.
The match is where plan documents and payroll systems most often drift apart. A typical formula reads something like "100 percent of the first 3 percent of compensation deferred, plus 50 percent of the next 2 percent." That is not one number; it is a tiered calculation, and it needs to be configured in ADP as exactly that, tier by tier.
The most common mismatches we find: a tiered formula flattened into a single percentage, a match calculated on the wrong compensation base, a match applied to Roth deferrals in a plan where treatment differs, or a per-payroll cap entered where the document describes an annual one. Each of these produces a match that looks plausible on any single check and is wrong across the year.
The discipline is simple: put the plan document and the payroll configuration side by side once a year and read them against each other. Fixed, discretionary, and safe harbor formulas each behave differently, and the payroll setup should mirror the specific language, not the general idea. When in doubt, ask the plan's advisor or TPA what the formula means before encoding your best guess.
Employee deferrals are capped by federal limits that adjust for inflation, usually annually. There is a limit on employee deferrals, a separate higher limit on total contributions including employer money, and a compensation cap on how much pay can be counted for plan purposes. We deliberately are not printing the current figures here, because they change and a stale number in a blog post is worse than none. Each fall, the IRS announces the next year's limits; make verifying them, from the official announcement, a standing item on your year-end checklist.
Inside ADP, deferral codes should carry the annual limit so the system stops deductions automatically when an employee reaches the cap. Two situations deserve special attention. Mid-year hires who contributed at a previous employer can exceed the personal limit across two payrolls even though each system sees only its own totals; the excess is the employee's issue to manage, but a heads-up from you prevents an unpleasant tax-time surprise. And every January, confirm the new year's limits are reflected before the first payroll runs. A limit left at last year's figure either stops high savers early or lets them run past the cap, and both create work.
Employees who reach age 50 by year end are generally allowed an additional catch-up contribution above the standard deferral limit, and recent law changes have added age-banded variations and special rules for higher earners, including requirements about Roth treatment in certain cases. The details shift, so treat this as a category to verify annually with your plan advisor rather than a set-and-forget number.
Operationally, catch-up handling comes down to a few questions. Does the system know the employee's birth date and apply the higher limit automatically? Does the plan use a separate catch-up election, or let deferrals spill over the standard limit? And if newer rules require certain employees' catch-up dollars to be Roth, is the coding ready? Employees over 50 tend to be your highest savers and most attentive pay-stub readers. They will notice errors before you do.
Every payroll sends contribution data to the recordkeeper, and elections made on the recordkeeper's website need to reach payroll. How automated that loop is defines whether plan administration is a background process or a part-time job.
In a 180-degree integration, data flows one way: payroll sends contributions and census data to the recordkeeper after each run, but election changes come back to you manually, as reports someone must key into ADP. In a 360-degree integration, the loop closes: an employee changes her deferral on the recordkeeper's site, and the change flows into payroll automatically, with contribution data flowing back the other way.
The gap between the two is where errors live. In a 180 setup, every election change depends on a human noticing a report and keying it correctly and on time. Miss one, and an employee who raised her deferral in March discovers in June that nothing changed, which can obligate corrective contributions. If you run 180 today, the mitigations are a fixed weekly routine for processing change reports and a monthly reconciliation comparing recordkeeper elections to payroll deductions. If a 360 connection is available between ADP and your recordkeeper, it is usually worth implementing; the setup effort pays for itself in the first prevented error.
Here is a scenario that confuses employees every January. Someone front-loads her deferrals and hits the annual cap by September. Her deferrals stop, and in a plan that matches payroll by payroll, the match stops too, because there is nothing left to match. Across the full year she deferred far more than enough to earn the maximum match, but she receives less match than a colleague who spread the same deferrals across all 26 periods.
A true-up fixes that. After year end, the plan recalculates the match on annual totals: full-year compensation and full-year deferrals run through the document's formula. If the sum of per-payroll matches falls short of the annual entitlement, the employer deposits the difference. Whether your plan does this is a plan-document question, not a payroll preference; some documents require a true-up, some prohibit it, and some compute the match annually so the issue never arises.
Payroll's role is to know which kind of plan you have and prepare for it. If your plan trues up, the calculation typically happens in the first quarter, needs clean annual compensation and deferral data by employee, and results in an employer contribution processed outside the normal per-payroll match. If your plan does not true up, tell your employees how the per-payroll match behaves, so your heaviest savers understand that front-loading can cost them match dollars.
A client with about 300 employees asked us to review their 401(k) payroll setup after an employee complaint. The plan document specified a match of 100 percent on the first 3 percent deferred plus 50 percent on the next 2 percent, an effective maximum of 4 percent of compensation. Years earlier, the formula had been entered in payroll as a flat 4 percent of deferrals up to 5 percent, close enough to look right, wrong enough to matter.
We tested a sample. An employee earning $80,000 and deferring 5 percent should have received $3,200 in annual match under the document. The configured formula was producing about $3,000 for some pay patterns and slightly over-matching others, depending on how deferrals fell across periods. Extended across roughly 220 participating employees, the drift totaled around $40,000 of misallocated match for the year, some over, some under.
The fix had three parts: reconfigure the formula in ADP as the two-tier calculation the document described, work with the plan's TPA to calculate corrective contributions where employees were shorted, and add an annual side-by-side review of document versus configuration to the client's calendar. The employee who complained was right, by about $180. The review she triggered was worth far more than that.
Check the path the change traveled. If elections start at the recordkeeper, confirm the change appears there, then confirm it reached ADP, by file in a 360 setup or by manual entry in a 180. Most gaps sit at that handoff, and the fix usually includes making up missed deferrals under correction rules your TPA can walk you through.
If the plan document allows Roth, payroll can support a split, and many employees value it. The operational requirement is two clean deduction codes and careful entry so each dollar lands under the right tax treatment. The choice of mix is personal tax planning, which belongs with the employee and her advisor, not with payroll.
The stakes are lower but not zero. Anyone whose deferral rate varies during the year, pausing for a tight month, jumping after a raise, can end up slightly short of the annual formula in a per-payroll match plan. Check what your document says first; it may already answer the question for you.
The healthy version of all this is boring, in the best way. Deferral codes match elections, verified by a monthly reconciliation against the recordkeeper. The match formula in ADP is a mirror of the plan document, reviewed side by side once a year. Annual limits are updated each January from the official IRS announcement, and the system enforces them automatically. Catch-up rules are confirmed annually as the law shifts. Data moves by 360 integration where available, and by a disciplined weekly routine where not. And the true-up question has a written answer everyone can point to before year end, not a debate in February.
Put those checks on a calendar and the plan becomes what it should be: a benefit employees trust and a process payroll barely notices.
If your setup has drifted, or you have never done the side-by-side review and suspect what it might find, we can run it with you. Ignite HCM is staffed by former ADP service professionals, and we work with ADP exclusively. No tickets, no hold queues, just a dedicated consultant who has reconciled more match formulas than we care to count.
Confident your match is calculating the way your plan document says it should? REQUEST A CONSULTATION.
ADP and the ADP logo are registered trademarks of ADP, Inc. This article is general guidance, not tax, legal, or benefits advice; contribution limits and plan rules change, so verify current figures with official IRS announcements and confirm plan specifics with your licensed advisor or plan counsel.