AI automation for Encompass lenders

Most Encompass shops don't want to rip out their LOS to get AI. They want the LOS they already run to do more. That's what Loandock does: an AI loan processor that works inside Encompass, so your system of record stays the single source of truth. We have been running live retail files in Encompass since 2025.

The integration, for your LOS admin

Forward this section to whoever owns your Encompass instance. Nothing migrates, nothing installs on your servers, and no Encompass configuration gets replaced: Loandock connects to the instance you already run and works inside it.

• Reads: the loan’s open underwriting conditions, the document list, and milestone state.
• Writes: documents into the file, attached to the specific condition they satisfy, and that condition’s status set to fulfilled.
• Never touches: pricing, credit decisions, AUS findings, your business rules, or your milestone triggers. Clearing conditions stays with your underwriter.
• Every read and write is logged with a timestamp and the document behind it, and the log exports in full for QC and audit.
• Borrower documents move over an encrypted connection and land in your instance, so Encompass remains the system of record.

Loandock marks the condition fulfilled in your LOS. Your underwriter reviews and clears it.

Loandock connects through ICE's Encompass Developer Connect API. Your Encompass super admin issues the API credentials and assigns the persona, which means you control the scope from the start and you can revoke it in one step. Nothing installs on your servers and no ICE certification is required for you to run it, because the access is yours, not ours.

Your admin will also want the auth method, seat and persona requirements, sandbox access, and the field-level list of everything read and written, including any custom fields. That spec sheet goes out the same day you ask for it, alongside the security and due-diligence packet, before anyone schedules a walkthrough.

It reads your condition list the way it is written

An approval does not arrive as one list. It arrives sorted, and the buckets are the whole shape of the work:

• Prior to docs: what has to be in the file before your closing docs are drawn.
• Prior to funding: what has to be satisfied before the wire goes out.
• At closing: what gets signed or collected at the table.

Loandock reads those buckets as your underwriter wrote them, in your own wording and your own templates, and works each open condition in its own bucket. There is no mapping exercise, no taxonomy to configure, and no request that your underwriters change how they write conditions.

What that looks like on a file

• Derives the exact documents each open condition needs, by income type, and sends one consolidated request.
• Works out who owes each condition and chases that party directly: the borrower, title, insurance, the HOA, an employer, or a payoff department.
• Texts and emails the responsible party until the documents land, on a cadence that respects quiet hours and opt-outs.
• Checks each document against what the condition requires: right type, right period, right person, legible.
• Sends a wrong document back with the reason instead of filing it to look complete.
• Files each accepted document to the condition it answers, so nobody has to sort a general bucket later.
• Takes the borrower’s explanation in their own words, formats it for signature, files the signed copy to the condition.
• Escalates anything uncertain to a person through the needs-you queue.
• Loandock marks conditions fulfilled; your underwriter clears them.

What Loandock doesn't do inside Encompass

• It doesn't clear conditions. Your underwriter does that, on the screen they already use.
• It doesn't underwrite or decision a loan.
• It doesn't file a document it couldn't check against the condition. Anything wrong goes back to the sender with the reason.
• It doesn't move your system of record. The file lives in Encompass, before and after.

When it is not sure, and when it is wrong

Nothing auto-clears. When a document is ambiguous, when the condition wording could mean two things, or when what came back does not match what the condition asked for, the item routes to your team in the needs-you queue and waits for a person. It does not get filed to look complete and it does not get marked fulfilled to clear a queue.

Every action carries a timestamp and the document behind it: what was requested, what came back, what was rejected and why, what was filed, and against which condition. The whole log exports for QC. That is also how a wrong fulfillment gets traced. You open the condition, you see the document that was filed against it and the moment it was filed, and you have the exact artifact your post-close reviewer needs to work backward from.

Security, in plain terms

• US-hosted. The workflow runs in the United States.
• Borrower documents and messages move over encrypted connections in transit and are encrypted at rest in the working store Loandock uses to process the file.
• Encompass stays the system of record, so the authoritative copy of every borrower file is yours, in your instance.
• Every read, write, message and check is logged, and that log exports in full for your QC and audit files.

The rest of what your CCO and IT lead will ask, and the due-diligence packet itself, are on the security page.

Why Encompass shops choose it

It plugs in without a rip and replace, and Encompass stays the system of record. It works your condition list in order, never changes a condition without a document behind it, and logs every action for audit. Your processors stop re-sending the same request, and your underwriter opens a file with the documentation already attached to the condition it answers. What that has done to live Encompass files, file by file, is on the results page.

What else Loandock connects to

Connected today: Encompass, Calyx Path, and Arive. nCino and Blend connect on request. Encompass is the proven production environment, with live retail files since 2025. Other LOS connections can be added the same way.

Adding one is a connector, not a migration. Nothing gets ripped out and your system of record does not move.

For the architects: each connection is a Model Context Protocol server. It changes nothing about what your admin does or what gets written, and it is here because a technical evaluator will look for it. The longer write-up on MCP and AI agents in lending goes into how the connection is built.

See a condition worked end to end

The condition demo on the homepage follows one condition from request to fulfilled. If you're still mapping the category, start with what an AI loan processor is. For the product overview, see the AI Processor page.