UAD1675
FATALOfficial message text · Appendix H-1: UAD Compliance Rules — URAR, v1.5
Indicate whether any vehicle storage has defects.
Fatal — a single unresolved Fatal makes the entire submission come back NOT SUCCESSFUL (UCDP Hard Stop 401).
What triggers UAD1675
The published rule logic, verbatim:
If CarStorageType <> "None" and VehicleStorageDefectsExistIndicator is not provided
- • Checked for the Subject property.
- • Bound to MISMO data point
VehicleStorageDefectsExistIndicatorat../VALUATION_ANALYSIS/PROPERTIES/PROPERTY/PROPERTY_DETAIL/
How to fix it
On the URAR, this lives at: Vehicle Storage → Apparent Defects, Damages, Deficiencies → {No Label}. Complete or correct that field in your form software, regenerate the package, and re-check before submission.
Because this is a Fatal edit, do not submit until it is resolved — one Fatal bounces the whole package.
UAD1675 is in UADCheck's reference library; automated coverage for it is on the roadmap. The inspection already runs the full GSE schema, the package-integrity layer, and every auto-checkable compliance rule — each report states exactly what was covered.
Begin inspection →Related messages
- UAD1664 WarningProvide the area of the 'Carport' or 'Garage'.…
- UAD1665 WarningProvide the attachment type for the 'Carport' or 'Garage'.…
- UAD1667 FatalThe type of vehicle storage must be included. Select 'None' if there i…
- UAD1668 FatalProvide a description when vehicle storage type = 'Other'.…
- UAD1669 WarningProvide the material used for the 'Driveway' or 'Shared Driveway'.…
- UAD1670 FatalProvide a description when street surface material = 'Other'.…
Source: Appendix H-1: UAD Compliance Rules — URAR, v1.5 (public GSE document). Verified against the published spreadsheet; not affiliated with Fannie Mae or Freddie Mac.