ACATS Reject Reason Codes: The Most Common Causes and How to Eliminate Them Before Submission
A reject in ACATS is almost never random. The Automated Customer Account Transfer Service, run by the NSCC under FINRA Rule 11870, auto-rejects a transfer when minimum data requirements are not met, and the receiving firm then waits a full cycle to resubmit. The good news: rejects cluster into a small set of predictable reason categories, and most are preventable before you ever press submit.
Why ACATS rejects are predictable, not random
Every transition desk has its own folklore about what causes rejects. One person swears it is title mismatches, another says signatures, a third says restricted assets. They are each partially right, because they are each working from whatever they happened to see last quarter. When you aggregate enough rejects across a real book, the distribution stabilizes, and a handful of categories account for the large majority of rebooks.
That is the whole opportunity. If you know which categories drive most of your rejects, you know exactly where to spend your pre-submission validation time. Fixing a cause behind 4 percent of your rejects is fine. Fixing one behind a quarter of them changes your timeline. This is the core logic behind FastTrackr's advisor transition platform: catch the predictable failures before submission instead of after.
The most common ACATS reject categories
These are the categories that show up again and again on a transition desk. None of them require guesswork to prevent.
| Reject category | What triggers it | The pre-submission fix |
|---|---|---|
| Tax ID / SSN mismatch | The number on the transfer does not match the carrying firm's record | Validate the SSN or EIN against the source statement, not the new-account form |
| Account title / registration mismatch | Name or registration type differs between firms (e.g. individual vs joint vs trust) | Match registration exactly to the delivering firm's records |
| Account number error | Transposed, truncated, or wrong account number entered | Pull the number directly from a recent statement and verify digit count |
| Signature / authorization | Missing, mismatched, or unauthorized signature on the TIF | Confirm the authorized party and signature before submission |
| Non-transferable or restricted assets | Proprietary funds, restricted securities, or assets not eligible to transfer in kind | Flag and pre-resolve non-transferable holdings before initiating |
| Account already in transfer | A prior ACATS request is still open on the account | Confirm no open transfer exists before initiating a new one |
| Documentation required | Estate, trust, or entity accounts needing supporting paperwork | Gather entity and authority documents up front |
The pattern across every row is the same: the data needed to prevent the reject already exists on a document the client gave you. The reject happens because that document was read by a human under time pressure, or not read at all.
Where the cost actually lands
A reject is not just a do-over. It is a do-over plus a lost cycle plus a client who is watching their accounts sit in limbo during the most fragile part of the move. The receiving firm has a limited validation window under the rules, and a kicked transfer resets the clock. Stack a few of those across a large book and the timeline stretches from days into weeks.
Paper-driven processes are where this gets worst, because the same field gets keyed by hand multiple times and every keystroke is a chance to introduce a mismatch. FastTrackr's platform data shows manual, paper-based intake producing dramatically higher not-in-good-order rates than digital workflows. That gap is the entire argument for reading the source documents with software instead of eyes.
How pre-submission validation eliminates each category
The fix is structural, not heroic. Read the source statements and account forms with document intelligence, extract the fields that drive rejects (tax ID, registration, account number, asset list), and validate them against the receiving-firm record before anything is submitted. The categories above stop being surprises and become checklist items the system clears automatically.
For desks running many transitions at once, this is what makes scale survivable. A consultant moving several books cannot personally eyeball every TIF. FastTrackr's tools for transition consultants push the validation upstream so the reject rate drops across every account in flight, not just the one in front of you. You can see the downstream effect on timeline and retention in this advisor transition case study.
Two habits make the biggest difference in the first hours of a move. First, validate from the statement, never from a re-typed form. Second, resolve non-transferable assets before initiating, not after the reject. For the broader operational sequence around all of this, the first 72 hours of an advisor transition checklist lays out where validation fits in the timeline.
Frequently asked questions
What is the most common reason an ACATS transfer gets rejected? There is no single cause, but mismatches dominate: tax ID or SSN that does not match the carrying firm's record, account title or registration that differs between firms, and account number errors. These are data-matching failures, which means they are preventable by validating against the source statement before submission.
How long does an ACATS reject delay a transfer? A reject resets the cycle. Because the receiving firm has a limited validation window under FINRA Rule 11870, a kicked transfer sends you back to resubmission and the clock starts again. Across a large book, repeated rejects can turn a days-long transfer into weeks.
Can ACATS rejects be prevented automatically? Most can. The data needed to prevent the common rejects already exists on the client's statements and account forms. Document intelligence reads those documents, extracts the reject-driving fields, and validates them before submission, which removes the manual keystrokes where mismatches are introduced.
Are non-transferable assets an ACATS reject or a separate problem? They surface as a reject category but are better handled before initiation. Proprietary funds and restricted securities that cannot transfer in kind should be flagged and resolved up front, so they do not kick the whole transfer mid-cycle.
