Connect Encompass to Proof – Proof Help Center
The document provides detailed guidance for organizations on setting up the Proof-Encompass integration for lenders, emphasizing collaboration between Encompass administrators and Proof Solutions Engineers, recommending use of a UAT instance for thorough testing (preferably by state and starting with top states), and outlining key configuration steps including providing Regression UID and Client IDs, obtaining API keys from ICE Mortgage Technology, and setting up API users to ensure a smooth onboarding and go-live process.
Audience: Organizations
Here's an overview of how to set up the Proof-Encompass integration for lenders, including best practices to make the experience as seamless and efficient as possible.
Recommendations
- Work with an Encompass Administrator for configuring the integration inside Encompass. This person should work closely with your Proof Solutions Engineer during onboarding.
- Use a UAT Encompass instance for testing before connecting your production instance to Proof. Testing eNotes in a UAT environment is strongly recommended.
- If you don't have a UAT instance, speak with your Proof Solutions Engineer to discuss workflow options for testing before sending live loans.
- Allocate resources to test the integration based on your desired go-live timeline. Breaking testing up by state is typically the most efficient approach. See "Encompass to Proof: Testing Tips" for guidance.
- To go live faster, start with your top states and get those live before moving on to less common states. This lets you send live transactions while continuing to test new states.
Your Proof Solutions Engineer will work with your team to configure your Encompass instance(s) for both Proof Testing (Fairfax) and Production accounts. Your team will need to complete the following onboarding steps.
Configuration in Encompass
- 1.Your Encompass administrator must provide your Proof Solutions Engineer with the Regression UID and Client IDs for your UAT and Production Encompass instances. Proof will then request your API keys from ICE Mortgage Technology (typically 3–5 business days).
- 2.Once ICE Mortgage Technology provisions your API keys, your Proof Solutions Engineer will help your Encompass admin set up the API user. See "Set up API users in Encompass." Notify your Proof Solutions Engineer when the API user is set up.
- 3.Once the connection between Proof and Encompass is successful, your Proof Solutions Engineer will provide your Encompass administrator with the CDO and Proof eClosing form to install. After logging in, confirm you have access to the Proof eClosing form.
Configuration in Proof
- 1.Proof will create a Fairfax (testing) and Production account and add any requested team members. Anyone testing the integration and closers who will use Proof should be added. Proof will also configure your billing method and states of operation.
- 2.Let Proof know how you'd like documents pushed back to Encompass.
- 3.For Hybrid transactions: if title agents need to view transactions in the Proof portal, they must be onboarded as members of the title agency in Proof. Otherwise, title agents can only view and print documents.
You're ready to start testing the Proof Encompass integration! See "Place an Order from Encompass to Proof" to get started.
Summary Checklist
- Involve your Encompass Administrator and use a UAT instance for testing before going live.
- Provide Proof with your Regression UID and Client IDs → set up API user → install CDO and eClosing form.
- Proof sets up your Fairfax and Production accounts — add team members and confirm document pushback options.
- Start testing with your top states first, then expand to other states.
Still unsure? Contact Proof Support for help.
Related
Set Up API Users in Encompass – Proof Help Center
The article guides Encompass administrators through creating an API user with specific permissions—including Read/Edit Loans, Edit Subordinate Loans, and Encompass LO Mobile Connect—to enable Proof's integration using provided API keys, and instructs notifying the Proof Solutions Engineer to complete the connection and receive necessary eClosing forms.
Encompass Integration Supported Features and Requirements
The Notarize with Proof Encompass integration supports hybrid, hybrid with eNote, and online closings via a custom form, requiring collaboration between Notarize with Proof and the lender to configure and test the integration in UAT and Production environments, adherence to specific validations such as properly formatted contact information, limited borrower and signer counts, unique signer emails, and use of original ICE Mortgage Technology documents ordered to the Encompass eFolder, with API keys provisioned by ICE Mortgage Transactions and thorough lender testing and training before going live.
Encompass Integration Overview for Lenders
The Encompass integration with Proof enables lenders to seamlessly automate loan processing and closing document management by converting Encompass loans into Proof transactions, allowing order placement and updates via a custom form within Encompass, automatically pulling borrower data and documents through ICE Mortgage Technology's APIs, and ensuring eSigned documents are pushed back into Encompass for centralized tracking across various closing types including hybrid and online closings.
Common Encompass Error Messages – Proof Help Center
The Proof Help Center provides lenders with a glossary of common Encompass error messages—such as missing or invalid borrower and contact information, missing closer contact, and account configuration issues—that prevent sending loans for online closings, along with specific instructions to identify and resolve each error to ensure successful closings through Notarize with Proof.
Complete a Hybrid with eNote Closing from Encompass – Proof Help Center
The Proof Help Center guide details the process for completing a hybrid loan closing with eNote from Encompass using eOriginal, highlighting current limitations (support only for eOriginal-generated eNotes, excluding DocMagic and Ginnie Mae notes), prerequisites such as successful onboarding and eVault configuration, and specific required Encompass fields (including loan details, property address, and ULDD data) that must be completed before placing an order through the Notarize with Proof eClosing form to generate and send the eNote for signing.
Complete an Online Closing from Encompass – Proof Help Center
The article explains that fully digital online closings using Encompass integrated with Notarize with Proof require specific prerequisites such as eOriginal eNotes and onboarded title agents, follow a defined workflow routing orders from lender to title to closing operations before reaching the signer, and highlights current limitations including unsupported DocMagic and Ginnie Mae notes.