Purchase contract and addenda
How do we collect the executed purchase contract and every addendum from the agents, and match the price, the dates and the concessions to the loan?
Ask both agents and read what they send. Callvu requests the fully executed contract and all addenda from the buyer's and the seller's agents through links, reads them on arrival (the parties, the property, the price, the earnest money, the financing and appraisal contingencies, the closing date, the seller concessions, the personal property, the signatures and dates), matches each term to the loan (the purchase price and loan amount, the closing date against the lock and the disclosure clocks, the concessions against the program's limit), flags a mismatch or a missing addendum, and writes the contract to the loan.
In scopeComplex: multi-party handoffsCallvu moves: chase and verify, classify, write back
Last updated November 7, 2026.
The problem today
The contract in the file is the first version, the price changed in an addendum, and the seller concession exceeds the limit.
The borrower uploads the contract they signed. An addendum changes the price and adds a seller credit. Another extends the closing date past the rate lock. The processor has the first version; the underwriter approves on it; the Closing Disclosure is wrong; the lock expires. The agents had every version.
The contract drives the loan: the price sets the loan-to-value with the appraisal; the closing date sets the lock and the disclosure timing; the seller concessions are capped by the program and affect the loan amount; the earnest money is an asset to verify; the contingencies tell underwriting what can still change.
The agents are parties to the loan for this document. Ask them, and read every page.
How it runs
From the requestto the system of record.
A purchase application names the property and the agents. Callvu opens the contract request to both agents and the borrower.
- Buyer's agent
- Provides the executed contract and every addendum through a link, and later versions as they are signed.
- Seller's agent
- Confirms the executed version and provides seller-side addenda through a link.
- Borrower
- Confirms the terms and provides the earnest money evidence.
- Processor
- Sees the contract's status and reviews only flagged mismatches.
- Callvu
- Requests, reads, matches, flags and writes the contract to the loan, and watches for later addenda.
Chase and verify the contract
Both agents receive links; the executed contract and all addenda are uploaded and read: the parties and the property against the application, every signature and date, the price, the earnest money and its holder, the contingencies and their dates, the closing date, the seller concessions and personal property, and any amendments. A missing signature or page is requested at once.
Classify and match
Each term is matched to the loan: the price and the loan amount for the loan-to-value, the closing date against the rate lock expiry and the Closing Disclosure timing, the seller concessions against the program's interested-party contribution limit, the earnest money against the assets, the financing contingency date against the approval timeline. A mismatch or a limit breach is flagged with the two values.
Decide
A matched contract clears the condition by rule. A concession over the limit, a closing date inside the disclosure period, or a price change without a loan change goes to the underwriter or the loan officer in the Decision Desk with the flag and only the allowed outcomes (restructure, re-disclose, request an addendum).
Write back and watch
The contract and addenda are filed to the loan in the LOS under their types, the loan terms are updated where a change was accepted, and the agents' links stay open so a later addendum is read and matched the day it is signed, feeding the changed-circumstance process.
Where it ends: The loan was underwritten on the executed contract with every addendum, each term matched and the mismatches decided, and a later change reaches the file the day it is signed. The Decision Trace shows each match; the Audit Trace shows every upload and decision.
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
Links to both agents and the borrower.
The back office
The processor and the underwriter work from a matched contract; the disclosure desk receives changes the day they are signed.
The Decision Desk
- A concession over the limit, a closing date inside the disclosure period, or a price change without a loan change goes to the underwriter or loan officer in the Decision Desk with the flag and only the allowed outcomes.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
Questions
What buyers ask next,answered plainly.
Why ask the agents instead of the borrower?
Because the agents hold every version and every addendum, and their links stay open so a later change reaches the file the day it is signed.
What is matched?
The price and loan amount, the closing date against the lock and disclosure clocks, the seller concessions against the program's limit, the earnest money against the assets, and the contingency dates.
What happens to a seller concession over the limit?
It is flagged with the limit and goes to the underwriter in the Decision Desk to restructure or request an addendum.
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.