Two Verified Facts
These are two claims on this page sourced directly from Enumerate's own public site and independent industry-tracker reporting, not inference. Everything else on this page compares what CommunityPay has built against what Enumerate has publicly stated — where Enumerate hasn't published a claim, we say so rather than guess.
A rebrand mid-migration: TOPS Pro/IQ discontinued end of 2024
Enumerate is the rebrand of TOPS Software following a Great Hill Partners investment in May 2023. Legacy TOPS Pro and TOPS IQ were discontinued at the end of 2024, requiring existing customers to migrate onto the new Enumerate Central platform — a forced-migration event for a live customer base.
No forced product migration for existing customers
CommunityPay has not discontinued or replatformed its core product out from under an existing customer base. The ledger an association is on today is the ledger it stays on.
Resale certificates via a partner, not confirmed native
TOPS Software (now Enumerate) announced an integration partnership with HomeWiseDocs, a separate company — no public source states Enumerate owns HomeWiseDocs or CondoCerts, or generates certificates from its own ledger.
Resale certificates and condo questionnaires from live ledger data
Statute-mapped resale certificates and Fannie 1076 / Freddie 476 condo questionnaires, generated directly from the association's own accounting records — no handoff to a separate vendor or platform.
Pricing & Reporting Depth
Enumerate publishes three unnamed-dollar tiers — Starter, Growth, Enterprise — available on request, with no published rate. We're not going to guess at a number Enumerate hasn't disclosed. On reporting depth, Enumerate's own site is thin compared to the rest of this market: we found no mention of CIRA-standard fund statements, RSI, or a CPA audit portal on any page we reached, which we note as "not published," not "confirmed absent."
| Dimension | CommunityPay | Enumerate |
|---|---|---|
| Pricing model | Published flat rate — see pricing | Not published; three unpriced tiers (Starter/Growth/Enterprise), quote-only |
| Platform fee over time | Flat — does not increase after signing | Not published |
| CIRA-standard fund reporting | 31 financial reports — balance sheet, changes in fund balances, budget-and-actual, RSI, cash flows by fund | Not published on any page reached |
| Outgoing vendor ACH payment | Vendor payments by ACH from the association's own funds. | Automated vendor payments included; per-transaction fee not published |
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. Enumerate does not publish claims in this category — it's built as general-purpose property management accounting, not an enforcement layer over the ledger.
| Feature | CommunityPay | Enumerate |
|---|---|---|
| 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 | Discussed as best practice; no enforced feature published |
| Bank reconciliation | Bank feed: daily posted transactions and the live balance, matched one to one by machine; a person reconciles and completes the month. Three-way reconciliation (bank, ledger, client liabilities) is the trust accounting product. | Transaction matching + read-only bank connections |
| 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 | No published feature |
| Vendor ACH payments | Vendor payments by ACH from the association's own funds. | Included; per-transaction fee not published |
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 | Enumerate |
|---|---|---|
| CIRA-standard financial reporting | 31 financial reports — balance sheet, changes in fund balances, budget-and-actual, RSI, cash flows by fund | General-purpose GAAP reporting (balance sheet, bank rec, cash flow) — no CIRA-specific statement set published |
| 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. | "Numa AI" embedded in the product suite; scope not published |
| Resident statement access | Available to all residents | Not published as a distinct capability |
| CARIScore — community association risk index | 5-component, 0–100 score for lenders, insurers & buyers | No |
| Budget builder | Native to the ledger — ties budget lines directly to GL accounts | Included |
| Full ledger read/write access for board & manager | Every entry itemized, no curated-report ceiling | Not published as a distinct capability |
| 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 published feature |
| Deterministic account-role matching (FLASH) | Accounts resolved by role from a scored rule lookup, not a model's guess. | No published feature |
Governance, Trust & Vendor Risk
The controls a board actually needs when real money and real vendors are involved — separation of duties on approvals, trust funds that reconcile against the bank and the client independently, and vendors verified before they get paid, not after something goes wrong.
| Feature | CommunityPay | Enumerate |
|---|---|---|
| Trust accounting, three-way reconciliation | Bank = GL = client, automated daily | No published feature |
| Board approval workflow & separation of duties | Approval tiers by amount and approval workflows, with separation-of-duties settings recorded on every decision. The treasurer self-approves until the board sets a tier. | No published payment-approval workflow |
| 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 published feature |
| Collection letters & fines automation | Included, tied to the ledger | Included, per Enumerate's own site |
| 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 Enumerate'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 | Enumerate |
|---|---|---|
| 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 Enumerate'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 Enumerate'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 Enumerate'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 Enumerate'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 Enumerate'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 Enumerate'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 Enumerate's public documentation |
| Entry with no recorded decision | Refused by the database. | Not independently verified from Enumerate's public documentation |