Repayment movements

Each repayment movement has a provider event ID, received date, amount, loan account and matched application. Its state tells the operations analyst whether a provider movement is unmatched, matched or an exception. Position snapshots supply related account context when a movement needs investigation.

The provider event identity anchors each received movement. Loan Operations Analyst uses the loan account and application link to decide whether a movement can be matched. The state remains Unmatched while its application is uncertain; Exception calls for investigation. A dated provider position can help explain the account context without replacing the movement source.

• Keep event identity. Use the provider event ID to recognize a repeated movement.
• Check both links. Confirm the loan account and matched application refer to the same borrower case.
• Expose uncertainty. Keep an unsupported match in Unmatched or Exception.

Agree which provider event ID is authoritative and how the team handles a repeated feed item. Define the evidence needed to match a movement to an application. Make an exception visible when the account, amount or application attribution needs investigation; keep the original event identity in the record.

Agree which provider record settles a disputed event and who examines repeated event IDs. Decide what evidence is sufficient to associate a movement with an application. Compare the event date and received amount with the source before changing its state. Keep the original event available for the Auditor.

Receive a $410 provider movement for a known loan account. Find the account and application, inspect the event ID and received date, then mark the supported match. Feed the same event again and confirm it remains one movement. Send an ambiguous event to the exception list until its application association can be supported.

The analyst should show why the $410 movement belongs to its recorded account and application. If the provider repeats that event ID, it should be recognized as the same source event. For an ambiguous item, leave the case visible in Unmatched movements or Movement exceptions and record the source that still needs checking.

• Unmatched movements — Find events awaiting an application match.
• Movement exceptions — Inspect disputed events with account, date and amount.

See the related process for the case sequence and the data model for the record relationships. Use roles to rehearse access before the team begins.