[{"data":1,"prerenderedAt":34},["ShallowReactive",2],{"arch-deep-/architecture/integrations/yardi":3},{"id":4,"title":5,"body":6,"category":23,"deepPage":24,"description":25,"extension":26,"layer":27,"meta":28,"navigation":29,"path":24,"relatedFlows":30,"replaces":30,"seo":31,"stem":32,"__hash__":33},"architecture/architecture/integrations/yardi.md","Yardi integration",{"type":7,"value":8,"toc":19},"minimark",[9,13,16],[10,11,12],"p",{},"Yardi is one of the two dominant property management systems in the residential operator market. The integration covers the two product lines most commonly deployed by Apareé clients — Voyager for institutional and mid-tier portfolios, and Breeze for smaller operators — and absorbs both behind the same operating-layer contract.",[10,14,15],{},"The integration consumes Yardi as the system of record for lease, ledger, and unit-state data. Lease activations and terminations flow into the onboarding and move-out engines on a defined cadence. Charges originating in the operating layer flow back into Yardi's ledger through the accounting integration with consistent metadata. The resident-facing experience does not depend on Yardi being reachable in real time; the operating layer caches the data the resident-facing flows need and reconciles asynchronously.",[10,17,18],{},"Where Yardi exposes a stable API, the integration consumes it directly. Where Yardi exposes only a portal, the integration is built against documented exports and a scoped service account. Either way, the building's resident experience is governed by the behavioral specification, not by the seam between the operating layer and the PMS.",{"title":20,"searchDepth":21,"depth":21,"links":22},"",2,[],"integration","/architecture/integrations/yardi","Yardi Voyager and Breeze wrapped through the property management integration layer.","md","4",{},true,null,{"title":5,"description":25},"architecture/integrations/yardi","fh5oUiIo8aETSy_wNjQUwTcInnHGwmzYPPoFw9ULIvk",1779718756836]