A resale certificate states what an owner owes and what the association holds. In most associations someone builds it by hand. They pull balances from the accounting system, reserve figures from a report, and the governing documents from a folder, then type the result onto a form.
On March 9, 2026, we published the idea behind a different method: the resale certificate, generated from the ledger. If the association's books hold every figure the statute asks for, the certificate can be read from the books.
How it works
The balances, assessments, and reserve figures on a CommunityPay certificate are computed from the association's ledger at the moment the certificate is generated. Each item cites the section of RCW 64.34.425 or RCW 64.90.640 that requires it. The finished certificate carries a SHA-256 hash, so a title company or lender can confirm that a copy has not changed.
The same method covers fourteen compliance profiles across ten states. Each profile is mapped to the statutory subsections it implements.
What "first" means here
We make a narrow claim. A certificate is "generated from the ledger" when the financial figures on it are computed from the association's own books at the time of generation, and when each item cites the statute behind it. Other products sell or deliver resale documents. CommunityPay was the first association product to produce the certificate this way, and it is still the only one.
Why the method matters
A certificate read from the books can be audited with the books. The association's CPA reviews the same entries that produced the figures. A change in the ledger changes the next certificate. Nothing is copied by hand, so nothing waits on a person to copy it.
CommunityPay is HOA accounting and compliance infrastructure, built in Washington state. Fund accounting, enforcement-driven controls, statute-compliant disclosures, and a CPA audit portal.
Scott Vuilleumier · Founder of CommunityPay, Inc.
Data science, investment banking, and financial systems engineering and ledger design.