Credit and loan intake

How do we stop re-keying loan application data into the loan system and the core?

Capture the application once, at whichever door it arrives, and let the data flow to the loan system without a person retyping it. Callvu prefills what the bank already knows, collects only what is missing, captures the consents the application needs, routes the approval, and writes the complete application to the loan system. The applicant answers once; nobody keys it twice. Live at Bank Leumi, where every loan application and servicing workflow was digitized within six months.

Live at Bank LeumiComplex: multi-party handoffsCallvu moves: prefill, classify, decide, write back

Talk to an expert Try it in the sandbox

Last updated November 6, 2026.

The problem today

The application is typed three times, and the third copy is the one the examiner sees.

Today, without Callvu

An applicant fills in a form online, or a banker takes the details on a call. Someone keys them into the loan origination system. Someone else keys the booked loan into the core. Each copy drifts from the one before: a transposed income figure, a missing middle name, an address that does not match the ID. The file is complete on the surface and wrong underneath.

The clocks run from the day the application is complete. Under Regulation B the bank owes a notice of action within 30 days of a completed application, and an adverse action notice has required content. When the consent form is on paper in one place and the credit report pull is logged in another, proving that the authorization came before the pull is a reconstruction, not a record.

Incomplete applications are the slowest kind. The missing pay stub is requested by phone, the borrower sends a photo to a personal inbox, and the loan officer forwards it. Nobody owns the chase, so nobody can say how long the file has been waiting.

How it runs

From the requestto the system of record.

An applicant starts online, on a call with the contact center, or with a banker in a branch. The same process runs from each door; the applicant is identified and the application opens prefilled.

Applicant: Answers only what the bank does not already know, uploads documents, and gives the consents the application needs.
Loan officer or banker: Starts or assists the application, sees the same prefilled form, and reviews before routing.
Underwriting: Receives a complete application with its documents and consents, decides, and records the decision.
Callvu: Prefills, classifies, chases what is missing, enforces consent before the credit pull, routes the approval and writes the application to the loan system.

