BNTouch and Encompass: A Documented Integration Review

Written by Yuri Polukeev, CEO, BNTouch
Updated August 2026

Short answer: BNTouch’s public Encompass documentation describes a BNTouch-to-Encompass application handoff and Encompass-to-BNTouch loan updates. A team evaluating the workflow should confirm the exact fields, data direction, record matching, review points, and exception handling for its own environment before relying on a connection.

Mortgage loan officer and operations specialist discussing a system handoff in a bright office — Review the record context, owner, and exception path behind a documented system handoff.

What the public documentation describes

The companion BNTouch and Encompass documentation is the first-party reference for the public flow below. It is not a statement that every field, timing behavior, prerequisite, or workflow is the same in every account.

Direction	Documented flow	What to verify before use
BNTouch to Encompass	The public documentation describes an application handoff when a lead is ready to apply.	The exact record, field map, prerequisites, matching rule, and responsible owner.
Encompass to BNTouch	The public documentation describes loan updates returning to the CRM contact record.	The supported update set, direction for each field, and the way a mismatch is surfaced.
Encompass to BNTouch	The public documentation describes loan-stage changes flowing to the CRM pipeline.	Stage mapping, custom labels, human review, and the path for a missing update.
Encompass to BNTouch	The public documentation describes a funded event updating the CRM contact status.	The person who reviews the resulting relationship action and the account-specific rules that apply.

Run a five-record integration review

Use representative, non-sensitive records to inspect the workflow rather than assuming behavior from a connector name.

Start with a record expected to follow the standard application handoff.
Change one documented field and review the result in the receiving record.
Test a stage change and confirm who sees the next action.
Use a known duplicate or incomplete record and document the decision path.
Pause a case that needs human review and confirm the correction owner.

Keep the observed context, expected result, reviewer, and exception outcome with the test. This helps a team distinguish a usable workflow from a product description.

Questions for a configuration review

Which Encompass objects and fields are supported in the workflow being evaluated?
What is the source of truth for each decision-relevant field?
How does the team recognize and resolve a non-matching record?
Who owns a next action when a record’s status or assignment changes?
What implementation and support questions must be confirmed for the account?

Use the connection as operating context

Relationship activity and loan-operation decisions should remain clear. A loan officer needs the right context to choose a next step, while the organization remains responsible for records, approvals, messages, and its operating process. The related Encompass transition checklist provides a record-inventory and exception-review framework.

Review your Encompass workflow with BNTouch

Bring one representative record, one expected handoff, and one exception. Ask to see the field, owner, and validation questions that apply to your environment.

Schedule a BNTouch demo

Sources and scope

This page describes a documentation-review framework. It does not establish implementation timing, product scope, legal or compliance status, commercial terms, or the suitability of a workflow for a particular organization.