Integration available · CSV / file exchange
NetSuite + Yardi Breeze
Yardi Breeze connects to NetSuite through 3988 by CSV / file exchange today. It is not a live API integration. If you want one, 3988 can build it as a scoped part of your engagement, the same way it built Cubby.
Last reviewed:
The Yardi Breeze integration, stated plainly.
- Integration
- Yardi Breeze to NetSuite, supported by 3988.
- Platform owner
- Yardi
- Status today
- Integration available by CSV / file exchange. Not a live API integration.
- Live API
- Available as a scoped build, using the same pattern as 3988’s live Cubby integration.
- System of record
- Yardi Breeze keeps the tenant ledger. NetSuite owns the financials.
- NetSuite edition
- NetSuite OneWorld, so every legal entity is its own subsidiary.
- Built for
- Operators running 10 or more legal entities. No upper size limit; 3988 clients run well over 500 locations.
- Delivered by
- 3988, a NetSuite consultancy headquartered in Toronto serving the United States and Canada.
Yardi Breeze runs the facility. NetSuite runs the enterprise.
Yardi Breeze is cloud-based property management software from Yardi that runs leasing, tenant accounts, payments and site operations — used by self storage and other real estate operators.
It isn't built to consolidate dozens of legal entities, tie out intercompany, or produce a different statement for every owner. That is a general ledger job, and NetSuite does it.
File exchange now. Live API if you want it.
| File exchange (today) | Live API (scoped build) | |
|---|---|---|
| How data moves | A scheduled CSV or file export from Yardi Breeze, mapped and imported into NetSuite. | Directly between the two systems, with no export or upload. |
| Manual steps | Someone or something has to produce and pass the file each period. | None once it is running. |
| Timeliness | As current as the last file. | Per facility, daily or per defined period. |
| Available | Today. | As a scoped build in your engagement. It adds to timeline and cost, priced as its own line. |
The same financial data, by file.
| Data from Yardi Breeze | How it lands in NetSuite |
|---|---|
| Rental revenue, by revenue stream | Rent, tenant protection / insurance, late fees, admin fees, merchandise and auction proceeds, each to its own line by facility and entity. |
| Deferred and prepaid rent | Held as a liability and recognised as it is earned. |
| Tenant deposits | Booked as a liability, not revenue. |
| Merchant settlement clearing | Gross charges, processor fees and the net deposit, so the bank reconciles. |
| Write-offs and credits | Posted to the facility and entity they belong to. |
The boundary
Yardi Breeze stays the system of record for the tenant ledger. NetSuite owns the financials. Tenant-level detail does not migrate.
NetSuite + Yardi Breeze: common questions.
Is there a NetSuite integration for Yardi Breeze?
Yes, through CSV / file exchange. Yardi Breeze data reaches NetSuite as a scheduled file that 3988 maps and imports. It is not a live API integration today.
Is the Yardi Breeze integration a live API?
No. Today it is CSV / file exchange. 3988’s live API integration is Cubby. A live API integration for Yardi Breeze can be built as a scoped part of an engagement, using the same pattern, and it adds to timeline and cost.
Does NetSuite replace Yardi Breeze?
No. Yardi Breeze stays the system of record for the tenant ledger and site operations, and tenant-level detail does not migrate into NetSuite. NetSuite owns the financials: the general ledger, intercompany, consolidation and owner reporting across entities.
Who is the Yardi Breeze integration for?
Storage and multi-asset real estate operators with 10 or more legal entities who report to more than one owner group. There is no upper size limit: 3988 supports portfolios well over 500 locations.
Who supports it?
3988, a NetSuite consultancy headquartered in Toronto that implements NetSuite for storage and multi-entity real estate operators in the United States and Canada.
Related
Running Yardi Breeze across 10+ entities?
We'll tell you straight what file exchange covers today, and what a live API build would add to timeline and cost.