Firms that sponsor their own '40 Act funds operate across fund admins, transfer agents, sub-advisors, and custodians — plus their advisory business. Your data platform should unify all of it.

A '40 Act fund sponsor data platform unifies data from the fund administrator (NAV, fund accounting, general ledger, trial balance), the transfer agent (shareholder records, flows, account-level activity), sub-advisors (holdings, trades, attribution), custodians (positions, cash), and internal systems (advisory CRM, billing, HR, compliance) into one firm-owned Snowflake environment. It is not a fund accounting system, not a transfer agent platform, and not a filer — it is the data layer that sits across all of them, owned by the sponsor, queryable by the sponsor, and independent of any single service provider's portal.

The '40 Act Fund Sponsor Data Problem

Sponsoring a proprietary mutual fund or ETF multiplies a firm's service provider footprint. The advisory business already depends on custodians, a CRM, a portfolio accounting system, and a billing platform. Add a '40 Act fund to the complex and five new relationships enter the operating map: a fund administrator, a transfer agent, a custodian for the fund (often distinct from the advisory custodians), a sub-advisor (if the fund is sub-advised), a distributor, a printer, and the fund board itself. Each of those parties holds a piece of the truth about the fund, and none of them hold all of it.

Fragmentation across service providers is the default state, not an edge case. The fund admin knows NAV and accounting. The transfer agent knows shareholders and flows. The sub-advisor knows trades and attribution. The custodian knows positions. The sponsor's own systems know the advisory side of the house. Assembling a single picture — of the fund, of the shareholders, of the sponsor's combined fund and advisory business — requires pulling from five or six portals, reconciling naming conventions, and stitching the pieces together in a spreadsheet that nobody else can reproduce.

The regulatory burden compounds it. Form N-PORT lands monthly (public every third month). Form N-CEN lands annually. Form N-1A prospectus updates run on a 16-month cycle. Rule 38a-1 compliance programs need year-round evidence. Rule 17j-1 personal securities monitoring, Rule 22c-1 forward pricing, Rule 22c-2 frequent trading, Rule 38a-1 fair value determinations, Rule 22e-4 liquidity classifications, Rule 18f-4 derivatives risk management — each has its own data dependency, its own source system, and its own reconciliation point.

The sponsor's advisory side and the fund side share clients but not data. A household that is both an advisory client and a fund shareholder appears twice — once in the CRM, once at the transfer agent — with no clean way to tie the records together. That matters for Rule 22c-2 frequent-trader monitoring, for conflict-of-interest disclosures, for allocation of trades, and for understanding the sponsor's own business mix. It also matters for the sponsor's chief executive, who needs to know how much of the advisory firm's revenue depends on flows into the proprietary fund.

Reconciliation across the fund admin, transfer agent, and custodian is its own ongoing practice. The fund admin's books should equal the transfer agent's shares-outstanding multiplied by NAV. The custodian's positions should equal the fund admin's accounting positions. The sub-advisor's trade blotter should equal the custodian's settled trades. When those equalities break — and they break regularly — the break lives in someone's inbox until it is chased down. A unified data platform makes the break a query, not an investigation.

Board reporting is the quarterly crescendo. Independent trustees expect the CCO, the CIO, and the treasurer to walk in with current data on fund performance, fee waivers and expense caps, sub-advisor performance, compliance exceptions, NAV errors, distribution and flow trends, and service provider oversight. The assembly of that book — two weeks out, manually, from five portals and a dozen PDFs — is the most visible symptom of the underlying data problem.

What a Unified '40 Act Fund Data Platform Enables

01

Unified Fund + Advisory View

Fund-side data and advisory-side data in one warehouse — so the sponsor's executives, CCO, and CFO can see the full business, not two halves that never meet.

02

Sub-Advisor Oversight Data

Sub-advisor trades, holdings, attribution, and compliance certifications in the same model — with 15(c) renewal materials assembled from continuous data instead of once a year.

03

Board Reporting Automation

Quarterly board packs rendered from the warehouse on a schedule. Fee waivers, expense caps, performance, compliance exceptions, service provider oversight — assembled, not rebuilt.

04

N-PORT/N-CEN Source of Truth

Position-level, derivatives, liquidity, service provider, and director data structured in one model and handed to the filer (DFIN, Confluence, Vermilion) without a last-minute scramble.

05

TA + Custodian Reconciliation

Daily equalities across fund admin, transfer agent, and custodian data surfaced as queryable breaks — not as emails the operations team chases one at a time.

06

Shareholder-to-Client Linking

Permissioned joins between transfer-agent shareholders and advisory CRM households — so Rule 22c-2 monitoring, conflicts disclosure, and business-mix analysis work across the full book.

How Milemarker Works for '40 Act Fund Sponsors

