These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Lending Platform
- Features
- Application evidence
Application evidence
Keep documents, provider events and review evidence with the loan request.
OverviewUnverified Application Evidence×
Lending Platform · Application evidence
New
Unverified Application Evidence
Application evidence
| Parent | Line number | Evidence type | Provider event ID | Occurred at | Verified | |
|---|---|---|---|---|---|---|
| LA-69406 | 260 | Statement | PEI-142 | 14 Oct | No | |
| LA-92631 | 910 | Confirmation | PEI-709 | 17 Oct | No | |
| LA-76499 | 730 | Settlement | PEI-369 | 23 Oct | No | |
| LA-25417 | 530 | Correction | PEI-259 | 06 Oct | No | |
| LA-60736 | 530 | Statement | PEI-790 | 25 Oct | No |
6 of 6 records
PEI-142Application evidence · AE-30703
StatementParentLA-69406
Line number260
Occurred at14 Oct
VerifiedNo
What you can do
Keep each source close to the application
Application evidence records a provider event, event time, amount, evidence type and verification state against an application. Record attachments hold the uploaded file, title, upload time, uploader, visibility and evidence type. Together they let the Credit Officer and approver inspect the material behind a requested loan and its later provider outcome. A document and an event are different evidence: one may be a signed or supplied file, while the other describes an observed provider event.
The team should preserve the application link when a correction arrives. Evidence lines carry a line number and revision, so the reviewer can distinguish a later correction from the original event. The verified state should reflect an actual check of the provider reference, event and related application. A shared attachment has a different audience from an internal attachment; select its visibility deliberately.
How the work is organized
- Documents. Attach files to the application with an uploader and visibility.
- Provider events. Keep the event identifier, time and evidence type on a separate evidence line.
- Verification. Review the evidence before using it to explain a confirmed outcome.
What to agree during setup
Decide who uploads files, who checks their contents and when an attachment may be shared. Set a convention for evidence titles and provider event references so a team member can locate the original source quickly. Define the cases where a corrected event should add a new line rather than change a previous observation. The approver needs access to the evidence for the application under review, while an Auditor needs an enduring account of what supported the decision.
Agree which provider responses can support a confirmed application and which require follow-up. A provider confirmation, settlement or correction should be categorized with the corresponding evidence type. An unverified item remains work for the responsible Credit Officer. Keep the amount and event time visible beside the provider identifier so a repeated or mismatched response can be spotted.
Check the handoff on an actual case
A Credit Officer attaches the borrower’s supporting document and records the provider event for a submitted application. The Independent Credit Approver checks the application revision and attachment before deciding. Later, the provider issues a correction to the transaction. The officer adds a correction evidence line with its own event identifier and checks the amount and time against the provider record. The original line remains available. An Auditor can follow the decision, the original source and the correction without confusing a file upload with the provider’s actual result.
What your team sees
- Unverified Application Evidence — Follow evidence lines that still need a source check.
- Shared Application Attachments — Find documents available to the wider case team.
- Credit Decisions — Read the reason and reviewer beside the application evidence.
Follow the work through
What it keeps track of
Data model- Application evidence
- Evidence lines attached to a loan application: document type, provider reference, received date and verification state.
- Record attachments
- Supporting documents attached to a banking instruction.
- Loan applications
- Loan applications moving through origination, underwriting, approval and disbursement.
- Review decisions
- Reviewer decisions recorded with the application source revision, outcome and reason.
- Operation receipts
- Operation receipts with stable operation keys and references for recorded effects.
- Team members
- Preparers, approvers, auditors and administrators working in the organization.
Who uses it
Permissions- Credit Officer
- Attaches and checks material.
- Independent Credit Approver
- Examines evidence for a decision.
- Auditor
- Reads the retained source trail.
- App Administrator
- Maintains team access.
Set up Lending Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.