UAD1685

FATAL

Official message text · Appendix H-1: UAD Compliance Rules — URAR, v1.5

Provide at least one defect when the Appraiser identified a defect, damage or deficiency with one or more amenities. In the UAD XML, a minimum of one RELATIONSHIP must be included linking each DEFECT to the AMENITY that has the defect. For assistance with this message, contact the appraisal software vendor.

Fatal — a single unresolved Fatal makes the entire submission come back NOT SUCCESSFUL (UCDP Hard Stop 401).

What triggers UAD1685

The published rule logic, verbatim:

If @ValuationUseType = "SubjectProperty" and SubjectPropertyAmenitiesDefectsExistIndicator = "true", and there is no instance of RELATIONSHIP with @xlink:arcrole = "urn:fdc:mismo.org:2009:residential/DEFECT_ContainsDefectOf_AMENITY" linking DEFECT to the AMENITY

• Checked for the Subject property.
• Bound to MISMO data point @xlink:arcrole at ../SERVICE/RELATIONSHIPS/RELATIONSHIP/

How to fix it

This requirement applies to the XML data itself — the field is delivered in the submission file but is not printed on the form. Your form software populates it from the report data; correct the underlying entry, regenerate the package, and re-check.

Because this is a Fatal edit, do not submit until it is resolved — one Fatal bounces the whole package.

UAD1685 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

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.