Prefill
Callvu reads what the core and the CRM already hold about the applicant (identity, contact details, existing accounts) and prefills the application. The applicant confirms or corrects; they do not retype.
Classify
The request is classified by product and by what it will need: income verification, collateral, a co-applicant, a credit pull. The required documents and consents for that product are set from the bank's policy, not chosen by the banker.
Consent before the pull
The applicant's authorization for a consumer report, their E-SIGN consent to electronic disclosures and the privacy notice are captured on a process-controlled screen, timestamped, before the credit report is requested. A pull without a recorded authorization is blocked.
Chase and verify
Each missing item (a pay stub, an ID, a co-applicant's signature) is requested from the person who has it, by text or email, with a link to upload it. Each document is read and checked as it arrives. The file shows what is missing and for how long.
Decide
The complete application is routed to underwriting, and the approval steps that policy allows to be automated run without a person. A decision that needs a person goes to the right approver in the Decision Desk with only the allowed choices.
Write back
The complete application, its documents, consents and decision are written to the loan origination system. The data the applicant entered once is the data in the system of record.

Where it ends: A complete application is in the loan system with its documents, consents and decision, and the applicant has the notice the decision requires. Every step is in the Decision Trace and the Audit Trace.

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.

Regulations

US requirements shown. Bank Leumi runs this process under national rules outside the US; Callvu loads each market's rules as policies the same way.

Regulation B (ECOA, 12 CFR 1002.9): Notice of action taken within 30 days of receiving a completed application. For an incomplete application, either a notice of incompleteness naming the information needed and a reasonable deadline, or an adverse action notice. An adverse action notice states the action, the creditor's name and address, the ECOA notice, and either the specific reasons or the right to request them within 60 days.
Fair Credit Reporting Act (15 USC 1681b, 1681m): A consumer report may be obtained only with a permissible purpose, here the applicant's own application for credit, and the authorization must exist before the pull. When adverse action is based in whole or in part on a consumer report, the notice must name the consumer reporting agency, state that the agency did not make the decision, and give the right to a free copy within 60 days and the right to dispute. When a credit score was used, the score and its key factors are disclosed.
E-SIGN Act (15 USC 7001): Before required disclosures are delivered electronically, the applicant consents in a way that demonstrates they can access the electronic form, after being told the hardware and software requirements and how to withdraw consent.
Regulation B (12 CFR 1002.5) and Regulation P (GLBA privacy): Limits on what an application may ask (for example, marital status and protected characteristics, except as permitted), and the privacy notice owed when a customer relationship is established.

Company policies

The required documents and consents for each loan product are set by policy and applied by Callvu, not selected by the banker.
No consumer report is requested until the applicant's authorization is recorded with a timestamp.
Manual approval steps that policy allows to be automated run without a person; the rest route to a named approver.
The loan origination system is the system of record. Callvu writes to it; nobody re-keys.

Controls

Prefill from the core and the CRM, so the applicant confirms rather than retypes.
Data validation on every field at entry: formats, cross-field checks and matches against what the bank already holds.
Consent gate: authorization, E-SIGN consent and privacy notice captured and timestamped before the credit pull.
Document checks as each item arrives, with the missing-item list and its age visible on the file.
Approval routing by product and amount, with automated steps where policy allows and a Decision Desk step where a person must decide.
E-signature on the application and the disclosures, timestamped.

Clocks and deadlines

Notice of action (Reg B): 30 days from the completed application; Callvu dates the application as complete when the last required item is verified.
Notice of incompleteness (Reg B): Names the missing items and a reasonable deadline; the chase runs against that date.
Right to reasons and free report (Reg B and FCRA): 60 days from the adverse action notice; the notice content is produced from the decision record.

Documents and checks

Government ID and the identity verification result
Proof of income (pay stubs, tax returns or bank statements, as the product requires)
The applicant's authorization for a consumer report, timestamped before the pull
E-SIGN consent and the privacy notice acknowledgment
The signed application and, where applicable, the co-applicant's signature
The decision record and the notice of action or adverse action

In the Decision Trace

Why the application was classified as it was (product, required items, whether a credit pull applied).
That the authorization was recorded before the report was requested, with both timestamps.
Which approval steps ran automatically under which policy, and which went to a person.
The decision, the approver, and the notice it produced.

In the Audit Trace

Every door the application was touched from, and by whom.
Each field's source: prefilled from the core, entered by the applicant, or corrected by a banker.
Each document requested, received and checked, with dates, and the age of every gap.
The write to the loan origination system and what was written.

The handoff

Between the front doorand the back office.

The front door

Online, on a call, with a banker, or started by an AI agent over MCP: the same process, the same prefill, the same consents on a process-controlled screen. Identity, consent and signatures never happen inside a chat.

The back office

Underwriting receives a complete file, and the loan origination system receives the application once, from Callvu. The second and third keyings, and the errors they carried, do not exist.

The Decision Desk

An approval that policy reserves for a person (an amount over a limit, a policy exception, a judgment call on income) goes to the right approver in the Decision Desk, with the complete case and only the allowed choices.
The approver is nudged by email or text until they act, and the file shows how long it has waited.

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 digitized all loan application and servicing workflows within six months.

BNK-01 · Customer-attested · verified 2026-11-02

Bank Leumi cut data errors by 77%.

BNK-03 · 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 reached a 94% average completion rate.

BNK-16 · 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 the applicant have to use one channel?

No. The application can start online, on a call or with a banker, and can be picked up in a different channel than it started in. The data entered once stays with the file.

How is the consent for a credit pull enforced?

The authorization is captured on a process-controlled screen and timestamped. Callvu blocks the report request until it is recorded, and the Decision Trace shows both timestamps.

What if a document never arrives?

The file shows the missing item and its age, the request is repeated on a schedule, and the Reg B notice of incompleteness and its deadline are produced from the record. A file that stalls is visible, not forgotten.

Does Callvu make the credit decision?

No. Callvu runs the approval steps the bank's policy allows to be automated and routes the rest to a named approver. The decision and who made it are in the Audit Trace.

What does Callvu write to the loan origination system?

The complete application, its documents, consents, the decision and the approval history, once. The loan origination system stays the system of record.

Related processes

Personal and auto loan application to approval Loan approval routing Home equity line application Compared with the alternatives Try it in the sandbox All banking and credit unions 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.