BNTouch and LendingPad: A Connection Review

Short answer: BNTouch publicly represents a connection with LendingPad. A team evaluating that connection should verify the exact environment, records, fields, direction, owners, review points, and exception handling it needs before relying on a workflow.

Start with the decision the record must support

A connection is useful when the right person can inspect the right record context and resolve an exception. Before evaluating a connector, identify the workflow that needs review, the record elements needed for the next action, the person who owns a correction, and the cases that should pause for human judgment.

Review area	Question to answer	Evidence to request
Environment	Which product version, account setup, and permissions are relevant to this workflow?	The current configuration context and named reviewer.
Record context	Which borrower, loan, relationship, or activity information needs to be visible?	A field map that identifies the source of truth and correction owner.
Direction	What should be sent, returned, or left in the source system for this specific workflow?	A representative case with expected values and review points.
Exceptions	What happens when a record is incomplete, duplicated, assigned differently, or needs a pause?	The escalation path and documented outcome from a test.

Use five representative cases

A standard record that should follow the expected path.
A record with an ownership change.
A record with missing or conflicting context.
A potential duplicate that requires a decision.
An exception that remains paused until a person reviews it.

For each case, retain the source record, expected outcome, actual result, reviewer, and correction route. That is a stronger readiness check than a generic feature walk-through.

Questions for a BNTouch review

Which systems and record types are in scope for the account?
Which fields are decision-relevant, and which system owns each one?
How should a team test matching, ownership changes, and incomplete records?
Where are exceptions reviewed and corrected?
What current product and implementation questions must be confirmed for this workflow?

Keep the source and next action clear

A system connection should support a clear operating process, not obscure it. The organization remains responsible for the data it relies on, the messages it approves, and the people who review each workflow. Use the BNTouch integrations directory for broader first-party connection context and the mortgage CRM evaluation methodology for a wider product review framework.

Review a representative LendingPad workflow with BNTouch

Bring one expected handoff and one exception. Ask to see the context, ownership, validation questions, and current scope that apply to your environment.

Schedule a BNTouch demo

Sources and scope

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