PAYMENTS.
ACCOUNTING. COMPLIANCE.

The system of record for financial risk governance

CommunityPay is financial risk governance infrastructure for community associations — payments and accounting systems that govern how money moves, record every decision, evaluate counterparty risk, and enforce statutory compliance.

Every transaction is enforced before it posts. Ownership changes hands. The record does not. Built to institutional audit standards, for community associations and any entity that accounts for shared property.

CommunityPay, Inc. · Verified 2026-10-07 · set digest f9f40caa How these figures are verified

Why shared property needs a ledger

An association spends other people's money on property they own together, through volunteers who change every year. The record has to outlast all of them.

Without a system of record System of Record
Spreadsheets no one trusts One double-entry ledger, every fund balancing on its own
Payments split across vendors Payments and their records in the same ledger
Board turnover erases history The record outlasts every board
Errors surface too late An entry that breaks the books is refused before it posts
No audit trail, no one accountable Every decision recorded and attributed, refusals included

Each line on the right is enforced by the ledger and the database beneath it, not by a policy someone has to remember.


ALSO BUILT ON THIS ENGINE
Standalone Products Powered by the Same Infrastructure

Same JournalEngine, enforcement guards, and bank reconciliation — separate product surfaces for specialized use cases. All included under one subscription.

Professional Managers · Attorneys · Escrow Officers · Title Officers · CDFIs · Lenders


PAYMENTS & POSTING LAYER

Automate Dues Collection & Records

Assessments and fees are collected and posted directly to the ledger—ensuring that every transaction is recorded accurately, on time, and without manual intervention.

Payments and records remain permanently linked within the system of record, reducing operational overhead while preserving auditability and financial control.

View interface
Resident Payment Ledger Posting Approval & Audit Statement Export

ACCOUNTING & LEDGER LAYER

Detailed Budgeting & Reports

Financial activity is recorded directly to the ledger, with income, expenses, and fund allocations permanently linked to supporting records.

Statements, reports, and board packets are generated from the same source of truth—ensuring accuracy, auditability, and compliance while supporting ongoing budgeting and long-term financial planning.

View interface
Transactions Fund Allocation Report Generation Board Packet

GOVERNANCE & RESPONSIBILITY LAYER

Governance & Accountability

Roles, responsibilities, and approvals are assigned directly within the system—ensuring governance workflows are routed to the appropriate parties and permanently recorded within an auditable system of record.

As board members transition, records, permissions, and historical context remain with the community—not the individual—preserving continuity and institutional memory.

Authority sits with the association’s admin; staff cannot change who holds it, and the board is emailed on every grant and removal. Money abilities start off for each admin after an association's first officer. Paying a vendor, changing a vendor’s bank, or changing the payout bank takes a fresh authenticator code, and the payout bank also takes two board members and the association’s own bank PIN. Every vendor payment and top-up is emailed to the whole board.

Secure resident access and payment portals included.

View interface
Role Assignment Responsibilities Alerts & Reminders Institutional Memory
CHOKE-POINT ARCHITECTURE
Every entry passes through the same point.
Decision provenance. The dispatcher decides. The decision is immutable. The statute it depended on is pinned to it.
Transaction Request JournalEngine single posting interface Enforcement Dispatcher mandatory choke point GUARD CHAIN · 18 ACTIVE · NO SHORT-CIRCUIT ON PASS balance period fund subledger vendor + 13 more ALLOW log + persist BLOCK log + reject OVERRIDE log + persist + audit EnforcementDecision IMMUTABLE · APPEND-ONLY Signal snapshot — guards, signals at decision time Legal authority — statute · snapshot content_hash

Every transaction enters the JournalEngine. The dispatcher runs every applicable guard in order and stops at the first block; a pass never skips a later guard. The outcome forks three ways, and the EnforcementDecision is sealed with both the signal state and the statute snapshot it relied on. Years later, the entry can still be reconstructed.

→ How the choke point was built

PLATFORM ARCHITECTURE
How CommunityPay connects your community
Board · Administrators CommunityPay Banking · Ledger · Compliance Members · Auditors · Insurers
→ View Full Architecture
→ Security & Trust
→ Design Rationale & Concepts — the principles behind the platform.
Go deeper
Pricing | Product Comparison | API
Login