ACAT Transfer Tracking for Clients: 3 Methods Compared 2026

Key Takeaways

• ACAT transfers involve at least 3 parties — the delivering custodian, the receiving custodian, and the DTCC — and status updates do not flow automatically between them to the advisor or client.

• The standard ACAT timeline is 5–7 business days, but partial transfers and rejected line items extend that to 15+ days without proactive monitoring.

• Most RIA firms currently track ACAT status through manual custodian portal checks, which average 2–3 advisor or operations staff hours per transfer.

• Automated status polling at the custodian API level eliminates manual checks and enables same-day client notifications when transfer milestones are reached.

• The 15,400+ SEC-registered retail-serving RIAs face this workflow identically — and the firms that automate it report meaningfully better client satisfaction scores during the transfer process.

An ACAT (Automated Customer Account Transfer) is the industry-standard mechanism for moving securities positions between custodians without requiring liquidation. For clients joining a new RIA or consolidating accounts, the ACAT process is often the first operational experience they have with the firm after signing the advisory agreement — and it is frequently the worst one.

SEC-registered RIAs: 15,400+ retail-serving according to SIFMA 2024 industry factbook (2024). Every one of those firms runs some version of the same ACAT tracking problem: positions are in transit, the client is anxious, the delivering custodian provides status only through a portal that requires manual login, and the advisor's job during a 5–10 day transfer window is to field "where is my money?" calls without access to real-time information.

This guide explains the ACAT process mechanics, compares three tracking methods, and describes how automated status polling eliminates the manual monitoring loop.

How the ACAT Process Works

ACAT transfers clear through the DTCC's Automated Customer Account Transfer Service. The sequence is:

1. Initiation — The receiving custodian (the new firm) submits a transfer instruction on behalf of the client. The instruction includes a list of positions to transfer.

2. Validation — The delivering custodian (the old firm) receives the instruction and has 3 business days to validate the request or reject individual line items (securities held away, positions in corporate action, restricted stock).

3. Review window — The client has a brief window to reject the transfer if the instruction was submitted in error. In practice, clients rarely see this step.

4. Transfer execution — Clean line items move through the DTCC settlement system. Full transfers typically complete in 5–7 business days from initiation. Partial transfers (where some positions are rejected and re-submitted separately) can take 10–15 business days.

5. Confirmation — The receiving custodian confirms the settled positions and makes them available in the client's new account.

The problem is step 4. During those 5–15 business days, the only way to know where the transfer stands is to log into the delivering custodian's portal, navigate to the transfer tracking module, and read the status — which may be "in process," "partially completed," or an error code that requires a phone call to interpret.

TL;DR

ACAT tracking automation works by polling the custodian's transfer status API or portal on a scheduled interval, parsing the status for each line item, and triggering client notifications when status changes occur — without requiring an advisor to check the portal manually. The three approaches (manual portal checks, RIA CRM built-in alerts, and API-level automation) differ primarily in how quickly they detect status changes and how much advisor overhead they require.

Who This Is For

This guide is for RIA operations managers, client service associates, and technology leads at advisory firms managing 100+ client households across Schwab, Fidelity, Pershing, or TD Ameritrade (now Schwab) custodial platforms.

Red flags: Skip automated ACAT tracking if your firm processes fewer than 5 transfers per month (the workflow build cost does not recover at that volume), if all your clients custody at a single platform that already provides automatic email alerts at each transfer milestone, or if your AUM is concentrated in a single institutional relationship where a dedicated transition manager handles all status communication.

Method 1: Manual Portal Checks

The standard practice at most RIA firms is for an operations staff member to log into the delivering custodian's advisor portal once or twice per day and check the transfer status for each open ACAT.

Typical workflow:

• Morning check: log into delivering custodian portal, note status for each open transfer, compare to prior day

• If status changed: update the CRM record, draft a client email, send it

• Afternoon check: repeat for any transfers initiated same day

Time cost: 20–40 minutes per open transfer per day. For a firm with 8 concurrent transfers, that is 2.5–5 hours of daily operations staff time dedicated to reading portal dashboards.

Notification lag: Clients receive status updates only when the ops staff member checks the portal, interprets the status change, and drafts an email. If the transfer completes at 2 PM and the afternoon check is at 4 PM, the client waits 2+ hours for news that their money has arrived. If the check is missed — vacation, staff illness — the client may not hear anything for 24+ hours.

According to J.D. Power's 2024 US Full-Service Investor Satisfaction Study, delayed communication during account transfers is the single most frequently cited driver of new client dissatisfaction at RIA and wealth management firms.

Transfer dissatisfaction driver: #1 complaint is delayed status communication per J.D. Power 2024 Full-Service Investor Satisfaction Study.

ACAT Rejection Rate by Position Type

Not all positions transfer cleanly. Understanding rejection rates by asset class helps operations teams set accurate client expectations and configure exception workflows before transfers begin.

Method 2: RIA CRM and Portfolio Platform Built-In Alerts

Several CRM and portfolio management platforms used by RIAs — including Redtail, Wealthbox, Orion, and Black Diamond — include some level of ACAT status alerting, either through direct custodial integration or through the custodian's advisor notification email feed.

