Loan documents checked against the credit approval

How do we check drawn loan documents against the credit approval before they reach the lender and the borrower?

Check the documents the way a processor would, on every loan, before anyone signs. When documents are drawn, Callvu reads them and matches the rate, the payment, the dates, the collateral and the parties field by field against the approval record, and routes each mismatch to a processor with the two values side by side. Live at Bank Leumi, under national rules outside the US.

Live at Bank LeumiComplex: multi-party handoffsCallvu moves: chase and verify

Talk to an expert Try it in the sandbox

Last updated November 6, 2026.

The problem today

The note says one rate, the approval says another, and the borrower has already signed.

Today, without Callvu

Documents are drawn in the document preparation system from data someone keyed from the approval. A rate typed as a different figure, a maturity date a month off, a guarantor missing from the guaranty, a collateral description that does not match the appraisal: each one goes out to the lender, who may or may not read it, and to the borrower, who signs what is in front of them.

A document that does not match the approval is a loan the bank did not approve. For a consumer loan it is also a Truth in Lending disclosure that is inaccurate. For any loan it is a re-sign, a correction, and a file that will be found at the next review.

The check is well understood; the problem is that it is done by a processor reading two screens, on the loans there was time for.

How it runs

From the requestto the system of record.

The document preparation system produces the loan documents for a loan with a recorded approval. Callvu picks them up at that moment, before they are released to the lender or the borrower.

Doc prep: Draws the documents in the document preparation system; sees the validation result.
Processor: Resolves each mismatch Callvu routes, with the approval value and the document value side by side.
Lender: Receives documents that passed, or a corrected set, and is told when a mismatch changed something material.
Callvu: Reads the documents, matches each field against the approval, routes mismatches, and records the validation result on the loan.

Read the documents
Callvu reads the note, the security agreement, the guaranty, the disclosures and the other drawn documents, and extracts the fields the approval governs: rate and rate type, payment and schedule, origination, first payment and maturity dates, amount, collateral description, borrower, co-borrower and guarantor names, fees.
Match against the approval
Each extracted field is compared with the approval record in the loan system, by field: an exact match for amounts, rates, dates and names; a structured match for the collateral description against the approved collateral and the appraisal or title record.
Chase and verify
This is the chase and verify move. Each mismatch is routed to a processor with the approval value and the document value side by side, the document and page it came from, and the allowed resolutions: correct the document, correct the approval record under authority, or accept with an approver's sign-off. Nothing is released while a mismatch is open.
Record the result
A validation pass, or the resolved mismatches with who resolved them and how, is written to the loan in the loan system, and the documents are released to the lender and the borrower.

Where it ends: The documents that go to the borrower match the approval, field by field, and the validation result with each resolution is on the loan in the loan system. The Decision Trace shows every field compared; the Audit Trace shows every mismatch and who resolved it.

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.

Reg Z accuracy of closed-end disclosures (12 CFR 1026.17 and 1026.18, with the tolerances in 1026.18(d) and 1026.22): The Truth in Lending disclosures must reflect the terms of the legal obligation between the parties. A finance charge or APR outside the tolerance, or a payment schedule that does not match the note, is an inaccurate disclosure. Matching the disclosure to the approval and the note catches the error before consummation.
Safety and soundness: loan documentation (12 CFR part 364 appendix A, loan documentation standards): The interagency standards expect loan documentation that enables the bank to make an informed decision, identifies the purpose and source of repayment, and establishes and protects the bank's position in collateral. A guaranty missing a guarantor or a security agreement describing the wrong collateral fails that standard.
Flood insurance before closing (Regulation H, 12 CFR 208.25): Where the collateral is a building in a special flood hazard area, the flood determination and the borrower notice must be on file before closing; the validation confirms the collateral in the documents is the collateral the determination covers.

Company policies

No drawn documents are released to the lender or the borrower while a mismatch is open.
A mismatch is resolved by correcting the document, correcting the approval record under the approver's authority, or an approver's recorded acceptance; a processor cannot waive a mismatch alone.
The fields matched, and the tolerance for each, are set by the bank's loan policy and applied to every loan.
The loan system is the system of record for the approval and the validation result; the document preparation system is the source of the documents.

Controls

Document reading and field extraction on every drawn set, not a sample.
Field-by-field match against the approval record, with the tolerance the policy sets.
Collateral match against the approved collateral and the appraisal or title record.
Party match: borrowers, co-borrowers and guarantors as approved.
Hold on release while any mismatch is open.
Resolution limited to the allowed outcomes, with authority checks on changes to the approval.

Clocks and deadlines

Release hold: Documents wait until every mismatch is resolved; the processor is nudged and the lender sees the status.
Disclosure timing (Reg Z): The validated disclosures reach the borrower before consummation, so a correction never costs the borrower the waiting period.

Documents and checks

The drawn documents: note, security agreement, guaranty, disclosures, and the others the product requires
The approval record in the loan system
The appraisal or title record for the collateral match
The mismatch list with document, page, approval value and document value
The validation result with each resolution and who made it

In the Decision Trace

Each field compared, the approval value, the document value, and the result.
The tolerance applied where one applies.
Each mismatch's resolution, the person, and the authority used.
The release decision.

In the Audit Trace

When the documents were drawn and when they were read.
Each mismatch routed, to whom, and when it was resolved.
Any change to the approval record and the approver who authorized it.
The write of the validation result and the release to the lender and borrower.

The handoff

Between the front doorand the back office.

The front door

The front door is the document preparation system producing the documents. Nothing changes for doc prep; the check runs on what they draw.

The back office

The processor receives only the mismatches, each with the two values side by side, instead of two screens to read on every loan. The lender receives documents that match the approval.

The Decision Desk

A mismatch whose resolution changes the approval (a rate, an amount, a party) goes to the approver whose authority covers it, in the Decision Desk, with the two values and only the allowed outcomes.
The processor is nudged while documents are on hold, and the lender sees how long the release 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 cut data errors by 77%.

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

Bank Leumi digitized all loan application and servicing workflows within six months.

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

Bank Leumi reached a 94% average completion rate.

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

Questions

What buyers ask next,answered plainly.

Which fields are checked?

The ones the approval governs: rate and rate type, payment and schedule, dates, amount, collateral, parties and fees. The list and the tolerances are the bank's policy, applied to every loan.

Can a processor waive a mismatch?

No. A mismatch is resolved by correcting the document, correcting the approval under the approver's authority, or an approver's recorded acceptance. The resolution and the person are on the loan.

Does this replace the document preparation system?

No. Documents are still drawn there. Callvu reads what is drawn, checks it against the loan system, and holds the release until it matches.

What does the lender see?

Documents that passed, or a corrected set, and a note when a mismatch changed something material. They no longer proofread the note against the approval.

Related processes

Loan approval routing Loan completeness check before Processing Lender-placed insurance exceptions 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.