Celebrating 31 Years of Client Service

Call
Investment data mapping and validation workspace

Data Services

Multi-custodian data aggregation for advisors

Custodial data aggregation means getting daily positions, transactions, and cash from each custodian and trust system into the one portfolio system your firm reports from, then proving the numbers agree. It is not consumer account aggregation, where apps link people's bank and card accounts. CSSI, an independent firm, helps advisory firms set up feeds, map accounts and securities, and reconcile the result.

Reviewed by Trevor Keast, Principal & Data Services Manager · Updated

  • Daily custodian and trust-system feeds into APX, Axys, and other portfolio systems
  • Account, security, and transaction mapping that holds up through new accounts, transfers, and corporate actions
  • Daily cash and position reconciliation before data reaches combined client reports
  • Help choosing between direct feeds, an aggregator, or your platform's own data service

From a CSSI customer engagement

Daily data feeds kept running through a move to Tamarac

When an APX client moved to Tamarac, CSSI's Data Services team set up the same daily data feeds to produce a format Tamarac accepts. The client pulls and processes that data daily.

Read the Tamarac data feed story

Definitions

Which kind of data aggregation does your firm need?

Consumer account aggregation

Most results for "financial data aggregation" describe consumer services. Plaid, MX, and Yodlee let people connect bank and card accounts to apps, with their permission. That is a different job from keeping an advisory firm's portfolio records.

Custodial data aggregation

This page covers custodial aggregation. Each custodian a firm uses sends daily account data. Trust departments may keep their books in a trust accounting system such as SEI Trust 3000. The job is getting both into the portfolio system the firm reports from, such as APX, Axys, Orion, or Tamarac, and checking that they agree.

Held-away account aggregation

Some client assets sit where the firm has no custodial feed, such as a 401(k). Third-party aggregators collect these through connections the account owner permits. Many firms report this data without posting it to the accounting book. Decide which treatment you need.

Combined reports come last

A household report that spans custodians needs every account mapped once, one agreed reporting date and basis, and transfers traced through both accounts. A custom layout cannot fix conflicting source dates or open cash and position differences. Reconcile first, then build the combined view.

How the work moves

From the old system to a verified cutover

  1. 01

    Source data

    History, accounts, and securities

  2. 02

    Map and convert

    Accounts, identifiers, and transactions

  3. 03

    Validate

    Balances and history reconciled

  4. 04

    Cutover

    Accepted, documented, and live

Aggregation approaches

Four ways to get multi-custodian data into one system

Most firms use more than one of these. Choose by source, not by vendor. A trust system, a large custodian, and a few held-away accounts may each need a different path. Test a sample before committing.

Scroll across to review all four columns.

Four ways to get multi-custodian data into one system
ApproachBest fitWhat your firm ownsTypical failure points
Custodian direct feeds into your portfolio systemAPX, Axys, or another accounting system with custodian interfaces. Advent Custodial Data, for example, delivers trade-date positions, transactions, and cash activity before the market opens on T+1.Custodian account authorizations, the import, the security master, translation rules, and daily reconciliation.New accounts missing from the feed. Unmapped transaction codes. Unknown securities. A late file that leaves yesterday's data in place.
Third-party aggregator or data vendorMany custodians, held-away accounts, or a source your system cannot reach directly. ByAllAccounts, for example, aggregates positions, transactions, prices, and tax lots through user-permissioned connections.Account permissions, reconnections, mapping the delivered format, and reconciliation.A connection stops when a login changes. Coverage varies by institution. Identifiers do not match your security master.
Platform-native aggregationFirms on a platform that runs its own custodian connections. Orion reconciles brokerage data with custodians overnight. Addepar connects directly to custodians. Black Diamond includes outsourced daily reconciliation.Clean account opening and linking, reviewing the exceptions the platform raises, and any source outside its network.Uncovered sources. History and cost basis at conversion. Firm-specific treatments that must fit the platform's model.
Managed or outsourced feed processingFirms keeping their current system without staffing the daily feed and reconciliation work, or needing cover for a key person.Approving the reconciled result, the exception policy, and telling the provider about new accounts, transfers, and closures.Unclear ownership of breaks. Late notice of new accounts or transfers. Procedures that live in one person's head.

Where CSSI helps

Feeds, reconciliation, and combined reports for firms with several sources

