Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A credit lands on the bank statement with an odd non-round amount, a truncated narration, no counterparty name the ledger recognises, and no candidate invoice on the accounts-receivable ledger within any rounding tolerance the analyst is willing to accept. The finance manager wants an answer at Friday standup. The controller wants the reconciliation signed off by Day 5 so the tax analyst can open the TDS window on Day 6. The absence of a documented walk-through of the common causes turns each such credit into a fresh forensic exercise rather than a routine elimination, and three or four of them a month is what makes a mid-market close bleed from Day 5 into Day 7 or Day 8.
The unmatched credit is almost always one of seven things — a TDS-net customer receipt back-solved against Section 194Q at 0.1 per cent or Section 194O at 1 per cent; a multi-invoice aggregation the customer paid as a single wire without sending remittance advice; a payment aggregator net settlement after MDR at approximately 2 per cent, GST on commission at 18 per cent, and refunds; a vendor refund against a prior debit note for a defective consignment; a customer settlement of a prior credit note issued under Section 34 CGST; an intercompany transfer misdirected between similar-named group entities; or a treasury sweep from an FCNR or EEFC foreign-currency account with a FIRC as the confirming document. Each cause has a specific ledger to check and a specific arithmetic to run. The walk-through takes ten to fifteen minutes per credit rather than the six-hour chase the same credit generates when the analyst has no protocol.
A one-page seven-cause reference at the accounts-receivable analyst's desk. The TDS-net check as the first cut on any odd-amount credit under Rs 5 lakh. The AR open-invoice register queried by subset-sum for any credit that returns no TDS-net match. The payment aggregator dashboards checked for any credit landing on a business day between the platform's standard settlement windows. The AP debit-note register queried for any credit on a vendor counterparty. The AR credit-note register queried for any credit whose amount matches an outstanding credit-note position. The intercompany reconciliation report queried for any credit whose narration contains a group-entity name fragment. The treasury sweep register queried for any credit that resolves cleanly to a USD, EUR, GBP, or AED sweep at the day's card conversion rate.
The credit is either tagged against a specific counterparty position within the first-tier walk-through, or it enters the exception queue with a named branch attempted and eliminated for each cause, an owner, an age, and a next-escalation date. The seven-cause elimination closes 80 to 90 per cent of odd-looking 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 under Section 37 or Section 41 with a defensible statutory anchor and a working-paper trail that survives a going-back audit sample.
You pulled the HDFC current-account statement on Monday morning and a Rs 47,236 credit is sitting there from three weeks ago. The narration reads “NEFT-INB-CITIN22XXXXXXXXX-SHREE.” No counterparty name you recognise. No open invoice on the accounts-receivable ledger for that amount within any rounding tolerance you’re comfortable with. No remittance advice in the inbox. And the analyst has already spent forty minutes on it this week trying to work out what it is. You are not doing anything wrong. It is almost always one of seven things.
The short answer
An unmatched credit on an Indian enterprise bank account is almost always a TDS-net customer receipt, a multi-invoice payment without a remittance advice, a payment-aggregator net settlement, a vendor refund, the settlement of a prior credit note, a misdirected intercompany transfer, or a treasury sweep from a foreign-currency account. Nine times out of ten it is one of the first three. The seven-cause walk-through takes ten to fifteen minutes per credit and closes 80 to 90 per cent of them without escalation.
Cause 1 — a TDS-net customer receipt
This is the highest-probability cause and the one to check first. When a customer whose turnover crosses Rs 10 crore purchases goods above Rs 50 lakh in a financial year from you, they must deduct tax at 0.1 per cent under Section 194Q — code 1031 under the new Section 393 schedule from 1 April 2026. A Rs 47,283 invoice therefore lands as a Rs 47,236 credit with Rs 47 withheld and deposited against your PAN.
Divide the credit by 0.999 and query the AR ledger for any open invoice between Rs 47,280 and Rs 47,286. If a match returns, tag the invoice, book the Rs 47 to the TDS receivable ledger, and move on. Also run the Section 194O check at 1 per cent — divide by 0.99 and query for Rs 47,713 on any Amazon, Flipkart, or Meesho counterparty.
Cause 2 — a multi-invoice payment without a remittance advice
The customer paid three of your open invoices in one wire and did not send the payment schedule. Query the AR ledger for any counterparty whose open-invoice count is between two and five and whose values are all under Rs 25,000, and run a SUMPRODUCT check for combinations summing to Rs 47,236 within a rounding tolerance. Three open invoices at Rs 18,240, Rs 12,996, and Rs 16,000 sum exactly. A phone call to the customer’s accounts-payable head usually confirms within ten minutes.
Cause 3 — a payment aggregator net settlement
Every payment gateway posts a net settlement to your current account after deducting the Merchant Discount Rate at approximately 2 per cent, GST on the commission at 18 per cent, and any refunds initiated in the settlement window. A Razorpay, PayU, Cashfree, BillDesk, or Instamojo settlement of Rs 47,236 typically back-decomposes to a Rs 49,236 gross minus roughly Rs 984 MDR minus Rs 177 GST on MDR minus Rs 839 in refunds. Open every platform’s merchant dashboard for the credit date and search for a settlement between Rs 47,200 and Rs 47,280.
Cause 4 — a vendor refund against a prior debit note
The credit is on a vendor, not a customer. Query the accounts-payable ledger for any debit note issued against a vendor in the six months prior for Rs 47,236 — a defective-consignment refund, a rate-difference adjustment, a wrongly-billed freight charge, or an excess-payment reversal. Vendor finance teams often release refund wires without a covering email, so the arithmetic is where you catch it first, not the correspondence.
Cause 5 — settlement of a prior credit note
Under Section 34 CGST, you issued a credit note against an earlier invoice for goods returned or an over-billing correction. The customer usually withholds the credit-note amount from a later invoice, but occasionally settles it separately as a bank wire that arrives with no candidate invoice on the AR ledger because it is clearing a credit-note position rather than an open invoice. Query the AR credit-note register for any credit note issued in the six months prior for Rs 47,236.
Cause 6 — a misdirected intercompany transfer
Group treasury teams sometimes credit the wrong bank account when two group entities have similar-named accounts at the same bank. The “SHREE” prefix in the NEFT narration matches your group’s parent-entity name, which is the tell. Email the group treasury team the same day. 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 in the receiving entity on the audit committee’s quarterly report.
Cause 7 — a treasury sweep from a foreign-currency account
A sweep from an FCNR or EEFC foreign-currency account into the operating INR account arrives at the bank’s card conversion rate on the sweep date, with no domestic invoice reference. A USD 570 sweep at Rs 82.87 per USD lands as exactly Rs 47,235.90, rounded to Rs 47,236. Query the treasury sweep register, cross-reference with the Foreign Inward Remittance Certificate for the underlying inflow, and tag the credit to the treasury reference.
The one to escalate first
If none of the seven causes fires within the first ten minutes, the credit is now an exception-queue item and the escalation clock starts on the credit date, not the discovery date. The three-tier escalation ladder from the bank reconciliation runbook — Tier 1 at 30 days is the analyst-level chase to the bank for the underlying 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 — is what turns an aged credit into a defensible closure rather than an indefinite carry-open on the bank reconciliation working paper. Below Rs 10,000 the writeoff is materiality-immaterial and the controller signs off; above Rs 10,000 the CFO co-signs; above Rs 1 lakh it enters the audit-committee report.
The tool that runs the walk-through for you
The bank narration parser workbook is the Excel companion to this article — the parsing routines that break down HDFC, ICICI, SBI, Axis, and Kotak narration strings into the underlying UTR, counterparty fragment, and payment mode, so the “who paid me” question becomes an Excel formula rather than a manual scan of the bank statement. It pairs with this walk-through as the first-cut identification tool.
When the 8pm chase outgrows itself
One unmatched credit a month is a normal residual for a 200-to-500-customer mid-market enterprise. Three or more per month sustained across a quarter is a structural signal — a stale counterparty master, a truncated bank narration pattern the 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 manual seven-cause elimination becomes a full-time analyst activity and starts absorbing hours that should have moved into the Day 6 TDS window. Terra Insight’s reconciliation software runs the seven-cause elimination against every unmatched credit at end-of-day as a first-class continuously-refreshed output, and the manual walk-through keeps its role as the discipline the system runs against rather than the process the analyst runs by hand at 8pm.
Go deeper
- The seven-branch decision tree — with statute anchors and a writeoff protocol — the full technical treatment of this walk-through, branch by branch, with the Section 37 versus Section 41 classification decision.
- Invoice-to-bank reconciliation failure modes — the design-layer counterpart that catalogues every way an invoice-to-bank match can fail and the controls needed to catch each one.
- Bank reconciliation runbook — Days 1 to 5 — the monthly cadence that positions this walk-through inside a five-day sign-off window.
- Bank statement narration patterns for Indian banks — the parser rules for HDFC, ICICI, SBI, Axis, and Kotak narration strings.
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, which is why a customer-side wire that should have arrived at a round-invoice amount lands as Rs 47,236 rather than Rs 47,283.
- ▸ 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 at the time of credit to the participant or at the time of payment, whichever is earlier. Payouts from Amazon, Flipkart, Meesho and similar platforms land net of this 1 per cent deduction and net of the Merchant Discount Rate, which is why a settlement never arrives at the sum of the invoice values.
- ▸ Section 34, Central Goods and Services Tax Act 2017 — Credit Notes — Where a tax invoice has been issued for a supply and the taxable value or tax charged in that 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. Occasionally a customer settles a prior credit-note position with a separate wire rather than netting it against a later invoice — which arrives on the bank statement with no candidate invoice to attach it to.
- ▸ Section 37, Income-tax Act 1961 — Business Expenditure — Any expenditure not being capital expenditure or personal expenses of the assessee, laid out or expended wholly and exclusively for the purposes of the business, shall be allowed in computing the income under the head Profits and gains of business or profession. Where an unmatched credit has been chased through every documented branch and cannot be identified against any counterparty, the residual writeoff is booked as an allowable business loss under Section 37 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 the assessee has obtained any amount in respect of a loss or expenditure or some benefit in respect of a 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 an unreconciled credit is traceable to an intercompany or related-party position that has ceased to be payable by the sending group entity, the Section 41 branch fires and the amount is recognised as deemed income rather than as a Section 37 writeoff.
- ▸ Foreign Exchange Management Act 1999 — Foreign Inward Remittance Certificate — The Reserve Bank of India requires the authorised dealer bank to issue a Foreign Inward Remittance Certificate (FIRC) for every inward remittance credited to an FCNR, EEFC, or resident current account. A treasury sweep from an EEFC or FCNR account into the operating INR account produces an INR credit at the bank's card conversion rate on the sweep date, with the FIRC as the confirming document that ties the credit back to the underlying foreign-currency inflow rather than to a domestic invoice.