--- title: "Collateral Management System® Integration with Appraisal Scope® per UAD 3.6 Updates" slug: "how-to-configure-and-map-cms-integrations-in-appraisal-scope-per-uad-36-updates-1" tags: ["Appraisal Scope"] updated: 2026-09-14T22:11:08Z published: 2026-09-14T22:11:08Z canonical: "docs.cotality.com/how-to-configure-and-map-cms-integrations-in-appraisal-scope-per-uad-36-updates-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.cotality.com/llms.txt > Use this file to discover all available pages before exploring further. # Collateral Management System® Integration with Appraisal Scope® per UAD 3.6 Updates ## Overview This article shows you how to configure integration settings, workflows, and mapping for key Appraisal Scope® integrations, including Cotality Collateral Management System® (CMS) and Mercury Network®. You can align integration mapping with the latest UAD 3.6 mandate, ensure accurate data transfer between systems, and efficiently manage order updates to support your appraisal operations. --- ## Collateral Management System® Integration ### 1. CMS Mapping Configuration Changes 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®. [Embedded content](https://cotality.storylane.io/demo/cgh1dglxvbix?embed=inline) 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. ![](https://cdn.document360.io/d7730790-9b0e-4a1e-800e-a32628b13559/Images/Documentation/image-2HGFAF7R.png?sv=2026-02-06&spr=https&st=2026-11-01T13%3A32%3A05Z&se=2026-11-01T14%3A32%3A05Z&sr=c&sp=r&sig=HZvjckqyapyhNnJciHRI2tlkWluW8MWNZ3iMYd7ybU4%3D) 1. 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.** 2. Click **Add,** your new JobType mapping will appear below. 3. Click **Close** to exit. 4. 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:** ![](https://cdn.document360.io/d7730790-9b0e-4a1e-800e-a32628b13559/Images/Documentation/image-U4S1ZBT4.png?sv=2026-02-06&spr=https&st=2026-11-01T13%3A32%3A05Z&se=2026-11-01T14%3A32%3A05Z&sr=c&sp=r&sig=HZvjckqyapyhNnJciHRI2tlkWluW8MWNZ3iMYd7ybU4%3D) Mapping the **CMS Loan Types,** **Property Types**, **Intended Use** and **Occupancy Types** include both **Modern and Legacy** values for simplified mapping. ![](https://cdn.document360.io/d7730790-9b0e-4a1e-800e-a32628b13559/Images/Documentation/image-RZJIR6BD.png?sv=2026-02-06&spr=https&st=2026-11-01T13%3A32%3A05Z&se=2026-11-01T14%3A32%3A05Z&sr=c&sp=r&sig=HZvjckqyapyhNnJciHRI2tlkWluW8MWNZ3iMYd7ybU4%3D) 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. ![](https://cdn.document360.io/d7730790-9b0e-4a1e-800e-a32628b13559/Images/Documentation/image-GWZ3QK42.png?sv=2026-02-06&spr=https&st=2026-11-01T13%3A32%3A05Z&se=2026-11-01T14%3A32%3A05Z&sr=c&sp=r&sig=HZvjckqyapyhNnJciHRI2tlkWluW8MWNZ3iMYd7ybU4%3D) **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®. ![](https://cdn.document360.io/d7730790-9b0e-4a1e-800e-a32628b13559/Images/Documentation/image-NNIQQ09M.png?sv=2026-02-06&spr=https&st=2026-11-01T13%3A32%3A05Z&se=2026-11-01T14%3A32%3A05Z&sr=c&sp=r&sig=HZvjckqyapyhNnJciHRI2tlkWluW8MWNZ3iMYd7ybU4%3D) ### 2. Order Form Updates from CMS [Embedded content](https://cotality.storylane.io/demo/rlbs5jq0zcf3?embed=inline) 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** ### 3. Structural Child Order Rejections 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."*** ### 4. Automatic PUD Indicator Extraction 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. --- ## Outcome After you complete these configuration steps, you will have configured integration settings for Collateral Management System®, mapped Modern and Legacy Jobtypes, ensured compliance with UAD 3.6 requirements, and enabled accurate, automated data exchange between Appraisal Scope®® and your integrated platforms. ---