Why Advisors' Client Transfer Paperwork Keeps Getting Rejected

Ask anyone who's run client onboarding at an RIA for more than a year and they'll have a story about a transfer that bounced back over something that felt almost insulting in how small it was — an account number transcribed one digit off from what the client read straight off their own statement, a name that didn't match exactly because of a maiden name still on file at the old firm. The client is excited to move their money to you. And then it just doesn't move, for reasons nobody explains clearly, and someone on your team spends the next two days untangling it.

We went looking for real numbers on how often this happens, because most of what's published on it is vague vendor language — "transfers can be delayed" — which isn't a number, it's a shrug. What we found, and where it actually came from, is worth walking through.

What's actually happening: ACATS, in plain terms

When a client moves from one custodian to another — say, from a wirehouse to Schwab because they just hired your firm — the transfer runs through a system called ACATS (Automated Customer Account Transfer Service), operated by the DTCC, the organization that clears most securities transactions in the US. Your team submits a transfer instruction with the client's account details, taken from their old statement. The old firm — "the carrying firm," in industry language — has a window to accept or reject it. If everything matches, the assets move. If anything doesn't, it bounces back, and someone has to figure out what went wrong and resubmit.

Almost every new client relationship at an RIA that doesn't start entirely in cash depends on this process completing cleanly. It's one of the least glamorous parts of the client experience and one of the most consequential for how the relationship starts.

How often this actually happens

We went to FINRA directly for a real figure — the industry's own self-regulator, not a software company with a fix to sell. Their Customer Account Transfer Task Force found a hard-reject rate of 11–13% of all transfer instructions. That's from an older FINRA report, so treat it as a historical baseline rather than an exact current-quarter number — but the mechanism behind it hasn't gone anywhere.

The single most common cause the task force identified wasn't client error. It was an account number, submitted by the receiving firm straight off the client's own statement, that didn't match what the old firm had on file — frequently because the old firm had gone through a systems migration or a merger and quietly renumbered accounts on its own end. The client did everything right. The transfer still bounced.

What a rejected transfer actually costs you

There's no clean industry-wide dollar figure for this, and we're not going to invent one just to have a number in a headline — a lot of what's published on RIA operations does exactly that, and it's not worth the paper it's printed on. What we can describe honestly is the mechanism: every rejected transfer means someone on your ops team has to notice it bounced, figure out why, get back in touch with the client — sometimes for information they already gave you once — correct the instruction, and resubmit, while that client sits there wondering why the firm they just chose can't seem to move their own money.

For a firm doing steady new-client volume, that's not one team member's occasional bad afternoon. It's a recurring tax on exactly the moment in a relationship where a client's first real impression of your operations gets formed — before you've had the chance to prove yourself any other way.

Walk through what one rejection actually involves and it stops being abstract. Someone submits the instruction on a Monday. Wednesday, it comes back rejected — account number mismatch. Someone has to notice the rejection sitting in a queue, pull up the client's file, call or email them to ask them to re-check their statement (awkward, because the client assumed this was handled), get a corrected number, resubmit, and wait out the transfer window again. That's not five minutes. It's a half-day of someone's attention spread across a week, on a task that should have taken one submission.

It also lands hardest on exactly the wrong client. A high-net-worth household moving a complicated mix of account types — trusts, retirement accounts, a taxable account, maybe a business account — is more likely to hit a mismatch somewhere in that mix than someone with a single simple IRA. Which means your most valuable new relationships are disproportionately exposed to the worst version of this experience, right when you most need them to feel like they made the right call.

The industry knows this is a problem — the plumbing is actively being rebuilt

This isn't just an RIA operations complaint. In September 2025, the DTCC announced it was removing an entire processing step from the ACATS cycle — eliminating what's called the "Settle Prep" stage — cutting a full, clean transfer down to 3–4 business days instead of the longer cycle firms had lived with for years. That's a real, dated, current change, and it's a signal that the infrastructure layer takes this friction seriously enough to re-engineer it. It doesn't fix the account-number-mismatch problem specifically — that's a data-quality issue between two firms, not a processing-speed issue — but it tells you the pain is recognized well above the level of any single firm's ops team.

What actually prevents the rejection in the first place

The fix that matters most happens before submission, not after rejection. Most of what causes a hard reject is checkable in advance: does the account number on the client's statement actually correspond to a live, correctly formatted account at the carrying firm; is the name on the transfer instruction spelled exactly as it appears on record; is every required signature and authorization actually attached and legible.

A system that reads a client's uploaded statement, extracts the account details automatically instead of someone re-typing them by hand at the end of a long day, and validates the format before the instruction ever gets submitted catches the same mismatches a careful human reviewer would — just before they cost you three or four days, instead of after. That's a document intelligence problem as much as it's an operations problem: getting structured, verified data out of a scanned or photographed statement reliably, right at the point of intake, rather than relying on someone typing carefully under time pressure.

Handle the data with the care it deserves

A transfer instruction carries a client's account number, tax ID, and enough personal detail to be a genuine target if it's handled carelessly. Any system touching this step needs the same standard you'd expect from your custodian: access limited to the people who actually need it, a clear audit trail of who touched what and when, and — because a transfer instruction still ultimately needs a human authorization — no fully automated submission without someone actually signing off first. The goal is catching the mismatch before a person approves it, not removing the person from the decision.

Why this is worth fixing before the rest of your ops stack

Onboarding tends to be the first thing worth automating at a firm, not the tenth, and there's a practical reason for that beyond it being the most visible. It's the one workflow every single new client passes through, it's short and self-contained enough to actually scope and fix, and it's the one place where a bad experience has a clean, direct line to a client wondering whether they made the right decision — before you've had a chance to earn their trust any other way. Compare that to something like ongoing compliance documentation, which matters just as much but where a client never sees the mess if it's handled badly. Onboarding, they see immediately.

That's also why it tends to be the first workflow an outside consultant scopes when they start working with a firm on operations — not because it's the biggest dollar number on a spreadsheet, but because it's the fastest place to prove that fixing the plumbing actually changes what a client experiences, which makes everything after it an easier sell internally.

Frequently Asked Questions

What is ACATS?

ACATS (Automated Customer Account Transfer Service) is the system, operated by the DTCC, that moves a client's brokerage account from one custodian to another. Almost every new client relationship at an RIA that doesn't start from cash depends on an ACATS transfer completing successfully.

Why do account transfers get rejected?

The most common cause identified in FINRA's own review is a mismatch between the account number the client provided, taken from their own statement, and what the old firm has on record — frequently caused by a systems change or merger on the old firm's side rather than client error. Missing signatures and authorization gaps are the other common causes.

How long should a transfer take?

Following a September 2025 change by the DTCC, a clean transfer with no exceptions now runs 3–4 business days. A transfer that gets rejected and has to be corrected and resubmitted takes considerably longer, with no fixed ceiling — it depends entirely on how quickly the mismatch gets identified and fixed.

Can this be automated without creating a compliance problem?

Yes, if it's built correctly. The automation belongs at the validation step — catching mismatches before submission — rather than at the authorization step. A person still needs to review and approve the actual transfer instruction; the system's job is making sure that person isn't approving something that's about to bounce.

See what this is costing you

We built a free calculator that estimates what manual document handling — including exactly this kind of transfer paperwork — actually costs a firm per year, using industry-standard per-document handling rates. It takes about two minutes and doesn't require your email to see the number. Try the Document Processing Cost Calculator, or if you'd rather just talk it through, book 30 minutes with us.