BRAVE Guide for JPMorgan Chase

JPMorgan Chase and the BRAVE Standard

JPMorgan Chase is the largest bank in the United States by total assets and one of the most significant players in commercial real estate lending. When JPMorgan evaluates BRAVE adoption, the bank's push toward automated appraisal ingestion — reducing turnaround times and improving data consistency across its massive loan portfolio — makes it a natural fit.

Appraisers preparing for potential JPMorgan BRAVE requirements should understand what comprehensive field coverage looks like. Getting ahead of these expectations will save revision cycles and accelerate the loan closing process when the time comes.

Anticipated BRAVE Field Requirements at JPMorgan

When JPMorgan evaluates BRAVE adoption, appraisers should expect the bank to require comprehensive coverage across the official BRAVE categories (6 categories, 99 fields total, created by Valcre as an open industry standard):

• Property (52 fields): Full address, Property.Type, Property.GrossBuildingArea, Property.NetRentableArea, Property.YearBuilt, Property.Latitude/Property.Longitude, and related fields. For multifamily properties, Property.UnitsCount is critical.
• Income (16 fields): Complete income reconstruction including Income.PotentialGrossIncome, Income.VacancyLoss, Income.EffectiveGrossIncome, Income.OperatingExpenses, and Income.NetOperatingIncome. A lender of this scale would likely flag submissions where expense ratios fall outside expected ranges.
• Value (24 fields): Value.ReconciledFinal is always essential. Value.IncomeApproach, Value.SalesApproach, and Value.CostApproach for each approach used. Prospective values (second value column) would be expected for any property not yet stabilized.
• Appraiser (4 fields): Appraiser.Name, Appraiser.LicenseState, Appraiser.LicenseNum, and Appraiser.LicenseExpiration.

Note: BRAVE does not include comparable sales fields. Comp data remains in the PDF report narrative.

For a complete breakdown of income fields, see our BRAVE Income & NOI Fields guide.

Expected Validation Requirements

When JPMorgan adopts BRAVE, the bank would likely run automated validation on every BRAVE file received. The system would check for:

1. Completeness: Are all required fields populated for the given property type?
2. Internal consistency: Does effective gross income minus operating expenses equal the reported NOI?
3. Range checks: Are cap rates, expense ratios, and values per square foot within expected ranges for the MSA?
4. Format compliance: Are numeric fields formatted correctly, with no text in numeric-only fields?

If any check fails, the file would be returned with a validation error report. The most frequent errors involve math inconsistencies in the income approach. Our Common BRAVE Validation Errors guide covers the top issues and how to fix them.

Preferred Submission Formats

A large lender like JPMorgan may accept BRAVE files in XLSX format. If your appraisal software exports CSV, you may need to convert it before submission.

The recommended workflow is to export from your appraisal software, validate the file using a tool like AppraisalAPI.com, and then upload the validated XLSX alongside your PDF report through the lender's vendor portal.

Tips for a Clean Submission

Double-check geographic fields. FIPS codes and census tracts are often auto-populated incorrectly by appraisal software. Verify these against Census Bureau data.

Reconcile your math. Before exporting, manually verify that PGI minus vacancy equals EGI, and EGI minus expenses equals NOI. Large bank validation systems catch even rounding discrepancies.

Use consistent property type codes. A bank like JPMorgan would map BRAVE property type codes to their internal classification system. If your code does not match the loan file, the submission would be flagged.

For more bank-specific guidance, explore our BRAVE guides for regional banks and community banks. For an overview of the standard itself, read What Is BRAVE? or learn how to create a BRAVE file step by step.