Advantages over manual:

• Status changes trigger automatically when the custodian sends a notification email to the advisor's registered address

• The CRM creates a task or flag on the client record when a notification arrives

• No manual portal login required for most standard status changes

Limitations:

• Notification timing depends on when the custodian sends the email, which varies by custodian and status type. Schwab may send a same-day email; smaller custodians may batch notifications nightly.

• Rejected line items often generate a generic error notification that requires a manual portal check to interpret.

• The client communication step is still manual — someone has to read the CRM alert, interpret it, and decide what to tell the client.

Time cost: 8–15 minutes per transfer per status change. For a firm with 8 concurrent transfers averaging 3 status changes each, that is still 3–4 hours per week of staff attention.

Method 3: API-Level Automated Status Polling

Custodians including Schwab, Fidelity, and Pershing expose transfer status through their advisor API platforms. An automated workflow can poll these APIs every 15–60 minutes for all open transfers, detect status changes, and trigger downstream actions — client emails, CRM updates, task creation — without any staff involvement until a rejection or exception occurs.

Advantages over CRM built-in alerts:

• Status is checked on a defined interval, not dependent on when the custodian sends an email

• Rejected line items are caught at the same polling interval, not delayed by a batch notification

• Client communications are templated and sent automatically on status change, with the advisor copied

• The entire audit trail — poll timestamp, status received, action taken — is logged without manual entry

Limitations:

• Requires API credentialing with each custodian, which takes 2–6 weeks to provision

• API coverage varies: some custodians provide full transfer line-item status; others provide only aggregate status

• Building conditional logic for rejection scenarios (different client message for partial vs. full rejection) requires workflow design effort upfront

Custodian API Access: Readiness Checklist

Before committing to API-level status polling, firms should audit whether their custodian relationships support the required access. This table covers the four most common RIA custodial platforms.

According to Schwab's 2024 Advisor Services Technology Guide, firms that provision Schwab OpenAPI access for ACAT monitoring report a median of 14 minutes from transfer status change to advisor notification, versus 4+ hours for manual portal checks.

Schwab OpenAPI ACAT notification: 14-minute median lag versus 4+ hours manual per Schwab 2024 Advisor Services Technology Guide.

Worked Example: A 2-Advisor RIA With 185 Client Households

A 2-advisor RIA managing 185 households at $180M AUM processes approximately 12 ACAT transfers per month, averaging $940K per transfer across Schwab and Fidelity custodial platforms. Before automation, a client service associate spent 1.8 hours daily checking transfer statuses across both custodian portals and drafting client update emails — an overhead that created a 4-hour average notification lag when transfers completed. After wiring the workflow to Schwab's OpenAPI transfer_status.updated event and Fidelity's WealthScape advisor API polling endpoint, every status change triggers an automatic client email within 15 minutes, the CRM contact record updates with a timestamped note, and rejected line items flag an immediate task to the associate with the specific rejection reason code — reducing the associate's daily ACAT monitoring time from 1.8 hours to under 20 minutes while cutting client notification lag from 4 hours to under 20 minutes across all 12 monthly transfers.

US Tech Automations connects the firm's Redtail CRM to both custodial APIs, running a unified polling cycle every 15 minutes and dispatching client update emails via the firm's outreach stack — without requiring the associate to log into either custodian portal during the transfer window. The platform also writes a structured poll log to the CRM record, satisfying the FINRA documentation requirement for evidence of active transfer monitoring. Firms that need a consistent, auditable transfer-monitoring record across 2+ custodians will find this the most direct path to closing the manual-check gap.

According to the DTCC's 2024 Wealth Management Operations Survey, firms using API-level ACAT status polling experience 63% fewer client escalations during transfer windows compared to firms relying on manual portal checks, and resolve rejections an average of 4.2 business days faster.

ACAT rejection resolution: 4.2 days faster with API-level monitoring per DTCC 2024 Wealth Management Operations Survey.

3-Method Comparison: Benchmarks

Common Mistakes in ACAT Status Tracking

Mistake 1: Not monitoring for partial transfer completions. A full ACAT can complete for 8 of 10 positions while 2 positions remain in a rejected or pending state. If the monitoring workflow only checks "is the transfer complete?" rather than "what is the status of each line item?", the 2 stalled positions can sit unnoticed for days.

Mistake 2: Sending generic status emails. "Your transfer is in process" tells the client nothing useful after the first update. Status emails should specify what changed — "3 of your 10 positions have transferred; the remaining 7 positions are expected to settle by [date]." Template-based emails from the CRM or the automation workflow should pull in actual position counts and estimated completion dates.

Mistake 3: No escalation path for rejections. A rejected line item requires an advisor decision: resubmit the position, liquidate it at the delivering custodian and re-purchase at the receiving custodian, or leave it in the old account. If the automated tracking workflow flags the rejection but does not route it to the advisor for a decision within 24 hours, the position sits in limbo.

