The Resale Certificate, Generated From the Ledger

You sell your condo. The buyer's lender needs a resale certificate before the loan closes. The association charges a preparation fee, up to $275 in Washington, and has 10 days to deliver.

The document itself is a few pages of numbers your HOA already has: what you owe, what the association owes, how much is in reserves, what insurance is on file.

Your HOA pays thousands of dollars a year for accounting software. That software has every number the certificate requires. But it still takes a human two to four hours to pull the data together, cross-check it against spreadsheets, and email a PDF.

The fee covers that staff time. The closing waits on it.

The Numbers

Roughly 350,000 to 400,000 condominiums and HOA homes change hands in the United States each year. State law requires a resale certificate for most of them. Some states call it a resale certificate. Others call it a disclosure packet or status letter. The requirement is the same: an official statement of the owner's financial status and the association's financial health.

Several states cap the preparation fee. The caps and deadlines:

California allows 10 days (Civil Code 4530(a)(1)). Most states give 10 business days.

Why It Takes So Long

The delay is not a staffing problem. It comes from how associations track money.

A typical HOA uses three to five disconnected systems:

• QuickBooks for the general ledger
• A spreadsheet for special assessments (because QuickBooks cannot track them per-unit)
• The bank portal for deposits and payment verification
• Property management software for owner records
• Another spreadsheet for resale certificate tracking

When a certificate request arrives, a staff member opens all five systems, reconciles the numbers, resolves discrepancies, and assembles the result by hand. The process is standard because the systems underneath it were built for other purposes.

General-purpose accounting software does not track fund segregation, per-unit balances, or statutory disclosure items. Staff fill that gap manually.

What the Certificate Actually Contains

The required items vary by state. Washington's Uniform Common Interest Ownership Act (RCW 64.90.640) requires 26 separate items. Florida requires 19. Texas requires 16 for HOAs (Prop. Code §207.003(b)) and 14 for condominiums (§82.157(a)). Each item maps to a specific statute subsection.

The required data includes:

• Current assessment amount and payment status
• Any past-due balance, special assessments, or liens
• Reserve fund balance and funding status
• Operating budget summary
• Insurance coverage details
• Pending litigation or known claims
• Governance information (board composition, attestation status)
• Transfer restrictions and buyer cancellation rights

Every one of these data points lives in the accounting system — if the accounting system is designed to hold them. Most are not. So the data lives in spreadsheets, email threads, and someone's memory.

What Generation From the Ledger Requires

Producing a resale certificate in minutes requires a specific architecture. Not a feature. An architecture.

A unified ledger. Every charge, payment, assessment, special assessment, late fee, and violation must post to the same double-entry general ledger. If special assessments live in a spreadsheet, the system cannot include them in the certificate without human intervention.

Per-unit AR tracking. The system must know exactly what each owner owes, with full posting history. Not an editable balance field. A computed balance derived from immutable ledger entries.

Fund-aware accounting. Operating funds and reserve funds are legally separate. The balance sheet, the reserve funding status, and the budget must each reflect this segregation. Software that lumps funds together cannot produce a compliant certificate.

Statute-mapped compliance profiles. Each state has different requirements. The system must know which items are required for a given state and statute, map each to the correct data source, and surface gaps honestly when data is missing.

Immutable output. The certificate is a legal document. Once generated, it should be tamper-evident. A SHA-256 content hash over the canonical data, locked at generation time, allows any party to verify the document has not been altered.

What Changes When This Exists

When the accounting system contains all the data and understands what a resale certificate requires, the generation process is:

1. Select the unit
2. Select the compliance profile (state-specific statute)
3. Review pre-filled statutory disclosures
4. Confirm

The system pulls every required data point from the live ledger. No exports. No reconciliation. No spreadsheets. The certificate is generated in minutes, once the disclosures are confirmed.

For title companies that process hundreds of closings per month, the difference is material. For an association on CommunityPay, a title company submits an API request. The property is matched to the association and unit. A board member, the treasurer, or the association's manager reviews the disclosures and approves. Approval generates the certificate; the requestor is billed after it is generated, and on payment the title company receives a signed webhook callback with a download link and verification URL.

The board's review time is the bottleneck — not data assembly. And the board's review is a disclosure confirmation, not a reconciliation exercise. They are confirming answers to statutory questions ("Is there pending litigation?"), not manually checking whether QuickBooks matches the spreadsheet.

The Fee Question

If certificate preparation takes minutes instead of hours, the economics change.

The preparation fee pays for the preparer's time, and most of that time goes to reconciling disconnected systems. CommunityPay makes no per-certificate charge to the association, its manager, or its accounting firm; certificates are included in the platform subscription. A requestor who orders a certificate through CommunityPay pays the preparation fee after it is generated.

This does not mean HOAs will stop charging transfer fees — many states permit them, and boards use them as revenue. What the association charges within its state's cap remains its decision. What changes is the staff time behind the fee: assembly drops from hours to a review step.

The Distribution Effect

This is where it gets interesting for the market.

Title companies process hundreds or thousands of closings per year. An escrow officer who receives a resale certificate generated from the books — verified, statute-mapped, with an audit trail — notices. They tell colleagues. They tell the next HOA they work with.

CPA firms that audit HOA financial statements need verified balance data. When a CPA accesses a verified trial balance through a token-authenticated portal instead of requesting exported spreadsheets, they notice. They tell their other HOA clients.

The pattern is the same one that made Stripe the default payment processor: the people who interact with the product in their daily workflow become the distribution channel. Not because someone marketed to them. Because the product removed friction from their job.

Fourteen Profiles. Ten States. One System.

CommunityPay currently generates resale certificates under fourteen compliance profiles across ten states, including:

Each required item is mapped to its statute subsection. Each data point is traced to its source in the general ledger. Missing data is disclosed as "Unknown" with an explanatory note — the system never omits a required section. Risk flags (stale balance sheet, unit delinquency, expiring insurance, missing reserve study) appear on every certificate.

Every certificate is an immutable institutional packet with a SHA-256 content hash, version chain, and full event audit trail. If the certificate needs correction, a restatement links to the original with a documented reason. Both remain in the record permanently.

The Market Opportunity

The resale certificate is a small document. But it touches every condo and HOA transaction in the country. It is the single artifact where the accounting system's integrity — or lack of it — is directly visible to buyers, sellers, agents, lenders, and title companies.

When that artifact is generated from verified ledger data, it does two things. It removes a friction point from every real estate transaction involving an association. And it shows, concretely, what a ledger built for associations produces.

The resale certificate is not the product. It is the proof.

In CommunityPay, an association's manager, accounting firm, or staff generates statute-mapped resale certificates from the association's ledger in minutes, with no per-certificate charge from CommunityPay. Fourteen profiles across ten states. Title company API for associations on CommunityPay.