UAD1680
FATALOfficial message text · Appendix H-1: UAD Compliance Rules — URAR, v1.5
The type of functional issue must be included. Select 'None' if there are no functional issues.
Fatal — a single unresolved Fatal makes the entire submission come back NOT SUCCESSFUL (UCDP Hard Stop 401).
What triggers UAD1680
The published rule logic, verbatim:
If at least one instance of FUNCTIONAL_ISSUE is not provided or FunctionalIssueType is not provided in a given instance of FUNCTIONAL_ISSUE
- • Checked for the Subject property.
- • Bound to MISMO data point
FunctionalIssueTypeat../VALUATION_ANALYSIS/PROPERTIES/PROPERTY/FUNCTIONAL_ISSUES/FUNCTIONAL_ISSUE/
How to fix it
On the URAR, this lives at: Functional Obsolescence → Functional Issues. 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.
UAD1680 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.