Every financial transaction evaluated before it posts.
Every decision logged. Every signal captured at the moment of evaluation.
CommunityPay is association payments and accounting built to stay correct under audits,
turnover, and real-world exceptions. Approvals and records work the same way in every
association, so whoever keeps the books can show where the money went.
Enforcement-first ledger · Immutable decision records · Guard chain evaluation · Signal snapshot at decision time
Best for
CPA and bookkeeping firms, management companies' accounting teams, and large associations that need approvals bound to payments, operating and reserve funds that each balance on their own, and records an auditor can verify.
Not designed for
Community social features (events, forums) or resident engagement platforms.
01
The Enforcement Thesis
Most HOA accounting errors share a root cause: decisions that were never logged
and controls that were optional. CommunityPay eliminates both by making enforcement
mandatory and decisions immutable.
Core invariant: No journal entry can exist without an enforcement decision.
No decision can be modified after creation. No bypass goes undetected. A missing decision
record is itself a signal — of a bug or a breach.
Journal Engine— single posting interface, all entries flow here
↓
Enforcement Dispatcher— mandatory choke point
↓
ALLOW
log + persist
↓
BLOCK
log + reject
↓
OVERRIDE
log + persist (with audit)
Guards run in order until one blocks. A pass never stops the chain.
The full signal state is captured at the moment of evaluation, so any decision
can be reconstructed from its snapshot alone.
02
The Layer Stack
The ledger is the foundation — the system of record everything else sits on.
Each layer above it consumes only the layer directly beneath: from enforcement and
decision telemetry at the base, through origination, governed workflows, risk
intelligence, and attestation, up to intelligence and distribution at the outer edge.
Select any layer to see what it is, what it governs, and what it produces.
PLANE
Legal & Compliance
Cross-cutting — Read at L2 · L4 · L6
L7
Intelligence & Distribution
Where the governed system reaches the world
L6
Attestation
Verifiable artifacts from governed state
L5
Risk Intelligence
Measure financial and governance risk
L4
Governed Workflows
Run association finance as governed operations
L3
Origination
Turn events into correct entries
L2
Enforcement & Decision Telemetry
Govern every action; log every decision
L1
Financial Ledger
Hold financial truth
Select a layer to explore
L7 · Intelligence & Distribution — consumes Attestation
What it is
The outer edge — external APIs and third-party consumers of the corpus.
What it governs
Locked-in data; artifacts that cannot travel.
What it produces
Machine-readable access for title, escrow, lenders, insurers, and CPAs.
Why it’s here
The deliberately open layer — the one we grow over time.
L6 · Attestation — consumes Risk Intelligence
What it is
Hash-bound, version-chained artifacts generated from governed state, built for third-party verification.
What it governs
Disclosures assembled from stale records; reports that cannot be verified.
What it produces
The full library of governance and institutional reports.
Why it’s here
A live-ledger disclosure is categorically different from a packet assembled by email.
Immutable decision records, the override audit trail, prevented-loss evidence.
Why it’s here
No journal entry exists without an enforcement decision; the database refuses one.
L1 · Financial Ledger
What it is
A double-entry, fund-segregated ledger with an immutable audit trail — the single source of financial truth.
What it governs
Silent edits, unbalanced entries, commingled funds, posting to closed periods.
What it produces
Journal entries, fund balances, financial statements, integrity snapshots.
Why it’s here
The floor everything is built on — owned by the association, not a board term.
Cross-cutting plane · Legal & Compliance
What it is
The Living Legal Corpus — statutes, case law, and drift detection mapped onto financial decisions. Read by many layers, owned by none.
Where it’s read
Read at L2 · L4 · L6
Three concerns cut across the stack rather than sitting in any one layer:
Legal & Compliance (the living legal corpus),
Identity & Authority (the member-bound authority model), and
Immutability & Audit (tamper-evidence spanning every record).
Read by many layers, owned by none.
03
System of Record
The foundation layer. True double-entry fund accounting with operating and reserve
segregation. Every journal entry flows through a single posting interface and is evaluated
by the enforcement dispatcher before persisting. Production guards
check invariants ranging from balance verification to fund segregation
to debt covenant compliance.
Double-Entry Ledger
Debits equal credits on every entry. Fund-native chart of accounts.
184 account templates.
Period Controls
Fiscal period and year-end locking. Configurable bank reconciliation
prerequisite for period close. No backdating.
Ledger Integrity Scan
Automated checks: balance verification, orphan detection,
missing enforcement, fund assignment, closed period, control account reconciliation.
Assessment calculation is a system-of-record function, not a spreadsheet exercise.
The platform stores the allocation method, applies it consistently across every unit,
and posts the result through the enforcement-evaluated journal engine.
01
Board approves annual budget.
Total operating and reserve expenses determine the assessment amount the association needs to collect.
02
Allocation method is selected.
The board chooses how to distribute the total across units: equal share, by square footage,
by ownership percentage, by unit type, by bedroom count, or custom weights.
03
Allocation engine computes per-unit amounts.
Deterministic calculation with rounding control. The last unit absorbs remainder
to prevent drift. Every allocation is auditable.
04
Assessment schedule generates invoices.
Monthly, quarterly, or annual cadence. Each invoice posts a balanced journal entry
through the enforcement dispatcher.
05
Unit-level AR tracks payment status.
Aging reports, late fee automation, collection queues. Every payment receipt
clears the receivable with a posted, enforced journal entry.
Enterprise Debt Subledger
Event-sourced loan management for both HOA liabilities and resident receivables.
Every loan state change is an immutable event. Amortization schedules are versioned
and never edited. The subledger balance reconciles to the general ledger daily.
HOA Loans
Term, revolving, construction, bridge, balloon. Fixed or variable rate
with index tracking. Full amortization schedule generation.
Resident Loans
HOA-to-resident lending with recovery plan allocation.
Automatically generates AR invoices for scheduled payments.
Subledger Reconciliation
Daily automated verification that subledger posted balances
match GL control accounts. Hard health alerts on mismatch.
Identity and authority are not a layer — they are a cross-cutting plane,
read wherever an action must be authorized. Before a posting can be evaluated,
the platform must know who is authorized to act, what policies govern them, and
what limits apply. Board member tenure, approval workflows, and policy
snapshots are written through governed workflows and read at enforcement to gate
every action.
Board Authority
Board member tenure tracking with role assignments, term dates,
and signature authority for attestation and approval.
Approval Workflows
Multi-level approval chains with configurable thresholds,
escalation rules, and latency tracking.
Policy & Transfer Controls
Fund policies, the transfer limit, and enforcement point configuration.
Every policy change creates an immutable snapshot.
Who Holds Authority
Only the association's admin changes, demotes, or removes a member who
holds authority; staff cannot. Grants and removals are emailed to the
board. Money abilities start off for each admin after an association's first officer and are granted only by
someone who holds them, with a fresh authenticator code.
Fresh Code Before Money Moves
An authenticator code entered within the last ten minutes is required to
pay a vendor, approve a bill, change a vendor's bank, write an override, or
change who may approve and pay. A text-message code never confirms a money
action.
The Association's Bank
One payout bank is pinned for the association, and a vendor's bank can
never be it. A bank PIN, separate from any login, guards changes. Changing
the payout bank takes two board members, and the first payout to the new
bank is held until a person releases it. A changed vendor bank waits three
business days before it is paid.
05
Governed Operations
Association money movement runs as governed workflows on top of origination —
resident payments, vendor disbursements, refunds, and reconciliation runs. Resident
payments flow directly from bank account to HOA bank account via Stripe Connect.
CommunityPay is the platform — not an intermediary in the funds flow. A
provider-agnostic gateway interface ensures business logic never couples to a single
processor.
Direct Bank Transfers
Stripe Connect direct charges. Resident bank to the association's own
connected balance, swept to its bank. No commingling. No platform
holding account.
Gateway Abstraction
Provider-agnostic interface with a normalized API surface.
Business logic never calls Stripe directly.
Daily Reconciliation
Automated provider-to-ledger reconciliation.
Payment, refund, and payout matching every 24 hours.
Every posting passes through the enforcement dispatcher — the mandatory choke
point that records ALLOW, BLOCK, or OVERRIDE with the full signal state captured at
decision time. Approval latency, override attempts, and policy violations are logged
as immutable decision telemetry. These records feed upward into risk intelligence,
where they inform eligibility evaluation, exclusion triggers, and governance risk
scoring.
Approval Latency
Tracks time from request to decision across all approval workflows.
Surfaces bottlenecks before they become governance failures.
Override & Bypass Detection
Every override attempt is logged with actor, scope, and outcome.
Missing decision records are themselves a signal.
Policy Violation Monitoring
Attempted actions that violate active policies are captured in real-time,
even when blocked by enforcement.
How Telemetry Feeds Risk Intelligence
01
A posting is submitted (L2).
A vendor payment, fund transfer, or journal entry is routed through the
journal engine to the enforcement dispatcher.
02
The decision is recorded (L2).
ALLOW, BLOCK, or OVERRIDE — with the signal snapshot, approval latency,
and any override attempts captured as immutable decision telemetry at the
moment of evaluation.
03
Signals aggregate into patterns.
Individual records become rates and trends — override frequency,
average approval latency, violation density by category.
04
Risk intelligence evaluates (L5).
Eligibility rules and exclusion triggers consume the decision telemetry.
High override rates, stale approvals, and repeated violations
feed directly into governance risk scoring and CARI.
05
Attestation seals the record (L6).
The enforcement decision, its signal snapshot, and the telemetry context
are captured in an immutable, hash-verifiable artifact.
Vendor Intelligence
Contractor compliance monitoring that combines public record data — licenses,
bonds, insurance, violations, debarment — with proprietary payment history
from the accounting layer below. Compliance signals feed upward into the
risk intelligence layer.
Cross-layer integration. Vendor Intelligence feeds payment history
into governed operations and risk intelligence, and produces the VECR attestation
artifact at the attestation layer. It is not a numbered layer — it is a
specialized intelligence service that enriches the stack.
License Verification
State licensing records for Washington and Oregon contractors:
status, expiry, class, specialty match. At payment, the guard reads the
stored record for a vendor matched to a contractor.
Insurance & Bond Tracking
Insurance expiry is read at payment for a matched vendor. The
certificate of insurance is checked when an invoice arrives by email.
Bond is recorded, not enforced.
VECR Attestation
Vendor Eligibility & Compliance Record. SHA-256 hashed
attestation artifact for escrow officers and auditors.
Attestation turns governed state into immutable artifacts designed for third-party
verification. Each artifact includes a SHA-256 content hash computed from canonical
JSON serialization, enabling independent verification that content has not been
altered after generation.
The CARI (Community Association Risk Index) layer generates four additional report types
for third-party subscribers via authenticated API: Lender Report, Insurer Report,
Title/Escrow Report, and Buyer Summary. Each is a signed attestation artifact
with SHA-256 content hash.
Risk intelligence scores governance and financial risk from governed ledger data.
It consumes the enforcement decision telemetry produced one layer down — guard
outcomes, override rates, approval latency, and policy-violation patterns — as
first-class signals, and turns them into eligibility evaluations, exclusion triggers,
and governance scores. Every evaluation is deterministic: the same inputs always
produce the same outputs.
18 Production Guards
Balance, closed period, fund segregation, fund consistency,
trust segregation, subledger, invariant, L5 exclusion, fund
eligibility, bill payment, vendor risk, disbursement compliance,
connect balance, fund policy, reversal, loan covenant, payment
split, interest calculation.
Controlled overrides. Guards can be overridden with explicit authorization,
documented reason, expiration date, and a maximum use count. Every override is linked
to the enforcement decision it enables. There are no silent bypasses.
CARI — Community Association Risk Index. Risk Intelligence
powers CARI, a standardized HOA health score used by lenders, insurers, and
title companies to assess community financial health. CARI consumes signals from
every layer — including enforcement decision telemetry — to produce a
unified 0-100 governance and financial health index.
09
Correctness Over Time
HOA boards turn over. Property managers change. Treasurers rotate.
In most systems, institutional knowledge leaves when people do. Decisions
that were made last year — why a vendor was chosen, why a reserve
transfer was approved, what the board agreed to — become hearsay.
CommunityPay is designed so the ledger is the institutional memory.
Every enforcement decision, every approval workflow, every policy snapshot
persists in the system of record. When a new board member takes office, a firm
takes over the books, or a CPA begins an engagement, the full history is there —
not in someone's email, not in a spreadsheet, not with the person who left.
Survives Board Turnover
Immutable decision records mean a new board inherits complete context.
No lost institutional knowledge. No "we think that's what happened."
Ready for Professional Review
CPAs, auditors, escrow officers, and attorneys can independently
verify the record. Every artifact is hash-verifiable.
Less Error, Less Risk
Enforced controls catch problems at posting time, not at year-end.
The longer the platform runs, the more complete the governance record.
Governance should not depend on who happens to be on the board.
It should depend on a system of record that enforces correctness, logs every
decision, and makes the full history available to whoever needs it next.