Repayment servicing

A repayment event has a provider event identifier, occurrence date, amount, loan account and match state. A matched receipt also points to its loan application. Reconciliation checks the receipt against a confirmed application for the same account. The amount and confirmed occurrence date must agree exactly. An amount that looks close or a date that falls on the next day still needs investigation.

Unmatched receipts remain in the servicing queue. A more serious discrepancy can be marked as an exception. This keeps the source event visible without assigning it to an unrelated loan just to clear a queue. Dated account figures and provider snapshot identifiers help the reviewer understand the surrounding balance, but the snapshot alone does not establish an exact repayment match.

• Provider receipt. The source event identifier and occurred date give each receipt its own identity across imports and reviews.
• Account context. The borrower-owned loan account connects the receipt to the provider and the relevant applications.
• Exception handling. A reviewer compares exact amounts and dates, then leaves a difference open with its source record intact.

Agree how provider receipt files or events arrive and who checks their source identifiers. A repeated event should refer to the existing receipt, not create a second match. Confirm the provider’s date convention and time zone before comparing events; the recorded occurrence date is the value used for the decision. Decide who investigates a missing application link, a different amount or an account mismatch, and when an exception is escalated.

Plan the account snapshot cycle as well. Each dated row has ledger and available figures with a provider snapshot identity. The servicing team should compare signed confirmed movements with those figures and explain any difference before reporting an account position. The Independent Credit Approver has a review role in reconciliation, while the Auditor needs a read-only view of the source and decision trail.

A provider sends a repayment event for an active loan account. The servicing reviewer checks the event identifier against earlier receipts, then compares its amount and occurrence date with a confirmed application connected to that same account. When both values match exactly, the receipt can be marked matched and linked to the instruction. Its source identity remains available for a later audit.

Now suppose the provider sends the same amount for a different date. The reviewer leaves the receipt unmatched or records an exception and examines the account snapshot and confirmation evidence. They do not substitute a nearby application or change a verified provider event to make the reconciliation pass. Once the cause is known, the team can resolve the source discrepancy with a traceable correction and recheck the operation receipt if an effect was involved.

• Repayment exceptions — Unmatched and exception provider receipts needing investigation.
• Matched repayments — Source events tied to a confirmed instruction and account.
• Active loan accounts — Provider and borrower context for each receipt.

Use repayment reconciliation for the operating sequence and reports for exception questions.