Connect Encompass to Proof

The short answer: 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.
  • 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. See:
   • User Management
   • Fairfax vs. Production Accounts
2. Let Proof know how you'd like documents pushed back to Encompass. See Document pushback options.
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.

Updated May 19, 2026 16:30