CSSI's Data Services team reviews source coverage, refresh timing, translation, mapping, and the daily checks around a feed. CSSI works with feeds from the custodians and trust systems a firm uses, and confirms coverage for each source during scoping.
Two published projects show the pattern. When an APX client moved to Tamarac, CSSI's Data Services team set up the same daily feeds to produce a format Tamarac accepts (read the Tamarac story). An SEI Trust 3000 client once reconciled its trust system to Axys monthly using Advent ACD and Axys. That process now runs on CSSI's CyGem platform with CSSI data feeds, CyGem reconciliation, and Portal+ reporting (read the Trust 3000 story).
Reconciled data then feeds the combined report. CSSI builds custom APX and Axys reports and client report packages, and Portal+ delivers them to clients. For reports built inside another platform, confirm the scope in the first review.
When the same breaks keep returning, the cause is often the source data or an undocumented process. CSSI's investment reconciliation services cover cash, position, and settlement checks, cost basis cleanup, and exception documentation.

Setup

How a multi-custodian feed gets set up

  1. Inventory sources and accounts

    List custodians, trust systems, held-away sources, and the target system. Note which accounts are not yet on a feed.
  2. Choose a path for each source

    Use a direct feed, an aggregator, the platform's own connection, or managed processing. Confirm coverage, fields, history, and delivery time with a sample.
  3. Map and translate

    Map accounts and securities. Translate each source's transaction codes, including transfers, fees, and corporate actions, into the target system's types. Replay a sample period.
  4. Reconcile, then report

    Compare cash and positions with each source daily. Agree tolerances, exception owners, and what holds a combined report. Add sources once the first ones run clean.

Project outputs

What a feed project should leave you with

Source and feed inventory

Every custodian, trust system, and aggregator connection, with accounts, record types, delivery time, and owner.

Mapping tables

Account, security, and transaction-code mappings, with rules for new accounts and unfamiliar codes.

Reconciliation procedure

Daily cash and position checks, tolerances, and the agreed treatment of transfers in transit and corporate actions.

Exception log and release rules

Who researches each type of break, when it escalates, and which exceptions hold a combined report. Written down so the next staff change does not reset it.

Connected services

When the problem sits next to the feed

Investment reconciliation services

If daily breaks are the bottleneck, scope cash, position, and settlement reconciliation as recurring BackOffice work. Explore reconciliation services.

Investment data management

If feeds arrive but identifiers, history, or classifications are wrong, fix the underlying dataset first. Review data management services.

Portfolio data migration

Changing platforms? CSSI converts data out of APX, Axys, Orion, Addepar, Black Diamond, and Tamarac. Scope history, cost basis, and cutover as a separate project. Explore migration services.

Sources

Vendor details referenced on this page

Third-party descriptions come from each vendor's public pages as of October 2026: Advent Custodial Data, the ByAllAccounts investor FAQ, Orion, Addepar, SS&C's annual report on Black Diamond, Plaid, MX, and Yodlee. Coverage and terms change, so confirm them for your sources.

Questions

Frequently asked questions

Straight answers to the implementation, workflow, and fit questions that usually come up first.

What is custodial data aggregation?

It is the daily collection of positions, transactions, and cash from each custodian and trust system a firm uses. The data is loaded into one portfolio accounting system and reconciled, so the firm works from a single book of record.

How do RIAs aggregate data from multiple custodians?

Most use a mix: direct custodian feeds into the portfolio system, a third-party aggregator for sources without a feed, or a platform such as Orion, Addepar, or Black Diamond with its own connections. Each still needs mapping, transaction translation, and daily reconciliation.

What is the difference between account aggregation and custodial feeds?

Custodial feeds come from the institution holding the assets, under the firm's custodial relationship. Account aggregation usually reaches accounts the firm does not hold, through connections the account owner permits. Feeds typically support the accounting book. Held-away data often supports reporting and planning.

Is financial data aggregation the same as open banking?

Not for an advisory firm. Open banking services such as Plaid, MX, and Yodlee let consumers share bank and card data with apps. Advisors need custodian positions, tax lots, transactions, and corporate actions reconciled to a portfolio system.

How should a combined report handle different source dates and transfers?

Document the reporting date and basis, and the as-of date of each source. Agree how late records and missing prices affect release. A transfer between custodians can post on different days at each end, so trace it through both accounts before the combined view goes out.

Can CSSI handle our custodian feeds if we keep our current portfolio system?

CSSI's data and BackOffice services are scoped around the system a firm already runs. Published work covers APX, Axys, and Tamarac. Coverage for your custodians and trust systems is confirmed during scoping.

Next step

Talk to CSSI about your custodian feeds

List your custodians, trust systems, and the portfolio system you report from, and describe where data arrives late, fails to reconcile, or holds up a combined report. CSSI can review the feed options, mapping, and daily reconciliation work for a defined scope.