Core Accounting & Fund Management
CommunityPay is a double-entry fund accounting system built from the ground up for community associations. Every journal entry flows through a single mandatory posting interface. Fund segregation is enforced at the ledger level, not by convention.
| Feature | CommunityPay | Yardi Breeze Premier | AppFolio Core |
|---|---|---|---|
| Double-entry ledger | Mandatory, enforcement-gated | Yes | Simplified GL |
| Native fund accounting | Operating, Reserve, Capital — enforced segregation | Configurable | Basic |
| Chart of accounts | 60 roles, 184-account template library | Standard chart | Standard chart |
| Automated assessment invoicing | Configurable frequency, allocation methods | Yes | Yes |
| Budget management | Multi-fund, variance analysis | Yes | Basic |
| Fixed asset depreciation | Straight-line + declining balance, schedules | Module | – |
| Prepaid amortization engine | Automated monthly, remainder absorption | – | – |
| Accrual cutoff automation | Auto-reversal entries | – | – |
| Allocation engine | 6 methods: equal, sqft, ownership %, unit type, bedrooms, custom | Manual | Manual |
| Period close | Automated with evidence pack generation | Manual checklist | Manual |
| Fiscal period controls | Lock + close with override audit trail | Period lock | – |
| Financial reporting | Balance sheet, P&L, TB, aging, fund recon | Standard reports | Standard reports |
Enforcement & Compliance
Every financial transaction is evaluated by a chain of enforcement guards before it posts to the ledger. Every decision is logged as an immutable record. No decision logged means a precise signal of bypass or bug.
| Feature | CommunityPay | Yardi Breeze Premier | AppFolio Core |
|---|---|---|---|
| Pre-posting transaction evaluation | 18 enforcement guards evaluate every transaction before it posts; the database refuses any entry that carries no decision | – | – |
| Immutable decision log | SHA-256 hashed, append-only | – | – |
| Fund segregation guard | Automated, blocks cross-fund violations | – | – |
| Trust account isolation | Commingling prevention guard | – | – |
| Vendor risk guard | For a vendor matched to a Washington or Oregon licensing record, debarment, license status, license expiry, insurance expiry, and active contractor strikes are read before the payment posts. Bond is recorded, not enforced. An unmatched vendor passes and the decision says so. | – | – |
| Balance verification guard | DR = CR enforcement, every entry | – | – |
| Closed period guard | Blocks posts to locked/closed periods | – | – |
| Subledger guard | Every subledger line carries a valid reference; control accounts are reconciled nightly | – | – |
| Eligibility rules engine | Declarative expressions; no rule in force | – | – |
| Exclusion triggers | Automated bind blocks; no trigger in force | – | – |
| Audit override with accountability | Board resolution, expiration, usage limits | – | – |
| Enforcement decision explorer | Full UI: filtering, guard chain drill-down | – | – |
Resale Certificates & State Compliance
Resale certificates are generated directly from live ledger data, mapped to the exact statutory subsections required in each state. Title companies can request certificates via API. Boards review disclosures before generation. Every certificate is a SHA-256 hashed institutional artifact.
| Feature | CommunityPay | Yardi Breeze Premier | AppFolio Core |
|---|---|---|---|
| Auto-generation from live ledger | Real-time data, statute-mapped items | – | – |
| Multi-state compliance profiles | 10 states, 14 profiles | – | – |
| Washington (RCW 64.34 + WUCIOA 64.90) | 20 + 26 required items | – | – |
| California (Cal. Civ. Code §4525) | 15 required items | – | – |
| Florida (Fla. Stat. §720 + §718) | 19 required items per profile | – | – |
| Texas (Prop. Code §207 + §82) | 16 required items (HOA), 14 (condo) | – | – |
| Oregon (ORS 94.670) | 11 required items | – | – |
| Cryptographic verification | SHA-256 content hash on every certificate | – | – |
| Board review workflow | Disclosure modal, approve/reject | – | – |
| Title company inbound API | 202 Accepted, HMAC-signed callback | – | – |
| Public request form | Buyer/agent self-service | – | – |
| Risk flags | Severity-ranked, deterministic | – | – |
Reserve Fund & Debt Management
Reserve fund tracking with 30-year projections, component registers, and funding adequacy analysis. The enterprise debt subledger manages HOA and resident loans with event-sourced balances, deterministic math, versioned amortization schedules, and automated covenant evaluation.
| Feature | CommunityPay | Yardi Breeze Premier | AppFolio Core |
|---|---|---|---|
| Reserve fund tracking | Fund balance, targets, percent funded | Basic | Basic |
| 30-year projection | Year-by-year cash flow with replacement events | – | – |
| Component register | Full register by category, deterministic sort | – | – |
| Reserve Funding Status Report | Institutional packet, SHA-256 hashed | – | – |
| Enterprise debt subledger | Event-sourced, 15 transaction types | – | – |
| HOA loan management | 6 instrument types, variable/fixed rate | – | – |
| Resident loan management | Recovery plan allocation, bulk origination | – | – |
| Amortization schedules | Versioned, immutable, supersede chains | – | – |
| Day-count conventions | Actual/365, Actual/360, 30/360 | – | – |
| Covenant evaluation | DSCR, reserve ratio, delinquency, insurance | – | – |
| Subledger/GL reconciliation | Automated daily with audit trail | – | – |
CPA & Audit Infrastructure
A token-gated portal that gives CPA firms direct read-only access to trial balance, journal register, fund reconciliation, and integrity scans. No login required — one link, scope-controlled, every page access logged. Close Evidence Packs bundle 12 evidence sections for period-end audit review.
| Feature | CommunityPay | Yardi Breeze Premier | AppFolio Core |
|---|---|---|---|
| Token-gated CPA portal | SHA-256 hashed tokens, shown once | – | – |
| Portal sections | 14 sections, including trial balance, fund reconciliation, integrity, journals, chart of accounts, artifacts, and AR/AP aging | – | – |
| Scope-controlled access | Per-section manifest per engagement | – | – |
| Immutable event logging | Every page access, resource type tracked | – | – |
| Close Evidence Pack (CEP) | 12 evidence sections, 14 risk flags | – | – |
| Ledger integrity scan | 13 automated checks, daily schedule | – | – |
| Integrity snapshots | SHA-256 hashed, immutable records | – | – |
| Enforcement decision audit | Full guard chain, signals snapshot | – | – |
| Audit engagement management | Vault tab: create, revoke, track access | – | – |
Payment Processing
Payments flow through a vendor-agnostic gateway abstraction. Stripe is the primary provider for resident payments. The gateway interface is provider-agnostic; Stripe is the live provider.
| Feature | CommunityPay | Yardi Breeze Premier | AppFolio Core |
|---|---|---|---|
| Online resident payments | Stripe Connect, direct charges | RentCafe | Built-in |
| ACH payments | Bank-to-bank via Stripe | Yes | Yes |
| Vendor payments | ACH via gateway | Yardi Bill Pay | AppFolio Pay |
| Multi-gateway abstraction | Stripe, Plaid, Dwolla, InternalACH interfaces | – | – |
| Fee passthrough accounting | 3-line JE: DR Fee, CR Cash, fee split | – | – |
| Fraud detection | Velocity limits, pattern analysis | Basic | Basic |
| Webhook-driven reconciliation | Real-time status, unified entry point | Batch | Batch |
| Daily payment reconciliation | Provider ↔ GL, automated daily | – | – |
| AI OCR bill scanning | Extracts vendor, amount, date & line items from uploaded invoices | – | – |
| Deterministic account-role matching (FLASH) | Accounts resolved by role from a scored rule lookup, not a model's guess | – | – |
| Invoice inbox for AP automation | Invoice inbox: two readings of each emailed invoice feed 23 deterministic gates; the outcome is submitted for approval, drafted, or held with one sentence. It never approves or pays. | – | – |
Vendor Intelligence & Risk Scoring
BuildRated is the vendor intelligence layer — contractor license, bond, and insurance records for Oregon and Washington, read from the state licensing boards. CARI is the Community Association Risk Index, a consent-gated scoring system that serves lenders, insurers, title companies, and buyers through an authenticated API.
| Feature | CommunityPay | Yardi Breeze Premier | AppFolio Core |
|---|---|---|---|
| License monitoring | Daily automated checks, multi-source | – | – |
| Bond and insurance records | Read from the state boards; insurance expiry is checked at payment, bond is recorded | – | – |
| VECR attestation | Vendor Eligibility & Compliance Record | – | – |
| CARI risk scoring | 5-component, 0–100 index | – | – |
| Third-party API | Consent-gated, tiered | – | – |
| Lender/insurer/title/buyer reports | Lender, insurer, title, and buyer reports | – | – |
| Score monitoring & webhooks | HMAC-signed webhooks | – | – |
| Condo questionnaire API (1076/476) | Auto-fill from live ledger data | – | – |
Governance, Attestation, & Trust Accounting
Board attestation binds a content hash to officer signatures. 10 institutional packet types are generated, hashed, and versioned. The Vault provides a browser for all institutional artifacts with sharing, revocation, and full event logging. Trust accounting enforces three-way reconciliation with daily automated checks.
| Feature | CommunityPay | Yardi Breeze Premier | AppFolio Core |
|---|---|---|---|
| Board attestation | Content hash binding, e-signature integration | – | – |
| Institutional packet system | 10 packet types, SHA-256 hashed | – | – |
| Artifact Vault | Artifacts, close packages, partner access, resale requests, audit portal, CARI, and an activity log | – | – |
| Restatement chain | Version history with fresh evidence snapshots | – | – |
| Trust accounting | Three-way reconciliation (bank = GL = client) | – | – |
| Commingling prevention | Guard-enforced trust/operating isolation | – | – |
| Board member portal | Full accounting access, Vault, attestation | Yes | Yes |
| Document management | Institutional artifacts, versioned | Yes | Yes |
Security, Audit Trail, & Integrations
Immutable decision, evaluation, snapshot, and artifact records form the audit trail. Field-level encryption protects identifiers and bank details. Bank statement import supports BAI2, OFX/QFX, and CSV with automatic format detection. The legal corpus tracks every statute, case, and regulation cited across the platform.
| Feature | CommunityPay | Yardi Breeze Premier | AppFolio Core |
|---|---|---|---|
| Field-level encryption | Identifiers and bank details | Yes | Yes |
| Immutable audit trail | Immutable decision, evaluation, snapshot, and artifact records | Basic audit log | Basic audit log |
| SHA-256 content hashing | All institutional artifacts | – | – |
| Bank statement import | BAI2 + OFX/QFX + CSV, auto-detect | CSV | Bank feed |
| BAI2 parser | 100+ type codes, integrity verification | – | – |
| Transaction matching engine | Exact one-to-one matching of bank lines to ledger entries; a person reconciles and completes the month | Basic | Basic |
| 1099-NEC/MISC reporting | Automated workflow, W-9 tracking | Add-on | Basic |
| CARI external API | Rate-limited, tiered billing | – | – |
| Title company API | Inbound RC requests, HMAC callbacks | – | – |
| Webhook system | HMAC-signed, dead letter | – | – |
| Living legal corpus | Statute, case law, session law, regulation tracking | – | – |
| Multi-factor authentication | Authenticator app with recovery codes, available on every account. A fresh code within ten minutes is required to pay a vendor, change a vendor's bank, or change who holds authority; a text-message code never confirms a money action. | Not independently verified from Yardi's public documentation | Not independently verified from AppFolio's public documentation |
| Dollar-threshold approval tiers | Approval tiers by amount and approval workflows, with separation-of-duties settings recorded on every decision. By default, a person who submits a bill and holds approval authority may also approve it; the approval is recorded as a self-approval, and one setting turns that off. | Not independently verified from Yardi's public documentation | Not independently verified from AppFolio's public documentation |
Money-Out Controls
What stands between an association's balance and a vendor's bank account. Each row is enforced on the server and recorded.
| Control | CommunityPay | Yardi Breeze Premier | AppFolio Core |
|---|---|---|---|
| Who changes authority | Only the association's admin changes, demotes, or removes a member who holds authority; staff cannot, and the board is emailed. | Not independently verified from Yardi's public documentation | Not independently verified from AppFolio's public documentation |
| Fresh code before money moves | A fresh authenticator code within ten minutes to pay a vendor, approve a bill, change a vendor's bank, write an override, or change the payout bank. | Not independently verified from Yardi's public documentation | Not independently verified from AppFolio's public documentation |
| Bank PIN | An association bank PIN, separate from any login, checked on the server; five wrong tries lock it; staff cannot set it. | Not independently verified from Yardi's public documentation | Not independently verified from AppFolio's public documentation |
| Changing the payout bank | Two board members: one asks, a different one confirms. The board is emailed and the first payout to the new bank is held until a person releases it. | Not independently verified from Yardi's public documentation | Not independently verified from AppFolio's public documentation |
| A vendor's bank changes | The rail waits three business days before paying it. A different board member can end the wait after calling the vendor at a number already on file, with a fresh code and the bank PIN. | Not independently verified from Yardi's public documentation | Not independently verified from AppFolio's public documentation |
| Notice to the board | Every vendor payment sent by transfer and every top-up from the association's bank is emailed to the whole board. | Not independently verified from Yardi's public documentation | Not independently verified from AppFolio's public documentation |
| What an approval covers | A bill's approval binds the amount, the vendor, and the fund, and on the transfer rail the bank, and a payment spends it once. | Not independently verified from Yardi's public documentation | Not independently verified from AppFolio's public documentation |
| Entry with no recorded decision | Refused by the database. | Not independently verified from Yardi's public documentation | Not independently verified from AppFolio's public documentation |
Single-platform breakdowns against specific competitors, dated so the comparison stands on its own.
CommunityPay vs. PayHOA → CommunityPay vs. Buildium → CommunityPay vs. Vantaca → CommunityPay vs. CINC Systems → CommunityPay vs. Enumerate → CommunityPay vs. QuickBooks → CommunityPay vs. FrontSteps → CommunityPay vs. MRI Software → Best HOA software, eleven platforms ranked →