Direct answer
A received payment needs a clear connection to the obligation it covers. Keep that match visible so your team can explain the balance and review exceptions.
Connect the payment to its contract and installment
Use a reliable contract reference to identify the account. Then record which installment the payment covers.
Receiving money is one step in a repayment workflow. Your team also needs to know which obligation it pays. That connection helps explain what remains unpaid.
This guide assumes an operation that manages installment contracts. It describes design choices to settle before building or changing software. The delivered project example appears separately below.
Give each contract a unique reference. Carry that reference into payment records where possible. The contract identifies the account, while the schedule identifies its expected payments.
An allocation records which obligation a payment covers. Use the installment reference supplied with the payment when it is reliable. Document the matching rule for cases where that reference is absent. The software should follow an agreed rule rather than guess.
Keep uncertain matches visible
Keep an unidentified receipt in an unmatched state and assign it for review. Apply it to a contract only after confirming the match.
A missing reference should create a visible task. Preserve the receipt so the reviewer can inspect the evidence and identify the correct contract.
Record the reviewer and the outcome. A queue of unmatched receipts gives the team a clear place to work through exceptions.
Agree how partial, combined and excess payments work
Record the amount allocated to each installment. Keep any remaining payment amount or unpaid obligation visible.
The amount received may differ from the scheduled amount. Decide how your operation handles each case before automating allocation. Any treatment of overdue amounts must follow the agreed contract rules.
A payment covers part of an installment
Allocate the received amount and show the unpaid portion. Keep both values connected to the installment record.
A payment covers several installments
Create a separate allocation for each installment. The allocations and any unallocated remainder should account for the full receipt.
A payment exceeds the amount due
Show the excess for review. Apply the operation's agreed process for advance payments or refunds instead of silently choosing a treatment.
Prevent duplicate records and preserve corrections
Recognize repeated payment imports and keep a history when staff correct a match.
Use a source transaction identifier where one is available. Interpret it within its source account or system, since different sources may reuse identifiers. A repeated import should recognize the existing payment. Where no reliable identifier exists, flag possible duplicates for review.
Staff also need a controlled way to correct a wrong allocation. Preserve the original action and record the correction. Include who changed it, when, and why. The corrected account position should remain traceable through that history.
Make each balance explainable
A reviewer should be able to trace the current position through the contract, schedule, payments and confirmed allocations.
A balance is more useful when someone can explain how it changed. Keep the supporting records accessible from the account view.
A management overview should show expected payments, received amounts, unpaid balances and unmatched receipts. Let reviewers inspect the records behind each figure. Keep a receipt's arrival distinct from the decision about which obligation it covers.
Automate clear matches first
Start with reliable references and documented rules. Keep uncertain cases under human review.
Check ordinary payments and known exceptions before expanding automation. Include partial payments, missing references, duplicate imports and corrected allocations. Define the expected result for each case.
A useful first release follows one complete route from receipt to account position. It also gives the team a clear way to review exceptions and explain changes.
What our repayment project delivered
Recode Asia connected installment contracts, schedules, payments, allocations, balances, penalty state and audit history for a residential property company.
In the delivered operating foundation, operations links receipts to installments. The account position recalculates from recorded allocations, and the audit history records the actor, time and reason for changes.
The public case study describes this operating route. It does not establish that every exception-handling design discussed in this guide was delivered. Its reconstructed screens use demonstration data; customer records and private allocation rules remain confidential.
Portfolio monitoring, forecasting and stress testing are described as the next layer. They are separate from the delivered foundation.
Follow one receipt through your operation
Start with one payment and check whether your team can explain its complete journey.
Any answer that requires searching disconnected records reveals a useful place to investigate. Use that gap to define a small, concrete improvement.
Identify the contract
Which contract does this receipt relate to?
Find the installment
Which obligation does it cover?
Inspect the allocation
Where is the match and allocated amount recorded?
Explain the position
How did the allocation change the balance?
Follow the history
Who made the change, when, and why?