One statement, many funds
An endowment's investment custodian statement arrives once a quarter, and needs to end up in two places: the overall pooled-account total for board reporting, and the individual fund-level shares that let each named fund's classification and spending calculation be maintained separately. Both pieces live in the same document, just in different fields.
This page describes how that statement gets read automatically, field by field, so both the pooled total and every individual fund's allocated share are available within minutes of the statement arriving, rather than after an afternoon spent transcribing it by hand — regardless of which custodian issued it, how many funds the pooled account covers, or how the statement itself is formatted.
Why custodian statements are hard to automate
Every custodian has its own statement format, and the relevant fields — period, gains, fees, ending value, sometimes even the sign convention for a loss — can appear in different order and under different headings from one custodian to the next. A solution built for one specific format breaks down the moment a new custodian or a new statement template comes into use.
The fields that get read
| Field | Used for |
|---|---|
| Contributions | New gifts added to the pooled account during the period |
| Realized and unrealized gains/losses | Investment performance to allocate across funds |
| Dividend and interest income | Income accruing to the pooled account |
| Management fees | Costs to allocate proportionally across funds |
| Ending market value | The pooled total each fund's allocation must sum to |
Pooled totals vs. individual fund allocation
The pooled account total is a direct read from the statement. Individual fund shares, which often appear in a separate unitization schedule rather than on the custodian statement itself, are what the pooled totals get allocated across — both documents are needed together to arrive at each fund's classified balance.
How it works
One or more custodian statements are uploaded, fields are recognized automatically regardless of the custodian's format, and the result is displayed structured and ready for review — with anything uncertain flagged for a quick manual check before it's exported.
More than one custodian at once
Many endowments split investments across more than one custodian — for diversification, or because a legacy relationship never got consolidated. Each statement is read on its own terms, so having more than one custodian in play adds no extra setup burden.
When holdings or allocations change mid-year
A rebalancing event, a new gift added to the pool, or a fund's unitization share adjusted mid-year each shows up as its own dated statement or schedule. Reading each period's documents independently, rather than assuming allocations are static, keeps the fund-level history accurate through any change.
Investment management fees
The management fee charged against the pooled account is read as its own line, ready to be allocated proportionally across every fund that shares the pool, rather than left as an unallocated deduction in the overall total.
The manual process this replaces
Manually, this means opening each custodian statement, finding the relevant fields, and typing them into a spreadsheet or fund accounting system — a process that for an endowment with dozens of funds easily takes an hour or more each quarter, and is vulnerable to transcription errors precisely because it's repeated so often.
With tooling vs. by hand
By hand, the task is fully workable for a small number of funds. The advantage of automatic reading shows up as the number of funds or the total volume of statements grows — the time per statement drops to seconds instead of minutes, without a loss in accuracy.
Who this is relevant for
Controllers and CFOs who receive quarterly custodian statements for a pooled endowment account, auditors reviewing multiple clients' endowment portfolios, and board treasurers who handle their own organization's bookkeeping directly.
How often statements arrive, and why it matters
Most custodian statements arrive quarterly, which makes this a recurring, predictable task — and that predictability is exactly what makes it worth automating, even if any single statement only takes a few minutes by hand.
Get started with your first statement
The easiest way to see if this fits your organization's custodian statements is to try it with one real statement — the result shows immediately which fields were recognized correctly.
What happens to your data
Uploads are encrypted with TLS from end to end.
Processing runs on infrastructure with SOC 2-aligned controls.
Original documents are deleted shortly after processing.
Nothing you upload is ever used to train AI models.
For records carrying both organizational and donor gift information, that matters — full details are on the security page.
A typical example with three funds
An organization with three endowed funds sharing one pooled investment account receives a single quarterly custodian statement.
| Fund | Allocated share of quarterly gain |
|---|---|
| Fund A (largest, 55% of pool) | $12,400 |
| Fund B (30% of pool) | $6,760 |
| Fund C (15% of pool) | $3,380 |
Read automatically, the three funds' results are ready in a couple of minutes, with the same accuracy as the manual allocation but without the repeated arithmetic and typing.
Donor-advised fund sponsor statements
A donor-advised fund sponsor's statement — from a community foundation's DAF program or a commercial sponsor — follows a broadly similar structure to a traditional custodian statement: contributions, investment activity, fees, grants recommended and paid, and an ending balance. Reading these statements the same way as any other investment statement means an organization managing both a traditional endowment and a DAF relationship doesn't need two separate processes.
Tying the reading back to a fund-level reconciliation
The structured data this produces is the input to a fund-level reconciliation, not the reconciliation itself — the pooled totals still need to be allocated across individual funds using your organization's own unitization schedule, and the resulting fund balances still need to be classified and reviewed. What this changes is how quickly that reconciliation can start: instead of spending the first hour of the process re-keying the statement, the structured data is ready the moment the statement is uploaded.
Building a historical record from old statements
Many organizations have years — sometimes decades — of prior custodian statements sitting in a filing cabinet or an old email archive, never digitized into a structured, searchable form. Reading a full backlog of historical statements at once is a practical way to build a complete fund history retroactively, useful both for an audit that asks about a prior year and for simply understanding how a fund has performed over its lifetime.
The range of statement formats this handles
Custodian statements vary widely — a large institutional custodian's multi-page PDF with detailed holdings, a smaller regional trust company's simpler one-page summary, or a community foundation's own internally generated fund statement. None of these require a separate setup; each is read from its own printed structure, so switching custodians or adding a second one doesn't require reconfiguring anything.
Who benefits most from automating this step
Organizations with more than a handful of funds sharing a pooled account see the clearest time savings, since the manual reading burden scales with fund count while the automated version doesn't. But even a nonprofit with a single endowed fund benefits from having a reliable, repeatable process in place before the fund count grows — building the habit early avoids a harder transition later.
Setting this up for your own organization
There's no setup or integration step required before the first statement can be uploaded — the easiest way to evaluate whether the extraction works well for your custodian's specific format is to try it with a real, recent statement and review the result immediately. Most organizations know within a single upload whether the fields are being recognized correctly for their situation.
For an organization ready to make this part of a regular routine, a sensible next step is running both the old manual process and the new automated reading side by side for one or two quarters, comparing the results, before retiring the manual step entirely.
Sharing results with an accountant or auditor
For an organization that uses an external CPA firm for its bookkeeping or audit, the structured output can be shared directly, without giving the accountant access to the entire account or requiring them to re-upload the same statements themselves. That avoids a document being processed twice by two different people, and keeps the accountant working from exactly the same structured data your own team sees.
Quarterly vs. monthly statement cadence
Most custodians issue statements quarterly, though some issue monthly summaries alongside a fuller quarterly report. Reading either cadence works the same way — a monthly statement is simply read more often, with smaller amounts of activity per document, rather than requiring any different handling. An organization that wants more frequent visibility into fund balances can request monthly statements from its custodian and process each one as it arrives, without waiting for the full quarter to close.
The underlying goal
None of this changes what an endowment's custodian statement actually says — it changes how quickly and reliably that information becomes usable. The goal is simple: turn a PDF that a person would otherwise have to read line by line into a structured record that's ready the moment it's needed, whether that's for a board report, a fund-level reconciliation, or an auditor's request.
What happens when a statement has an obvious error
Occasionally a custodian statement itself contains an error — a duplicated line, a corrected figure issued as a restated statement weeks later. Reading the statement exactly as printed means an error in the source document is read faithfully rather than silently corrected, so it's visible and can be reconciled against the restated version when it arrives, rather than being masked by an automatic adjustment nobody asked for.
The value of a consistent method across custodians
An organization that changes custodians every few years, or that has always split assets across two or three custodians for diversification, benefits particularly from a reading method that's not tied to any one provider's format. The alternative — a different manual process or template for each custodian relationship — multiplies the maintenance burden every time a new custodian is added, exactly the opposite of what a growing endowment needs.
How this scales as an endowment grows
A small endowment with one pooled account and a handful of funds has modest statement volume to begin with, so the time saved on any single quarter is real but modest too. As a foundation grows — more funds, sometimes more than one pooled account or custodian relationship — the volume of statements to process grows right alongside it, and that's exactly where reading every document the same way, regardless of count, starts to matter most.
An organization that builds this into its routine early, while volume is still low, tends to have an easier transition than one that waits until the manual process has already become unmanageable before looking for a better way.
A small change with a large downstream effect
Reading a custodian statement automatically feels like a minor convenience on its own, but it sits at the very start of the endowment accounting chain — everything downstream, from fund allocation to net-asset classification to the annual audit, depends on this first step being accurate and complete. Getting it right consistently, quarter after quarter, is what makes every later step in the process faster and more reliable.
A single mistyped figure at this first step can propagate all the way through to a fund's classification and its spending calculation, which is exactly why getting the raw statement data right, before any allocation or classification happens, matters as much as any later step in the process.
