If you administer or advise retirement plans, you learn quickly that the Employee Retirement Income Security Act is not just a disclosure statute. It carries bright-line fiduciary rules, and some of those rules hinge on the simple mechanics of a bond. The ERISA fidelity bond is one of the cheapest protections available, yet it is also one of the most commonly mishandled requirements I see in audits and operational reviews. The mistakes are rarely malicious. They often stem from a fuzzy understanding of who must be bonded, what the bond must cover, and how to calculate the right amount. A few oversights, left alone, can turn into a reportable deficiency that lands in a Form 5500 note, a DOL inquiry, or a frantic rush to fix gaps before a corporate transaction closes.
This is a practitioner’s map of the pitfalls I see most, why they matter, and the workable steps to correct them. Whether you manage a one-participant 401(k) or sit on the committee of a multi-employer plan, the same principles apply, with some wrinkles worth calling out.
What an ERISA bond actually does, and what it doesn’t
The ERISA fidelity bond is not fiduciary liability insurance, and that distinction drives half the confusion. The bond protects the plan against theft or fraud by people who handle plan funds or property, in other words, loss caused by dishonesty. It is narrowly focused, and ERISA requires it for most plans that hold assets. The Department of Labor sets the rules in 29 C.F.R. § 2580, and qualifying bonds must be written by a surety on the Treasury Department’s list of approved companies. The bond rides for the benefit of the plan, not the plan sponsor or the fiduciary as individuals.
Fiduciary liability insurance, by contrast, protects fiduciaries against claims of breach of duty. It deals with negligence, imprudence, documentation failures, prohibited transactions, and the long catalog of ways fiduciary decisions can go sideways. The DOL does not require fiduciary liability insurance, though many committees sensibly buy it. When someone says “We’ve got the ERISA policy covered,” ask a follow-up question. Nine times out of ten, they mean fiduciary liability insurance. That will not satisfy the statutory bonding requirement.
Who must be bonded, really
The statute does not bond job titles. It bonds functions. Anyone who handles plan funds or property must be bonded. Handling includes physical contact with cash or checks, power to transfer assets, authority to sign checks, authority to direct disbursements, and decision rights that cause movement of plan money. This picks up more people than plan sponsors typically assume.
Recordkeepers and custodians have their own blanket bonds that satisfy the requirement for their handling of assets. That does not eliminate the need to bond your internal staff if they can initiate or approve wires, reconcile accounts, or move money within the trust. Payroll personnel who transmit deferrals, treasury staff who initiate plan contributions, and even an HR generalist with access to vendor portals that can change bank instructions may fit the handling definition. Third‑party administrators vary. Some never touch money. Others move rollovers, issue loans, or process distributions. Always confirm the scope of your vendors’ handling and how their bonding intersects with yours.
I once evaluated a plan where a conscientious controller swore that only the custodian touched assets. We pulled portal logs and discovered two AP clerks could approve hardship distributions through the recordkeeper interface. They were not bonded. The fix took 48 hours and a modest premium, but the surprise could have been worse if a distribution had been misdirected.
The dollar amount trap: five formulas that trip people
Most plans understate the bond amount. The default rule is simple in concept: the bond must cover at least 10 percent of plan funds handled in the prior year, with a typical floor of 1,000 dollars and a standard cap of 500,000 dollars per plan. If the plan holds employer securities, the cap rises to 1,000,000 dollars. In practice, five calculation points go wrong:
- Misidentifying the base. The 10 percent test keys off funds handled during the preceding plan year, not the plan assets at year end. For a mature plan, those numbers track each other, but heavy rollovers, large distributions, or a one-time transfer can skew the figure. If your plan had 40 million dollars in assets but processed 15 million dollars in distributions and 12 million dollars in contributions, the 10 percent base could exceed what a simple asset snapshot suggests. Using the bond’s aggregate limit as if it were per-loss. Many bonds specify an aggregate limit for all losses in a year. The ERISA standard looks for the amount applicable to a single loss. If your schedule says “Aggregate 500,000 dollars, sublimit 250,000 dollars per loss,” the compliance limit is 250,000 dollars. Ignoring the employer stock cap. If the plan holds employer securities, the maximum required bond jumps to 1,000,000 dollars. I have seen plans with company stock tracked in a unitized fund where the sponsor missed the employer security rule because they assumed only direct share holdings counted. If participants’ balances track the employer’s stock performance and the plan trust holds the underlying security, treat it as employer securities. Assuming a service provider’s bond covers all. A recordkeeper’s bond may protect against its employees’ dishonesty, but it will not automatically satisfy the bond requirement for the plan sponsor’s employees who handle assets. Unless the provider’s bond names your plan as a covered plan and covers your staff’s handling, you still need your own bond. Neglecting midyear changes. Adding payroll locations, switching banks, or migrating to a new recordkeeper often changes who handles funds and how much flows through specific hands. The bond amount can become stale. If you increase salary deferrals by opening eligibility to a new division, the 10 percent number may move enough to justify a midyear adjustment, even though ERISA requires an annual lookback.
When I review plans, I run a quick reconciliation: cash in, cash out, and any non-routine transfers over the prior plan year. If the 10 percent figure materially exceeds the current bond amount, I treat that as a red flag and coordinate with the surety for a rider.
Plans with unique assets or structures
Most 401(k) plans invest in mutual funds or collective trusts. The asset handling risk is concentrated in contributions, distributions, loans, and payroll feeds. ESOPs, defined benefit plans with annuity purchases, and multi-employer funds bring their own quirks.
ESOPs frequently trigger the 1,000,000 dollar cap. They also involve valuation processes and internal transfer mechanics that expand who “handles” property. Stock certificates are rare now, but the authority to direct purchase orders, control escrowed cash, or manage dividend flows can constitute handling. Underestimate it and you under-bond.
Multi-employer plans often have larger cash flows and more complex remittance patterns. Contribution delinquency collection can involve staff who receive checks, record receipts, and negotiate payment plans. Those people may need to be included in the bond’s definition of handlers, even if the plan’s custodian is heavily automated.
Defined benefit plans with annuity buyouts or lump-sum windows sometimes spur enormous distributions over a short period. If your plan distributes 50 million dollars to participants in a one-time event, the next year’s 10 percent floor jumps, even if ongoing payroll contributions are modest. You do not get to ignore that spike just because it was a one-off.
Common documentation gaps
The DOL does not require you to file the bond policy with Form 5500, but the form asks whether the plan is properly bonded. Auditors often ask for the policy, and the DOL will ask for it on inquiry. I look for three things every time: proof that the surety is Treasury-listed, confirmation that the plan is named or otherwise covered specifically, and a clear per-loss limit equal to or greater than the required amount.
Too many sponsors keep a generic certificate in a shared drive that references “employee dishonesty” without a line to ERISA. That may be a commercial crime policy, not an ERISA bond. Some commercial policies can incorporate an ERISA endorsement. Others cannot substitute for the statutory bond. If you cannot find the rider or endorsement that ties the policy to ERISA’s requirements, do not assume coverage.
I also check the policy term. Bonds typically renew annually. Lapses happen during M&A, staff turnover, or vendor changeovers. If you miss a renewal and discover the gap after a loss, the plan lacks the statutorily required protection during the gap, which can become a fiduciary breach conversation independent of any loss.
Vendor assumptions that backfire
Recordkeepers and custodians are usually diligent about their own bonds. Where I see sponsors trip is in believing those bonds obviate the need to bond internal finance staff. The handling test applies to anyone with the power to initiate, direct, or authorize movement of plan funds. If your treasury team can approve a wire to the trust or out of the trust, they handle funds. The fact that a vendor performs the mechanical step does not eliminate your handling authority.
Another common theme arises with payroll providers. Some payroll vendors transmit deferrals and loan repayments directly to the trust, and they pitch that service as an internal control enhancement. It can be. It does not mean you have no handlers. If HR or payroll can edit routing instructions, change contribution files, or approve transmission amounts, they handle plan property indirectly. Align the bond to that reality.
What happens if the bond is insufficient
ERISA does not impose monetary penalties simply for being under-bonded, but it does treat maintaining the bond as a fiduciary duty. Two things follow. First, reporting a deficient bond on Form 5500 invites follow-up. Second, if a loss occurs that would have been covered by a compliant bond, fiduciaries may be liable for the shortfall. I have seen internal investigations where a small embezzlement, later recovered, still resulted in legal fees and committee time that a clean bond might have prevented from becoming a governance issue. The practical risk is reputational as much as financial. Plan audits include a compliance section, and recurring bonding exceptions tend to draw auditor emphasis.
Plans subject to an IQPA audit sometimes receive a modified opinion if the auditor cannot verify proper bonding. That is a headache you can avoid with paperwork that takes an afternoon to assemble and, if needed, a quick endorsement to purchase.
How to diagnose your current state
A structured review beats guesswork. In mid-size companies, I schedule an hour with treasury, payroll, and benefits operations. We pull the policy, walk the cash path, and map handlers by role, not by org chart. Five questions efficiently surface issues:
- Which positions can initiate, approve, or release movement of plan funds or direct the recordkeeper or custodian to do so? What is the total amount of plan funds that moved in and out last plan year, including contributions, rollovers, distributions, loan activity, and any internal transfers? Does the plan hold employer securities, directly or through a unitized fund? Is the named insured the plan itself or a rider that schedules the plan by name or plan number, and is the surety on the Treasury list? What is the per-loss limit, not just the aggregate, and how does it compare with the 10 percent requirement and the applicable cap?
If you can answer those in writing and support them with exhibits, you are 80 percent of the way to a defensible ERISA bond posture.
Correcting the classics: focused fixes
Under-bonded amount. Ask your broker or surety to issue an endorsement raising the per-loss limit to the required number. If the plan holds employer securities, set a target at or near 1,000,000 dollars unless your 10 percent calculation exceeds it. Keep a copy of the endorsement with your fiduciary files and the Form 5500 support.
Wrong policy type. If you discover that your document is a commercial crime policy without an ERISA rider, request an ERISA-compliant bond. Many carriers can add a rider to a crime policy that meets DOL specifications. Confirm that the policy names the plan and that the plan is the insured party for purposes of loss recovery.
Missing handlers. If internal staff with handling authority are absent from the bond’s coverage definition, work with your carrier to clarify the definition. Most ERISA bonds are blanket, covering all “employees” as defined, but the term employee may or may not capture committee members, leased employees, or independent contractors who function as plan staff. When in doubt, request clarifying language or broadened coverage.
Service provider strategies. If you plan to rely on a service provider’s bond for some functions, obtain a certificate naming your plan as covered. Verify the provider’s surety is Treasury-listed, and retain copies in your files. Do not treat this as a substitute for bonding your own handlers unless you have documentary proof that the provider’s bond truly covers the plan for those handlers’ actions, which is uncommon.
Lapse repair. If you find a past lapse, document the dates and secure coverage prospectively immediately. Many sponsors also record an internal memo to the file describing the lapse, steps taken to remediate, and process changes to prevent recurrence. If an IQPA audit is in play, share the remediation memo with the auditor early rather than waiting for fieldwork.
Edge cases that reward a closer look
Participant-directed brokerage windows. If your plan offers a brokerage window, assets remain within the trust even if participants buy individual securities. The recordkeeper or brokerage provider handles those trades, but internal staff who can move money into or out of the brokerage sweep accounts may be handlers. Also consider that trading spikes can inflate funds handled.
Hardship and distribution fraud risk. The last few years saw a rise in social engineering that targets plan distributions. If your internal team processes or approves bank account changes or distribution requests, treat those roles as handlers. Some sponsors tighten multifactor authentication and dual approvals, then forget to adjust the bond to the higher movement of funds through those approval points.
Multiple EINs or plans after acquisitions. Post-merger environments often leave you with several plans or legacy payroll systems. Each plan needs to be evaluated on its own. A parent-level bond is not automatically compliant for each plan. A global bond can work, but you should schedule each plan and confirm per-loss limits at the plan level.
Trust-to-trust transfers. When consolidating plans, transfers between trusts can reach large numbers that dwarf ordinary cash flows. Those amounts count in the funds handled figure. If the transfer occurred last year, revisit the 10 percent calculation and adjust the bond if needed for the current year.
Plan-to-Plan loans or related-party notes. Unusual, but I have seen money purchase or DB plans hold notes from controlled group entities. The authority to originate or service those notes can constitute handling. Ensure the people who manage those instruments are within the bond’s scope.
The governance angle: how committees keep this clean
A recurring calendar item solves most bonding issues. In well-run plans, the fiduciary committee or its delegate reviews bonding annually, timed a few months after fiscal year end when cash movements are known. The review includes the prior year’s funds handled, current handlers by role, vendor attestations, and the policy. The committee minutes reflect that the bond amount and coverage were reviewed and deemed compliant, or that a change was requested. That single page of minutes often saves time during audits and demonstrates a prudent process if the DOL asks questions.
I also encourage controllers to maintain a simple one-page process map of plan cash flows, from payroll files through vendor interfaces to the trust and back out through distributions and loans. This makes it easier to keep the handler list current when someone leaves or when systems change. If a new executive joins with signatory rights, the map reminds the team to add that person to the bond’s employee definition or confirm blanket coverage.
Working with brokers and carriers who know ERISA
Most major carriers write ERISA bonds. The difference shows up in service. A broker who routinely places these bonds will not blink when you ask for the Treasury listing for the surety, a confirmation of per-loss limits, or a rider naming specific plans. If the broker struggles to answer basic ERISA questions, consider moving the placement to a firm with retirement plan experience. The cost difference is typically minimal, while the paperwork clarity is night and day.
I also ask carriers to avoid aggregate sublimits that threaten to sink per-loss coverage below the required number when layered policies sit on top of crime programs. Simpler is better, especially if you anticipate leadership turnover or M&A activity that will put your policy under a microscope.
A brief word on Form 5500 and auditor interactions
On Form 5500, Schedule H, the plan reports whether it is covered by a fidelity bond in the required amount. If you answer no or leave the item blank, expect questions. Auditors will request the policy and often verify the surety’s Treasury listing. If they cannot tie the per-loss limit to the statutory minimum, they may cite a compliance finding.
Be prepared to explain your 10 percent calculation. I keep a short worksheet with total contributions, rollovers in, loans issued, distributions, loan repayments, and any unusual transfers. I then show the 10 percent figure, the applicable cap, and the selected bond amount. This avoids debates later about what exactly “funds handled” included. When a plan holds employer stock, I include a line item that confirms the 1,000,000 dollar cap is in play.
Preventive controls that reduce the chance of loss
A bond is a backstop. It does not replace internal controls. The same practices that deter fraud also make the bonding conversation simpler: segregation of duties between initiators and approvers, positive pay and call-back verifications for bank changes, MFA on recordkeeper portals, and rapid reconciliation of payroll contributions to trust receipts. I care less about perfect theoretical controls and more about pragmatic gates a fraudster would actually struggle to bypass. If your process can move six figures on a single person’s approval, tighten it or document why the risk is tolerable and how the bond level reflects that reality.
Cost, budget, and proportionality
ERISA bonds are inexpensive relative to the assets at stake. Premiums commonly run a few hundred to a few thousand dollars per year, depending on bond size and structure. I rarely see cost as a barrier, which is why auditors have little patience for under-bonding. If your calculation points to a higher amount, pay for it. The delta in premium is small compared with the risk of reporting a deficiency or Swift bonds guide absorbing a loss that the bond could have covered.
For small plans, especially one-participant 401(k)s, the bond can be an afterthought until a rollover or distribution event spikes the handled amount. Most sureties will write small bonds quickly. If you serve that market, maintain a ready list of carriers and a short intake template so your clients are bonded within a day of your notice.
What to do this week
If you cannot say with confidence that your plan’s ERISA bond is the right type, in the right amount, and tied to the right people, take these concise steps:
- Pull the policy, verify the surety is on the Treasury list, confirm the per-loss limit, and check that the plan is specifically named or clearly covered. Recalculate last year’s funds handled using contributions, distributions, loan activity, rollovers, and unusual transfers, then apply the 10 percent rule and applicable cap. Map handlers by role and system access across payroll, treasury, HR, and vendor portals, and align the bond’s coverage definition with that map.
None of this requires a committee offsite or a consultant’s slide deck. It requires focused attention, a few emails to your broker, and a half hour with your treasury lead. Once you do it cleanly once, the annual refresh takes minutes.
A closing perspective from the field
The most damaging ERISA bond problem I encountered did not involve a seven-figure fraud. It was a 42,000 dollar distribution misdirected after an HR generalist approved a bank change without a call-back. The recordkeeper processed exactly what the plan told them to do. The plan’s bond was 100,000 dollars, but the policy was a crime form without an ERISA rider, and the carrier initially denied coverage. We fixed the control in a week. We remediated the participant and recovered most of the funds. We spent months, however, fielding auditor questions and documenting why the bond had not complied with the statute at the time of loss. The premium difference between the incorrect policy and an ERISA-compliant bond would have been under 300 dollars per year.
The lesson is not fear. It is proportionality. The ERISA bond is one of the cleanest boxes you can check in plan governance. Get the type right, calculate the amount from the facts, name the plan properly, and revisit the moving parts once a year. Everything else in fiduciary work is harder. The bond, if managed with the same care you give payroll files and investment menus, can be the easiest part of your compliance year.
A well-kept ERISA bond also speaks to culture. It says your plan fiduciaries do not rely on assumptions, vendor marketing language, or “we’ve always done it this way.” They verify. They adjust when facts change. And they preserve the trust that participants place in the promise of their benefits. When the DOL or your auditor reads your file, that is what you want them to see.