Devancore Inc.
Devancore Post-Trade Glossary
Glossary
Fund Admin Operating Data
Fund administration operating data is the packet exchanged across the manager–administrator boundary: trade and expense files, the NAV pack, trial-balance shadowing, governed queries, and sign-off evidence.
Document source: https://devancore.com/glossary/fund-admin-operating-data/
Devancore Post-Trade Glossary
Fund Admin Operating Data
Fund administration operating data is the packet exchanged across the manager–administrator boundary: trade and expense files, the NAV pack, trial-balance shadowing, governed queries, and sign-off evidence.
Definition
Fund administration operating data is the packet that moves across a service boundary. The administrator keeps the official fund books. The manager remains responsible for knowing what was sent, what came back, what was challenged, and what was accepted. If that exchange is only email and PDFs, oversight becomes reconstruction after the NAV is already in the market.
Fund accounting is how NAV is calculated. Middle office is how trades become settlement state. Transfer agency is the shareholder register. The operating-data problem is the handoff across two firms: they must share one explainable version of activity, breaks, and sign-off.
Handoff records, not ledger math
Handoff records, not ledger math
The useful record is what was sent, what came back, what was challenged, and what was accepted.
| Record area | What the exchange holds | Control question |
|---|---|---|
| Inbound file | Trades, expected cash and positions, expense instructions, and investor activity sent to the administrator | Was this the complete, versioned file the administrator actually booked? |
| NAV pack | Trial balance, valuation log, position and cash recon, accruals, capital activity, and exception list | Can each NAV movement be traced to a pack artifact, not only to a final price per share? |
| Shadow or oversight | Manager recast, checklist result, materiality threshold, and unexplained residual | Did the manager recast the books, review the pack, or only accept the NAV? |
| Query | Pack line, owner, clock, administrator answer, accept or reject, and NAV impact | Is the challenge a governed item, or an unowned email? |
| SLA clock | Expected delivery, actual delivery, completeness, and late or partial pack flag | Did the clock start on a complete pack, or on a notice that NAV was sent? |
| Sign-off | Reviewer, approver, pack version, open-query residual, and restatement link | Was the NAV accepted after the recon and query state was visible? |
Manager oversight of third-party fund administrators lives in these records. A portal login is not evidence. Evidence is a complete NAV pack, a comparison result, a query with an owner and a close, and a sign-off that names the pack version.
Why the packet matters is that NAV is an output of many inputs the manager does not book. Expenses, equalizations, illiquid marks, admin fee accruals, and capital allocations often originate on the administrator side. The manager cannot supervise those lines by inspecting only the final price per share. The NAV pack is the bundle that makes those lines inspectable: trial balance, valuation log, position and cash reconciliations, expense and fee support, investor activity, and the exception list.
Completeness is a separate control from accuracy. An on-time email that NAV is ready does not start a valid SLA clock if the valuation log or cash recon is missing. A restated NAV is a new pack. It should point at the pack it replaces, the queries that caused the restatement, and the second sign-off.
Fund admin operating data — boundary cycle
Devancore Glossary · devancore.com
Fund admin operating data — boundary cycle
Devancore Glossary · devancore.com
How it works
The workflow is a cycle across the boundary. The manager sends activity. The administrator books it and returns a pack. The manager compares, queries, and signs. Multi-book accounting still applies inside each firm — IBOR, ABOR, and performance views remain distinct — but the control that fails first is usually the join between manager expected data and administrator official data.
Boundary control points
Boundary control points
Breaks live in the handoff: a booked file that was not sent, a pack that cannot be joined, or a NAV accepted while queries remain material.
| Step | Data required | Failure mode |
|---|---|---|
| Send activity | Trade file, cancels, allocations, expense instructions, and cutoff time | Administrator books a stale file while the manager shadows a later version |
| Receive pack | Pack version, contents list, trial balance, recon reports, and delivery timestamp | SLA is marked met because an email arrived, but the valuation log is missing |
| Compare books | Manager expected balances versus administrator trial balance and recon residuals | Shadow accounting trial balance reconciliation is done at NAV-only, hiding a large offsetting error |
| Open query | Pack line, materiality, owner, and required administrator evidence | A fee or pricing dispute stays in email and never attaches to the NAV that was signed |
| Resolve | Administrator response, revised line, or documented accept-as-is | Query is closed as 'explained' with no artifact that an auditor can replay |
| Sign NAV | Pack version, open material queries, maker-checker, and restatement pointer | Sign-off occurs while a material query is still open, or a later restatement has no link to the first pack |
Inbound files need identity, not only rows. Trade files, cancels, allocations, expense instructions, and investor activity should carry cutoff, version, and the acknowledgment of what the administrator loaded. Shadow accounting trial balance reconciliation fails quietly when the manager recasts from file v3 while the administrator booked v2.
The difference between fund admin shadowing and NAV oversight is depth, not virtue. NAV oversight is a review of the delivered pack against a checklist and materiality. Shadowing recasts all or part of the ledger — often the trial balance, sometimes every transaction — then reconciles to the administrator. A firm can run oversight without a full shadow book. A firm that shadows at NAV-only can miss two large offsetting errors that net to a clean price per share.
An automated fund admin query management workflow is the feedback loop. Each query should point at a pack line or recon residual, carry materiality, age against the NAV clock, and retain the administrator's answer. Closing a query as explained without an artifact leaves the next restatement or audit with no path back to the challenge.
Sign-off is a state change on a specific pack version. Maker-checker should see open material queries, unexplained residuals, and whether this NAV is original or restated. Performance books and investor reporting consume the signed NAV. They cannot repair a handoff that was never evidenced.
Shadowing versus NAV oversight
Devancore Glossary · devancore.com
In Devancore™
Devancore — administrator handoff evidence
Devancore · evidence stack
Inbound packet
Trade, cash, expense, and investor-activity files enter with version, cutoff, and the copy the administrator was sent.
Returned pack
Trial balance, recon, valuation log, accruals, and capital reports stay attached to a pack version and delivery clock.
Compare state
Shadow recast, NAV-oversight checklist, and residuals are visible as workflow, not a private spreadsheet.
Query state
Open, assigned, answered, accepted, rejected, or aged remains owned and tied to a pack line.
Sign-off package
Approver, pack version, open-query residual, and restatement link remain with the same operating record.
Devancore supports fund administration operating data as a post-trade operating-record layer around the manager–administrator exchange: files sent, packs received, comparison residuals, queries, SLA clocks, and sign-off. It can help teams keep that chain visible without becoming the administrator.
Devancore does not act as a fund administrator, registrar, custodian, or auditor. It does not strike official NAV, hold the legal books, approve valuations, or determine that oversight was adequate. Those functions remain with the appointed administrator and the manager's responsible parties. The product boundary is the controlled operating copy of the handoff that accounting and reporting already depend on.
In a Devancore-style workflow, an inbound file, returned pack, residual, query, SLA breach, or sign-off enters as a source event. The record is mapped to fund, pack version, trial-balance line or recon item, owner, clock, and workflow state. Draft, complete, queried, accepted, rejected, signed, or restated remains visible with timestamp, reason, and source reference.
That structure is what oversight actually uses. The administrator may know the official books. The manager may know expected positions. The operating question is whether the packet, the challenge, and the acceptance still join as one explainable record.
Conversational finance depends on the same chain. A user can ask which NAVs were signed with material queries still open, which packs arrived incomplete, which trial-balance lines have no manager file, or which restatements lack a link to the original pack. The answer should resolve to files, pack versions, queries, owners, and evidence.
Related terms
- Fund Accounting Platform
https://devancore.com/glossary/fund-accounting-platform/
A fund accounting platform is the controlled operating layer that organizes fund-level records, NAV inputs, expenses, income, allocations, investor activity, reconciliation, approvals, and reporting evidence.
- Investment Fund Middle Office
https://devancore.com/glossary/investment-fund-middle-office/
Investment fund middle office is the operating layer that turns executions, allocations, positions, cash, collateral, corporate actions, and exceptions into controlled records for settlement, accounting, oversight, and reporting.
- Accounting Book of Record
https://devancore.com/glossary/accounting-book-of-record/
The ABOR: custodian-confirmed settled positions used as the authoritative basis for NAV calculation, financial statements, and regulatory reporting.
- Investment Book of Record
https://devancore.com/glossary/investment-book-of-record/
The IBOR — a real-time position record used by investment managers, capturing unsettled trades, accruals, and corporate actions ahead of custodian confirmation and ABOR settlement.
- IBOR Solution
https://devancore.com/glossary/ibor-solution/
An IBOR solution maintains the investment book of record: a timely operating view of positions, cash, trades, exposures, projected activity, reconciliation status, and evidence for portfolio and operations teams.
- Performance Book of Record
https://devancore.com/glossary/performance-book-of-record-pbor/
The PBOR — a position record that extends the IBOR with return attribution, risk analytics, and benchmark data, providing the authoritative basis for investment performance measurement and client reporting.
- Cash Reconciliation Software
https://devancore.com/glossary/cash-reconciliation-software/
Software that matches a broker-dealer's internal cash ledger against bank statements and clearing utility records in real time, surfacing breaks for resolution before they create reserve formula errors, missed sweeps, or Rule 15c3-3 violations.
- Custody Reconciliation
https://devancore.com/glossary/custody-reconciliation/
Custody reconciliation is the daily match of internal positions and cash to the custodian statement: timing versus genuine breaks, owners, aging, and the evidence that holdings are actually safekept.
- Corporate Action Processing
https://devancore.com/glossary/corporate-action-processing/
Corporate action processing is the operational workflow that captures issuer events, calculates per-account entitlements, and reconciles cash and position changes against custodian records.
- Reference Data Management
https://devancore.com/glossary/reference-data-management/
The governance and maintenance of static data that financial systems depend on — instrument identifiers, counterparty LEIs, and settlement rules — to process transactions correctly.
Contact
Request a briefing or platform walkthrough with the Devancore team.
Request access https://devancore.com/access/