CommunityPay

Oregon Resale
Certificates

ORS 94.670 requires planned community associations to provide resale certificates disclosing financial and governance status. CommunityPay generates them from live ledger data in minutes.

One statute profile. 11 required disclosure items. Every data point pulled from the system of record — no manual assembly, no re-keying, no second copy of the books.

1 statute profile · 11 required disclosure items · 10-business-day delivery deadline · Reasonable cost fee · Generated from live ledger data

Written for
Title officers, escrow closers, real estate agents, board members, managers, and accounting firms who need to understand Oregon resale certificate requirements under the Planned Community Act.
Statute reference
ORS 94.670 (Oregon Planned Community Act). Applies to planned communities governed by ORS Chapter 94.
01

What Oregon Requires

Oregon has one statute governing resale certificates for planned communities. ORS 94.670 defines 11 required disclosure items that must be provided to buyers within 10 business days of a request.

Planned Community Act
ORS 94.670 governs resale disclosures for planned communities. 11 required items covering financials, reserves, insurance, governing documents, and restrictions.
Key Distinctions
Deferred maintenance disclosure (unique to OR — known capital improvement needs and deferred maintenance must be disclosed), alienability restraints, balance sheet or financial condition statement.
Fee and Delivery
Reasonable cost (no specific statutory cap), 10-business-day delivery deadline, no specified buyer review period.
Deferred maintenance. Oregon is the only state in CommunityPay’s coverage that explicitly requires disclosure of known deferred maintenance and capital improvement needs. ORS 94.595 makes this a first-class disclosure item — not buried in reserves or general financials.
Resale certificate automation →
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.

ORS 94.670 · 94.580 · 94.595 · 94.675
Planned Community Act · 11 items
(8)(a) Written statement of unpaid regular and special assessments, fines, interest, and late charges
(8)(a) Approved special assessments included in the assessment statement
(10)(c) Current operating budget of the association
(10)(d) Reserve study (as described in ORS 94.595)
(1)(a) Hazard and public liability insurance maintained on common property
(10)(a) Declaration, bylaws, recorded plat, and association rules and regulations
(2)(l) Restrictions on alienation of lots stated in the declaration
(2)(o) Restrictions on use, maintenance, or occupancy of lots stated in the declaration
(4) Maintenance plan (reviewed and updated as necessary by the board)
(10)(b) Most recent annual financial statement maintained for duplication
(4)(a) Annual financial statement (balance sheet and income/expenses)
Oregon is the only state in CommunityPay’s coverage that explicitly requires disclosure of known deferred maintenance and capital improvement needs (ORS 94.595). CommunityPay pulls this data from the FixedAsset model — reserve components with deferred maintenance flags.
03

What Changes for the Preparer

Today the preparer — the manager, the accounting firm, or the association's own staff — gathers each figure from the accounting system, the insurance file, and the violation log. The 10-business-day deadline runs while they do. In CommunityPay, those figures are already in the association's books. The preparer confirms the disclosures only the association can answer, and the certificate is generated in minutes.

Manual Process System-Generated
Turnaround Depends on gathering each record Minutes, once the disclosures are confirmed
Data accuracy Re-keyed from source records Live from ledger
Statute mapping Checked against a written checklist Every item mapped to subsection
Balance sheet May be months old Current — drawn from live ledger
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 and files Immutable packet with event log
04

Sample Certificate

A sample resale certificate generated for a fictional Oregon planned community using ORS 94.670. The same format, structure, and compliance mapping used in production — with demo data.

Sample in Development
ORS 94.670 · Planned Community Act · Sample Data
  • Cover page with compliance profile and statutory reference
  • Compliance matrix showing status of all 11 required items
  • Deferred maintenance disclosure from reserve component data
  • Reserve fund status with percent funded
  • Insurance coverage summary
  • 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. For an association that uses CommunityPay, title companies can submit requests via API or form. The manager, the treasurer, or a board member reviews the disclosures before generation. The certificate is generated from live ledger data. The association bills its fee and releases the certificate, delivered with an HMAC-signed callback.

01
Request received. Title company submits via API (POST /api/v1/rc/request/), public form, or the association's preparer starts it directly. Property address matched to HOA and unit.
02
Review. Request appears in the Vault RC Requests queue. The manager, the treasurer, or a board member reviews disclosure items and can set overrides for items requiring board-confirmed information (litigation, warranties).
03
Approval. Disclosure modal shows all items that will be included. The reviewer 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

Oregon is one of 10 states with active compliance profiles. The same compliance-profile-driven architecture supports all states through a shared 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 Davis-Stirling Act 15 Active
OR ORS 94.670 Planned Community Disclosure 11 Active
FL Fla. Stat. §720.30851 HOA Act 19 Active
FL Fla. Stat. §718.116 Condominium Act 19 Active
TX Tex. Prop. Code §207.003 HOA Act 16 Active
TX Tex. Prop. Code §82.157 Condominium Act 14 Active
CO C.R.S. §38-33.3-316 CCIOA (unified) 12 Active
NV NRS 116.4109 CIC Act (unified) 10 Active
PA 68 Pa.C.S. §5407 UPCA (planned community) 18 Active
PA 68 Pa.C.S. §3407 UCA (condominium) 18 Active
VA Va. Code §55.1-2310 Resale Disclosure Act (unified) 30 Active
AZ A.R.S. §33-1806 Planned Community Act 16 Production
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.

Resale certificate automation → Platform architecture → Request a certificate → Verification model →
Statute data reflects Oregon law as of 2026. Disclosure item counts match the production compliance profile registry.
Each resale statute on this page is re-verified against the official text on a 90-day cycle, and a release fails if one lapses.
Compare and order
Resale & condo certificate software How the preparer generates a certificate from the association's books. How it works → Best condo management software Condo accounting, compliance, and certificate generation, compared. Read the review → Best HOA software for accounting & compliance A control-focused review of the HOA software market. Read the review → Order a resale or condo certificate For an association that uses CommunityPay: its manager or board reviews, then the certificate is generated from the live ledger. Start a request →

See It in Action

Download the sample certificate. Each figure in it traces to the association's books, and its content hash lets any recipient confirm it has not changed.

View Resale Certificate Feature Request a Certificate Book a Walkthrough
CommunityPay