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
- Repayments and reconciliation
Repayments and reconciliation
Review provider repayment events beside account balance snapshots.
OverviewRepayment Exceptions×
Lending Platform · Repayments and reconciliation
New
Repayment Exceptions
Repayments
| Account | Provider event ID | Occurred at | Amount USD | State | Matched instruction | |
|---|---|---|---|---|---|---|
| LA-140 | PEI-876 | 05 Oct | 370 | Unmatched | LA-18222 | |
| LA-130 | PEI-346 | 13 Oct | 660 | Exception | LA-68776 | |
| LA-110 | PEI-838 | 04 Oct | 670 | Unmatched | LA-95808 | |
| LA-110 | PEI-839 | 23 Oct | 350 | Exception | LA-14794 | |
| LA-140 | PEI-683 | 25 Oct | 220 | Unmatched | LA-72300 |
6 of 6 records
PEI-876Repayments · RPY-86414
UnmatchedAccountLA-140
Occurred at05 Oct
Amount USD370
Matched instructionLA-18222
What you can do
Connect each repayment to an account
Repayment records hold the provider event identifier, event time, amount, matching state, loan account and matched application. The Credit Officer can use them to follow payments reported by the provider. An unmatched event needs a source check; a matched event names the application used for context. An exception signals follow-up when the event cannot be reconciled cleanly.
Loan account snapshots hold dated provider balances, including ledger and available amounts and a provider snapshot identifier. They provide a time series to inspect alongside repayment events and disbursement records. The Credit Officer should compare the right account and date, not treat a snapshot as an explanation of every movement by itself. The provider event and snapshot references let a reviewer return to the original source.
How the work is organized
- Event identity. Keep the provider repayment identifier and occurrence time together.
- Matching state. Distinguish unmatched, matched and exception work.
- Balance history. Use dated snapshots to check whether the account record aligns with provider balances.
What to agree during setup
Define how provider repayment events enter the app, who checks duplicates and how a team member handles a correction. Agree the matching basis for linking a repayment to an application. The application connection is useful context, while the loan account remains the direct financial account for the event. Set an escalation path for an exception that requires provider investigation.
Decide how often provider snapshots are recorded and how to compare their dates and currencies. The ledger and available amounts can differ, so the team should agree which figure answers each operational question. An Auditor should be able to trace a questioned amount to its provider event or snapshot identifier and the related application decision.
Check the handoff on an actual case
A provider reports a repayment against an active account. The Credit Officer checks the provider event identifier, amount and occurrence date, then identifies the loan account and related application. If the source agrees, they mark the event matched. If the account or amount cannot be reconciled, they keep the event in exception work and investigate the provider record. At the next balance check, they compare the dated account snapshot with the movement history. The snapshot remains a separate observation; it does not erase the earlier exception or change the original repayment event.
What your team sees
- Repayment Exceptions — Find unmatched and exceptional provider events.
- Account Snapshot History — Compare ledger and available balances over time.
- Active Loan Accounts — Open the borrower and provider account context.
Follow the work through
Follow repayment review and evidence and exceptions.
What it keeps track of
Data model- Repayments
- Provider repayment events received against a loan account, with matching state.
- Loan accounts
- Loan account identities with provider reference, currency, active state and borrower owner.
- Loan account snapshots
- Dated provider balance snapshots per loan account, used for servicing and reconciliation.
- Loan applications
- Loan applications moving through origination, underwriting, approval and disbursement.
- Disbursements
- Disbursement and account movement lines posted against an approved loan application and loan account.
Who uses it
Permissions- Credit Officer
- Reviews repayment events and account balances.
- Auditor
- Reads the provider and matching evidence.
- App Administrator
- Maintains organizational access to the accounts.
Set up Lending Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.