1. Micro-finance System
  2. Features
  3. Repayment and evidence review
Feature · Repayment and evidence review

Repayment and evidence review

Investigate repayment events against loan accounts and dated provider positions.

OverviewUnmatched Repayments
Micro-finance System · Repayment and evidence review

Unmatched Repayments

Repayments

New
Provider event IDReceived atReceived USDStateLoan accountMatched loan application
PEI-99302 Oct190UnmatchedLA-130LA-69561
PEI-85704 Oct60ExceptionLA-110LA-82007
PEI-81201 Oct130UnmatchedLA-110LA-99746
PEI-90602 Oct160ExceptionLA-140LA-49079
PEI-55710 Oct10UnmatchedLA-120LA-99167
6 of 6 records
PEI-993Repayments · RPY-62847
Unmatched
Received at02 Oct
Received USD190
Loan accountLA-130
Matched loan applicationLA-69561
Example screen with sample data

What you can do

Examine the event and account together

A repayment event carries the provider’s event identity, received date, amount and loan account. Its state can be unmatched, matched or an exception. Staff should compare the event with the account and the originating application before linking it to an application. A similar amount on another account is not the same event. The Auditor needs to see the provider identity and date behind a match.

Repayment schedules hold dated provider positions for an account, including ledger and available amounts and the snapshot identity. These positions help staff check whether recorded movements agree with what the provider reported. Disbursements hold signed direction through debit or credit values. Operation receipts give a separate trail for attempted actions and their actual effects, including an operation key, expected revision and result state.

How the work is organized

  • Repayment triage. Review unmatched and exception events against their loan account and provider identity.
  • Position check. Compare dated provider snapshots with confirmed account movements.
  • Operation verification. Inspect the receipt’s effect references before accepting a completed result.

What to agree during setup

Agree which provider event date is used to match repayments, how corrections arrive and who may resolve an exception. Decide how a provider snapshot is imported and how a revised snapshot is distinguished from the earlier one. Staff need a consistent rule for comparing USD movement amounts with the ledger position, especially when the account’s currency differs. Define who may mark an operation for review and who can investigate its failure reason.

A repeat request with the same operation key should refer to the original effect. If the receipt claims completion but the linked effect is absent, investigate the discrepancy; do not create a second external instruction to make the receipt look complete. Retain the original provider event and position while correcting a local association. This lets the team explain why a repayment remained unmatched or became an exception.

Check the handoff on an actual case

A repayment arrives for a loan account with a familiar amount. The Credit Officer compares its provider event identity and received date with the application and the dated account position. The amount matches, but the relevant date differs, so the repayment stays unmatched or becomes an exception. The Auditor can inspect that decision and the original event. When a corrected provider event arrives, the team reviews the new evidence and records the appropriate association without erasing the first event or silently changing a confirmed application.

What your team sees

  • Unmatched Repayments — Events requiring an account and application evidence check.
  • Open Operation Receipts — Pending, failed or review-needed effects with their failure reasons.

Follow the work through

What it keeps track of

Data model
Repayments
Provider repayment events recorded against a loan account, matched to the originating loan application.
Repayment schedules
Dated provider positions for a loan account, used to reconcile recorded movements.
Loan accounts
Loan accounts opened from approved applications, with their provider identity and status.
Loan applications
Loan applications moving through authorization, submission and confirmation.
Disbursements
Individual amounts moved against a loan application and its loan account.
Operation receipts
Idempotent operation receipts with stable operation keys and actual effect references.
Application evidence
Provider evidence supporting a loan application revision, with validity and verification.

Who uses it

Permissions
Credit Officer
Investigates event and account references.
Auditor
Examines the retained provider and operation evidence.
Independent Credit Approver
Reads relevant decisions.
App Administrator
Maintains organization access.

Set up Micro-finance System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started