01
Approved report exports
Use the rent roll, receivables, or expense reports your customer account is authorized to export. Confirm the edition and report fields first.
Integrations · ERP
Yardi reporting from an approved data route.
Bring customer-approved Yardi exports into Permute for portfolio reporting. Start with a licensed report extract, align property identifiers and cutoffs, and keep the source evidence behind the dashboard.
Customer-approved export route
Yardi
ERP data
Permute financial intelligence layer
Connected, reconciled, and ready for use
ReportingAnalyticsAI
What this connection unlocks
Put Yardi into the same trusted layer as the rest of your business.
02
Property-level definitions
Distinguish physical occupancy from leased units, billed rent from collected rent, and the property cutoff from the extraction time.
03
Scoped portfolio access
Select the property records needed for the workflow and review Permute access before publishing a report to another team.
Data, setup, and reporting scope
| Source records | Reporting use |
|---|---|
| Licensed rent roll exports | Map property and unit identifiers and inspect occupancy or lease status at a stated snapshot. |
| Approved receivables and receipt reports | Compare charges and applied receipts within a named period and cutoff. |
| Approved property expense extracts | Apply the owner’s expense scope and compare it with the appropriate budget. |
Before connecting
Confirm the Yardi product, edition, licensing, and report export permissions. Use a customer-authorized file route for the first reporting workflow. Inspect the property IDs, date fields, and amount definitions before combining the export with other sources.
This page does not promise a native, one-click Yardi API connector. Direct API access and other licensed routes require separate verification and customer or vendor approval. Scheduled report delivery also needs a supported ingestion route; an emailed attachment is not automatically a connected source.
Freshness and limits
File-backed reports are current only through the last accepted export and its stated cutoff. Keep an export register with reporting period, extraction time, source report, and owner. A missing property file should remain a visible gap rather than appear as zero rent.
Access to an export does not establish rights to every tenant record or every Yardi product. Use the minimum records the workflow needs and avoid tenant personal data when aggregate property reporting is sufficient. Source corrections remain in the customer’s system.
Synthetic worked example
Preserve a missing property as a gap
Synthetic September reporting pack: property P100 has an approved rent extract totaling $100,000. P200 has no current extract. The expected portfolio includes both properties.
| Property | September source status | Reported rent |
|---|---|---|
| P100 | Current approved extract | $100,000 |
| P200 | Missing extract | Unknown |
The known subtotal is $100,000; the portfolio total is incomplete. Reporting $100,000 as the full portfolio total would hide the missing property. Refresh the source and review it before publishing a complete total.
One connected workflow
From Yardi data to trusted business answers.
01
Connect
Bring Yardi data into Permute.
02
Reconcile
Align records, fields, and definitions.
03
Use
Power reporting, analytics, and AI.
Start with one workflow
Review your Yardi reporting route
Bring an authorized sample export, the expected property list, and your reporting definition. Confirm access and freshness before choosing an ongoing workflow.