Preapproval with credit authorization
How do we issue mortgage preapprovals with the credit authorization captured first, the documents checked for completeness and the decision recorded?
Treat the preapproval as a decision with evidence. Callvu prefills the borrower, captures the credit pull authorization and the consents on a secure screen before the report is requested, collects the income and asset documents through links and checks them as they arrive, runs the completeness check, routes the preapproval decision to the underwriter or the automated path the policy allows, records the decision with its conditions and expiry, and issues the preapproval letter from the record. 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
The preapproval letter was issued on a pay stub nobody read, and the credit was pulled on a verbal yes.
A buyer needs a preapproval letter for an offer this weekend. The loan officer pulls credit on a verbal authorization, glances at a pay stub, and issues the letter. The authorization is not on file. The income was wrong. The loan is declined in underwriting after the contract is signed, and the borrower, the agents and the seller all blame the lender.
FCRA requires a permissible purpose and, in practice, the borrower's authorization before the pull; the lender's policy requires documents reviewed before a preapproval is issued; and the letter's conditions and expiry are what protect the lender when the file changes. A preapproval done well is a small underwriting decision with a record.
The speed the market demands is possible when the documents arrive by link and the check runs on arrival.
How it runs
From the requestto the system of record.
A borrower asks for a preapproval online, in the app, or with a loan officer. Callvu identifies the borrower and opens the preapproval with the data from any prequalification.
- Borrower
- Authorizes the credit pull, provides income and asset documents, and receives the letter with its conditions.
- Loan officer
- Assists, sees the file fill, and issues the letter from the recorded decision.
- Underwriter
- Decides preapprovals the policy reserves in the Decision Desk.
- Callvu
- Prefills, captures consents before the pull, chases and checks documents, runs completeness, routes the decision, records and issues.
Prefill and consent
The borrower's data is prefilled from the core, the CRM and any prequalification. The credit pull authorization, the E-SIGN consent and the privacy notice are captured on a secure screen with timestamps before the report is requested; a pull without a recorded authorization is blocked.
Chase and verify documents
Pay stubs, W-2s or tax returns, and asset statements are requested through links and read on arrival: the employer and pay period against the stated income, the account balances against the stated assets, large deposits flagged. The file shows what is missing.
Completeness and decision
The completeness check runs against the lender's preapproval checklist. A file inside the automated path (credit score, debt-to-income and documentation within policy) is preapproved by rule; others go to the underwriter in the Decision Desk with the file and only the allowed outcomes: preapprove with conditions, preapprove for a lower amount, or decline with reasons.
Write back and issue
The decision, its conditions (property, appraisal, no change in income or credit), its maximum amount and its expiry date are written to the LOS, and the preapproval letter is issued from the record, with the borrower told what the conditions mean.
Where it ends: The preapproval rests on a recorded authorization, documents that were read, and a decision with conditions and an expiry in the LOS, and the letter matches the record. The Decision Trace shows the consent timing, the checks and the decision; the Audit Trace shows every document and 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 app, or a loan officer; documents and consents on the borrower's phone.
The back office
The underwriter decides only the reserved files; the letter is issued from the LOS record.
The Decision Desk
- A file outside the automated path goes to the underwriter in the Decision Desk with the documents 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 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 cut data errors by 77%.
BNK-03 · Customer-attested · verified 2026-11-02
Questions
What buyers ask next,answered plainly.
When is credit pulled?
Only after the borrower's authorization is recorded on a secure screen with a timestamp. A pull without it is blocked.
What makes the letter reliable?
It is issued from a recorded decision based on documents that were read and checked, with conditions and an expiry the borrower is told about.
Who decides?
The automated path where the file is inside policy; otherwise the underwriter in the Decision Desk.
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.