ACAT transfers are a follow-up problem

An ACAT transfer can look simple from the client’s side. They sign paperwork, give the receiving firm a recent statement, and expect their assets to move. Inside the advisory firm, that same transfer can create a chain of small operational tasks that’s hard to track.

Someone checks the application for missing information. Someone submits it to the receiving custodian. Someone watches for status changes, follows up when the transfer stalls, and tells the client what’s happening. If the transfer includes multiple accounts or assets that don’t move in kind, there may be more questions to resolve. Then there’s the final check that the assets arrived and the account is ready for the next step.

The work isn’t always difficult. It’s fragmented. Status details may arrive in a custodian portal, a secure message, an email, or a file. The firm’s CRM may show that a transfer is underway without showing its actual stage. A client asks for an update, and an operations teammate has to reconstruct the latest information before replying.

For a firm managing a busy book, that manual coordination adds up. It can delay the client’s first meaningful planning conversation, tie up operations capacity, and create avoidable uncertainty at the start of a relationship.

Workflow automation can help by keeping a clear record of each transfer, surfacing the next action, following up on missing items, and sending timely client updates. It doesn’t mean handing custody decisions to software. It means giving your team a reliable process that’s easier to monitor and less dependent on someone remembering to check another inbox.

Map the transfer before automating it

Start by documenting what happens from signed paperwork to a completed transfer. The details differ by firm, custodian, account type, and transfer method, so a useful workflow should reflect your actual process rather than a generic checklist.

A typical workflow might include:

The client confirms the account details and provides a recent statement.
The team checks that the transfer request is complete and that account details match.
An authorized person reviews and submits the paperwork through the appropriate channel.
The receiving firm or custodian acknowledges the request.
The transfer moves through processing, with questions or rejections routed back to the team.
The client receives a progress update, particularly if the process takes longer than expected.
The team confirms that assets arrived and records any remaining items, such as a residual sweep or follow-up review.

For each stage, define three things: what counts as evidence that the stage is complete, who owns the next action, and how long the team waits before checking again. A status called “in progress” isn’t enough if nobody knows whether it means the request was received or the assets are actually moving.

The same discipline applies to paperwork. Decide which information must be checked before submission, who can approve an exception, and where the firm stores the final records. If your process for collecting transfer paperwork is the biggest source of delay, see how to automate ACAT transfer paperwork in your advisory. For firms looking at the wider account-movement process, automating account transfer paperwork may help you spot connected steps that belong in the same workflow.

What the automation should track

A useful workflow gives the team one place to see what’s happening, even if status information comes from more than one source. That doesn’t always require a direct connection to every custodian. Depending on your systems and access, updates may come through a supported integration, a secure portal export, or a teammate confirming a status change.

The key is to track the information that changes the next action:

Client and household name, with the relevant account reference.
Receiving and delivering institutions.
Date paperwork was received, reviewed, and submitted.
Current stage and the source of that status.
Missing documents or corrections requested.
The teammate responsible for the next action.
The date for the next check-in.
Client updates already sent.
Confirmation of assets received and any remaining transfer items.

That record helps answer basic questions quickly. Which transfers have been waiting for an acknowledgment? Which applications need a client’s signature? Which cases are near an internal follow-up deadline? Which clients haven’t heard from the firm since submission?

A workflow can also use simple rules to flag delays. For example, if a submitted request hasn’t received an acknowledgment after the firm’s defined interval, create a task for an operations teammate to verify the status. If a request is rejected, route it for review rather than sending a generic message. The rule should prompt a person to investigate, not assume why the transfer stopped.

That distinction matters. A missing update might mean the custodian hasn’t processed the request, the transfer was rejected, or the information hasn’t reached your system yet. An automated process should make uncertainty visible rather than papering over it with a confident-sounding status.

How an ACAT workflow agent works end to end

An agent for this process acts like a workflow coordinator. It reads information from the systems and documents the firm has approved, updates the transfer record, and prepares the next action for a person or client. The agent should work within defined permissions and preserve a record of what it did.

Here’s what that can look like.

1. A transfer request enters the workflow. A teammate marks a new request in the CRM or transfer tracker, or an approved intake process creates the record. The workflow checks that the expected fields are present. It may flag a missing account statement or an incomplete form, but it shouldn’t submit a request simply because the fields look complete.

2. The paperwork gets checked against a defined list. The agent compares the submitted information with the firm’s checklist. It can flag inconsistent names, missing signatures, or account details that need a person to verify them. Where a check requires professional judgment or access to a system the agent can’t safely use, the task stays with a teammate.

3. A person reviews and submits. The authorized team member confirms that the information is correct and submits the request using the firm’s approved process. The workflow records the submission date and the available confirmation. This keeps accountability clear and avoids treating a draft or upload as proof that a transfer is underway.

4. The workflow watches for updates. When a new status comes in through an approved source, the workflow updates the case and captures where the information came from. If a status hasn’t changed by the next check date, it creates a follow-up task. The assigned teammate sees the context, including the previous check and the specific question that needs answering.

5. The agent prepares follow-up messages. If the client needs to provide a document or correct information, the agent can draft a clear request based on the actual issue. A person reviews messages when required by the firm’s policy. Once the client responds, the item is marked received and returned to the review queue.

6. Clients get useful updates. A client shouldn’t have to ask whether anything is happening. Based on confirmed transfer stages, the workflow can prepare a short update that explains what’s complete, what’s pending, and whether the client needs to do anything. If the information is unclear or a delay needs a sensitive explanation, it routes the case to a person instead of sending a guess.

