How to Configure and Map Collateral Management System® Integrations on Appraisal Scope® per UAD 3.6 Updates

To support the UAD 3.6 mandate, Appraisal Scope® integrates seamlessly with Cotality CMS. This integration ensures that new data-centric UAD fields are accurately mapped and that order activity in CMS is reflected in Appraisal Scope®.

The configuration for mapping CMS Jobtypes, Loan Types, Property Types, and Occupancy has been updated to align with the Modern/Legacy distinction.

1. Click the Settings tab on the main menu.

2. Choose Options from the menu tabs.

3. Select Integrations from the list on the left.

4. The section for CoreLogic CMS will appear on the right, click Configure  on Map CMS Service Type. This will open the Establish Mapping for CMS Service Type and Sub Loan Type to Appraisal Scope® JobType screen.

Modern Mapping Tab: CMS Service mapping features a new Modern tab for mapping UAD 3.6 fields (Order Product Type, Property Type, etc.) to the Appraisal Scope® JobType.

5. First select a CMS Service Type, choose an option from the dropdown menu, then select a CMS Sub Loan Type, then select your Appraisal Scope® JobType.

6. Click Add, your new JobType mapping will appear below.

7. Click Close to exit.

8. Mapping for Map CMS Sub Loan Types, Map CMS Property Types, Map CMS Loan Purpose (Intended Use), and Map CMS Occupancy Types includes both Modern and Legacy values for simplified mapping.

CMS Service Type:
The CMS Service Type mapping screen enforces rules based on whether a Service Type is Modern or Legacy. The modern Product Type banner is displayed below the CMS Service Type dropdown when a modern service is selected, then only Appraisal Scope® jobtypes related to the specific Product Type are displayed to map. The CMS Loan Type dropdown then contains only Modern Loan Types:

Mapping the CMS Loan Types, Property Types, Intended Use and Occupancy Types include both Modern and Legacy values for simplified mapping.

The CMS Loan Purpose (Intended Use) mapping screen now includes all legacy and modern values. To maintain data consistency and prevent manual overrides during validation, modern mappings are securely locked. Legacy mappings remain available for selection to support form-centric workflows during the transition period.

Service Type ID Visibility:

The CMS Service Type mapping configuration screen now includes an explicit Service Type ID column displayed across both the Legacy and Modern tabs . This ID provides administrators with exact visibility into incoming data strings, simplifying troubleshooting and mapping configurations between CMS and Appraisal Scope®.

Appraisal Scope® has implemented dedicated endpoints to process updates originating from CMS.
This includes ensuring that key UAD 3.6 fields below are displayed in the order form.

• Property Valuation Method

• Accessory Dwelling Unit Total Count

• Living Unit Excluding ADU Count, and

• PUD Indicator

The integration engine evaluates incoming payloads to ensure parent-child structural integrity. If a client mistakenly transmits a parent product type through CMS as a child order attached to an existing record, the system will reject the order creation request and note the following failure in the CMS Order Exception queue:

"The order cannot be created in the platform because a parent product type was submitted as a child order."

For modern orders originating via CMS API transmissions, the platform automatically extracts the PUD Indicator flag directly from the incoming XML order creation and update event payloads. The value maps directly to the Appraisal Scope® internal PUD Indicator field without requiring manual user intervention or visual reconciliation.