Custody Statement Reconciliation Automation for Multi-Custodian RIAs

Every quarter, the same week arrives, and with it the same sentence from the operations lead. Not "we're behind." Something closer to: "We already know two or three of these are going to be off. The only question is how long it takes us to find them and prove why."

That sentence is what custody statement reconciliation actually feels like at a mid-market RIA running $200 million to $2 billion in assets across Schwab, Fidelity, and Pershing. It is never one reconciliation. It is three, sometimes four, each custodian delivering statements in its own format on its own schedule, each needing to tie back to whatever Orion or Black Diamond shows as the client's official position. When the numbers agree, nobody notices. When a small pricing difference shows up on a thinly traded bond, or a dividend posts a day early at one custodian, or a transfer clears at Fidelity before it clears at Schwab, somebody has to find the break, decide whether it matters, and write down what they did about it.

In practice, at firms this size, the person finding those breaks is rarely the compliance officer. It is a client service associate or a junior operations analyst who has quietly become the reconciliation specialist, checking three browser tabs against a spreadsheet before anyone else is allowed to touch the numbers. That person's judgment is valuable. The three hours a week they spend re-typing custodian data into a format Orion can compare against is not.

The cost of manual reconciliation, in partner and staff hours

The economics here are straightforward, even without a precise industry-wide figure to cite. A firm with three custodians runs the same reconciliation exercise three times over, once per custodian relationship, and the work scales with the number of custodians and accounts, not with the complexity of any single account. Add a fourth custodian relationship, whether from an acquisition or a new referral source, and the reconciliation workload does not grow by a quarter. It grows by roughly a third, because a new file format and a new set of quirks just entered the pipeline.

What partners actually pay for is not the reconciliation itself. It is what the firm gives up while someone is doing it by hand: the same person is not reviewing exception reports, not preparing for the next client meeting, not doing the work an advisory firm bills for. Every hour spent matching a Pershing statement line to an Orion position report is an hour that does not show up as billable advisory time, and it does not show up as a client conversation either. That is the real payback calculation for automating this work. It is not "the software costs less than the labor." It is "the labor was never supposed to be spent here in the first place."

There is a compliance cost layered on top of the economic one. Under SEC Rule 204-2, the Investment Advisers Act's books and records rule, a registered investment adviser has to maintain accurate records supporting the firm's calculations and client statements, and an examiner can ask to see how the firm confirmed that a client's custodial records match its own books. A reconciliation process that lives in someone's personal spreadsheet, updated inconsistently and never versioned, is a weak answer to that question. It is not that the manual process is necessarily wrong. It is that nobody can prove, months later, exactly what was checked and when.

How automated matching and exception routing actually works

The mechanics are less exotic than the phrase "AI automation" tends to suggest, and that is deliberate. The system pulls the custodian statement, whether that arrives as a CSV, a PDF, or a feed through the custodian's own data API, and normalizes it into a common structure: account number, security identifier, quantity, price, and date. It does the same with the corresponding export from Orion or Black Diamond. Then it matches line by line, flagging anything that does not tie out within a tolerance the firm sets itself, whether that is a price variance of a few cents or a quantity mismatch of any size.

The part that actually changes the operations lead's week is what happens after a mismatch is found. Instead of a person scanning an entire statement for anything unusual, the system routes only the breaks, the lines that failed to match, into a queue with the specific reason attached: price variance, missing trade, timing difference, or a security that exists at the custodian but not yet in the portfolio system. A human still makes the judgment call on each one. The system's job is to make sure that person is looking at three flagged lines instead of three thousand matched ones.

This is worth stating plainly, because it is where the "AI will replace my team" fear usually comes from. The system does the reading and the matching. The people keep the review and the sign-off. Nobody on the operations team stops being the person who understands why a break happened; they just stop being the person who has to find it in the first place by eye.

Where the data lives, and why that answers the audit trail question

For a firm already running Orion or Black Diamond against Schwab, Fidelity, and Pershing, the real apprehension is rarely about whether reconciliation can be automated. It is about what happens to custody data once a new system touches it, and whether that new system becomes one more vendor with access to client account numbers and positions.

The answer that matters to a compliance officer is that this kind of automation is built to sit inside the firm's existing stack rather than replace or bypass it. The custodian connections the firm already has, whether through direct feeds or its existing Orion or Black Diamond integration, stay exactly where they are. The reconciliation logic runs on infrastructure the firm controls, deployed in the firm's own cloud environment rather than a third-party platform's shared servers, so client custody data is not handed to a new SaaS vendor as a condition of automating the matching work.

