ACAT Rejections

Last Updated: July 2026

For many advisors, an ACAT transfer feels like it should be the easy part of a transition. Submit the request, wait a few days, and the assets move from one firm to another.

That's often true—until the transfer gets rejected.

An ACAT rejection doesn't necessarily mean something is seriously wrong. It simply means the delivering firm couldn't process the transfer request as submitted. Until the issue is corrected, the transfer stops.

Most rejections are preventable. The challenge is knowing what to look for before the request is ever submitted.

What Is an ACAT?

ACAT stands for Automated Customer Account Transfer Service. It's the industry system used by most broker-dealers and custodians to transfer eligible client accounts electronically.

Instead of manually moving every security, participating firms use the ACAT system to exchange account information and transfer assets through a standardized process.

It's efficient, reliable, and widely used—but only when the information submitted matches what the delivering firm expects.

What Is an ACAT Rejection?

An ACAT rejection occurs when the delivering firm cannot accept the transfer request because something doesn't match or doesn't meet transfer requirements.

Think of it like mailing a package to the wrong address.

The delivery system works perfectly. The information doesn't.

Until the discrepancy is corrected, the transfer cannot move forward.

Common Reasons ACAT Transfers Are Rejected

Account Registration Doesn't Match

One of the most common reasons for rejection is a mismatch between the account registration at the delivering firm and the registration entered on the transfer request.

A missing middle initial, different trust name, outdated business entity, or ownership discrepancy can all prevent processing.

See Account Registration Mismatches for a deeper explanation.

Incorrect Account Number

It sounds simple, but incorrect account numbers remain a frequent cause of rejected transfers.

Even a single incorrect digit can stop the process before it begins.

Account Restrictions

Accounts that are frozen, restricted, involved in legal proceedings, or subject to certain compliance reviews may not be eligible for immediate transfer.

Ineligible Assets

Not every investment can move through the ACAT system.

Certain proprietary mutual funds, alternative investments, annuities, private placements, and limited partnerships may require separate transfer processes—or may not transfer at all.

Learn more in Non-ACAT Assets.

Outstanding Account Activity

Pending trades, unsettled transactions, recent deposits, corporate actions, or account maintenance activity can temporarily delay an otherwise valid transfer request.

Incomplete Documentation

While ACAT is electronic, supporting paperwork still matters.

Missing authorizations or incomplete documentation can prevent processing until everything is in good order.

Why Rejections Matter

A rejected ACAT request doesn't just delay one account.

It often creates a chain reaction.

Operations teams investigate the rejection. Advisors contact clients. New paperwork may need to be completed. Processing timelines restart.

Meanwhile, clients wonder why their assets haven't moved.

The operational delay becomes a client experience issue.

Some Rejections Are Predictable

Experienced transition professionals develop a good sense for which accounts deserve additional attention before transfers begin.

Trust accounts, retirement accounts, business entities, inherited IRAs, margin accounts, and accounts holding alternative investments often require closer review.

Identifying potential issues early dramatically reduces unnecessary delays later.

Preparation Is Better Than Resubmission

Correcting a rejected transfer isn't usually difficult.

It's simply time-consuming.

The better approach is preventing avoidable rejections through preparation.

Verify account numbers directly from current statements.
Confirm registrations match exactly.
Review asset eligibility before requesting transfers.
Identify special account types early.
Confirm required documentation is complete.
Track every submitted transfer until completion.

These steps aren't glamorous, but they save significant time over the course of a large transition.

Technology Doesn't Replace Review

Modern custodians have excellent transfer systems.

The technology itself isn't usually the problem.

Most ACAT rejections occur because the information entering the system doesn't match reality.

Technology processes information exactly as it's submitted. It doesn't know that a trust changed names two years ago or that a client recently updated ownership after a spouse passed away.

That's where operational review remains essential.

Don't Assume Every Delay Is an ACAT Problem

It's common for advisors to blame ACAT whenever an account transfer takes longer than expected.

Sometimes the ACAT system isn't the issue at all.

The real cause may be pending paperwork, non-transferable assets, missing cost basis information, or post-transfer reconciliation work happening outside the ACAT process.

Understanding the difference helps advisors set realistic expectations for clients.

Successful Transfers Start Before Submission

The smoothest transfers don't happen because someone reacts quickly after a rejection.

They happen because someone anticipated the issue before the request was submitted.

Reviewing registrations, verifying documentation, identifying special asset types, and preparing clients ahead of time dramatically improves transfer efficiency.

That's one reason transition execution has become a specialized discipline rather than simply another administrative task.

Key Takeaway

Most ACAT rejections aren't surprises. They're the result of information that didn't match, documentation that wasn't complete, or assets that required a different transfer process.

The firms that experience the fewest transfer delays aren't necessarily lucky—they're prepared. By identifying potential problems before requests are submitted, advisors can keep transfers moving, reduce client frustration, and spend less time correcting issues after the fact.