When the ARC collects from a charged-off account and remits the proceeds, the institution has three separate reconciliation obligations: apply the cash receipt to the correct charged-off loan account, reduce the SR balance outstanding against that account by the appropriate amount, and determine whether the recovery represents income (to the extent it exceeds the written-off carrying value) or a return of principal. Each of these is a different accounting treatment, and none of them happens automatically when the ARC sends a bank transfer and a remittance advice. The Post Charge-Off Recovery AI processes every ARC remittance, reconciles it to the account-level SR ledger, and generates the accounting entries before the CFO's office has seen the statement.
The three reconciliation obligations — and why they are routinely confused
The first obligation is cash matching: mapping each rupee received from the ARC to the specific loan account or accounts it represents. The ARC's remittance advice states the amounts and account references — but the account reference format the ARC uses (its internal reference) may differ from the institution's CBS loan account number, and a single ARC remittance may cover partial recoveries from multiple accounts in a single bank transfer. The Post Charge-Off Recovery AI maintains the mapping table between ARC references and CBS account numbers, and applies each remittance to the correct accounts.
The second obligation is SR ledger reconciliation: each loan account in an SR structure has an associated SR face value — the amount of Security Receipts issued against it. As cash is recovered by the ARC, the SR balance reduces. The institution must track the outstanding SR balance for each account, because: the SR carrying value on the balance sheet must be marked down as recoveries come in; the SR redemption triggers specific regulatory capital and provisioning releases; and when the SR is fully redeemed (or written off as unrecoverable), that triggers a P&L event. The Post Charge-Off Recovery AI maintains the SR sub-ledger account by account, update by update.
The third obligation is income recognition: under Ind AS 109 / RBI guidelines, recoveries from charged-off accounts that exceed the carrying value of the SR are recognised as income in the period received. Recoveries that do not exceed the carrying value reduce the SR balance without income recognition. The boundary between the two — the point at which a recovery switches from balance sheet reduction to income recognition — must be tracked at the account level, not the portfolio level.
The recovery ledger: post-charge-off proceeds tracking
The reconciliation workflow: from ARC remittance to accounting entry
ARC sends bank transfer and structured remittance advice — Recovery AI receives both
On the day of remittance, ARC-Alpha transfers ₹95,60,000 to the institution's designated collection account and sends a structured remittance advice file listing 22 accounts with the amount recovered from each. The Recovery AI receives the remittance file, verifies the total against the bank credit (amounts match within the same business day), and begins account-level reconciliation.
→ Same-day receipt · Bank credit vs remittance advice total: verified · Discrepancy triggers immediate ARC queryEach account in the remittance advice mapped to the CBS loan account number
The remittance advice uses ARC-Alpha's internal reference codes. The Recovery AI's reference mapping table converts each ARC code to the CBS loan account number and verifies the match. For accounts where the ARC's reference is ambiguous (multiple accounts with similar details), the Recovery AI flags for manual resolution — the operations team confirms the correct account before any booking occurs.
→ All 22 accounts matched · 0 ambiguous references in this batch · Reference mapping table updatedSR balance for each account reduced by the recovery amount — income recognition assessed
For each matched account, the Recovery AI reduces the SR carrying value by the recovery amount. It then checks whether the cumulative recovery for that account now exceeds the SR's carrying value — if it does, the excess is recognised as income. In this month's batch, no account has crossed the income recognition threshold — all 22 recoveries reduce the SR balance without triggering income recognition. The SR sub-ledger is updated account by account, with the opening balance, the recovery amount, and the closing balance recorded for each.
→ SR sub-ledger: 22 accounts updated · Income recognition: nil (no account exceeded carrying value) · Accounting entries generatedCBS updated for each recovered account — CIBIL update queued where applicable
The recovery amount for each account is posted to the CBS against the charged-off loan record. Where a full recovery results in the loan being settled (recovery equals or exceeds the SR face value), the account status is updated to "Settled post charge-off" and a CIBIL update is queued to reflect the settlement. The CIBIL update changes the account status from "Written Off" to "Settled" — an important improvement for the borrower's credit history that the institution is obligated to submit promptly.
→ CBS: 22 accounts updated · CIBIL queue: 3 accounts settled this month · Status update: Written Off → SettledRecovery report generated — month-to-date and cumulative recovery status for CFO dashboard
By end of business on the remittance day, the Recovery AI generates the management report: total recovery for the month (₹95.6L, Month 8), cumulative recovery to date (₹4.18 crore, 48% of SR issued), the 5 highest-recovery accounts this month, the 5 accounts with no recovery to date (flagged for ARC performance review), the SR balance outstanding by account, and the projected remaining recovery timeline based on ARC-Alpha's current recovery pace. This report is ready for the CFO before the month-end close, not after it.
→ Report: CFO dashboard · SR balance · Income recognition status · 36-month recovery projection updatedThe exception types that require manual resolution
The bank received a different amount than the remittance advice states
A difference between the bank credit and the remittance advice total — even by a few rupees — requires resolution before any booking occurs. The most common cause: banking fees or TDS deducted by the ARC's bank before transfer. The Recovery AI flags the amount and reason, and the operations team confirms with ARC-Alpha's finance team before posting.
→ All booking suspended · ARC finance team contact · Resolution before postingRecovery proceeds received but cannot be attributed to a specific loan account
Held in suspense account pending identification. The ARC is contacted for clarification. The most common cause: the ARC's remittance advice contains the borrower's name and an old loan account number that was subsequently renumbered in the CBS. The reference mapping table is updated once resolved.
→ Suspense account · ARC contact · 48-hour resolution SLAWhen cumulative recovery for an account exceeds the SR face value, the excess is income
The Recovery AI flags the account, calculates the income amount (recovery − SR carrying value), and generates the income recognition accounting entry separately from the SR reduction entry. This requires a specific journal entry that the accounting team reviews — income recognition from a charged-off account is a material P&L event that requires accurate treatment under Ind AS 109.
→ Income recognition entry generated · Accounting team review · P&L booking on approvalRare but requires immediate investigation — the ARC may have collected on an account that was regularised by the borrower directly
If a borrower regularised their account directly with the institution (paying the CBS amount) and also paid the ARC (who was not informed of the regularisation), the institution may have received a double payment. This requires immediate investigation: refund the ARC's collection to the borrower (or offset against future remittances), update the CBS, and review the ARC assignment management process.
→ Immediate investigation · Possible double payment · ARC + CBS + borrower coordinationEvery rupee recovered from a charged-off portfolio has a precise accounting destination — the Recovery AI finds it automatically
A charge-off does not extinguish the accounting obligation — it transforms it. The written-off balance does not disappear from the institution's records; it moves from the active loan book to the written-off ledger, and every subsequent recovery against it requires a precisely documented accounting treatment. An institution that books ARC remittances as a single "recovery income" line item has not accounted for the SR balance reduction, the income recognition threshold, or the CIBIL update obligation — it has simply made the problem less visible. The Post Charge-Off Recovery AI accounts for every recovery with the precision the written-off portfolio demands: account by account, SR by SR, threshold by threshold — so the CFO's view of the charged-off book is accurate, current, and audit-ready at all times.