How does a payment mismatch get resolved at Aster Financial?

At Aster Financial, a reconciliation analyst opens the daily exception queue and finds item **REC-3306**: the loan repayment ledger shows a payment of 1,250.00 against **ACC-5521**, but the bank settlement file shows 1,205.00 for the same reference.

The analyst compares the two entries. The ledger line was keyed by the contact centre, and the bank figure came from the direct debit file. A note on **CASE-0412** shows the customer rang to confirm the amount. The analyst concludes the contact centre transposed two digits.

Policy allows a correction of this kind below a set tolerance without sign-off, provided the original entry is reversed rather than overwritten. The analyst posts a reversal and a corrected entry, links both to REC-3306, and closes the item with the reason code keying error.

The state change is that the ledger balance for ACC-5521 now matches the settlement file, and the item moves from open to resolved. Skipping the reversal would leave an audit trail with no explanation for the changed amount, and a later arrears notice could be calculated on the wrong balance.

**What it teaches:** a good record of this workflow includes the competing records, the supporting note, the policy that permits the fix and the exact correction steps. A model scored only on whether the balances match would miss the reversal requirement.