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.
- Credit Scoring Engine
- Features
- Provider evidence
Provider evidence
Keep supporting documents and provider events attached to the right case.
OverviewEvidence to verify×
Credit Scoring Engine · Provider evidence
New
Evidence to verify
Assessment evidence
| Application | Evidence type | Provider event ID | Received at | Verified | |
|---|---|---|---|---|---|
| APP-15565 | Statement | PEI-539 | 07 Oct | No | |
| APP-42626 | Confirmation | PEI-461 | 09 Oct | No | |
| APP-11668 | Settlement | PEI-414 | 10 Oct | No | |
| APP-83564 | Correction | PEI-980 | 03 Oct | No | |
| APP-12958 | Statement | PEI-406 | 03 Oct | No |
6 of 6 records
PEI-539Assessment evidence · AE-34469
StatementApplicationAPP-15565
Received at07 Oct
VerifiedNo
What you can do
Preserve the basis for confirmation
A case can carry a supporting attachment and separate provider evidence. Record attachments holds the file, title, upload time, uploader and visibility. Assessment evidence records statement, confirmation, settlement or correction events with a line number, revision, provider event reference, amount, receipt date and verification setting. Keeping those records with the application lets a reviewer compare an internal decision with what the provider actually reported.
Consider an authorized application that has a provider instruction reference. Operations Manager sees a confirmation event and records it against the same application. The provider event reference and received date help identify that event later. Credit Reviewer can compare the amount and evidence type with the case and its decision before the application is treated as confirmed. A correction event should remain visible beside the original event rather than erase it.
How the work is organized
- Attachments. record attachments keeps documents and their internal or shared visibility with the parent application.
- Provider events. assessment evidence keeps dated event details, evidence type and verification state.
- Case link. Applications ties the applicant, provider instruction reference and confirmation date to the evidence.
What to agree during setup
Decide which documents are internal and which may be shared. Assign a person to check each provider event and agree what constitutes verified evidence. Keep provider event references consistent so repeat notices can be compared. Define who records a correction and how it affects a pending or confirmed application. Establish how an auditor finds the underlying event for a decision, confirmation or repayment receipt.
A provider event is an observation to check, not a substitute for the reviewer’s decision. The team should also distinguish a statement from a confirmation or settlement notice. A statement may explain a balance while confirmation supports a specific provider effect. The evidence type and linked application make that distinction visible during follow-up.
Check the handoff on an actual case
Take a submitted application with an attachment. Record a provider confirmation event with its provider reference and receipt date. Compare the evidence amount and revision to the application and later repayment record. Mark the evidence verified only after the comparison. Add a correction event to the same case and check that both are still available to Auditor. Rehearse an event that references the wrong application and leave it unresolved until identified.
What your team sees
- Evidence to verify. Find provider events awaiting a check.
- Confirmed applications. Review cases whose provider confirmation is recorded.
- Decision history. Compare the human decision with the evidence trail.
Follow the work through
See provider follow-up and reconciliation.
What it keeps track of
Data model- Record attachments
- Supporting documents attached to an application.
- Assessment evidence
- Provider statements, confirmations, settlement notices and corrections for an application.
- Applications
- Credit applications moving through authorization, submission and confirmation.
- Credit decisions
- Independent reviewer decisions recorded against a frozen application revision.
- Repayments
- Confirmed repayment receipts with stable operation keys and actual effect references.
- People
- Preparers, approvers, auditors and administrators working in the organization.
Who uses it
Permissions- Operations Manager
- Attaches documents and records events.
- Credit Reviewer
- Checks decision and evidence consistency.
- Auditor
- Follows the preserved trail.
Set up Credit Scoring Engine your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.