Statement & Capital-Call Ingestion Engine
A document-AI pipeline that ingests the year-round financial document corpus — statements, capital-call notices, distribution notices, trade confirms — extracts the relevant fields, classifies the transaction, and posts to the ledger of record with confidence-graded review queue.
- Engagement
- 6–10 week build · year-round operation
- Built for
- Controllers · Operations directors · Junior accountants
Family offices receive a constant stream of financial documents — monthly custodian statements, capital-call notices arriving with 10 days' notice, distribution notices, trade confirms from a dozen brokerages. The team enters them by hand, makes typos, misses calls.
What this is
The year-round document pipeline for everything that isn't a K-1. Three layers:
- Multi-format ingestion. Per-custodian, per-GP, per-broker templates registered into the pipeline. Email-attachment intake, SFTP for higher-volume sources, manual upload for one-offs.
- Extraction and classification. Document type identified, relevant fields extracted, transaction classified (capital call, distribution, dividend, trade, fee, wire). Confidence scoring per field.
- Posting and notification. Routing to the ledger with priority lanes for time-sensitive document types. Capital-call notices get fast-path handling with deadline flagging.
How it's built
LayoutLM-class extraction layered with format-specific templates. Classification head trained on labeled document corpus, extended per FO as new formats are encountered. Priority routing logic configurable per document type. Adapters into AtlasFive / Sage / QuickBooks / NetSuite / Addepar downstream.
What you get
- The ingestion-and-extraction pipeline, running year-round.
- Per-format templates for the standard custodian, GP, and brokerage corpus.
- Priority-routing logic for capital-call notices and other time-sensitive documents.
- The review queue UI for the controller.
- Ongoing template-library expansion as new formats arrive.
Engagement is shape, not list.
Length and price are functions of the data and the destination. The shape below is the typical engagement.
- Length
- 6–10 week build · year-round operation
- Lead
- Bogdan
- Cadence
- Async, weekly
- Bar
- Production
Scoped during the discovery call against the actual data and the operation it integrates with.
Principal engineer. Architecture and most code ships through one keyboard.
Written updates between, calls when the decision needs the room.
Async correctness, capacity under burst, observability at every boundary.
Products this composes with.
Same suite, or vertical-specialized versions in another.
- Same suite · Family Office Suite
K-1 Extraction & Validation Engine
A document-AI pipeline that ingests the K-1 corpus as it arrives, extracts all 200+ fields with confidence scores, maps to the FO's chart of accounts, flags inconsistencies against partnership returns, and posts to AtlasFive (or your fund-accounting system) with audit trail.
- Same suite · Family Office Suite
Invoice & Bill-Pay Engine
An AP pipeline that ingests invoices from email and vendor portals, classifies the vendor, predicts the GL code, suggests payment-batch timing, detects duplicates and anomalies, and posts to the ledger of record with audit trail.
- Same suite · Family Office Suite
Multi-Entity Consolidation Platform
A consolidation platform that ETLs from each entity's source-of-record system, normalizes to a unified chart of accounts, handles FX and intercompany eliminations, surfaces per-family-member and per-asset-type views, and enforces privacy partitions where the structure requires them.
What buyers ask about this one.
How is this different from K-1 Extraction?
K-1s are one form, one annual cycle, very high stakes per document. The non-K-1 corpus is many formats (each custodian and GP has their own), arriving year-round, lower stakes per document but much higher volume. Different commercial shape: K-1 is a tax-season operation, this is year-round.
What document types are covered?
At launch: monthly custodian statements (Schwab, Fidelity, Goldman, JP Morgan, BNY Mellon, Northern Trust, plus the standard private-bank formats), capital-call and distribution notices from PE / VC funds (per-GP layout), brokerage trade confirms, wire confirmations, fee invoices from advisors. New document types added as the FO encounters them.
How do you handle the capital-call deadline pressure?
Capital-call notices get the priority lane — extraction within hours of arrival, the controller gets the structured notice with the deadline flagged and the wire instructions extracted. The pipeline reduces 'capital call sat in someone's inbox' incidents that are otherwise the worst-case error.
Does this replace a portfolio aggregator like Addepar?
No. Addepar (or Eton or comparable) takes the cleaned, posted data and presents the wealth view. This pipeline gets the data INTO that system — handles the document-to-structured-data conversion that's otherwise manual or partially-automated. They're complementary; many of our deployments feed an Addepar instance downstream.
Pricing?
Scoped to document volume and the breadth of formats encountered. Discovery call covers both.
If the deliverable matches the gap, the next step is one call.
We'll scope length and price against your data and the operation it integrates with. No retainer, no fishing.
Bogdan and team · async-first · OP—2026