CommunityPay

California Resale
Certificates

Cal. Civ. Code §4525-4530 requires associations to provide disclosure documents to prospective buyers. CommunityPay generates them from live ledger data in minutes.

One statute profile. 15 required disclosure items. Every data point pulled from the system of record — no manual assembly, no re-keying, no stale spreadsheets.

1 statute profile · 15 required disclosure items · 10-day delivery deadline · Actual cost fee · Generated from live ledger data

Written for
Title officers, escrow closers, real estate agents, and board members who need to understand California resale certificate requirements under the Davis-Stirling Act.
Statute reference
Cal. Civ. Code §4525-4530 (Davis-Stirling Common Interest Development Act). Applies to all common interest developments in California.
01

What California Requires

The Davis-Stirling Common Interest Development Act governs all common interest developments in California — condominiums, planned developments, stock cooperatives, and community apartment projects. It defines exactly what must be disclosed to a prospective buyer before a sale closes.

Davis-Stirling Act
Governs all CIDs in California. 15 required disclosure items covering financials, reserves, insurance, governing documents, and restrictions on use and occupancy.
Key Distinctions
Meeting minutes from the preceding 40 days, assessment enforcement policy per §5310, exclusive use common areas, and form of title — items unique to California not found in other states' statutes.
Fee and Delivery
Actual cost of preparation (no statutory cap). 10-day delivery deadline. No specified buyer review or cancellation period tied to the certificate.
California-specific items. The Davis-Stirling Act requires disclosure of the assessment enforcement policy (§5310), meeting minutes from the preceding 40 days, the form of title, and a description of exclusive use common areas. These items have no equivalent in Washington, Oregon, Florida, or Texas statutes.
02

Required Disclosure Items

The statutory items that must be included in the resale certificate, mapped to the specific subsection of law. This is the checklist title officers and board members use to verify completeness.

Cal. Civ. Code §4525-4530
Davis-Stirling Act · 15 items
§4525(a)(1) Copy of the operating budget or summary
§4525(a)(2) Amount of reserve funds and anticipated reserve expenses
§4525(a)(3) Most recent fiscal year-end financial statement
§4525(a)(4) Insurance summary including policy types, limits, and deductibles
§4525(a)(5) Statement of assessment enforcement policy per §5310
§4525(a)(6) Assessment and fee information including delinquent assessments
§4525(a)(7) Special assessments approved but not yet billed, or assessments to be increased
§4525(a)(8) Pending litigation involving the association
§4525(a)(9) Governing documents (CC&Rs, bylaws, operating rules)
§4525(a)(10) Minutes of board and member meetings for preceding 40 days
§4525(a)(11) Form of title under which the interest is sold
§4525(a)(12) Description of exclusive use common area or separate interests
§4525(a)(13) Outstanding code violations of which the association has been notified
§4525(a)(14) Restrictions on occupancy, leasing, or rental of separate interests
§4525(a)(15) Age restrictions or senior housing compliance information
California-specific data models. The Davis-Stirling Act requires specific items not found in other states' statutes — meeting minutes from the preceding 40 days, the assessment enforcement policy, and the form of title. CommunityPay maps each item to the specific statute subsection and pulls data from the appropriate model.
03

Manual vs System-Generated

Most California associations still produce resale certificates by hand — pulling numbers from accounting software, hunting for insurance certificates, checking violation logs, and copying it all into a Word document. The 10-day deadline makes this a recurring fire drill that creates real liability.

Manual Process System-Generated
Turnaround 3–7 business days Minutes
Data accuracy Depends on who prepares it Live from ledger
Statute mapping Manual checklist, easy to miss items Every item mapped to subsection
Balance sheet May be months old Current within 120 days (enforced)
Verifiability None — Word doc or scanned PDF SHA-256 content hash, QR verification
Risk flags Not surfaced Deterministic (stale data, delinquency, gaps)
Audit trail Email chain, maybe Immutable packet with event log
04

Sample Certificate

A sample resale certificate for a California common interest development using Cal. Civ. Code §4525-4530. The same format, structure, and compliance mapping used in production — with demo data.

Sample California Resale Certificate
Cal. Civ. Code §4525-4530 · Demo Data
Sample in development
  • Cover page with compliance profile and statutory reference
  • Compliance matrix showing status of all 15 required items
  • Assessment enforcement policy disclosure
  • Meeting minutes availability (preceding 40 days)
  • Reserve fund status with percent funded
  • Insurance coverage summary with policy details
  • Risk flags panel with severity-based indicators
  • SHA-256 content hash and verification section
  • Branded footer with QR verification code
Every certificate includes a SHA-256 content hash and verification URL. Recipients can independently confirm the document has not been altered after generation.
05

How It Works

From request to delivery. Title companies can submit requests via API or form. The board reviews disclosures before generation. The certificate is generated from live ledger data and delivered with an HMAC-signed callback.

01
Request received. Title company submits via API (POST /api/v1/rc/request/), public form, or board initiates directly. Property address matched to HOA and unit.
02
Board review. Request appears in the Vault RC Requests queue. Board reviews disclosure items and can set overrides for items requiring board-confirmed information (litigation, warranties).
03
Board approves. Disclosure modal shows all items that will be included. Board confirms, and the system pulls live data from every relevant model in the ledger.
04
Certificate generated. Compliance profile selected, snapshot assembled, compliance check computed, risk flags evaluated, PDF rendered with branded footer and verification QR. SHA-256 content hash computed from canonical JSON.
05
Delivered. Requestor notified. 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.
06

Multi-State Coverage

California is one of six states with active compliance profiles. The same compliance-profile-driven architecture supports all states through a single generation engine.

State Statute Profile Items Status
WA RCW 64.34.425 Condominium Act 20 Production
WA RCW 64.90.640 WUCIOA 26 Production
CA Cal. Civ. Code §4525-4530 Davis-Stirling Act 15 Active
OR ORS 94.670 Planned Community Act 13 Active
FL Fla. Stat. §720.30851 HOA Act 19 Active
FL Fla. Stat. §718.116 Condominium Act 19 Active
TX Tex. Prop. Code §207 HOA Act 10 Active
TX Tex. Prop. Code §82.157 Condominium Act 10 Active
Profile-driven, not template-driven. Each compliance profile defines required items, statutory references, fee caps, delivery deadlines, and mandatory disclosures. Adding a new state means adding a new profile — the generation engine, PDF rendering, and verification infrastructure are shared.

A resale certificate is only as trustworthy as the data behind it. When the certificate is generated from the same system of record that processes payments, tracks reserves, and enforces governance controls, every figure is verifiable back to the source transaction.

See It in Action

Download the sample certificate. Compare it to what you receive today. The difference is the system of record behind it.

CommunityPay