Storing a COI in AppFolio, Buildium, or Yardi
DueFiles
Last reviewed 2026-09-23
AppFolio, Buildium, and Yardi can store a certificate and often an expiration date. That answers whether a document was filed and when someone thinks it ends. It does not, by itself, treat CG 20 10 and CG 20 37 as separate rules, and it does not show a short limit against the requirement on the vendor file.
What the property system is the record of
AppFolio is the system of record for the property and the vendor. Buildium is the same kind of record for teams that run on Buildium. Yardi holds the vendor and the property. VendorShield is Yardi's vendor credentialing product. TenantShield is resident coverage, not a vendor certificate. None of these sentences means the property system read the endorsement.
What moves between the systems
On the Business plan, teams move vendor records and reviewed status with CSV. A CSV import is not an API. There is no live connector hiding behind that sentence. An Enterprise conversation can scope a live connection to the fields both systems should own. The path you can run without that contract is the CSV.
What the reviewer still does
DueFiles holds the requirement, the certificate, the endorsement gaps, and the review. The reviewer confirms the file. The property system can keep the expiration the team wants its staff to see. The two records answer different questions. Do not clear a CG 20 37 gap because the property system shows a date in the future.
This is an operations summary for people collecting vendor files. The policy, the endorsement schedule, and your contract control. It is not legal advice.