Milemarker ingests the sponsor's fund-side and advisory-side data into a firm-owned Snowflake warehouse. Fund admin feeds from Ultimus, SEI, ALPS, SS&C, BNY Mellon, and State Street deliver daily NAV, holdings, fund accounting, general ledger, and trial balance data. Transfer agent feeds from DST, Ultimus, SS&C GIDS, and others bring shareholder-of-record activity, share-class-level flows, and dividend reinvestment data. Custodian feeds bring positions and cash. Sub-advisor feeds bring trade blotters, holdings, and attribution. Advisory CRM, billing, and HR systems sit alongside them in the same model.

Normalization happens in the warehouse, not in a rigid middleware layer. Different fund admins label the same fields differently; different TAs deliver flows in different formats; sub-advisors use their own accounting conventions. Milemarker's unified fund data model reconciles those differences once, at ingestion, so every downstream query — board reporting, N-PORT assembly, oversight analysis — runs against consistent shape regardless of source.

Entity modeling reflects the actual structure of a fund complex. A fund has share classes; share classes have CUSIPs; CUSIPs have holdings; holdings have issuers. A shareholder has accounts; accounts have activity. A fund is overseen by a board; the board approves service providers; service providers generate feeds. The relationships are modeled explicitly, which is what makes the warehouse queryable at any level — share class, fund, fund complex, sponsor — without rebuilding the join every time.

Navigator AI lets executives, the CIO, the CCO, the CFO, and operations teams ask questions in plain English against the warehouse. "What is our exposure to a given security across the fund AND advisory book?" "Which share classes had net outflows last quarter, and how did that move the expense ratio against the cap?" "Which accounts appear in both the TA and the advisory CRM, and what is our combined revenue from those relationships?" The answers come from the firm's own Snowflake data with source lineage — not from an external black box.

Milemarker Relay automates the recurring work that currently lives in inboxes and spreadsheets. Board prep — the two-week quarterly scramble — runs on a schedule against the warehouse and assembles the book section by section. Fee waiver and expense cap calculations pull from fund admin GL and trial balance data and route to the treasurer for sign-off. Shareholder reporting and semi-annual/annual report workflows collect the pieces from the fund admin, printer, and legal in one tracked process. 15(c) sub-advisor contract renewal materials assemble from the oversight data that has been flowing all year.

Critically, the firm owns the Snowflake instance. The unified fund data, the lineage, and the historical record belong to the sponsor, not to a vendor. That matters when a regulator asks for three years of supporting detail, when a board member asks an unscheduled question, when the sponsor renegotiates its fund admin or TA contract, or when the firm's own analytics and reporting tools need direct access to the data without going through an intermediary.

Before Milemarker

Five portals to check (admin, TA, custodian, sub-advisor, CRM)

Two-week quarterly board prep

CCO pulls evidence from emails and PDFs

Fund and advisory data live in separate worlds

N-PORT data assembled in a last-week scramble

Sub-advisor 15(c) renewal built once a year from scratch

With Milemarker

One data layer spanning every service provider

Auto-assembled board pack from the warehouse

CCO self-serve queries against continuous evidence

Fund and advisory data unified in one model

N-PORT data pre-assembled and handed to the filer

15(c) oversight data continuous, not annual

Who This Is For

RIAs with Proprietary Mutual Funds ($250M+)

Registered investment advisors that have launched their own '40 Act fund — most commonly as a series trust participant or as a stand-alone complex — sit at the crossroads of advisory and fund operations. These firms typically cross $250M+ in fund AUM and operate a parallel advisory business with its own custodians, CRM, and reporting stack. The sponsor data platform is built for exactly this dual profile: fund admin, TA, sub-advisor, and custodian data on one side; advisory CRM, billing, and custodian data on the other; and a single warehouse where they meet. Firms that grew into fund sponsorship from an advisory base — Flat Iron Wealth is a representative example — benefit most from the unified model because their two sides serve overlapping households.

Asset Managers Launching Their First Fund

Asset managers bringing a first '40 Act product to market — whether a mutual fund, an ETF conversion, or a new ETF series — need data infrastructure from day one. Waiting until after launch to assemble the warehouse means the first annual audit, the first N-CEN, and the first board meeting all arrive before the data layer does. Milemarker's model is to stand up the warehouse alongside the fund launch so fund admin, TA, and custodian feeds start flowing in parallel with the fund's operational go-live, and the first board book is rendered from the warehouse, not hand-assembled.

Fund Complexes with Multiple Strategies

Sponsors that run multiple strategies — an equity fund, a fixed-income fund, a liquid alternatives sleeve, and perhaps an actively managed ETF — accumulate data complexity faster than any single fund warrants. Each additional strategy often adds a sub-advisor, adds share classes, adds custodian relationships, and adds reconciliation obligations. A unified data platform scales across the full complex without requiring a separate reporting build for each new fund, and makes cross-fund analysis — issuer concentration across the complex, expense ratio trends across classes, shareholder overlap between funds — a standard query instead of a project.

