Multi-property GL coding, approval routing by property, utility-invoice throughput at month-end, and construction-contractor documentation — handled natively inside your Yardi Voyager workflow.
Housing Authority of Covington runs EZ Cloud on Yardi Voyager. 7-day cycles dropped to 2 days, invoice errors fell 80%, and they save roughly $79,000 a year in labor. Read the case study →
And how EZ Cloud handles each of them inside Yardi.
Contractor invoices carry insurance certificates, W-9s, and lien waivers. When AP staff have to chase documentation before coding, invoice cycle time balloons. EZ Cloud flags supplier records as "certificate-required" at data entry, blocks approvals if certificates are missing or expired, and stores supplemental documents at the supplier level so they travel with every invoice.
Utility invoices arrive in bursts, are low-dollar but high-count, and require consistent GL coding across dozens of properties. Manual coding at this cadence produces errors. EZ Cloud codes utility invoices using per-supplier defaults and per-property overrides, so the accountant only reviews exceptions.
Property companies need approvals routed to property managers, not just GL-account owners. Most generic AP tools can only route by amount or GL code. EZ Cloud routes by supplier, property, amount, and entity — in any combination — and can auto-assign approvers at the supplier level.
Most AP automation tools connect to Yardi via nightly batch or a loose file-drop, which leaves images in one system, invoice metadata in another, and reconciliation as manual clean-up. EZ Cloud's Nexus Integration Layer writes bi-directionally into Yardi: invoice metadata, intercompany records, ACH payment data, and linked images flow into Yardi; expense accounts, PO numbers, active vendors, and property details flow back.
Standardizing intercompany records across properties is a source of constant cleanup. EZ Cloud handles intercompany at the point of coding — a single invoice splits into the correct entity and property records, posted together.
Yardi licenses for occasional approvers are hard to justify. EZ Cloud approvers do not need Yardi licenses — approval happens inside EZ Cloud and posts into Yardi on approval.
Invoices, intercompany records, ACH, and images post directly through a prebuilt, EZ Cloud-maintained integration. Not a nightly batch.
Build approval chains by property, entity, GL account, and amount — in any combination.
A supplier record maps directly to the right approver, so AP staff don't route manually.
Insurance certificates, W-9s, and lien waivers attached to suppliers flow with every invoice. Expiration flags block posting if docs are out of date.
Active vendors, expense accounts, PO numbers, and property details stay current in EZ Cloud; invoice and payment data flows back into Yardi Voyager.
Approvers use EZ Cloud only.
HACOV runs EZ Cloud on Yardi Voyager. Live since 2021.
EZ Cloud has made my life in a busy accounts payable environment more efficient. The whole team was skeptical at first about how EZ Cloud and Yardi were going to work together but they have, and it has been seamless.
— Denise Steffen, Staff Accountant, Housing Authority of Covington
Read the full case studyModel the impact of EZ Cloud against your current AP cost structure.
Estimates. Model uses a 75% processing-time reduction and 90% exception-automation baseline, before your EZ Cloud subscription.
* Estimates based on industry averages. Your actual results may vary.
Book a 30-minute discovery call and we'll walk through the integration against your setup.