UAD1752
FATALOfficial message text · Appendix H-1: UAD Compliance Rules — URAR, v1.5
Provide the party that initiated the request for reconsideration of value.
Fatal — a single unresolved Fatal makes the entire submission come back NOT SUCCESSFUL (UCDP Hard Stop 401).
What triggers UAD1752
The published rule logic, verbatim:
If ReconsiderationOfValueIndicator = "true" and ReconsiderationOfValueRequestedByType is not provided
- • Bound to MISMO data point
ReconsiderationOfValueRequestedByTypeat../VALUATION_ANALYSIS/VALUATION_REPORT/RECONSIDERATIONS_OF_VALUE/RECONSIDERATION_OF_VALUE/
How to fix it
On the URAR, this lives at: Revision History → Reconsideration of Value → Type. 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.
UAD1752 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
- UAD1751 FatalProvide the commentary on the outcome of the reconsideration of value.…
- UAD1753 FatalIndicate whether the reconsideration of value request resulted in a ch…
- UAD1754 FatalProvide the date the appraiser completed the reconsideration of value.…
- UAD1755 FatalThe reconsideration of value date must include year, month and day.…
- UAD1756 WarningThe reconsideration of value date must be on or after the 'Effective D…
- UAD1757 WarningThe reconsideration of value date cannot be more than a year old.…
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.