Sponsors with Sub-Advised Funds

Sponsors that delegate portfolio management to one or more sub-advisors carry the investment advisor's fiduciary responsibility without running the book themselves. That makes sub-advisor oversight — performance monitoring, compliance certification, trade surveillance, 15(c) contract renewal — one of the defining functions of the sponsor's operating model. A unified data platform brings sub-advisor data into the same warehouse as the fund admin and TA data, so oversight is continuous and specific: a question about a sub-advisor's trade pattern last quarter can be answered from the warehouse, not from a request back to the sub-advisor.

Frequently Asked Questions

Do we still need our fund administrator?

Yes. Milemarker does not replace the fund administrator. Ultimus, SEI, ALPS, SS&C, BNY Mellon, and State Street continue to strike NAV, keep the books of account, and own the regulated accounting function. Milemarker ingests the outputs of that work — NAV files, general ledger extracts, trial balances, holdings files, expense accruals — into the firm-owned Snowflake warehouse so the sponsor has a queryable copy of its own fund data alongside advisory, shareholder, and sub-advisor information.

What fund admins does Milemarker integrate with?

Milemarker integrates with the major '40 Act fund administrators — Ultimus, SEI, ALPS, SS&C (including GlobeOp and Advent), BNY Mellon, and State Street. Integration is typically file-based (SFTP of daily NAV, holdings, accounting, and trial balance files) but can include API connections where the admin supports them. The outputs are normalized into a consistent fund data model so the sponsor's internal reporting is independent of the admin's portal.

How do you handle transfer agent data?

Milemarker ingests shareholder and flows data from the transfer agent — DST, Ultimus, SS&C GIDS, and others — at the account and share-class level. That includes daily purchases, redemptions, dividend reinvestments, exchanges, and account-level positions. The TA feed is joined to the custodian and fund admin data so the sponsor can reconcile shareholder activity against fund-side NAV and accounting without pulling three separate reports.

Can Milemarker help with N-PORT or N-CEN?

Yes, indirectly. Milemarker does not file N-PORT or N-CEN. It assembles and structures the underlying data — positions, derivatives detail, liquidity classifications, service provider registries, directors and officers, securities lending activity — and hands that data to the firm's filer (DFIN, Confluence, Vermilion) in the format they need. The filing workflow continues with the existing vendor; the data assembly step stops being a scramble.

How does this work for sub-advised funds?

For sub-advised funds, Milemarker ingests the sub-advisor's trade blotters, holdings files, attribution data, and compliance certifications into the same warehouse that holds the fund admin and TA data. The sponsor — who retains fiduciary responsibility under the investment advisory agreement — can run oversight queries, compare sub-advisor performance against benchmarks, and assemble the annual 15(c) contract-renewal materials from continuous data instead of a once-a-year manual pull.

Is fund shareholder data kept separate from advisory CRM data?

Yes. Shareholder-of-record data from the transfer agent and household-level client data from the advisory CRM are modeled as distinct entities in the warehouse, with permissioned joins where appropriate. A single individual may appear in both — as a shareholder in a proprietary fund and as an advisory client — but the two records are linked through role-based access rather than merged. That separation matters for privacy, for Rule 22c-2 monitoring, and for the boundary between fund business and advisory business.

What does implementation look like?

Implementation follows the sponsor's service provider map. The first phase establishes feeds from the fund admin and custodian, which typically delivers daily NAV, holdings, and position data into the warehouse within 2–4 weeks. The second phase brings in the transfer agent, sub-advisor blotters, and advisory-side systems. Full setup — including entity modeling, board-reporting automations, and N-PORT/N-CEN data assembly — typically takes 8–12 weeks depending on fund complexity and the number of service providers.

How is this different from our fund admin's reporting portal?

The fund admin's portal shows fund-side data only, in the admin's format, controlled by the admin. Milemarker's warehouse belongs to the sponsor, sits in a Snowflake instance the firm owns, and combines fund-admin data with transfer agent, sub-advisor, custodian, and advisory-side data in one model. The admin's portal answers "what did you do for us last quarter." The Milemarker warehouse answers "what is true across our entire business right now."

Related guides

Part of the Data Infrastructure series:

• N-PORT Reporting Automation: Streamline Quarterly Form N-PORT Filings

• NAV Reconciliation Automation for '40 Act Funds

• Transfer Agent Data Integration: Unifying TA, Fund, and Firm Data

• '40 Act Fund Compliance Data: Rule 38a-1, 17j-1, 22c-1 in One Data Platform

• Data Platform for RIA Aggregators & Consolidators

• Custodian Data Aggregation: Unified Reporting Across Schwab, Fidelity & Pershing