FundGuard: Investment Accounting, Private Markets and Contingent NAV

FundGuard presents its platform as a single accounting engine supporting multiple books and views. The accounting book of record supports official fund accounting and NAV work; the investment book supplies current positions and cash for investment decisions and middle-office workflows. GAAP, tax, performance and currency views apply different accounting treatments to the underlying activity.[3]

The private-markets offering names four document tools: Loan Agreement Analyzer, Investor Statement Analyzer, Fund Performance Analyzer and LPA Analyzer. They extract and structure facility, investor and partnership data for the accounting record. The public page describes these capabilities but does not publish an independently tested extraction-accuracy rate.[5]

FundGuard’s IBOR is intended to feed both the start-of-day view and subsequent activity. Cash forecasting and strategy-level tagging make its output usable for portfolio decisions, while corporate-action and income processing contribute to the same investment record. An IBOR view is therefore a calculated operational dataset, not simply a dashboard laid over an administrator’s last overnight file.[4]

The published architecture uses APIs and adapters to connect accounting with custodian and administrator feeds, market and reference data, front-office tools and reporting. FundGuard’s September 2026 explanation names Snowflake and Databricks as data-platform choices and discusses CTM/DTCC settlement workflows. These references describe connection routes; the configured interface, message scope and permissions still determine an individual deployment.[8]

FundGuard’s integration model puts accounting state at the center: trades and confirmed custody activity update the books, and downstream consumers read the resulting positions and cash. A connected risk or reporting tool can still have its own calculations. The benefit of a shared record depends on the firm agreeing which accounting view, effective date and correction history each interface should use.[8][7]

FundGuard does not publish a subscription tariff, per-fund rate, implementation fee or standard minimum commitment in the product materials reviewed.[2]

FundGuard’s October 2026 implementation account is unusually specific about the work involved. The client owns scope, rollout decisions, data sign-off, acceptance criteria and the go-live decision, while FundGuard runs delivery. Historical data is mapped from incumbent-system files, and the client’s extraction work remains a substantial part of migration. Accountants and operations staff participate in configuration and acceptance while continuing to run the existing platform.[11]

Implementation capacity includes a certified partner program. Meradia completed the inaugural delivery announced in October 2024. The published certification pathway has Foundations, Intermediate and Expert levels, covering progressively more complex platform implementations. Partner certification is evidence of a training route, rather than a fixed implementation duration for all clients.[12]

FundGuard describes AWS/Azure SaaS delivery with continuous monthly upgrades.[5]

Its AWS announcement documents an automated test center and an exception-rule library. This release model places maintenance in an ongoing service cycle; client-specific interface tests and accounting acceptance remain part of operating the configured platform.[10]

For contingent NAV, the company describes separate infrastructure, event-driven calculation, continuous comparison with the primary NAV and a continuously exercised fallback. The useful distinction is between keeping a backup copy and keeping another accounting calculation ready to operate. The public material does not publish a contractual recovery-time or recovery-point objective.[6]

The Trailmark case describes weekly working sessions after go-live to expand automation in pricing, corporate actions and other workflows. That is a named customer arrangement. Universal staffed hours, severity-response targets and a standard support SLA were not established in the public materials reviewed.[13]

FundGuard describes secure API access and a protected AI processing environment in which client data is not used to train its models. The August 2026 architecture update explains its use of Amazon Bedrock for model access and governed agent permissions. These are the provider’s published architecture statements; the reviewed material does not expose the customer-specific model configuration, retention schedule or complete subprocessor contract.[15]

The AWS Marketplace announcement describes authentication and authorization, encryption at rest and in transit, DDoS protection and support for in-country residency. It does not establish that every customer can select any desired country. The actual cloud region and operating arrangement need to be part of the contracted deployment.[10]

The Trailmark case specifically says its vendor review incorporated FundGuard SOC 2 materials. It separately refers to Trailmark’s own SOC 1 report, which should not be misattributed to FundGuard. The underlying FundGuard report, audit period and exceptions were not public in the material inspected.[13]

FundGuard supplies investment-accounting technology. Its books, control evidence and contingency capability support the responsibilities of the asset manager, administrator or custodian using them; they do not transfer those firms’ regulated roles to FundGuard. Its privacy policy identifies the customer as responsible for required consents and legal compliance for individuals using the service through that customer relationship.[16]

The published operator is FundGuard, Inc. Its website gives a New York address at 540 Madison Avenue, 24th Floor, alongside offices in the Boston area, Tel Aviv and London. The company identifies Lior Yogev as CEO/co-founder, Yaniv Zecharya as CTO/co-founder and Uri Katz as VP R&D/co-founder; Simon Behan is Chief Commercial Officer.[16][2][1]

FundGuard’s AWS announcement dates its inception to 2018. Its October 2026 company description names strategic backers Citi and State Street and investment firms Blumberg Capital, Key1 Capital, LionBird Ventures and Team8. Those investment relationships are relevant company context and do not by themselves establish that an investor supplies custody, guarantees the platform or participates in every client deployment.[10][14]

Operator

FundGuard, Inc.

Service scope

Cloud investment-accounting system of record supporting fund accounting, IBOR, public/private assets and contingent NAV for investment operations and fund servicing.

Customer types

Asset managers; Asset owners; Fund administrators; Custodian banks; Investment-accounting and middle-office teams

Delivery

SaaS; API

Pricing publication

Not disclosed

Platforms

Fund Accounting / ABOR; Investment Accounting / IBOR; Private Markets; Contingent NAV

Integrations

APIs and standard adapters; Gresham enterprise-data management; Snowflake and Databricks interfaces; MCP and governed client AI tools

Pricing scope

No public subscription tariff or implementation fee found; AWS Private Marketplace procurement is documented.

Implementation

Data mapping and parallel operation with reconciled books and agreed exit criteria; the client owns acceptance and go-live decisions.

Support

Direct company contacts and client-success/implementation support; no universal public hours or response SLA established.

Permissions and regulatory scope

Investment-accounting software supporting institutional users; no brokerage, custody or investment-management permission is conferred by the software relationship.

Provider metadata checked 21 Oct 2026Source 16Source 2Source 1Source 3Source 5Source 6Source 8Source 10Source 11

Bitemporal accounting is an important part of FundGuard’s model. Effective time records when an event belongs in the books; knowledge time records when the system learned about it. A late trade amendment can therefore change the corrected historical position while preserving the position that staff actually saw before the amendment arrived. The distinction helps investigate an earlier NAV or control decision without silently replacing its original context. It is separate from multi-book accounting, which applies different treatments to the same activity.[7]

FundGuard also describes native accounting for digital and tokenized assets within the same engine as equities, fixed income, derivatives and private markets. The published July 2026 explanation covers position keeping, valuation, lifecycle events and reconciliation against custodians, transfer agents and on-chain records. This is an accounting capability, not evidence that FundGuard issues tokens, safeguards private keys or operates a trading venue. Neither universal blockchain coverage nor a named wallet-connector catalog is established by that page.[17]

The single-ledger design removes duplication between internal accounting books. External reconciliation remains: FundGuard’s migration guidance and live customer account still compare positions, cash and NAV with other records.[5][11][13]