Report rent to the credit bureaus from the property management software you already use
Turn on-time (and delinquent) rent payments into bureau-ready Metro 2 tradelines. Send us a ledger export from Buildium, AppFolio, Yardi, or any system, and we hand back a validated, CRRG-compliant first file ready for Equifax, Experian, TransUnion, and Innovis.
Built for
What makes reporting hard here
Rent is invisible to credit files by default
Residents pay their largest monthly obligation on time for years and get zero credit benefit, because property managers rarely have a bureau furnisher relationship or a Metro 2 pipeline to report it.
Your PM software exports a ledger, not a Metro 2 file
Buildium, AppFolio, Yardi, and the rest produce rent rolls, delinquency reports, and transaction ledgers. None of them emit the fixed-width Metro 2 records the bureaus require, so the data sits in a CSV no one can submit.
Positive-only vs full-file is a compliance decision, not a checkbox
Reporting only on-time payments is treated very differently from full-file reporting that includes delinquencies. Get the policy, the disclosures, and the consent wrong and you create FCRA accuracy and fairness exposure instead of a resident benefit.
Consent, deposits, and lease nuances break naive exports
Security deposits are not balances, co-signers are not joint account holders, mid-lease move-ins change the date opened, and a resident who never opted in must never appear in the file. A raw export ignores all of this.
Four bureaus mean four formats, codes, and SFTP endpoints
Equifax (via the RentBureau pathway), Experian, TransUnion, and Innovis each have their own subscriber codes, header expectations, and delivery cadence. Hand-managing four pipelines is where rent-reporting programs stall.
Send us one ledger export. Get back a validated, bureau-ready first file.
The fastest way to launch rent reporting is to stop trying to build the Metro 2 file yourself. Export your resident ledger from whatever software you run, hand it to us, and we return a fully mapped, CRRG-validated first file with a line-by-line review of what we found and fixed.
- We auto-detect your export's columns and map them to Metro 2 / CRRG fields, including the account-type and ECOA codes appropriate for a lease tradeline.
- Every record is run through the 240+ rule validation engine against the current CDIA CRRG before anything is called "ready."
- You get a plain-language review of every flagged record, the fix we applied, and any rows we held back (missing consent, security-deposit-only ledgers, obsolete delinquencies).
- We help you choose positive-only vs full-file reporting and configure the program so the policy is consistent across the whole portfolio.
- The first file is delivered in test/sandbox mode so you can confirm it against the bureau before a single live record is furnished.
- Once the first file passes, monthly generation, validation, and multi-bureau SFTP delivery run on a schedule you set.
How your first file comes together
- 1
Export your resident ledger
Pull a rent roll or transaction/ledger export from your PM software (or your generic CSV). Include resident identity fields, lease dates, monthly rent obligation, amount paid, balance, and payment status per period.
- 2
Auto-map fields to Metro 2 / CRRG
Upload the file and the importer detects your headers and proposes a mapping to Metro 2 fields. You confirm the account type, ECOA/association code, and how a lease maps to a tradeline (typically one tradeline per responsible resident).
- 3
Validate against the CRRG
The 240+ rule engine checks every record for format, cross-field, and logic errors: date-opened vs lease start, balance vs deposit handling, delinquency status sequencing, and consent flags. You see exactly which rows pass and which need attention.
- 4
Fix and confirm holdbacks
Resolve flagged records and review the rows we intentionally held back, including residents with no opt-in on file, accounts past the FCRA obsolescence window, and deposit-only ledgers that should not produce a balance tradeline.
- 5
Generate the bureau-ready file
Produce the fixed-width Metro 2 file with correct header, base segments, and trailer for each bureau's subscriber configuration. Run it once in sandbox/test mode to confirm structure before going live.
- 6
Deliver and schedule monthly reporting
Deliver to Equifax, Experian, TransUnion, and Innovis over automated SFTP, then schedule recurring monthly generation so each cycle's ledger flows through the same validated pipeline with a full audit trail.
Where your data lives
We never imply a one-click "live" furnishing button that does not exist. Most property platforms are reported via their standard CSV/SFTP export; "request-access" means we enable a per-account feed (and RentVine, Yardi, Rent Manager, and Entrata are common request-access setups). When in doubt, the generic CSV/SFTP path always works.
We ingest Buildium's rent roll and transaction/ledger exports as CSV; there is no self-serve furnishing connector, so data flows via the standard export.
We map AppFolio's tenant ledger and delinquency exports; reporting runs from the CSV export rather than a live API connector.
Yardi integrations are enabled per-account; depending on your Yardi configuration we ingest scheduled CSV/SFTP exports or a data feed we set up with your team.
RentVine publishes an integration guide; we enable a RentVine feed per-account and fall back to its ledger export where a direct feed is not provisioned.
We read DoorLoop's rent ledger and payment-history exports as CSV; furnishing runs from the export, not a live connector.
Rent Manager exposes an API and scheduled exports; we enable the appropriate feed per-account, defaulting to its CSV/SFTP export.
We ingest Propertyware's portfolio and ledger exports as CSV; reporting is driven by the export file.
Entrata data access is provisioned per-account; we set up a scheduled CSV/SFTP feed or use its resident-ledger export.
Any system that can export a resident ledger to CSV or drop a file on SFTP works; this is the universal fallback regardless of platform.
Rent Reporting Launch Checklist
Everything to settle before your first file goes live, from program policy and consent to the field-level data you need in the export.
- Decide positive-only vs full-file reporting
- Capture written resident opt-in / consent
- Add a furnishing disclosure to the lease or addendum
- Map each lease to the right tradeline structure
- Set the account type for a lease obligation
Property Management Export to Metro 2 Mapping Template
A starting map from the headers most PM ledger and rent-roll exports use to their Metro 2 / CRRG fields. Adjust to your software's exact column names; the importer auto-detects most of these.
| Your column | Metro 2 field |
|---|---|
| Resident First Name | Consumer First Name |
| Resident Last Name / Surname | Consumer Surname |
| Property / Unit Address | Consumer Address (current) |
| Lease ID / Account Number | Account Number |
| Account Type | Account Type |
| Co-signer / Guarantor | ECOA / Association Code |
Compliance you can stand behind
FCRA furnisher accuracy and integrity (15 U.S.C. 1681s-2)
As a data furnisher you must report accurate, complete information, investigate disputes, and correct or delete errors. Positive-only and full-file programs both require a documented, consistent policy and a working dispute path before you furnish.
Resident consent and disclosure
Report only residents who have opted in, disclose the furnishing in the lease or a signed addendum, and give a clear way to opt out or dispute. Consent is treated as a gating field, so a resident without a documented opt-in never appears in the file.
FCRA obsolescence and CDIA CRRG conformance
Delinquent rental records must age off per the FCRA obsolescence rule (records are omitted once past the reporting window, rather than reported with a deletion flag), and every file is validated against the current CDIA Credit Reporting Resource Guide.
FDCPA and state rent-reporting rules where applicable
If past-due rent is being collected, FDCPA and state-specific rules can apply, and some jurisdictions regulate rent reporting and opt-out rights directly. Confirm the rules for the states you operate in before enabling full-file reporting.
Frequently asked questions
What is the difference between RentBureau and full-file Metro 2 reporting?
Equifax's RentBureau is the rental-data pathway many programs use to get rent payment history into Equifax. Full-file Metro 2 reporting produces standard fixed-width tradeline records that can be furnished to Experian, TransUnion, and Innovis as well. Our pipeline generates validated Metro 2 files and delivers to each bureau's endpoint, so you can support the RentBureau pathway and the other bureaus from one workflow.
Should I report positive-only or full-file (including late payments)?
Positive-only reporting furnishes only on-time payments and is often used as a resident-benefit amenity. Full-file reporting also includes delinquencies, which carries more accuracy and fairness obligations under the FCRA. We help you pick one policy and apply it consistently across the whole portfolio rather than mixing approaches resident by resident.
Do residents have to opt in before I report their rent?
Treat consent as mandatory. Best practice is a documented opt-in plus a furnishing disclosure in the lease or a signed addendum, with a clear way to opt out. In our pipeline, consent is a gating field: any resident without a documented opt-in is held back and never appears in the generated file.
How are security deposits handled?
A security deposit is not a balance or an amount owed, so it is never furnished as one. If a resident's ledger only reflects a deposit, that does not by itself create a balance-bearing tradeline. Deposits are kept for reference, not reported as credit obligations.
How does a lease become a tradeline?
Typically one tradeline is created per financially responsible resident, with the lease start date as the date opened and the monthly rent as the scheduled payment. Co-signers and guarantors are handled with the correct ECOA association code rather than being reported as joint account holders by default. Per-bed student-housing leases can map one unit to multiple resident tradelines.
Which property management systems do you support?
Buildium, AppFolio, Yardi, RentVine, DoorLoop, Rent Manager, Propertyware, and Entrata are all common, plus a universal CSV/SFTP fallback that works with any system that can export a resident ledger. Most platforms are reported via their standard export; some (such as Yardi, RentVine, Rent Manager, and Entrata) are set up as a per-account feed on request.
What does the concierge first file include?
You send one resident-ledger export and we return a fully mapped, CRRG-validated first file plus a line-by-line review: which records passed, which we fixed and how, and which rows we held back (missing consent, deposit-only ledgers, obsolete delinquencies). The first file is produced in sandbox/test mode so you can confirm it before any live furnishing.
How often do files get sent to the bureaus after launch?
Rent reporting is generally monthly. After your first file passes, monthly generation, validation, and multi-bureau SFTP delivery run on the schedule you set, with a full audit trail of every cycle and dispute handling available for corrections.
Other solutions
Get a validated first rent-reporting file
Send us one ledger export from your property management software and we'll hand back a bureau-ready, CRRG-validated Metro 2 file with a line-by-line review of what we found, fixed, and held back.