In-service distributions and incoming rollovers are the two transaction types most plan sponsors treat as paperwork — and they are the two most likely to be approved without anyone confirming the plan document actually permits them. Every dollar that leaves the trust while a participant is still employed, and every dollar that comes in from another plan or IRA, is a decision the plan has to be able to defend later.
The recordkeeper will process what it is told to process. It does not know what your adoption agreement says about age-based withdrawals, which money sources you allow to be withdrawn, or whether the check a new hire mailed in came from a qualifying plan. That verification is the employer’s job, and it belongs to whoever holds the ERISA plan administrator role.
Why these transactions are fiduciary, not clerical
ERISA requires the plan to be operated in accordance with its written terms. A distribution that the document does not authorize is an operational failure regardless of who keyed it in, and it can put the plan’s tax-qualified status at risk.
Incoming rollovers carry the mirror-image risk. Accepting money that did not come from an eligible source, or accepting after-tax or Roth money the plan is not set up to track, contaminates the trust with amounts the plan cannot administer correctly.
Start with what your document actually allows
Before you write a procedure, read your adoption agreement. In-service withdrawal rights are elective features — plans differ enormously, and two plans at the same recordkeeper can have opposite answers. The questions to answer in writing:
- Does the plan permit in-service distributions at all, and at what age or on what condition?
- Which money sources are available — deferrals, match, profit sharing, rollover accounts, after-tax?
- Is a source required to be fully vested before it can be withdrawn?
- Does the plan accept rollovers in, and from which plan types and account types?
- May a participant roll money in before satisfying eligibility for deferrals?
- Does the plan allow rollover-source withdrawals at any time — a common and frequently forgotten election?
If your answers do not match what the recordkeeper’s system is configured to do, you have found a problem before it becomes a correction. That reconciliation belongs in the same review cycle you use for plan document restatements.
What sponsors must verify on an outgoing in-service request
1. Confirm the triggering event exists under the document
Age-based, rollover-source, after-tax, and disability withdrawals are different features with different conditions. Identify which provision the request is being approved under and record that reference.
2. Verify the source and the vested amount
Available balance and vested balance are not the same number. If your service records and the recordkeeper’s disagree, fix the data first; see our guidance on reconciling payroll and recordkeeper records.
3. Confirm this is not really a hardship or a loan
Participants frequently ask for “a withdrawal” when the facts point to a hardship request or a loan, each with its own documentation standard. Route the request to the right feature rather than reshaping the feature to fit the request. Our posts on hardship withdrawal and loan documentation and plan loan defaults cover those tracks.
4. Check spousal consent and beneficiary implications
Some plans — particularly those with annuity or joint-and-survivor features, and plans that trace back to a merged money-purchase or defined benefit arrangement — require spousal consent for certain distributions. Confirm what your document requires before paying,.
5. Confirm required notices were delivered
Eligible rollover distributions carry a notice explaining the participant’s rollover rights and withholding consequences. The plan must be able to show it was provided, not merely that the recordkeeper “usually sends it.”
6. Approve in writing, then verify what was paid
An approval that exists only as a checkbox in a portal is thin evidence. Keep a record showing who approved it, under which provision, on what date, and reconcile the amount actually distributed and withheld against what was authorized.
What sponsors must verify on an incoming rollover
1. Confirm the plan accepts it
Check both the source (another qualified plan, a 403(b), a governmental 457(b), an IRA) and the character of the money (pre-tax, Roth, after-tax). If the plan does not accept Roth rollovers, accepting one creates a tracking obligation the plan cannot meet.
2. Get reasonable evidence the money is what it claims to be
A plan is allowed to rely on reasonable documentation — a distribution statement, a letter from the prior plan, a check made payable to the trust. Decide in advance what package you require, apply it consistently, and keep it.
3. Confirm the money lands in the right source bucket
Rollover money is generally not subject to your plan’s vesting schedule and is often withdrawable on different terms. If it is coded as employer money, the participant’s rights are wrong from day one and nobody notices until a distribution or a compliance test.
4. Track Roth basis and after-tax amounts separately
Roth rollovers carry holding-period and basis information that must move with the money. If the receiving system cannot hold it, the tax reporting on the eventual payout will be wrong.
5. Handle rollovers from participants not yet eligible to defer
Some documents allow this and some do not. Where it is allowed, the person becomes a participant for rollover-account purposes without becoming eligible for deferrals or match.
An eight-step self-check you can run this quarter
- Pull your adoption agreement and write a one-page summary of every in-service and rollover-in provision, by money source.
- Compare that summary against how the recordkeeper’s system is configured, in writing.
- Pull the last twelve months of in-service distributions and incoming rollovers from the recordkeeper.
- For each one, identify the document provision it was approved under. Flag any you cannot map.
- Confirm vested amounts against your own service and payroll records, not just the recordkeeper’s balances.
- Confirm each incoming rollover has source documentation on file and was coded to a rollover source.
- Confirm notices and, where required, spousal consents are retrievable — not assumed.
- Write down who approves these requests, what evidence they must keep, and where it is stored.
If step 4 produces requests you cannot map to a provision, treat it as a scope question rather than a one-off. Isolated fixes tend to hide a configuration or training issue affecting an entire class of requests, and a documented correction path is far cheaper than one discovered during an audit.
Where sponsors get hurt
- Approving an age-based withdrawal the document does not offer, because the portal made the option visible.
- Paying an unvested amount because “available balance” was read as vested balance.
- Accepting a rollover check with no supporting statement, then discovering it came from a non-qualifying arrangement.
- Coding rollover money as employer money, subjecting it to a vesting schedule that should never have applied.
- Missing spousal consent on a plan that inherited survivor-annuity features through a merger.
- No retrievable evidence of who approved what — the failure mode that turns a small operational issue into a finding.
What you can delegate — and what stays with you
A capable 3(16) plan administration partner can own the operating machinery: reviewing each request against the document, verifying sources and vesting, requiring and retaining rollover documentation, tracking notices, and keeping an evidence file that survives an examination.
What cannot be delegated is the settlor side. Only the employer decides which in-service features the plan will offer and signs the document that creates them. Only the employer holds the service and payroll history behind vesting. And under ERISA someone must still be the named fiduciary responsible for the plan’s operation. Prudent selection and ongoing monitoring of the providers doing the work stays with the sponsor too — including the fee reasonableness review that supports keeping them, and periodic plan reviews.
Admin316 accepts the appointment most providers decline
This is where Admin316 differs. We accept the ERISA 402(a) named fiduciary appointment in writing — the role most providers explicitly refuse to take — alongside 3(16) administration. That means the responsibility for operating the plan according to its written terms, including approving and documenting in-service distributions and incoming rollovers, sits with a fiduciary who has signed up for it rather than with an HR generalist reading a form.
If you cannot currently produce the document provision behind your last five in-service distributions, that is the honest place to start. Book a short call and we will walk your adoption agreement, your recordkeeper configuration and your approval evidence side by side, and tell you plainly what needs to change.
