A payment collected by an agency and not reconciled to the correct loan account within 24 hours is a payment that is floating — the borrower has paid, their DPD continues to accumulate, the provision is not reduced, and the collection agent may receive a target credit for a payment that has not been posted. In a high-volume collections operation, floating payments are not rare exceptions — they are a daily operational challenge. The Collections Agency Monitor AI reconciles every agency-collected payment to the correct loan account within 4 hours of receipt, and flags every exception before end of business.
Why payment reconciliation fails in manual agency operations — and what it costs
Agency payment reconciliation fails at three points. First, the reference number mismatch: the borrower pays via UPI or NEFT with a reference field the agency has given them, but the institution's CBS uses a different account number format, and the payment arrives without a reference that the CBS can automatically match. Second, the partial payment complication: a borrower pays ₹8,000 against an EMI of ₹9,200 — the agency logs it as a partial payment, but the CBS requires a decision about how to apply the partial amount (to principal first, interest first, or pro-rata) before the account can be updated. Third, the timing gap: the agency collects a cash payment at 4 PM on Thursday but does not deposit it to the institution's account until Friday morning — in between, the borrower's DPD continues to accumulate, the field agent is called on Friday by a different agent who does not know the payment was made, and the borrower is contacted again unnecessarily.
The reconciliation process: from agency receipt to CBS posting
The Collections Agency Monitor AI receives payment data from agencies through a structured data feed — a daily file in a prescribed format, submitted by 9 PM on the day of collection. Each payment record in the file contains: the borrower's loan account number, the borrower's mobile number, the payment amount, the payment date and time, the payment mode (UPI, NEFT, cash, cheque), and the UTR number or receipt reference. The AI runs five reconciliation checks against each record before the payment is cleared for CBS posting.
Check 1 — Loan account existence: does the stated loan account number exist in the CBS? Check 2 — Borrower identity match: does the mobile number in the payment record match the mobile number registered against that loan account in the CBS? A mismatch may indicate the payment was applied to the wrong account. Check 3 — Payment mode corroboration: if the payment mode is UPI or NEFT, does the stated UTR number match a corresponding bank credit in the institution's settlement account? If the mode is cash or cheque, has the agency deposited the stated amount to the institution's designated collection account within the required timeframe? Check 4 — Amount validation: is the amount within the expected range for this account's current overdue balance? A payment significantly above the current EMI (e.g., ₹50,000 against an overdue of ₹9,200) requires a check — it may be a partial advance or it may be an error. Check 5 — Duplicate check: has this UTR number already been processed? A duplicate UTR submitted by two different agencies for the same payment indicates a double-counting attempt.
The daily reconciliation dashboard
The 5 exception types and how the AI handles each
Partial payments require an application rule — the AI routes to CBS team with a specific application recommendation
When an agency collects ₹5,000 against a ₹9,200 overdue, the CBS team must decide how to apply the partial amount. The Collections Agency Monitor AI flags the partial payment with the account's current status (interest accrued vs principal overdue split), the institution's standard partial payment application rule (typically: interest first, then principal), and a recommended application. The CBS team approves the application, not the AI — but the AI has done the preparation so the decision takes 2 minutes, not 20.
→ Route to CBS team with application recommendation · SLA: 4 hoursBefore posting a payment, the institution must confirm the payment was made by or for the correct borrower
An identity mismatch (mobile number differs) could mean: the borrower recently changed their registered mobile number; the payment was made by a family member using their own mobile; or the loan account number in the agency's record is incorrect. The AI flags the mismatch and routes to the CBS team for manual verification — calling the number in the payment record to confirm who made the payment and on whose behalf.
→ CBS team verification call required · Do not post until identity confirmedA duplicate UTR is either a system error or a double-counting attempt — both require investigation
If the same UTR is submitted twice by the same agency: likely a file processing error. The duplicate record is removed and the original is posted. If the same UTR is submitted by two different agencies: this means the same borrower has been assigned to two agencies simultaneously (a governance failure) or one agency is claiming credit for a payment the other collected. This is a financial controls breach — the institution immediately investigates account assignment and suspends the disputed payment until resolved.
→ Same agency: remove duplicate · Two agencies: account assignment investigation · Payment suspended until resolvedThe institution has received money it cannot identify — held in suspense account while investigation proceeds
The payment is credited to the institution's collection account (the bank confirms the UTR exists) but the reference in the payment record does not match any loan account in the CBS. The amount is held in a suspense account. The Collections Agency Monitor AI triggers the institution's collections operations team to contact the agency for the correct account details. Resolution SLA: 24 hours. If unresolved after 24 hours: borrower contact to confirm payment and loan account number.
→ Suspense account · Agency contact for correct details · 24-hour resolution SLACash collected by the agency is not the institution's money until it is deposited — lag creates financial exposure
When an agent collects cash from a borrower, it should be deposited to the institution's designated collection account within 24 hours. The Collections Agency Monitor AI tracks cash collection records and compares them against the institution's bank account credits. A cash collection record with no corresponding bank credit after 24 hours is flagged. After 48 hours without deposit: the agency receives a formal notice. After 72 hours: the account manager for the agency is called. Persistent cash lag patterns trigger a special audit of the agency's cash handling controls.
→ 24-hr: flag · 48-hr: formal notice to agency · 72-hr: account manager contactA payment posted to the wrong account or posted late is not a minor operational error — it is a credit quality event
A borrower whose payment is not posted to their account continues to accumulate DPD — potentially crossing the NPA threshold on a loan that was actually paid. A provisioning decision made on an account that shows outstanding payment when the payment was received but not yet posted understates the recovery. A SARFAESI notice sent to a borrower who paid the previous week creates a grievance, an Ombudsman complaint, and a relationship breakdown that cannot be easily repaired. The Collections Agency Monitor AI's same-day reconciliation is not an operational efficiency target — it is the mechanism that ensures the institution's financial records accurately reflect reality, its provisioning decisions are based on current data, and its borrowers are not penalised for payments that the institution failed to post.