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.
- Engagement
- 8–12 week build · annual tax-season operation
- Built for
- CFOs · Controllers · Tax operations leads
Tax season at a family office means hundreds of K-1 PDFs arriving in irregular formats over six weeks — 200+ extractable fields each, manual entry to the GL, manual reconciliation against the partnership filings the CFO already received.
What this is
A document-AI pipeline for the single most painful annual workflow in a family office. Four layers:
- Ingestion. Email-attachment and SFTP intake. Per-partnership tracking so the controller can see what's arrived and what's still outstanding.
- Extraction. All 200+ K-1 fields with per-field confidence scoring. Standard layouts processed end-to-end automatically; layout anomalies routed to review.
- Validation. Cross-check against partnership returns where available. Internal consistency checks within the K-1 itself. Year-over-year reasonableness for recurring partnerships.
- Posting. Structured journal entries to AtlasFive / Sage Intacct / QuickBooks / NetSuite / custom FO ledger, with source-PDF linkage for audit trail.
How it's built
LayoutLM-class document model for the structured-field extraction, with per-partnership templates as a fast path. Validation rules expressed as a declarative rule engine — the rule library compounds as new anomaly patterns are caught and codified. Postgres for canonical storage, with the source PDFs versioned in cold storage. Integration adapters per fund-accounting system.
What you get
- The ingestion-and-extraction pipeline, running through tax season.
- The review queue UI for the controller — low-confidence and amended-K-1 workflows.
- Audit trail from source PDF to GL entry.
- The validation rule library, documented and versioned.
- Annual tax-season operation — we keep the pipeline current with new IRS K-1 form revisions.
Engagement is shape, not list.
Length and price are functions of the data and the destination. The shape below is the typical engagement.
- Length
- 8–12 week build · annual tax-season 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
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.
- 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.
What's the accuracy on extraction?
On the standard K-1 layout, the model extracts 95%+ of fields at high confidence — those go straight to the GL with audit logging. The remaining 5% (low-confidence fields, layout anomalies, or fields the model hasn't seen before) go to a review queue the controller works through. Net effect on a typical tax season: the controller spends a few hours on edge cases instead of several weeks on routine entry.
We use AtlasFive. Does this integrate?
Yes — AtlasFive integration is the canonical case. We also support Sage Intacct, QuickBooks, NetSuite, and custom-built FO ledgers. The pipeline writes structured journal entries with the K-1 source linked so the controller can audit back to the source PDF.
What about state K-1s and amended K-1s?
State K-1s are supported (each state's format is registered as a layout). Amended K-1s flow through a separate path — when an amended K-1 arrives for a partnership the engine has already processed, the controller gets the diff with both versions side-by-side and a one-click reposting workflow once they accept.
How do you handle the partnership filings cross-check?
If your fund-accounting system has the partnership returns ingested, the engine cross-checks K-1 reported income against the partnership-level allocations and flags discrepancies. Where the FO has direct partnership relationships (LP into managed funds), this catches the 'partnership says $X, K-1 says $Y' problem before it reaches the tax preparer.
Pricing?
Scoped to K-1 volume and integration surface. 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