Consumer Rental Metro 2 Reporting Guide
- Map a durable lease identifier; never group consumers solely by address.
- Report one Base account per lease and consenting co-tenants in J1 segments.
- Credit Limit is zero; High Credit and Scheduled Payment equal the monthly obligation.
- Use full consumer identity and address data, with either a valid SSN or complete DOB.
- Each bureau route selects its own rental reporting-program overlay.
Required source structure
Every imported or integrated record needs a durable lease identifier. A shared street address is not evidence of a shared lease, especially at multi-unit properties.
- Exactly one primary consumer per lease belongs in the Base segment.
- Other consenting obligated consumers on that lease belong in J1 segments.
- Separate leases keep separate account numbers even when the property address matches.
- Put unit and apartment identifiers in Address Line 2.
Monthly monetary fields
Rental reporting uses the monthly obligation, not the full lease-term total. BureauRelay checks these relationships before an enforced route can transmit.
| Field | Rental value |
|---|---|
| Credit Limit | 0 |
| High Credit / Original Loan Amount | Monthly rent |
| Scheduled Monthly Payment | Monthly rent |
| Actual Payment Amount | Authoritative payment for the period |
| Current Balance | 0 when current, except a supported partial-payment case |
Identity and relationship checks
Each consumer needs full name and address plus either a structurally valid SSN or complete date of birth. Business-only ECOA relationships cannot be silently recoded into consumer liability.
Bureau route overlays
Rental reporting programs are not identical across bureaus, so BureauRelay composes the shared rental validation profile with the selected bureau route before transmission. Keep the source mapping bureau-neutral, then review the route manifest for bureau-specific enrollment, consent, and suppression rules.
- Choose the intended bureau route before treating a sample file as ready for live transmission.
- Confirm landlord, property manager, and furnisher identifiers match the enrolled rental program.
- Review route-level suppressions for non-consenting tenants, incomplete identity data, and unsupported lease states.
Test checklist
Before enabling a rental route for transmission:
- Map lease_key and confirm every multi-tenant lease has one primary.
- Review every projected field in the composed-validation manifest.
- Resolve all blocking shared-rental and bureau-program findings.
- Generate only through the production API route so normalization, UTC handling, audit recording, and storage are preserved.