A resale certificate is required for every unit sale in a community association.
Waiting days or weeks for one delays closings, frustrates buyers, and creates
liability for the board. CommunityPay generates statute-compliant certificates
from live accounting data — the moment your board approves, the document is ready.
Generated from Live Data
Assessments, reserves, insurance, governance —
every disclosure item is pulled directly from your
ledger. No re-keying. No spreadsheets. No guesswork.
Statute-Compliant by Default
Each certificate follows the exact compliance profile
for your state and statute. Required items are mapped
to specific statutory subsections. Nothing is missed.
Board Review Built In
Requests queue in your Vault. The board reviews
disclosure items, confirms board-level information,
and approves generation — all in one workflow.
Title Company API
Title officers and escrow closers can submit requests
directly via API. Board gets notified. Certificate
delivered automatically on approval.
Independently Verifiable
Every certificate includes a SHA-256 content hash and
QR verification code. Any recipient can confirm the
document has not been altered.
Complete Audit Trail
Every request, review, approval, and delivery is
logged with timestamps. The board always has a
defensible record of what was disclosed and when.
How it works. A request arrives — from a title company, escrow closer, or your
own board. The board reviews disclosures in the Vault and approves. CommunityPay pulls live data
from every relevant account, generates a statute-compliant PDF with verification QR, and delivers
it to the requestor. The entire process is logged in your audit trail.
The certificate includes two categories of information. Live data pulled directly
from the ledger, and board-confirmed disclosures that require human attestation.
Items without board-confirmed information resolve as "unknown" — never omitted,
never fabricated.
Assessment balances, delinquency, special assessments
Reserve fund balance, percent funded, component register
Current operating budget
Balance sheet and revenue/expense statement
Insurance coverage, carrier, expiration
Board composition and governance attestation
Open violations (FL §720/§718)
Capital expenditures (TX §207/§82.157)
Pending litigation and unsatisfied judgments
Health, building, or environmental code violations
Qualified warranty coverage and claims history
Transfer restrictions and right of first refusal
Board transfer approval requirements
Assessment enforcement policy (CA)
Deferred maintenance (OR)
Use, occupancy, and rental restrictions
"Unknown" is truthful. When board-confirmed information has not been provided,
the system emits a disclosure with the value "unknown" and an explanatory statement. The certificate
never omits a required item. It never fabricates an answer. Unknown data is a first-class output.
Eight compliance profiles across six states. Each profile defines the required
disclosure items, statutory references, fee caps, delivery deadlines, and mandatory
disclosure text blocks for a specific jurisdiction and community type.
| State |
Statute |
Profile |
Items |
Fee Cap |
Delivery |
Buyer Review |
| WA |
RCW 64.34.425 |
Condominium Act |
20 |
$275 |
10 days |
5 days |
| WA |
RCW 64.90.640 |
WUCIOA |
26 |
$275 |
10 days |
5 days |
| CA |
Cal. Civ. Code §4525 |
Davis-Stirling Act |
15 |
Actual cost |
10 days |
— |
| OR |
ORS 94.670 |
Planned Community Act |
13 |
Reasonable cost |
10 days |
— |
| FL |
Fla. Stat. §720.30851 |
HOA Act |
19 |
$299 |
10 biz days |
3 days |
| FL |
Fla. Stat. §718.116 |
Condominium Act |
19 |
$299 |
10 biz days |
15 days |
| TX |
Tex. Prop. Code §207 |
HOA Act |
10 |
$375 |
10 biz days |
7 days |
| TX |
Tex. Prop. Code §82.157 |
Condominium Act |
10 |
$375 |
10 biz days |
7 days |
Profile-driven, not template-driven. Each compliance profile is a data structure
defining required items, statutory references, fee caps, delivery deadlines, and mandatory disclosures.
Adding a new state means adding a new profile definition — the generation engine, PDF rendering,
and verification infrastructure are shared.
From request to delivery. Title companies can submit requests via API or public form.
The board reviews disclosures before generation. The certificate is generated from live
ledger data and delivered with a signed callback.
01
Request received.
Title company submits via API (POST /api/v1/rc/request/ → 202 Accepted),
public buyer/agent form, or board initiates directly. Property address matched to HOA and unit
via PropertyMatchingService.
02
Board review.
Request appears in the Vault RC Requests queue. Board reviews disclosure items
and sets overrides for items requiring board-confirmed information —
litigation, warranties, transfer restrictions.
03
Board approves.
Disclosure modal shows all items that will be included in the certificate.
Board confirms. The system pulls live data from every relevant model in the
ledger — invoices, funds, insurance policies, violations, budgets.
04
Certificate generated.
Compliance profile selected. Evidence snapshot assembled. Compliance check computed.
9 risk flags evaluated. PDF rendered with branded footer, verification QR code, and
SHA-256 content hash computed from canonical JSON.
05
Delivered.
Requestor notified by email. If a callback URL was provided, HMAC-SHA256 signed POST
delivered with exponential backoff (5 retries). Certificate available in the Vault
with full event log — created, generated, viewed, downloaded, shared.
Every certificate is an institutional artifact. It can be independently verified,
its integrity can be confirmed, and its lineage can be traced through the event log.
SHA-256 Content Hash
Computed from canonical JSON with sorted keys and minimal
separators. Any modification to the certificate data
invalidates the hash.
QR Verification Code
Branded footer includes a QR code linking to an
independent verification endpoint. Recipients can
confirm authenticity without contacting the association.
9 Risk Flags
Deterministic risk indicators evaluated at generation:
BALANCE_SHEET_STALE, UNIT_DELINQUENT, NO_INSURANCE,
COMPLIANCE_GAPS, and 5 more. Severity-ranked.
Immutable Packets
Certificates are stored as immutable institutional packets.
PII redaction is the only exception — logged as a
PII_REDACTED event with audit trail.
Restatement Chain
Corrections create a new packet linked to the original
via restatement_of FK. The original is never modified.
Full version chain preserved.
Event Log
Every action is timestamped: created, generated, viewed,
downloaded, shared, voided, restated. Complete audit
trail for institutional review.
Each state page details the specific statutory requirements, required disclosure items,
fee caps, delivery deadlines, and buyer review periods for that jurisdiction.
The certificate is the product's calling card.
Every resale certificate that reaches a title company carries the CommunityPay
brand, a verification QR code, and the implicit message: this association
uses a system of record.