ETFcomply

How it works

Your first week: day one you connect, by Friday the ledger answers.

ETFcomply works with your provider stack, and onboarding is hands-on. Day one, we set up your providers and connect your email read-only. Over the days after, the documents file themselves, the ledger fills against your own funds, and the first reports generate. By the end of the week the record answers filing and exam questions on demand. Here is the path.

01

Providers

Pick your service providers

Every issuer runs a different stack. Choose your administrator, index provider, and distributor from a registry of known providers. Each choice seeds the sender addresses to watch and the document streams to expect, so ETFcomply knows what should arrive and when.

  • Administrator, index provider, distributor, auditor
  • Ultimus connects by direct API
  • Others captured from their known email streams
02

Email

Connect your email, read-only

Grant read-only access to Gmail or Microsoft 365 and documents from your providers start filing themselves: ETFcomply previews what it found in the last thirty days before any full backfill, so you see the capture working before it runs. Prefer not to connect a mailbox? Skip this step and upload documents directly, and everything else works the same.

  • Read-only Gmail or Microsoft 365 scopes
  • Sender-only gate; non-provider mail is skipped
  • Message bodies never stored, only provider documents
  • Thirty-day preview before full backfill
  • Reads and files documents; never sends or deletes
03

Map

Funds map automatically

Documents captured from your providers link to the fund they belong to. Fund-level streams fan out per fund; trust and adviser records seed once per firm. The mapping is automatic, and anything ambiguous lands in a review queue rather than being misfiled.

  • Provider documents linked to the right fund
  • Fund-level per fund, trust-level once per firm
  • Ambiguous items queued, not misfiled
04

Ledger

The ledger fills

As the streams come in, the per-fund ledger populates: daily net assets, NAV and market price, flows, creations and redemptions, premium and discount, and holdings by date. A first sync shows per-fund coverage and flags anything missing.

  • Daily series per fund, queryable by date
  • Coverage check surfaces gaps
  • Missing expected documents raise an alert
05

Reports

First reports generate

With the ledger filling, your daily, quarterly, and annual reports generate from the record, with source documents linked. The 13F and exam export bundles draw on the same data when you need them.

  • Daily, quarterly, and annual reports
  • Single-click 13F from tracked holdings
  • Exam export bundles with hashed manifests
06

Code of ethics

Add your people and open a period

Add the access persons who owe attestations. Each gets their own sign-in that reaches only their own filings, never the fund data. Open the periods you need in one action and the reminders run themselves. Coming from another provider mid-year? Start on the quarter in progress rather than reopening one you have already filed.

  • Access persons on a separate surface from your fund data
  • Open several attestations and periods in one action
  • Reminders and the overdue list without you chasing
·

Later

Launch the next fund from the record

When you add another fund to the trust, ETFcomply derives a launch template from your own filed documents and walks the deltas, generating counsel-ready draft prospectus and SAI documents and registering the new fund so its ledger and vault are live from day one. Drafts are for counsel review; nothing is filed with the SEC.

  • Template derived from your filed funds
  • Guided setup: objective, strategy, risks, fees, PMs
  • Counsel-ready Word drafts; not legal advice
07

Optional

Connect your AI

Optional: mint a read-only, revocable token and point Claude, or any MCP-compatible assistant, at your data scoped to your firm. Your AI answers open questions and helps compile reports from your own record, and cites the numbers. Prefer not to connect anything? The built-in question box still answers direct data questions from the ledger.

  • Read-only token, scoped to your firm, revocable
  • Works with the AI subscription you already have
  • Or ask the built-in question box, no AI required
ETFcomply/Funds · Ledger
CCO

One fund · daily record

Source docs attached

Net assets

Tracked

NAV / close

Daily

MTD flow

Net + / -

Prem / disc

By day

Creations & redemptions

DateCreatedRedeemedNet
05/142 units0 units+2
05/131 unit1 unit0
05/120 units3 units-3
05/094 units0 units+4
ETFcomply/Reports
CCO

Built from the ledger

Source docs linked
ReportPeriodState
Daily fund reportPrior closeGenerated
Quarterly fund reportQ1Generated
Annual fund reportFYEGenerated
Board data packMeeting cycleReady

The provider registry is data, not code

Because the registry of providers is a table rather than a release, adding your administrator or index provider is a row, not a wait. When a rule regime is in flux, it carries a pending note and an effective-date range. Nothing here is legal advice; confirm every date and applicability against current SEC and IRS releases and counsel.

Ready to see it against your own funds?

Onboarding is hands-on. We connect your provider stack and let the ledger fill before your first login.

Request accessaccess@etfcomply.com