That distinction matters for Rule 204-2 specifically. Every match, every flagged exception, and every resolution gets logged with a timestamp and the reasoning behind it, which is exactly the kind of record an examiner asks for when reviewing how a firm reconciles client accounts against custodial records. The audit trail belongs to the firm's own compliance function. It is not a report a vendor produces on request; it is a log the firm's own team can pull at any time, because the system runs on infrastructure they control.

One clarification is worth making directly, because it comes up often in reconciliation discussions that borrow language from the wrong jurisdiction. The UK's CASS rules, the Client Assets Sourcebook enforced by the Financial Conduct Authority, govern how UK-regulated firms safeguard client money and assets. They do not apply to a US-registered investment adviser. The relevant US obligation is SEC Rule 204-2, and any reconciliation process built for a US RIA should be built against that rule, not a UK framework that happens to show up in generic reconciliation content.

Why a mid-market RIA does not need an enterprise reconciliation platform

Most of what gets written about statement reconciliation is aimed at a different buyer entirely: a bank, a fund administrator, or a large broker-dealer reconciling millions of transactions a day across dozens of internal systems. That is the market the large reconciliation platforms, the Ducos and Smartstreams of the world, are built to serve, and the pricing and implementation timelines reflect it.

A $200 million to $2 billion AUM RIA with three custodian relationships and one portfolio system does not have that problem. It has a narrower, more specific one: match statements from Schwab, Fidelity, and Pershing against Orion or Black Diamond, flag what does not tie out, and keep a clean record of how it was resolved. Buying an enterprise-grade platform built for balance-sheet-level reconciliation to solve that problem is a mismatch on both cost and complexity, and it usually means handing custody data to a vendor whose primary customers are banks, not a wealth management practice with a compliance officer who wants to keep control of the process.

The right-sized answer is automation built specifically around the stack the firm already runs, not a new platform that requires the firm to adapt its process to someone else's enterprise workflow.

Frequently asked questions

What is custody statement reconciliation, exactly?

Custody statement reconciliation is the process of confirming that the positions, balances, and transactions shown on a custodian's statement, from Schwab, Fidelity, or Pershing, match what the firm's own portfolio system, such as Orion or Black Diamond, records for the same accounts. Any difference, whether a pricing discrepancy, a missing trade, or a timing gap between when an event posts at the custodian versus the portfolio system, is a break that has to be investigated and resolved before the firm can rely on its own reporting.

Does SEC Rule 204-2 require RIAs to reconcile custodian and portfolio records?

SEC Rule 204-2 requires registered investment advisers to maintain true, accurate, and current books and records, including records that support the firm's calculations and client account statements. While the rule does not spell out a specific reconciliation methodology, an examiner reviewing how a firm confirms its records match custodial data will expect to see evidence of a consistent process and a record of how discrepancies were identified and resolved, which is precisely what a documented reconciliation workflow provides.

Will reconciliation automation replace the operations team or the compliance officer?

No. The system is built to handle the repetitive matching work, comparing custodian statements against the portfolio system and flagging what does not tie out, so staff spend their time reviewing genuine exceptions instead of scanning full statements by eye. The judgment calls, deciding whether a flagged discrepancy matters and what to do about it, along with the compliance sign-off, stay with the firm's people.

Can this run alongside Orion or Black Diamond without replacing either system?

Yes. The reconciliation layer is built to sit alongside the portfolio system a firm already uses, pulling data from Orion or Black Diamond and from the custodian feeds the firm already has in place, rather than requiring the firm to migrate to a new platform. The existing systems keep doing what they already do; the automation removes the manual matching step between them.

Ready to see what this looks like for your custodian mix

If your operations team is still matching Schwab, Fidelity, or Pershing statements against Orion or Black Diamond by hand every reporting cycle, the fastest way to know whether automation makes sense for your firm is a direct conversation about your specific custodian mix and reconciliation cadence. Book a free strategy call and we will walk through where the manual work is costing your team the most time, and what a reconciliation workflow built around your existing stack would actually look like.

For firms weighing this against a broader compliance automation effort, our RIA compliance automation page covers how the same approach extends to ADV filings, annual reviews, and other recordkeeping obligations under the Investment Advisers Act. And for a wider view of how custom AI systems fit into a wealth management firm's operations beyond reconciliation, see our financial services automation overview.