Run a loan application completeness check before underwriting
The agent checks each application against your checklist of documents and fields, spots figures that do not agree between forms and asks a person to approve the request for anything missing.
Works with
- Custom REST
- Loan origination system · via Custom REST
and any system with an API via Custom REST
What is a loan application completeness check?
The procedure
A completeness check makes sure an application has each document and field your checklist requires before an underwriter opens it. Processors also look for figures that disagree between forms, such as revenue on the application and in the financial statements. Your team then asks the applicant for whatever is missing.
What the agent does
Reads the application fields from your loan origination system
Lists the documents in the application folder in Google Drive
Matches each document and field to the checklist for that product
Drafts the request for anything missing
What your team decides
Approving each request before your team sends it
Which figure is correct when two documents disagree
Exceptions to the checklist
Changes to the request wording
Example runs for loan processors, underwriters and lending operations
Completeness Agent
Checks each application against your checklist before underwriting.
- API
- +1
Trigger: Inbound webhook · application submitted
From a procedure Completeness · v1.2
Lena
Check the Halden Trading application is complete.
Completeness Agent
- Pulled the application fields from the loan origination system through Custom REST
Listed the documents in the application folder
- Matched each document and field to your checklist
- Nothing is missing
checklist.missing.size() == 0
Complete. Each required document and field is present. The application moved to the underwriting queue with the checklist result attached.
4 steps · 0 reviews
Completeness Agent
Checks each application against your checklist before underwriting.
- API
- +1
Trigger: Inbound webhook · application submitted
From a procedure Completeness · v1.2
Marcus
Check the Harbor Lane application is complete.
Completeness Agent
- Pulled the application fields through Custom REST
Listed the documents in the application folder
- Two required documents are missing from the checklist
checklist.missing.size() > 0 - Drafted the request listing both documents
- Asked a person to approve the request before it is sent Waiting for a reviewerPriya: approved, your team sends it
Request approved. Priya approved the request for the two documents and handed it to your team to send. The application stays in the incomplete queue until they arrive.
5 steps · 1 review
Completeness Agent
Checks each application against your checklist before underwriting.
- API
- +1
Trigger: Inbound webhook · application submitted
From a procedure Completeness · v1.2
Tom
Check the Ostrava Metals application is complete.
Completeness Agent
- Pulled the application fields through Custom REST
Read the financial statements in the application folder
- The revenue on the form differs from the statements
form.revenue != statements.revenue - Paused for a person to choose between the two figures Waiting for a reviewerDiego: ask the applicant which figure is correct
Query raised. Diego decided the applicant should confirm the figure, and your team sends the query. Both numbers and the source documents are attached.
4 steps · 1 review
Setting up the Completeness Agent
Connect your systems
Read the application folder in Google Drive, read fields from your loan origination system through Custom REST, and update the queue through the same connection.


- Custom REST
- Loan origination system · via Custom REST
Write the rules
Your checklist is a set of CEL conditions for each product, and the agent checks each application against it.
checklist.missing.size() > 0Request documentsform.revenue != statements.revenueAsk a personchecklist.missing.size() == 0Send to underwritingAdd reviewers where the procedure says
A person approves the request before your team sends it to the applicant, and the agent shows exactly what is missing.
Review requested: Harbor Lane application
- Reason
- Two required documents missing
- Rule
- checklist.missing.size() > 0
- Procedure
- Completeness · v1.2
Send requestEdit request
Start it from the event
A submitted application starts the check by webhook, and each uploaded document starts another. A daily schedule lists applications that are still incomplete.
- Inbound webhook · application submitted
- Daily at 06:00 · incomplete applications
- Inbound webhook · document uploaded
Version and evaluate
When the checklist changes, test the new version on a complete file, a file with two documents missing and one where figures disagree. It publishes only if all three pass.
Completeness · v1.2Published
12/12 scenarios passed
Completeness · v1.2 Superseded
Completeness · v1.1 Superseded
Share with the team
Loan processors approve requests and settle figure queries, underwriters pick up files once they are complete, and lending operations author the checklist. Auditors read each check.
Admin
Author
Reviewer
Auditor
Questions about loan application completeness checks
Does the agent contact applicants?
No. It drafts the request, a person approves it, and your team sends it. The application stays in the incomplete queue until the documents arrive.
Can each loan product have its own checklist?
Yes. Each product has its own conditions in the procedure, and you change them by publishing a new version.
Does it check figures, or only that documents exist?
Both. It checks documents and fields against the checklist, and compares figures such as revenue between the form and the statements.
Controls your auditors will ask about
These controls apply to each agent you build. Sample data
Admin
Author
Reviewer
Auditor
Role-based access
Admin, Author, Reviewer and Auditor roles, scoped to each workspace.
- 41
7c2e… - 42
a91f… ← 7c2e - 43
03d8… ← a91f
Hash-chained audit log
Each entry carries the hash of the one before it. Verifying the log recomputes the chain and flags entries that no longer match.
- 41
- v1.1v1.2v1.3Published
Versioned specs
Each run records the exact version it followed; old versions stay readable.
- vault/sumsub/key
Secrets in a vault
Steps point to a vault path, and the key stays in the vault.
- Signed delivery accepted
- Unsigned delivery rejected
Signed webhook triggers
Unsigned or stale deliveries are rejected before a run starts.
- SandboxLive
Sandbox before live
New versions run on test data first. Going live is a separate step.
Related use cases
-
Credit file checkCompare the application with the credit file, apply your flags and route differences to an underwriter.
-
Vendor due diligenceCheck each new vendor's papers, screen the company and its owners and flag gaps for a person.
-
Complaints triageCategorize each complaint on arrival, apply your response timelines and route sensitive cases to a person.
Run this procedure as an agent
Book a demo with your own version of this procedure, and we'll show it running with each step logged.
Book a demo