Overview
This article shows you how to configure integration settings, workflows, and mapping for key Appraisal Scope® integrations, with 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.
Mercury Network® Integration
1. Mapping Screen Updates
All integration mapping screens (CMS, Mercury) have been updated:
Modern Mapping Tab: Mercury mapping features a new Modern tab for mapping UAD 3.6 fields (Order Product Type, Property Type, etc.) to the Appraisal Scope® JobType.
2. Modern JobType Mapping Requirements
The Mercury mapping screen features a new Modern tab for mapping UAD 3.6 fields (Order Product Type, Property Type, etc.) to the Appraisal Scope® JobType.
The Modern tab enforces a multi-field mapping requirement for all UAD 3.6 orders.
Click the Settings tab on the main menu.
Choose Options from the menu tabs below.
Select Integrations from the list on the left.
The section for Mercury Network will appear on the right, click Configure on Map Mercury Products. This will open the Establish Mapping for Mercury Product to Appraisal Scope® JobType screen.
Notice you now have two tabs Moderns and Legacy
To route incoming orders correctly, choose the Modern tab, you must map the following 5 fields.
Mercury Order Product Type
Mercury Property Type
Mercury Property Valuation Method Type
Mercury Mortgage Type
Rent Schedule Indicator
Click Add, your new JobType mapping will appear below.
Click Close to exit.
3. Automatic Handling for Modern Orders
For Modern orders, mapping for Loan, Property, and Occupancy Types is handled automatically by the system.
These mappings are displayed in the UI with a lock icon to prevent manual deletion.
Tip: Valuation Modernization features cannot be enabled if legacy Jobtype mapping is still in use for Mercury Network® mapping.
4. SSRs to Mercury Network®
Appraisal Scope® can send the SSR PDFs via the integration automatically. If manual submission is required, users can manually upload the SSRs and enter the Sequence # and Document ID.
Note: Mercury Network® integration requires OAuth 2.0 authentication.
5. ADU Data Handling
If no data is provided for the ADU Total field from Mercury Network, Appraisal Scope® will reflect the field data as "N/A" or remain empty.
Tip: Loan Number Validation Guardrails To prevent automated submission errors, the Mercury Network integration enforces strict cross-referencing on subsequent child orders. If an incoming child order payload matches an existing parent record but contains a mismatching loan number string, the platform rejects the request. The UI logs a specific failure reason within the Mercury Failure Orders queue requiring the client to update the loan number within the Mercury Network platform to match the parent URAR before resubmitting.
Note: Mercury Network integration requires OAuth 2.0 authentication.
Outcome
After you complete these configuration steps, you will have configured integration settings for Mercury Network®, 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.