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 accounts and reconciliation
Provider accounts and reconciliation
Compare provider account balances and movements with application records.
OverviewReconciliation exceptions×
Credit Scoring Engine · Provider accounts and reconciliation
New
Reconciliation exceptions
Reconciliation items
| Provider event ID | Account | Matched instruction | Occurred at | Amount USD | State | |
|---|---|---|---|---|---|---|
| PEI-477 | SM-1873 | APP-50060 | 23 Oct | 320 | Exception | |
| PEI-958 | SM-5585 | APP-24618 | 27 Oct | 700 | Exception | |
| PEI-416 | SM-7435 | APP-38617 | 14 Oct | 330 | Exception | |
| PEI-221 | SM-7653 | APP-57876 | 14 Oct | 950 | Exception | |
| PEI-285 | SM-7267 | APP-99115 | 17 Oct | 20 | Exception |
6 of 6 records
PEI-477Reconciliation items · RI-33338
ExceptionAccountSM-1873
Matched instructionAPP-50060
Occurred at23 Oct
Amount USD320
What you can do
Connect movements to the case
Provider account records identify the owner, provider, external account reference, currency and active setting. Dated snapshots hold ledger and available amounts with a provider snapshot reference. These records give Operations Manager a way to inspect provider account context while working on credit cases. They do not replace the application’s requested amount, a reviewer decision or provider confirmation evidence.
Reconciliation items records source-identified provider movements. Each item has an event reference, occurrence date, dollar amount, state, account link and matched application. A movement can be unmatched, matched or an exception. Those distinctions let the team review a provider event without forcing it into a confirmed case just because the amount looks similar.
How the work is organized
- Account. score models holds the provider account identifier and applicant owner.
- Snapshot. score results records a dated provider snapshot with ledger and available balances.
- Movement. reconciliation items ties a provider event to an account and application, with a match state.
What to agree during setup
Agree which provider account belongs to each applicant and how external account references are maintained. Decide how often balance snapshots are received and who checks their provider snapshot references. Use the provider event identifier as the starting point for a movement match. Set a clear owner for exceptions and preserve the movement when its case cannot be confidently identified.
A practical case is a provider movement arriving after an application was authorized. Operations Manager compares the event identifier, amount, account and linked instruction. If these agree with the application and recorded evidence, the movement can be marked matched. If the amount or account differs, leave it as an exception for Credit Reviewer to investigate. Auditor should be able to trace the decision and movement without relying on a balance snapshot alone.
Check the handoff on an actual case
Open an active provider account and its dated snapshot. Find a movement against the account, then compare its event reference, amount and matched application with the provider evidence for the case. Move a correctly linked item to matched state. Rehearse a duplicate event identifier and a movement with the wrong account. Confirm that both remain visible for investigation and that no application confirmation is inferred from the snapshot alone.
What your team sees
- Reconciliation exceptions. Investigate provider movements with a recorded mismatch.
- Unmatched movements. Find events awaiting a reliable application match.
- Active provider accounts. Look up the applicant’s external account context.
Follow the work through
See reconciliation and provider follow-up.
What it keeps track of
Data model- Score models
- Provider-held score models owned by an applicant.
- Score results
- Dated provider results recorded for a score model.
- Reconciliation items
- Source-identified provider movements matched against applications.
- Applications
- Credit applications moving through authorization, submission and confirmation.
- Assessment evidence
- Provider statements, confirmations, settlement notices and corrections for an application.
- Applicants
- Applicants eligible to raise and be assessed for credit applications.
Who uses it
Permissions- Operations Manager
- Records and matches provider events.
- Credit Reviewer
- Examines exceptions.
- Auditor
- Reads the account, movement and case trail.
Set up Credit Scoring Engine your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.