Home lending application and servicing workflows
How does a bank run its home lending application and servicing workflows end to end under its own national lending rules, from the banker's screen to the bank's systems?
By configuring the national lending rules as policies and running every workflow on one layer. At Bank Leumi, home lending applications and servicing requests start with the borrower or the banker, run through document collection, approvals and signatures with the local rules enforced at each step, and end in the bank's own systems, with the whole set digitized within six months and dozens of processes added since. The pattern is the same for a US lender under TRID, Reg B and RESPA: the rules change, the process does not. Live at Bank Leumi, under national rules outside the US.
Live at Bank LeumiComplex: multi-party handoffsCallvu moves: prefill, chase and verify, decide, write back
Last updated November 7, 2026.
The problem today
Every home lending workflow is its own project, and the rules live in the heads of the people who run it.
A mortgage bank runs dozens of workflows: the application, the pre-approval, the property and income documents, the approval committee, the signing, the disbursement, and then the servicing requests (a payment change, a partial prepayment, a release, a refinancing). Each was built separately, each enforces the national rules the way its builder understood them, and each ends in the bank's systems by a different path.
The rules are national and change: disclosure content and timing, affordability tests, collateral and insurance requirements, data protection, the regulator's reporting. A bank that enforces them workflow by workflow re-implements them every time, and proves compliance by sampling.
The alternative is one layer where the rules are policies, applied to every workflow the same way, with a trace for every run.
How it runs
From the requestto the system of record.
A borrower starts an application or a servicing request online, in a branch with a banker, or on a call; or a back-office event (a maturity, a rate reset, a document expiry) starts a servicing workflow. The same layer runs all of them.
- Borrower
- Applies, provides documents, signs, and makes servicing requests on their own device.
- Banker
- Starts and assists on the same screens, and decides within authority in the Decision Desk.
- Back office
- Approves, disburses and services from the decided cases, with the rules already enforced.
- Callvu
- Runs each workflow in the five moves under the bank's policies, and writes to the bank's systems.
Prefill from the bank's systems
The borrower's identity, accounts, existing loans and prior applications are read from the core and the loan system, so the application or the request starts filled.
Classify under the policies
The product, the amount, the collateral and the borrower's situation classify the workflow and apply the national rules configured as policies: the disclosures and their timing, the affordability test, the collateral and insurance requirements, the data protection consents, the approval authority.
Chase and verify every party
Documents are requested from the borrower, the employer, the insurer, the valuer and the lawyer through links, read on arrival and checked against the policy; the file shows what is missing and for how long.
Decide
Automated steps run where the policy allows; approvals route to the banker, the credit committee or the back office in the Decision Desk with only the allowed outcomes; signatures are captured on the borrower's device.
Write back
The application, the decision, the signed documents and the servicing change are written to the bank's core and loan systems, and every run leaves a Decision Trace and an Audit Trace.
Where it ends: Every home lending workflow, from application to servicing, runs on one layer under the bank's national rules as policies and ends in the bank's own systems with a trace. At Bank Leumi this covered all loan application and servicing workflows within six months. The Decision Trace shows the policies applied to each run; the Audit Trace shows every step.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
Online, the branch, a call, or a back-office event; the borrower acts on their own device.
The back office
Approvals, disbursement and servicing run from decided cases with the rules enforced before they arrive.
The Decision Desk
- Every approval the policy reserves for a person (credit, committee, back office) runs in the Decision Desk with the case and only the allowed outcomes.
Proof
Live at Bank Leumi.Published results only.
Each result is a published claim, with its code on agents.callvu.com, where its status, source and last verified date are kept.
Bank Leumi runs its home lending (mortgage) workflows on Callvu, under national lending rules outside the US.
MTG-01 · Self-asserted · verified 2026-11-06
Bank Leumi digitized all loan application and servicing workflows within six months.
BNK-01 · Customer-attested · verified 2026-11-02
Bank Leumi makes loan decisions more than a week faster, because manual approval steps are automated in the workflow.
BNK-14 · Customer-attested · verified 2026-11-02
Bank Leumi saved more than $3M on transcription and paper storage.
BNK-02 · Customer-attested · verified 2026-11-02
Questions
What buyers ask next,answered plainly.
Does this apply to a US lender?
Yes. The mechanism is the same: the rules are policies applied to every workflow. At Bank Leumi they are the national rules of its market; for a US lender they are TRID, Reg B, RESPA and HMDA.
What did Bank Leumi digitize?
All loan application and servicing workflows within six months, with dozens more processes since, ending in the bank's own systems.
What happens when a rule changes?
The policy is changed once in Callvu Studio and applies to every workflow it governs from then on, with the trace showing which version ran.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.