7. Completion is checked, not assumed. The case remains open until the team confirms that the expected assets arrived and records any outstanding items. The workflow can then prompt the next onboarding or planning task. It shouldn’t mark the transfer complete solely because a status changed to “processed” if the firm still needs to verify the receiving account.

If this is the kind of operational bottleneck you’re dealing with, book a 60-min Omni Audit. We’ll map the handoffs, identify where the record should live, and decide which steps are suitable for automation.

Reduce follow-up without hiding exceptions

The goal isn’t to eliminate every email or every human check. The goal is to stop making your team repeatedly rediscover what’s going on.

A good workflow reduces routine follow-up in a few concrete ways. It assigns an owner when a transfer needs attention. It sets a next-check date when there’s no new information. It distinguishes between an item waiting on the client and one waiting on an institution. It keeps the last confirmed status and its source visible. And it prompts a client update when the firm has reached a meaningful point in the process.

The workflow should also make exceptions easy to spot. Examples include a rejected request, a mismatch between the statement and form, an account type that needs special handling, or a transfer with both in-kind and cash components. Those cases can be routed to the right person with the facts already gathered.

This approach complements other operational workflows. For example, the Meeting Prep Agent can bring portfolio information, recent communications, and goal progress into a one-page brief before a client meeting. The Client Onboarding Agent can guide a new client through fact-finding and document collection, then prepare an onboarding pack. If meeting preparation is another recurring time drain, read about AI meeting prep for financial advisory firms.

Those workflows should connect at the handoff, not create another disconnected task list. When a transfer is confirmed, the onboarding record should reflect it. When the adviser has a review meeting, the brief should show the transfer’s actual status and any open issue. The team should be able to see what happened without searching across email threads and spreadsheets.

Keep people in control of sensitive steps

A transfer involves personal and financial information. Automation needs clear boundaries around what information it can access, what it can change, and what actions require a person’s approval.

Set permissions so the workflow only sees the records and documents needed for its tasks. Keep transfer submissions, approvals, and decisions with authorized staff. Record the source of status updates and the actions taken. Define what should happen when information is incomplete or conflicting. Test the workflow using realistic cases, including rejected requests and delayed updates, before relying on it in live operations.

Client communications need similar care. A workflow can prepare a useful update from confirmed information, but it shouldn’t make promises about completion dates or interpret a custodian’s message beyond what it says. Let the team review messages in situations where the status is ambiguous or the client needs a more personal conversation.

You’ll also want a fallback. If a data source stops updating, the workflow should flag that fact and keep the case visible. Quietly relying on old information is worse than asking a teammate to check the portal. For more on setting boundaries and oversight for firm workflows, see AI agent governance for financial advisory firms.

Make the business case with your own numbers

ACAT tracking is a good automation candidate when the firm has enough transfer volume to create repeated follow-up, but not enough visibility to manage it easily. Don’t assume every saved minute turns into lower costs. Some capacity gets redirected to client work, planning, or other operations. Measure the change against your process.

Start with a baseline over a few weeks:

How many transfers are active at once?
How many times does the team check status for each transfer?
How much time goes to locating documents, reconstructing history, and asking for updates?
How many transfers need a second request for missing or corrected information?
How long does it take the firm to notice a stalled or rejected request?
How often does a client contact the firm first to ask for an update?

Then compare those measures after the workflow has been in use for a reasonable period. Track the number of manual status checks, time spent per case, age of open tasks, and client update intervals. Also track exception rates and corrections. A faster process isn’t a win if it creates more cleanup work or sends inaccurate messages.

Operational leakage can arise across many processes. That’s not a forecast of savings from ACAT automation. It’s a reminder to look at the combined cost of repeated admin, delays, and work that depends on individual memory. Transfer tracking may be one part of that picture, alongside meeting preparation, advice documentation, and client onboarding.

For instance, meeting preparation and notes can take time away from other work. The Meeting Prep Agent can reduce the manual gathering required before a review. Other workflows may support advice documentation, depending on the firm’s process. Each workflow needs its own controls and measures. The useful question is where repeated work is taking capacity away from client service and advice delivery.

What to bring to an Omni Audit

An Omni Audit is a working session to map the workflow as it runs today, identify manual handoffs, and look at the systems and information involved.

The session can produce practical outputs such as:

A process map showing the transfer stages, owners, sources of status information, and common exceptions.
An automation opportunity list identifying which follow-ups and updates could be prepared or triggered, and which steps need a person’s review.
A first-step recommendation covering the workflow to test, the information it needs, and the measures you can use to evaluate it.

Bring a recent example of a completed transfer and one that took longer than expected. Remove or protect personal information according to your firm’s policies. We can use the examples to understand where status was hard to find, what caused repeat work, and what a more reliable handoff would look like.

To see the service context for your firm, see Omni for financial advisory firms. You can also book a 60-min Omni Audit and use the session to decide whether ACAT tracking is the right first workflow. For the firm-specific audit overview, visit the financial advisory audit page.

The best starting point is usually a narrow one. Pick a transfer stage where the team is doing repeated checks or waiting on missing information. Make the current status visible, give each next action an owner, and make client updates reflect confirmed facts. Once that works, you’ll have a clearer basis for deciding what to automate next.

How to Automate ACAT Transfers at Your Firm