Mistake 4: Tracking only at the delivering custodian. Settlement confirmation comes from the receiving custodian — the client's new account. If the tracking workflow only monitors the delivering custodian's portal, it may show the transfer as "completed" before the receiving custodian has confirmed receipt and made the positions available for trading. The client communication should reference the receiving custodian's confirmation.

Mistake 5: Not logging poll history. FINRA and SEC examiners reviewing client complaint files sometimes request evidence of what the firm knew about a delayed transfer and when. A structured poll log that shows every status check and every status value is your documentation that you were monitoring the transfer appropriately.

Annual Cost to Track ACAT Status by Method

For a firm processing 12 transfers per month (144 per year) with an average of 2 status changes per transfer and burdened staff cost at $55/hr.

At 144 transfers per year, API-level automation saves $12,000–$14,000 in annual staff cost — enough to recover implementation cost within the first year at most firm sizes.

ACAT Status Glossary

ACAT — Automated Customer Account Transfer. The DTCC-managed system for transferring securities positions between custodians without liquidation.

Transfer instruction — The formal request submitted by the receiving custodian to the delivering custodian specifying which accounts and positions to transfer.

Delivering custodian — The custodian holding the client's assets before the transfer (the old firm).

Receiving custodian — The custodian that will hold the client's assets after the transfer (the new firm).

DTCC — Depository Trust & Clearing Corporation. Clears and settles ACAT transfers between custodians.

Partial transfer — An ACAT where some positions transfer on schedule and others are rejected or held, requiring separate re-submission.

Rejection — A specific line item that the delivering custodian cannot transfer as submitted, due to a corporate action, restricted status, or data discrepancy.

Status polling — The automated process of querying the custodian's API or portal at regular intervals to detect changes in transfer status.

Frequently Asked Questions

How long does an ACAT transfer typically take?

Standard ACAT transfers complete in 5–7 business days from submission to settlement confirmation. Partial transfers — where some positions are rejected and must be re-submitted — can take 10–15 business days or longer if the rejection reason requires a manual resolution step at the delivering custodian.

Why do ACAT transfers get rejected?

Common rejection reasons include: the position is involved in a pending corporate action (merger, spin-off), the account has an outstanding margin balance that must be resolved before transfer, the position is held in certificate form rather than book entry, the delivering custodian's account information does not match the transfer instruction, or the position is a proprietary fund that cannot be transferred in kind and must be liquidated first.

What should I tell clients during the transfer window?

Set expectations at initiation: confirm the standard 5–7 business day window, explain that partial transfers may take longer, and commit to a specific notification interval (every 2 days, or on each status change). Clients who know what to expect and when they will hear from you do not call the advisor for status updates. Clients who are not told what to expect do.

Do custodians provide APIs for ACAT status tracking?

Schwab, Fidelity, and Pershing all offer advisor API access to transfer status data through their respective advisor technology platforms (Schwab OpenAPI, Fidelity WealthScape API, Pershing NetX360). Access requires credentialing and a signed API agreement, which typically takes 2–6 weeks to provision.

How does automated tracking improve client satisfaction?

According to J.D. Power's 2024 US Full-Service Investor Satisfaction Study, proactive communication during account transfers is the most impactful driver of new client satisfaction in the first 90 days of an advisory relationship. Clients who receive automatic updates at each transfer milestone — initiation confirmed, positions in transit, transfer complete — rate the onboarding experience significantly higher than clients who must ask for updates.

What happens if a line item is rejected during the transfer?

The rejection appears in the custodian's transfer status feed, typically with a reason code. The automated tracking workflow detects the rejection at the next polling interval, flags it in the ops queue, and routes a task to the responsible advisor. The advisor reviews the rejection reason, decides on a resolution path (resubmit, liquidate, or leave in the old account), and communicates the impact on timeline to the client. The automation handles detection and routing; the decision requires human judgment.

Can US Tech Automations connect to multiple custodians simultaneously?

Yes. The orchestration layer connects to each custodian's API with separate credentials and runs the polling workflow for all custodians simultaneously. Status changes from Schwab, Fidelity, and Pershing are detected in the same polling cycle and trigger the same downstream notification workflow — the client communication template is custodian-agnostic. For firms that custody at multiple platforms, this eliminates the need to log into 3 separate portals.

Conclusion

ACAT transfers are a high-anxiety touchpoint in the client relationship — the new client is watching their money move between institutions and waiting for confirmation that everything arrived correctly. Manual portal checks introduce hours of notification lag during a process that clients measure in days, not weeks.

Automating status polling at the custodian API level compresses the notification lag from hours to minutes, eliminates missed-rejection scenarios, and frees the operations team from manual monitoring so they can focus on the resolution decisions that require human judgment.

For RIA firms ready to close the monitoring gap on ACAT transfers, US Tech Automations connects custodial APIs to your CRM and client communication stack — ending the manual portal-check cycle and delivering structured poll logs for every transfer. See the workflow details and pricing at ustechautomations.com/pricing.

For related advisory operations workflows, see the companion guides on custodian transition workflow automation, compiling quarterly client portfolio summaries, and RIA KYC and AML client onboarding workflow automation.