What is required in an Oregon HOA resale certificate?

Oregon requires resale certificates under ORS 94.670 (Planned Community Act). 13 required disclosure items covering monthly assessments, special assessments, operating budget, reserve fund status, insurance coverage, pending litigation, governing documents, transfer restrictions, use restrictions, code violations, deferred maintenance, annual financial statement, and balance sheet.

How much can an HOA charge for a resale certificate in Oregon?

Oregon law requires that the fee for a resale certificate be a reasonable cost. Unlike some states, ORS 94.670 does not specify a statutory fee cap. The association must deliver the certificate within 10 days of the request.

What is the deferred maintenance disclosure in Oregon resale certificates?

ORS 94.670(1)(k) requires disclosure of known deferred maintenance or capital improvement needs. This requirement is unique to Oregon among CommunityPay's covered states. CommunityPay pulls this data from the FixedAsset model, which tracks reserve components with deferred maintenance flags.

ORS 94.670 is Oregon's statute governing resale disclosures for planned communities under ORS Chapter 94 (Oregon Planned Community Act). It requires associations to provide a resale certificate with 13 required disclosure items within 10 days of a request, at a reasonable cost.

Oregon HOA Resale Certificates — ORS 94.670

What Oregon Requires

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

Planned Community Act

ORS 94.670 governs resale disclosures for planned communities. 13 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-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.670(1)(k) makes this a first-class disclosure item —
                not buried in reserves or general financials.
            

Resale certificate automation →

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

Planned Community Act · 13 items

(1)(a) Monthly assessment amount and any unpaid assessments or fees

(1)(b) Approved special assessments not yet due

(1)(c) Current operating budget and most recent financial statement

(1)(d) Amount of reserve fund and designated purposes

(1)(e) Summary of insurance coverage maintained by the association

(1)(f) Pending suits or judgments against the association

(1)(g) Declaration, bylaws, and rules of the association

(1)(h) Right of first refusal or other transfer restrictions

(1)(i) Restrictions on use, occupancy, or leasing of units

(1)(j) Outstanding code violations affecting common areas or unit

(1)(k) Known deferred maintenance or capital improvement needs

(1)(l) Most recent annual financial statement

(1)(m) Current balance sheet or financial condition statement

Oregon is the only state in CommunityPay’s coverage that explicitly requires disclosure of known deferred maintenance and capital improvement needs (ORS 94.670(1)(k)). CommunityPay pulls this data from the FixedAsset model — reserve components with deferred maintenance flags.

The Problem with Manual Assembly

Most Oregon 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

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 13 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.
            

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.

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.

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).

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.

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.

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.

Multi-State Coverage

Oregon is one of six 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-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.

Resale certificate automation → Platform architecture → Request a certificate → Verification model →

Oregon Resale
Certificates