Institutional Export Formats

CommunityPay provides standardized institutional exports designed for consumption by external validators — CPAs, insurance underwriters, and escrow officers. Each export type delivers a structured JSON document with versioned schema, comprehensive metadata, and cryptographic verification.

This page describes the three export types, their schemas, and the verification model.

Export Architecture

All institutional exports share a common architecture:

Base Structure

Every export produces an ExportResult containing:

{
  "success": true,
  "export_type": "AUDIT_READINESS",
  "data": { ... },       // Export-specific content
  "metadata": { ... },   // Standard metadata
  "errors": [],           // Any errors encountered
  "warnings": []          // Non-fatal warnings
}

Standard Metadata

Every export includes ExportMetadata:

The content_hash enables independent verification: any party with the data can recompute the hash and confirm the export has not been modified.

Export Type 1: Audit Readiness

Schema: audit_readiness_v1 Consumer: CPAs and external auditors performing annual audits Scope: Full fiscal year

Contents

HOA Identity - Legal name, EIN, address, total units, fiscal year end month

Financial Statements - Balance Sheet (as of period end): total assets, total liabilities, total equity, is_balanced flag, assets by category, liabilities by category - Income Statement (full period): total revenue, total expenses, net income, revenue by category, expenses by category

Fund Balances - Per-fund breakdown: fund name, fund type (OPERATING, RESERVE, etc.), current balance, as_of_date, restriction status and purpose - Fund segregation proof: each fund's balance is independently verifiable

Journal Entry Summary - Total entry count, total debits, total credits - Entry type breakdown (how many of each transaction type) - Monthly totals (entries per month with debit totals) - Immutability confirmation: entries are append-only after posting

Approval Audit Trail - Total approval requests processed - Approval decisions by type (APPROVED, REJECTED, ESCALATED) - Approval response times - Policy snapshots active during the period

Internal Controls - Enforcement decision statistics: total evaluations, pass rate, block rate - Guard performance: per-guard pass/fail counts - Override summary: count, types, reasons - Control effectiveness metrics

Reconciliation Status - Bank reconciliation status by account - Last reconciled date - Outstanding items count and amount

Audit Notes - System-generated notes about data quality, coverage gaps, or anomalies

Use Case

A CPA preparing for an annual audit requests an AUDIT_READINESS export. The export provides fund-segregated financials, journal entry trails, approval decisions, and control documentation in a machine-parseable format. The CPA can import the data into their audit workpapers, verify the content hash, and trace any entry back through the approval chain and enforcement decision.

Export Type 2: Controls Snapshot

Schema: controls_snapshot_v1 Consumer: Insurance underwriters assessing risk Scope: Configurable period

Contents

Governance Posture - Governance score and trend - Board attestation status (current, expired, never attested) - Meeting frequency and quorum compliance - Board member tenure and turnover

Enforcement Statistics - Total enforcement evaluations in period - Decision distribution: ALLOW, BLOCK, OVERRIDE, ERROR - Guard-level pass rates - Average evaluation time - Blocking reasons and frequency

Risk Profile - Active exclusions (bind blocks) and their severities - Exclusion resolution rate and mean resolution time - Trigger hit frequency - SLA compliance rate - Escalation chaining rate

Financial Health Indicators - Reserve ratio and trend - Delinquency rate - Operating ratio - Cash position

Vendor Compliance - Total vendors monitored - Compliance rate (all credentials current) - Active alerts by severity - VECR coverage (percentage of vendors with current attestations)

Use Case

An insurance underwriter evaluating an HOA's D&O risk profile requests a CONTROLS_SNAPSHOT export. The export quantifies governance effectiveness, enforcement activity, risk exposure, and financial health — all derived from production data, not self-reported questionnaires.

Export Type 3: Escrow Disclosure

Schema: escrow_disclosure_v1 Consumer: Escrow officers and title companies processing unit sales Scope: Per unit

Contents

Association Identity - HOA legal name, address, EIN, total units, management type

Unit Information - Unit identifier, owner name, ownership dates - Current assessment amount and frequency

Owner Financial Status - Current balance (amounts owed) - Payment history (trailing 12 months) - Special assessments (pending and historical) - Late fees and violations with financial impact

Association Financial Health - Reserve fund balance and percent funded - Operating fund balance - Annual budget summary - Pending special assessments (association-wide) - Pending litigation with financial exposure

Governance Status - Current board composition - Meeting compliance - Insurance coverage summary - CC&R enforcement activity

Compliance - Statutory disclosure requirements for jurisdiction - Compliance completeness score - Missing or incomplete disclosures

Use Case

An escrow officer processing a unit sale requests an ESCROW_DISCLOSURE export. The export provides owner-specific financial data (what the seller owes) and association-level data (financial health, governance, pending litigation) in a format the title company can process. The content hash verifies that the data hasn't been modified between generation and the closing.

Verification Model

All three export types use the same verification model as Evidence Packs:

1. Generate: The export service builds the data payload and metadata
2. Hash: SHA-256 is computed from canonical JSON of the data payload (sorted keys, minimal separators, UTF-8)
3. Include: The content_hash is stored in the metadata alongside the data
4. Verify: Any recipient can recompute the hash and compare to the stored content_hash

Verification does not require API access, credentials, or trust in CommunityPay. It requires only the data and a SHA-256 implementation.

Schema Versioning

Each export type uses a versioned schema identifier (e.g., audit_readiness_v1). When the schema changes:

• The version number increments (e.g., audit_readiness_v2)
• Previous versions remain supported for a deprecation period
• Integration partners can specify which schema version they expect
• Schema changes are documented with migration guidance

This ensures that automated integrations (e.g., a CPA firm's import script) are not broken by schema evolution.

What These Exports Enable

Institutional exports transform CommunityPay from a closed system into an integration point:

1. Audit readiness becomes exportable — CPAs receive machine-parseable data instead of PDFs and spreadsheets
2. Underwriting becomes data-driven — Insurers assess risk from production data, not questionnaires
3. Closings become faster — Escrow officers receive structured disclosures instead of manually assembled packages
4. Verification is independent — Recipients verify data integrity without trusting the source system
5. Integration is standardized — Versioned schemas enable automated data pipelines between systems

CARI Integration

CARI reports — Lender Report, Insurer Report, Title Report, and Buyer Report — are available as institutional export formats with the same SHA-256 content hashing, version chaining, and PDF rendering infrastructure as all other institutional packets. These are the first export formats designed specifically for external third-party consumers who subscribe to an HOA's CARI score. Each CARI report type surfaces the sub-score components and underlying signals most relevant to that consumer's decision context.

For published methodology and component weights, see CARI Methodology and Scoring Framework.