
Connect to Yardi Voyager's SOAP-based web services at your client-specific URL (yardiasp13.com/{CLIENT_URL}/webservices/) using interface username and password credentials. Metro2 calls the ItfResidentTransactions and Billing & Payments interfaces to extract tenant demographics, lease terms, charge and payment transactions, and property data. Each response field is mapped to the Metro 2 Base Segment, validated against CDIA formatting rules, and submitted to Equifax, Experian, and TransUnion. Yardi already partners with Experian RentBureau for daily native rent reporting — this integration extends that to a full Metro 2 file covering all three bureaus with your own data furnisher credentials.
Metro2 authenticates to Yardi Voyager's SOAP web services using interface username/password credentials at your client-specific URL (https://www.yardiasp13.com/{CLIENT_URL}/webservices/{interface}.asmx). It calls ItfResidentTransactions for tenant and lease data, and the Billing & Payments interface for charge and payment records. Each field is mapped to the Metro 2 Base Segment, validated against CDIA rules, and submitted to Equifax, Experian, and TransUnion.
Yardi VoyagerYardi exposes tenant and payment data through SOAP interfaces (ItfResidentTransactions, ItfCommercialAPI, Billing & Payments) at your client-specific .asmx endpoints. Metro2 calls these interfaces to extract the data needed for Metro 2 reporting.
Pull data across your entire Yardi Voyager instance — residential, commercial, and mixed-use — and generate a single Metro 2 file covering all properties under one data furnisher agreement.
Yardi already partners with Experian RentBureau for daily rent reporting. This integration extends coverage to a full Metro 2 file submitted to Equifax, Experian, and TransUnion under your own credentials.
Yardi Voyager is used by the largest property management companies in the world. Payment records from Yardi's accounting engine are reliable and audit-ready for credit bureau reporting.
Metro2 integrates with both Yardi Voyager 7 (enterprise) and Yardi Breeze (SMB) — same SOAP interfaces, same data mapping, same Metro 2 output.
Report on-time rent payments across thousands of units to all three credit bureaus, giving tenants a credit-building amenity and reducing turnover across your portfolio.
Metro2 maps these fields from Yardi Voyager to Metro 2 format automatically.
Yardi API access requires an interface partnership agreement. If you don't already have one, contact your Yardi account representative to set up an interface. API access costs approximately $25,000/year per interface. Metro2 can also work with scheduled SFTP file exports if API access is not feasible.
In Metro2, go to Integrations > Add > Yardi Voyager. Enter your Yardi client URL, interface username, and interface password. Metro2 will authenticate via SOAP and verify the connection to your .asmx endpoints.
Review the automatic field mapping from Yardi SOAP response fields to Metro 2 Base Segment fields. Configure grace periods, late payment thresholds, and select which properties to include in reporting.
Run a test sync to pull data from Yardi and generate a sample Metro 2 file. Review Account Status codes, Payment Ratings, balance calculations, and verify that resident transaction data maps correctly.
Confirm tenant consent is collected, verify your interface credentials have the correct permissions, and enable automatic monthly submissions to the credit bureaus.
We support Yardi Voyager 7 (enterprise) and Yardi Breeze (SMB). Both expose the same SOAP web service interfaces (ItfResidentTransactions, Billing & Payments) that Metro2 uses for data extraction.
For real-time SOAP API access, yes — Yardi requires an interface partnership agreement at approximately $25,000/year per interface. If that's not feasible, Metro2 also supports scheduled SFTP file exports from Yardi as an alternative.
Yardi uses interface-specific username/password credentials sent via SOAP headers. Each interface (ItfResidentTransactions, Billing & Payments, etc.) has its own .asmx endpoint at your client-specific URL: https://www.yardiasp13.com/{CLIENT_URL}/webservices/{interface}.asmx.
Yardi partners with Experian RentBureau for daily native rent reporting. However, that only covers Experian. This Metro2 integration generates a full Metro 2 file for submission to all three bureaus (Equifax, Experian, and TransUnion) under your own data furnisher credentials.
Yes. Metro2 pulls data across all properties in your Yardi instance and generates a single Metro 2 file. You can configure which properties to include or exclude in your reporting settings.
Yardi does not document webhook support in its public-facing materials. Metro2 uses scheduled batch pulls from the SOAP interfaces. You can configure the sync frequency in your integration settings.
Metro2 calculates the Payment Rating (0-6) by comparing charge due dates from Yardi's billing interface against payment dates. 0 = current, 1 = 30-59 days past due, 2 = 60-89 days, up to 6 = 180+ days. Configurable grace periods are applied before calculating delinquency.
There is an unofficial Python SDK (yardi-sdk on PyPI) that wraps Yardi's SOAP interfaces. Metro2 uses its own optimized SOAP client, but the SDK can be useful for testing and prototyping integrations.

Pull tenant, occupancy, and payment data from AppFolio's REST API via OAuth 2.0 to generate Metro 2 credit reports for all three bureaus.

Pull tenant, lease, and payment data from Buildium's REST API via API key authentication to generate Metro 2 credit reports for all three bureaus.

Pull resident, lease, and payment data from Rent Manager's WAPI12 REST API via SSL-encrypted Authentication Token to generate Metro 2 credit reports for all three bureaus.