Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
An aged unmatched bank credit is the single most reliable time-sink in an Indian enterprise finance function. A Rs 47,236 credit landing on the HDFC statement 45 days ago, still open, no counterparty in the narration, no candidate invoice on the AR ledger — the AR analyst has spent forty minutes chasing it every week since it landed, the finance manager has asked for a status update at every Friday standup, and the credit has now aged into the 60-day escalation bucket without resolution. The absence of a documented decision tree is what turns each such credit into a fresh forensic exercise rather than a routine seven-branch elimination — and the compounding effect across three or four such credits per month is what makes the bank window bleed into the TDS window and forces the finance manager's sign-off from Day 5 to Day 7 or Day 8.
Run a seven-branch elimination in the documented order of highest-probability-first, statute-anchored resolution per branch, and calendar-clocked escalation to writeoff at Tier 3. Branch 1 — TDS-net receipt back-solved against Section 194Q code 1031 at 0.1 per cent or Section 194O code 1011 at 1 per cent. Branch 2 — multi-invoice aggregation split against the AR open-invoice register with remittance advice as the tie-breaker. Branch 3 — platform aggregator batch line against the Razorpay, PayU, Cashfree, Amazon, Flipkart, or gateway settlement file. Branch 4 — refund from a vendor against a prior defective consignment, tracked through the AP debit note register. Branch 5 — settlement of a prior credit note under Section 34 CGST, tracked through the AR credit-note register. Branch 6 — intercompany or group-entity transfer misdirected, resolved through group treasury and potentially triggering Section 41 remission or cessation. Branch 7 — treasury sweep from an FCNR or foreign-currency account, requiring RBI FEMA reporting confirmation. Residual case — writeoff under Section 37 as an allowable business loss or Section 41 as deemed income for a related-party cessation, with Ind AS 8 change-in-estimate disclosure and a CARO 2020 audit working paper trail.
The seven-branch tree published as a one-page decision aid at the AR analyst's desk. The escalation ladder from the bank runbook — Tier 1 at 30 days, Tier 2 at 60, Tier 3 at 90 — applied per branch. A working paper template that captures the credit date, the credit amount, the bank account, the narration text, the branches attempted, the branches eliminated, the counterparties contacted, and the escalation dates. A monthly review by the finance manager of every credit still open past Tier 1, and a quarterly review by the controller of every credit closed under the Section 37 or Section 41 writeoff protocol. The RBI FEMA foreign inward remittance register for any branch involving foreign currency. The intercompany reconciliation report for any Branch 6 investigation.
Every unmatched bank credit at end-of-day carries a branch tag (or a working-paper note recording every branch eliminated), an owner, an age, and a next-escalation date. The seven-branch elimination completes on 80 to 90 per cent of credits within 72 hours. The residual 10 to 20 per cent runs through the escalation ladder and either resolves before Tier 3 or is written off with a defensible statutory anchor. The bank-window sign-off on Day 5 releases the TDS window on Day 6 without a queue of unclassified credits hanging over the tax analyst's handoff. The CARO 2020 working paper base is defended against a going-back audit sample by the documented decision-tree trail on every aged item.
It is 8pm on Day 5. I have been running the bank window since Monday morning. The finance manager wants sign-off tonight so the tax analyst can open the TDS window at 9am tomorrow. Every other credit on the HDFC statement has cleared — auto-match on Day 1, aggregation on Day 2, TDS-net on Day 3, platform settlements on Day 4. Every other credit except this one. A Rs 47,236 credit posted 45 days ago against the current account with a NEFT narration that reads “NEFT-INB-CITIN22XXXXXXXXX-SHREE.” No counterparty name I recognise. No candidate invoice on the accounts-receivable ledger within a rounding tolerance. No remittance advice in the email archive. No standing rule in the customer master that matches the pattern.
Every practitioner has lived this moment. The chase for the one credit that will not close. If I am honest, I have chased this credit for six hours across the last three weeks and I still do not know what it is. Tonight I need to close it or route it into an escalation bucket that the controller can defend against the auditor next quarter.
This is the seven-branch decision tree I run at the 8pm chase, in the order of highest-probability-first, so the average investigation closes fast and the residual case ends in a defensible writeoff rather than an indefinite carry-open. The tree sits inside the wider bank reconciliation runbook for Days 1 to 5 as the resolution protocol for the Bucket C unidentified-credit case, and it pairs bidirectionally with the invoice-to-bank reconciliation failure modes brief that catalogues the design-layer failures the tree is engineered to catch operationally.
Branch 1 — Is it a TDS-net receipt?
Ninety seconds. I divide Rs 47,236 by 0.999. The result is Rs 47,283.28, which rounds to a Rs 47,283 gross invoice. I query the AR ledger for any open invoice between Rs 47,280 and Rs 47,286. If a match returns, this credit is a Section 194Q deduction — the buyer withheld Rs 47 at 0.1 per cent as the TDS, deposited it against my PAN, and remitted Rs 47,236 to my bank. The tag goes on the invoice, the Rs 47 goes to the TDS receivable ledger pre-populated for the tax analyst on Day 6, the branch closes.
I also run the Section 194O check at the 1 per cent rate — divide Rs 47,236 by 0.99 and query the AR ledger for a Rs 47,713 open invoice on any e-commerce-operator counterparty. If either returns, the branch closes. Reference: Section 194Q code 1031 and Section 194O code 1011, both of which move to the Section 393 payment-code schedule from 1 April 2026 under the cross-era TDS reconciliation framework.
Tonight, neither back-solves to an open invoice. Branch 1 is eliminated.
Branch 2 — Is it a multi-invoice split?
I query the AR ledger for any customer whose open invoices sum to Rs 47,236 within a rounding tolerance. The subset-sum problem is not literally solvable in seconds against 500 open invoices, but the tightest version is — I filter on any customer whose open-invoice count is between 2 and 5, and whose invoice values are all under Rs 25,000. The Excel routine is a SUMPRODUCT against a candidate-flag column and it returns three candidate combinations in under a minute.
Tonight one candidate returns. A regional customer has three open invoices — Rs 18,240, Rs 12,996, and Rs 16,000 — summing to Rs 47,236. I chase the customer’s AP head by phone at 8:12pm. She confirms the wire, apologises for not sending the remittance advice, and forwards the payment schedule. The tag goes on all three invoices, the branch closes.
If the phone call had not confirmed, the credit would have entered Bucket A of the exception queue with the customer name flagged and a Tier 1 escalation date thirty days from the credit date. See the multi-invoice aggregation pattern for the standing structure.
For the walkthrough of the tree — assume the phone call did not confirm and Branch 2 is eliminated. The narration text does not match the customer’s usual wire structure. Move to Branch 3.
Branch 3 — Is it a platform aggregator batch line?
Every payment gateway posts a net settlement to the current account after deducting the Merchant Discount Rate at approximately 2 per cent plus GST on commission at 18 per cent, minus refunds and chargebacks initiated in the settlement window, minus any Section 194O deduction. The Rs 47,236 could be a Razorpay, PayU, Cashfree, BillDesk, or Instamojo net settlement against a specific closed-window gross transaction total.
I open every platform’s merchant dashboard for the credit date and search for a settlement value between Rs 47,200 and Rs 47,280. If Razorpay returns a net settlement of Rs 47,236 for a specific settlement ID, I download the settlement file, verify the decomposition — a Rs 49,236 gross total minus Rs 984 MDR at 2 per cent minus Rs 177 GST on MDR at 18 per cent minus Rs 839 in refunds gives Rs 47,236 net — book the commission to expense and the GST on commission to input tax credit under the general Section 16 ITC rules, and the branch closes. The Razorpay reconciliation library documents the structural pattern.
Tonight, no dashboard returns a match. Branch 3 is eliminated.
Branch 4 — Is it a refund from a vendor?
I query the AP ledger for any debit note issued against a vendor for Rs 47,236 in the six months prior to the credit date. A defective consignment refund, a rate-difference adjustment, a wrongly-billed freight charge, an excess-payment reversal — any of these arrives as a bank credit with the vendor as the counterparty rather than the customer.
Tonight the AP ledger shows a Rs 47,236 debit note issued against a raw-material vendor three months ago for a rejected consignment. The controller had chased the vendor twice and the refund was overdue. The vendor’s finance team has finally released the amount without sending a covering email. The credit goes against the AP debit note, the branch closes.
For the walkthrough — assume no debit note matches. Branch 4 is eliminated.
Branch 5 — Is it settlement of a prior credit note?
Under Section 34 CGST, a supplier issues a credit note against an earlier invoice for goods returned, rate reduction, or over-billing correction. The customer typically withholds the credit-note amount from a later invoice — but occasionally, a customer settles the credit-note position separately with a wire that arrives as an unmatched credit because there is no candidate invoice to attach it to.
I query the AR credit-note register for any credit note issued in the six months prior to the credit date for Rs 47,236. If a match returns, the credit is the customer’s settlement of the credit-note position. I clear the credit-note balance and the branch closes.
Tonight no credit-note match returns. Branch 5 is eliminated.
Branch 6 — Is it an intercompany transfer misdirected?
I query the group intercompany reconciliation report for any Rs 47,236 transfer initiated by another group entity in the week prior to the credit date. Group treasury teams occasionally credit the wrong entity when two group companies hold similar-named accounts at the same bank — the “Shree” prefix in the NEFT narration tonight is the group’s parent-entity name, which is a red flag.
I email the group treasury team at 8:34pm. Twenty minutes later, they confirm the credit was intended for a sister entity — the AP analyst at the parent entity had used the wrong beneficiary saved-payee list. The reversal is initiated on the following morning. The credit is booked as receivable-from-group-entity and cleared on the settlement date.
Where the group decides to leave the amount in the receiving entity rather than reverse it, the Section 41 remission or cessation framework applies — the amount ceases to be a payable in the sending entity and becomes deemed income under Section 41 in the receiving entity. This is a controller-level decision that goes on the quarterly audit-committee report.
For the walkthrough — assume group treasury confirms the credit was not intercompany. Branch 6 is eliminated.
Branch 7 — Is it a treasury sweep from an FCNR or foreign-currency account?
The last branch. A treasury sweep from an FCNR or EEFC foreign-currency account arrives as an INR credit at the bank’s card conversion rate on the sweep date, with no invoice reference. The RBI FEMA foreign inward remittance advice — the Foreign Inward Remittance Certificate — is the confirming document.
I query the treasury sweep register for any USD, EUR, GBP, or AED sweep initiated in the week prior. A USD 570 sweep at Rs 82.87 per USD on the credit date produces exactly Rs 47,235.90, rounded to Rs 47,236. The register confirms — the treasury team had swept USD 570 from the EEFC account to fund a domestic payment run. The credit is tagged against the treasury reference, the Ind AS 21 spot-rate variance is calculated against the invoice-date rate for the original inward remittance the sweep amount came from, and the branch closes.
The residual case — nothing resolves
If all seven branches eliminate, the credit enters the residual protocol. The controller carries the working paper through the three escalation tiers from the bank runbook — Tier 1 at 30 days is the standing bank-side chase for the counterparty behind the truncated NEFT or RTGS UTR; Tier 2 at 60 days is the finance manager’s suspense posting so the reconciliation does not carry open indefinitely; Tier 3 at 90 days is the controller’s writeoff proposal.
The writeoff itself is booked under Section 37 as an allowable business loss where the credit represents a genuine unidentifiable position taken after documented follow-up. Where the credit is traceable to a related-party or intercompany position that has ceased to be payable, Section 41 remission or cessation applies instead and the amount is recognised as deemed income. The classification decision — Section 37 versus Section 41 — is a controller call, and the working paper trail (branches attempted, counterparties contacted, escalation dates, correspondence archived) is what defends the classification against a going-back auditor sample under the wider CARO 2020 framework. The disclosure follows Ind AS 8 change-in-accounting-estimate treatment where the writeoff is based on new information not previously available, and prior-period error treatment where the writeoff represents the correction of a misapplied receipt.
Below Rs 10,000 the writeoff is materiality-immaterial and the controller signs off. Above Rs 10,000 the writeoff is co-signed by the CFO. Above Rs 1 lakh it enters the audit-committee report as a discrete line item.
The failure-mode counterpart
Every branch in this tree is the operational execution of a specific failure mode documented in the invoice-to-bank reconciliation failure modes brief. The design-layer brief identifies each failure, rates it on Severity, Occurrence, and Detection, and specifies the controls needed to bring the aggregate action-priority to acceptable. The seven-branch tree is one of those controls — specifically, the Detection control against the mode “aged unmatched credit misclassified against the wrong invoice or written off without documented follow-up.” The human errors detection envelope documents this as part of the Family 5 bounce-pair-and-unapplied-credit anchor — the class of reconciliation failure that most reliably survives a routine bank reconciliation and only surfaces at a much later audit sample.
When the 8pm chase outgrows itself
One credit a month is a normal residual for a mid-market enterprise. Three or more per month, sustained across a quarter, signals a structural cause — a stale counterparty master, a truncated narration pattern from a specific bank that the bank narration parser does not handle, a customer whose remittance advice has stopped arriving, or an aggregator platform whose settlement file has changed format.
Above five per month sustained, the seven-branch elimination becomes a full-time analyst activity and the exception queue starts absorbing reconciliation hours that should have moved into the Day 6 TDS window. This is the threshold where the manual runbook still works as a training discipline, but the continuous detection layer needs to move off the analyst’s spreadsheet — Terra Insight’s reconciliation software treats the residual queue as a first-class continuously-refreshed output with the branch elimination running against every unmatched credit at end-of-day rather than as an 8pm chase against one credit at a time, and the manual tree keeps its role as the discipline the system runs against rather than the process the analyst runs by hand.
Where this fits
- Reconciliation playbook — monthly close pillar
- Bank reconciliation runbook — Days 1 to 5
- Invoice-to-bank reconciliation failure modes — the design layer
- Human errors detection envelope — Family 5 anchor
- Bank statement narration patterns
- HDFC bank reconciliation
Related reading
- ICICI bank reconciliation
- TDS payment codes 1001 to 1092
- Form 168 — the new TDS statement
- Section 16(4) ITC time bar
- Reconciliation software for India — pillar
- GST reconciliation software
Frequently Asked Questions
Why start with the assumption that a Rs 47,236 credit is a TDS-net receipt?
Because it is the highest-probability branch and it has the cleanest arithmetic. A Section 194Q deduction at 0.1 per cent on a Rs 47,283 gross invoice produces a Rs 47 TDS and a Rs 47,236 net credit — the residual is a rounding artefact that shows up on any receipt from a customer whose ERP posts the invoice-net value after the deduction is applied. The check takes ninety seconds — divide the credit by 0.999 and see if the resulting gross number matches any open invoice on the AR ledger within a rounding tolerance. If it does, the fork closes on Branch 1 and the credit gets tagged against the invoice, the receivable is pre-populated in the TDS ledger, and the reconciliation moves on. If it does not, the branch has been eliminated and the tree moves to Branch 2. The order matters — starting with the highest-probability branch keeps the average investigation time lowest across the year.
What if the credit turns out to be an intercompany transfer that was misdirected?
Branch 6 fires when the transferring entity’s accounts payable analyst credited the wrong bank account on a group entity’s request — a common failure where two group entities have similar-named accounts at the same bank. The resolution is administrative: the intercompany reconciliation report identifies the correct receiving entity, the group treasury team initiates the reversal to the sending entity or the onward transfer to the correct entity, and the receiving entity books a receivable-from-group-entity entry that is cleared on the settlement date. Where the transfer stays in the receiving entity indefinitely because the group has decided to leave the amount in situ, the Section 41 remission or cessation framework becomes relevant — the amount ceases to be a payable in the transferring entity’s books and becomes deemed income under Section 41 in the receiving entity’s books. This branch typically resolves within one week if group treasury is engaged; the failure to engage group treasury is what turns an intercompany credit into an aged reconciliation item that only surfaces at year-end consolidation.
When does the residual branch — the credit that resolves to nothing — get written off?
Not before ninety days from the credit date. The controller carries the working paper through the three escalation tiers documented in the bank runbook — Tier 1 at 30 days is the analyst-level chase to the bank for the counterparty behind a truncated NEFT or RTGS UTR, Tier 2 at 60 days is the finance manager’s authorised suspense posting so the reconciliation does not carry open indefinitely, and Tier 3 at 90 days is the controller’s writeoff proposal. The writeoff itself is booked under Section 37 as an allowable business loss where the credit represents a genuine unidentifiable position taken after documented follow-up, provided the amount is not traceable to a related-party position that would trigger the Section 41 remission-or-cessation framework. Below Rs 10,000 the writeoff is typically materiality-immaterial and the controller signs off; above Rs 10,000 the writeoff is escalated to the CFO for co-sign; above Rs 1 lakh it enters the audit committee report as a discrete line item.
Does this decision tree apply to unmatched debits as well?
The seven-branch structure is receipts-specific because the branches follow the pattern of how funds arrive at an Indian enterprise bank account. Unmatched debits — a bank charge with GST that was not booked, a wire transfer that was initiated but never landed at the beneficiary, a NACH bounce reversal that never rolled back the original receipt — follow a different four-branch structure that is documented separately in the bank runbook Bucket D disputed debit protocol. The two decision trees share the calendar-based escalation ladder (Tier 1 at 30 days, Tier 2 at 60, Tier 3 at 90) but the specific branches differ. Do not attempt to apply the receipts tree to a debit or vice versa — the resulting misclassification wastes analyst hours and can produce a systematically wrong writeoff or reversal.
When does an 8pm chase against one Rs 47,236 credit signal a systemic problem?
One credit a month is normal for a mid-market enterprise with 200 to 500 active customers — it is the residual of an otherwise-clean auto-match and aggregation window. Three or more per month, sustained across a quarter, signals a structural cause — a stale counterparty master that the auto-match cannot resolve, a truncated narration pattern from a specific bank that the parser does not handle, a customer whose remittance advice has stopped arriving, or an aggregator platform whose settlement file is arriving in a changed format. The chase itself is not the problem; the volume of chases is. Above five per month sustained, the decision tree becomes a full-time analyst activity and the exception queue starts absorbing reconciliation hours that should have moved into the Day 6 TDS window or the Day 11 GSTR-2B window. This is the threshold where the manual runbook still works as a training discipline but the continuous detection layer needs to move to a system that handles the residual queue as a first-class continuously-refreshed output rather than as an 8pm chase against one credit at a time.
Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
- ▸ Section 194Q, Income-tax Act 1961 (Section 393 payment code 1031 from 1 April 2026) — TDS on purchase of goods. A buyer whose total sales, gross receipts, or turnover exceed Rs 10 crore in the immediately preceding financial year must deduct tax at 0.1 per cent on the value of purchase of goods from a resident seller where the aggregate value of purchases exceeds Rs 50 lakh in a financial year. The receivable-side receipt lands net of the 0.1 per cent deduction, and Branch 1 of this decision tree is the fork that back-computes the gross invoice value from the net credit — a Rs 47,236 credit at Section 194Q rates back-solves to a Rs 47,283 gross invoice with a Rs 47 TDS deduction posted against the seller's PAN and expected to flow into Form 168 in the next quarter.
- ▸ Section 194O, Income-tax Act 1961 (Section 393 payment code 1011 from 1 April 2026) — TDS on e-commerce operator payments. An e-commerce operator paying an e-commerce participant for the sale of goods or provision of services must deduct tax at 1 per cent of the gross amount of such sales or services or both at the time of credit to the participant or at the time of payment, whichever is earlier. Branch 3 of this decision tree is the fork against a Razorpay, PayU, Cashfree, Amazon, or Flipkart payout that lands as a net figure after commission at approximately 2 per cent, GST on commission at 18 per cent, and any Section 194O deduction is applied — and the settlement file per platform is what turns the unmatched bank credit into an itemised transaction ledger.
- ▸ Section 34, Central Goods and Services Tax Act 2017 — Credit Notes — Where a tax invoice has been issued for supply of any goods or services and the taxable value or tax charged in that tax invoice is found to exceed the taxable value or tax payable in respect of such supply, or where the goods supplied are returned by the recipient, the registered person, who has supplied such goods or services, may issue to the recipient a credit note. Branch 5 of this decision tree is the fork against a credit landing as the settlement of a prior credit note — the supplier issued a Rs 47,236 credit note the previous quarter, the customer withheld the amount from a later invoice, and the reconciling credit arrives with no invoice tag because it is settling the credit-note position rather than an open invoice.
- ▸ Section 37, Income-tax Act 1961 — Business Expenditure — Any expenditure, not being expenditure of the nature described in Sections 30 to 36 and not being capital expenditure or personal expenses of the assessee, laid out or expended wholly and exclusively for the purposes of the business or profession shall be allowed in computing the income chargeable under the head Profits and gains of business or profession. The residual writeoff branch of this decision tree — where every reconciliation branch has been exhausted and the credit cannot be identified against any counterparty — is booked as an allowable business loss under Section 37 when the writeoff represents a genuine irrecoverable position taken after documented follow-up, provided the write-off does not fall within Section 41's remission or cessation framework.
- ▸ Section 41, Income-tax Act 1961 — Remission or Cessation of Trading Liability — Where an allowance or deduction has been made in the assessment for any year in respect of loss, expenditure, or trading liability incurred by the assessee, and subsequently during any previous year the assessee has obtained any amount in respect of such loss or expenditure or some benefit in respect of such trading liability by way of remission or cessation thereof, the amount obtained or the value of the benefit accruing shall be deemed to be profits and gains of business or profession. Where the unreconciled credit is traceable to an intercompany or related-party position that has ceased to be payable by the group entity that originally received the payment, the Section 41 branch fires and the amount is recognised as deemed income rather than as an allowable writeoff under Section 37.
- ▸ Ind AS 8 — Accounting Policies, Changes in Accounting Estimates and Errors — The effect of a change in an accounting estimate shall be recognised prospectively by including it in profit or loss in the period of the change if the change affects that period only, or the period of the change and future periods if the change affects both. A material writeoff of an aged unreconciled bank credit falls within the change-in-estimate framework when the writeoff is based on new information not previously available and is not a correction of a prior-period error. Where the writeoff represents the correction of a prior-period misapplication of a receipt, the prior-period error framework applies and the correction is retrospective rather than prospective.
- ▸ Companies (Auditor's Report) Order 2020, Clause 3(xii) — The auditor is required to report on whether the company has defaulted in repayment of loans or other borrowings, and separately whether the company has been declared a wilful defaulter by any bank or financial institution. An unreconciled bank credit that has aged beyond ninety days without resolution and is written off without documented follow-up creates an audit observation risk under the wider CARO 2020 framework, and the working paper trail — the decision-tree branches attempted, the counterparties contacted, the escalation dates — is what defends the writeoff against a going-back auditor sample.