Two Verified Gaps
These are the two claims on this page sourced directly from PayHOA's own public documentation, not inference. Everything else on this page compares what CommunityPay has built against what PayHOA has publicly stated — where PayHOA hasn't published a claim, we say so rather than guess.
Vendor payments are check-only
PayHOA's Payables module currently supports mailed or printed checks. ACH and virtual-card payments to vendors are listed as "on the roadmap" — not shipped.
Native ACH vendor payments
Vendor bills are paid by ACH directly from the association's own funds — no check to print or mail.
Resale documents through HomeWiseDocs
PayHOA's resale documents run through a partnership with HomeWiseDocs, a separate platform.
Resale certificates generated from live ledger data
Statute-mapped, SHA-256 hashed, and generated from the association's own accounting records by its manager, accounting firm, or staff, with no per-certificate charge from CommunityPay.
Enforcement & System of Record
This is where "enterprise" stops being a marketing word and starts meaning something specific: every posting evaluated against a fixed rule set before it lands, logged whether it passes or not. PayHOA does not publish claims in this category.
| Feature | CommunityPay | PayHOA |
|---|---|---|
| Pre-posting transaction evaluation | 18 enforcement guards, every transaction | No |
| Immutable decision log | SHA-256 hashed, append-only | No |
| Fund segregation enforcement | Automated, blocks cross-fund violations | No |
| Full ledger read/write access for the firm or manager that keeps the books, and for the board | Full ledger access, not a curated report | No |
| Token-gated CPA audit portal | SHA-256 hashed tokens, no login required | No |
| Enterprise debt subledger | Event-sourced, covenant evaluation | No |
| Reserve funding status report (RSI) | Institutional packet, SHA-256 hashed | No |
| Multi-state resale compliance profiles | 10 states, 14 profiles | Through HomeWiseDocs |
| Vendor ACH payments | Vendor payments by ACH from the association's own funds. | Check-only (roadmap: ACH) |
Reporting, Legal Corpus & Institutional Tools
Beyond enforcement, this is the depth a real audit or lending relationship actually requires — CIRA-standard financial statements, a living record of the statutes a certificate cites, and requests tracked by status for resident handling.
| Feature | CommunityPay | PayHOA |
|---|---|---|
| CIRA-standard financial reporting | 31 financial reports — balance sheet, changes in fund balances, budget-and-actual, RSI, cash flows by fund | No |
| Token-gated CPA audit portal | No login required, scope-controlled per engagement, every access logged | No |
| Living legal corpus | Statute, case law, session law & regulation tracking with sourced quotes | No |
| Condo questionnaire API (Fannie 1076 / Freddie 476) | Auto-filled from live ledger data | No |
| Resident handling | Violation reports and maintenance requests are submitted, handled, and tracked by status in the database; violation fines can be linked to an accounting invoice. ARC requests run as signed documents. | No |
| Resident statement access | Available to all residents | Not published as a distinct capability |
| Full ledger read/write access for the firm or manager that keeps the books, and for the board | Every entry itemized, no curated-report ceiling | No |
| 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. | No |
| Deterministic account-role matching (FLASH) | Accounts resolved by role from a scored rule lookup, not a model's guess. | No published feature |
| CARIScore — community association risk index | 5-component, 0–100 score for lenders, insurers & buyers | No |
Governance, Trust & Vendor Risk
The controls between the people who keep the books and the board that approves the spending — separation of duties on approvals, trust funds reconciled against the bank and the client independently, and a check of each matched vendor's license and insurance before it is paid.
| Feature | CommunityPay | PayHOA |
|---|---|---|
| Trust accounting, three-way reconciliation | Bank = GL = client, automated daily | No |
| Board approval workflow & separation of duties | 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. | No |
| Vendor risk check before payment | 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. | No |
| Fraud controls on payments | Velocity limits and a risk score that flags a resident payment for review. Vendor payments are governed by the bill's approval, the three-business-day wait on a changed vendor bank, and an email to the board on every payment. | No |
| Two-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 PayHOA'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 | PayHOA |
|---|---|---|
| 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 PayHOA'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 PayHOA'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 PayHOA'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 PayHOA'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 PayHOA'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 PayHOA'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 PayHOA's public documentation |
| Entry with no recorded decision | Refused by the database. | Not independently verified from PayHOA's public documentation |