Insights on Reconciliation in Indian Enterprise Finance
Practitioner guides written by finance operations professionals with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Covering TDS, GST input credit, platform settlements, NACH batch matching, and bank reconciliation for Indian enterprises.
TDS
54 articlesForm 26AS, every active section, corrections, 2026 migration
Browse cluster →GST
17 articlesGSTR-2B matching, ITC, IMS, DRC-01B/C, annual 9/9C
Browse cluster →Platform Settlements
13 articlesRazorpay, Amazon, Flipkart, UPI, MDR, chargebacks
Browse cluster →NACH & Statutory
10 articlesReturn codes, mandates, PF/ESI, MSME 43B(h)
Browse cluster →Banking
9 articlesHDFC, ICICI, SBI, MT940, narration patterns, CARO 2020
Browse cluster →Buyer's Guide
10 articlesEvaluation, ROI, board justification, security checklist
Browse cluster →Ajio and Myntra Seller Settlement Reconciliation: Fulfilment Models, Returns, TDS 194O
Ajio and Myntra sellers operate under multiple fulfilment models — Ajio Own Inventory, Ajio Sell On, Myntra Flex, and Myntra FBF — each with a different commission structure, return treatment, and tax deduction pattern. Reconciling seller payouts across these models requires separating orders by fulfilment type before any matching begins.
Amazon SPN Seller GST Reconciliation: Easy Ship, FBA, and Returns Impact on GSTR-1
Amazon SPN (Service Provider Network) partners and sellers manage GST reconciliation across two fulfilment models — Easy Ship, where the seller stores and Amazon picks up, and FBA, where Amazon holds the inventory. Each model produces different return pathways, TCS timing, and GSTR-1 template entries that must be reconciled independently.
Busy Accounting Software Reconciliation in India: DBF Data, Multi-Company, and Import-Export Patterns
Busy Accounting Software runs on a DBF data layer and ships with strong India-specific modules — GSTR-2A/2B import, TDS tracking, multi-company consolidation. Reconciliation at scale, across multi-branch operations and across external tax portals, often needs a layer on top. This guide covers the integration patterns.
CA Firm Client Reconciliation Workflow: Onboarding to Monthly Cycle
A CA firm running outsourced compliance for 80 enterprise clients runs a predictable monthly cycle: onboarding new clients, pulling statutory data on the 1st, matching by the 10th, exception review by the 15th, filing by the 20th. This guide covers the full workflow including role allocation and deliverable timelines.
CA Firm GST Reconciliation Tool: Running GSTR-2B for 50+ Clients
A CA firm servicing 80 clients faces 200 to 400 GST registrations every month, each requiring a GSTR-2B pull, an ITC match against the client's purchase register, and an exception queue feeding GSTR-3B. This guide covers how a purpose-built CA firm GST reconciliation tool structures that workflow.
Concurrent Audit of Reconciliation: Daily Verification for Banks and NBFCs
Concurrent audit is the daily shadow of operations in Indian banks and larger NBFCs. Mandated by the RBI for branches above specified thresholds, the concurrent auditor must verify bank reconciliations, nostro balances, suspense accounts, and NACH return files as transactions occur — not after month-end. This guide covers the reconciliation checks a concurrent auditor signs off each day.
D2C COD vs Prepaid Settlement Reconciliation: 3PL Remittance and Gateway Payouts
D2C brands operating on Shopify or custom storefronts carry two parallel settlement flows that must be reconciled separately: cash remittance from 3PL partners for COD orders, and gateway payouts for prepaid orders. Each has its own timing, deduction structure, and variance pattern, and collapsing them into a single revenue line hides RTO leakage and commission errors.
ICFR and Reconciliation Controls: Design, Testing, and Reporting Under Section 143(3)(i)
ICFR — Internal Financial Controls over Financial Reporting — is the Indian equivalent of a SOX Section 404 control framework, but it applies to a much wider population of companies. Under Section 143(3)(i) of the Companies Act, 2013, statutory auditors must opine on the adequacy and operating effectiveness of these controls. Reconciliation is the single largest ICFR control domain, and a failing reconciliation control is the most common cause of a material weakness finding.
Internal Audit of Reconciliation in India: Testing, Sampling, and Evidence
Internal audit of reconciliation is no longer a year-end checklist exercise. Under Section 138 of the Companies Act, 2013 and the ICAI Standards on Internal Audit, internal auditors must test the design and operating effectiveness of reconciliation controls across bank accounts, party ledgers, and statutory dues — with documented sample selection, variance analysis, and evidence that stands up to statutory audit review.
Magento India Payment Gateway Reconciliation: PayU, Razorpay, Cashfree for Multi-Vendor Stores
Magento and Adobe Commerce stores in India often run multi-vendor extensions where a single gateway payout must be split across multiple sellers. Reconciling these payouts requires matching the gateway settlement to Magento's order-line structure first, then unpacking the split per vendor with commission and TDS implications per seller.
Microsoft Dynamics 365 Reconciliation in India: Business Central and Finance & Operations Localisation
Microsoft Dynamics 365 Business Central and Finance & Operations ship with Indian localisation covering TDS deduction, GST tax determination, and e-invoice. Reconciliation against Form 26AS, GSTR-2B, and NACH batch files remains an external step in standard deployments. This guide explains the boundary and the integration paths.
Odoo Reconciliation in India: Localisation, Community vs Enterprise, and Integration Paths
Odoo has a fast-growing footprint in Indian SMEs through both Community (free) and Enterprise editions. Its India localisation covers GST and TDS at module level, with differences between editions. Reconciliation at scale typically uses Odoo's XML-RPC interface to bridge to an external layer. This guide covers the specifics.
Oracle Fusion Cloud ERP Reconciliation in India: What Localisation Does and Doesn't Cover
Oracle Fusion Cloud ERP ships with an India Localization module that handles TDS withholding and GST tax determination. Reconciliation against Form 26AS, GSTR-2B, payment gateway settlements, and NACH batch files is not part of that module. This guide covers the exact boundary.
Outsourced GST Compliance Reconciliation: The Enterprise-CA Shared Surface
Mid-market and enterprise Indian companies increasingly outsource GST compliance to CA firms, but the reconciliation work itself remains a shared surface — the client owns the purchase register and invoice data, the firm owns the matching and filing. This guide covers how the handoff is structured, where liability sits, and what reconciliation software must support for both sides.
Quick Commerce Seller Reconciliation for Blinkit, Zepto, and Swiggy Instamart
Brands selling to quick-commerce platforms operate on a different reconciliation model than marketplace sellers. Blinkit, Zepto, and Swiggy Instamart buy inventory at a negotiated margin off MRP and stock it at their dark stores, so the seller's payout is a wholesale price net of commission bands, TCS, and return or damage deductions.
Reconciliation Software for CA Firms in India: Beyond Audit Tools
Chartered Accountant firms in India running GST, TDS, and bank reconciliation for 30 to 500 clients hit workflow limits that audit tools and spreadsheets cannot solve. This guide covers what reconciliation software designed for CA firms must do differently — client data isolation, per-client rate cards, batch month-end cycles, and white-label output.
Sage Reconciliation in India: X3 and Sage 300 for Mid-Market Finance Teams
Sage X3 and Sage 300 are common choices for Indian mid-market manufacturers and distributors. Their India localisation is lighter than SAP's or Oracle's, which shifts more of the TDS, GST, and platform reconciliation work to an external layer. This guide covers the integration approach and the audit-trail compliance angle.
SAP FI Reconciliation in India: Where S/4HANA and ECC Stop Short
SAP FI in S/4HANA and ECC ships with India localisation that covers TDS deduction posting and GST tax determination. It does not natively reconcile Form 26AS, GSTR-2B, or NACH batch credits against the FI ledger. This guide explains the exact gaps and where a reconciliation layer fits.
Shopify India GST Reconciliation: SGST, IGST, and Gateway Payout Matching
Shopify stores selling across Indian states carry a reconciliation problem that the Shopify admin does not solve: the tax split between SGST and IGST must be derived from each order's ship-to state, and the gateway payout arrives net of MDR and platform fees that do not appear in Shopify's order report. Reconciling these two flows to a single GSTR-1 line is the core task.
SOX Compliance Reconciliation: What Indian Subsidiaries of US-Listed Parents Must Prove
An Indian subsidiary of a NYSE or Nasdaq-listed parent sits inside two overlapping control frameworks: US SOX Section 404 (testable under PCAOB AS 2201) and Indian ICFR under Section 143(3)(i). Reconciliation controls are the most heavily scoped area under both. This guide covers what SOX compliance testing looks like for reconciliation at an Indian entity, how it maps to ICFR, and where the two diverge.
Statutory Audit Reconciliation Checklist: Bank, Party, TDS, and GST Items
Statutory auditors in India follow a standard reconciliation checklist during year-end fieldwork: bank reconciliations, intercompany balances, party confirmations, TDS receivable against Form 26AS, GST input credit against GSTR-2B, and statutory dues. Each item has a specific audit procedure, a documented evidence standard, and a qualification threshold. This guide is the practitioner-level checklist that finance teams can pre-run before the audit arrives.
Tally Prime Reconciliation Automation: Integration Paths for Indian Businesses
Tally Prime handles the deepest India-specific functionality among SME ERPs — GSTR-2B import, TDS challan tracking, bank reconciliation. Automating it at scale requires one of three integration paths: XML import/export, TallyODBC, or the Tally Connector HTTP interface. This guide compares them.
Tax Audit Form 3CD: Reconciliation Items the Auditor Verifies Under Section 44AB
A tax audit under Section 44AB of the Income Tax Act, 1961 is the single most reconciliation-heavy audit in Indian practice. Form 3CD has 44 clauses, and most of them require the auditor to reconcile reported figures against statutory portals — Form 26AS, GSTR-2B, TRACES, and the MCA filings. With Form 3CD being replaced by Form 26 under the new Income Tax Act 2025, the reconciliation bar has moved higher.
White-Label Reconciliation for CA Firms: Branded Client Deliverables
A CA firm's client deliverable — the GST reconciliation report, the Form 26AS match file, the bank reconciliation statement — carries the firm's name, not the software vendor's. White-label reconciliation software is the category that supports this: firm-branded PDFs, custom sub-domains, and portal access for clients under the firm's identity.
Zoho Books Reconciliation Limits: What Breaks When Indian Businesses Scale
Zoho Books is a capable accounting platform for Indian SMEs with built-in GSTR-2B reconciliation and bank feeds. The limitations appear when transaction volume crosses 1,000 per month, when multiple payment gateways settle daily, or when variance classification needs to drive audit response. This guide covers the exact break points.
Advertising TDS: Why Creative Services Fall Under 194J, Not 194H
Advertising and creative agency invoices are frequently misclassified as commission under Section 194H when the correct provision is 194J professional services. This guide explains the classification split, shows where pure media buying commission ends and creative advertising begins, and covers reconciliation for Indian media agencies.
Cross-Era TDS Reconciliation: Matching Old Section Codes to New Payment Codes
An Indian IT services company in July 2026 will open its quarterly TDS reconciliation and see Form 16A certificates from March dated under Section 194J alongside Form 131 certificates from May carrying payment code 1003. The receivable ledger has a 194J receivable from a client that settles in May. The matching problem is not complicated; it is cross-era, and it will repeat for three financial years until the correction windows close.
Form 131 TDS Certificate: The Quarterly Deductor Certificate Under the Income Tax Act 2025
Form 131 is the quarterly TDS certificate issued by deductors under the Income Tax Act 2025, replacing Form 16A from April 1, 2026. It carries the new payment code, Tax Year labelling, and an expanded data schema that changes how Indian finance teams reconcile TDS credits against the deductor-issued certificate.
Form 141 Challan-cum-Statement: The Unified Filing for Property, Rent, Contractor, and Crypto TDS
Form 141 is the unified challan-cum-statement introduced by the Income Tax Act 2025, consolidating the four separate filings used today for property sale TDS, rent TDS, specified contractor payments, and virtual digital asset TDS. This guide covers the scope, the combined schema, and what Indian taxpayers should know about the April 1, 2026 switchover.
Form 168 TDS Statement: The New Unified Annual Statement Under the Income Tax Act 2025
Form 168 is the new unified annual statement introduced by the Income Tax Act 2025, replacing Form 26AS as the authoritative record of tax credits for every PAN. This guide covers its structure, the additions beyond the legacy statement, and the reconciliation workflow change Indian finance teams should plan for before the April 1, 2026 switchover.
Manpower Supply TDS: Why It Falls Under 194C, Not 194J
Staffing and manpower supply invoices are one of the most commonly misclassified TDS entries in Indian enterprise AP systems. This guide explains why Section 194C is the correct provision, how the 10% over-deduction cycle hurts staffing vendors, and how finance teams reconcile the resulting Form 26AS variances.
Tax Year vs Assessment Year in India: The Terminology Change Under the Income Tax Act 2025
Tax Year replaces Assessment Year as the period label under the Income Tax Act 2025, effective April 1, 2026. This guide covers the exact mapping rule, the filing forms affected, and the reconciliation impact on finance teams comparing pre-2026 and post-2026 records.
TDS 2026 Migration Checklist: What Indian Finance Teams Must Do Before April 1
The April 1, 2026 switch-over to the Income Tax Act 2025 is not a flag flip at year-end. It is a migration programme with ERP master data updates, GL code additions, correction statement deadlines, obsolete compliance filters to remove, and a cut-over weekend to plan. This checklist covers what an Indian finance team must complete before the first April challan deposit.
TDS Payment Codes 1001–1092: New Numeric Taxonomy Under Income Tax Act 2025
From April 1, 2026, challans, certificates, and quarterly returns stop identifying TDS by section number and start using four-digit payment codes in the 1001–1092 range. Payment codes sit under three parent sections: 392 for salary, 393 for non-salary TDS, and 394 for TCS. Finance teams need a working mapping from day one, because TRACES, OLTAS, and the new Form 168 all key off the numeric code rather than the legacy section reference.
TDS Rate by Date Reconciliation: How to Apply the Correct Rate When Rates Change Mid-Year
TDS rates and thresholds have changed mid-year in 2024 and 2025. Reconciliation systems that apply a single rate per section across the full year generate false variances and under-deductions. This guide explains rate-by-date reconciliation, lists the recent changes, and shows how to match the correct rate to each payment date.
Deferred Revenue Reconciliation for Indian SaaS Companies
Under Ind AS 115, recognizing a 12-month SaaS subscription as revenue on the date of receipt is a material misstatement. The full amount is a liability — deferred revenue — that converts to recognized revenue at ₹1 lakh per month against a ₹12 lakh annual contract. Reconciling the deferred revenue schedule against actual cash, invoices, and the general ledger each quarter is where most Indian SaaS companies discover discrepancies.
Ind AS 115 Revenue Reconciliation for Indian IT and SaaS Companies
An IT services company with 80 active contracts and mid-year scope changes risks material misstatement on revenue if contract modifications are not tracked against the five-step model. Ind AS 115 replaced the old revenue recognition framework in April 2018, and Indian IT and SaaS companies operating with milestone billing, time-and-material contracts, and multi-element SaaS arrangements must reconcile revenue at the contract level — not just the invoice level.
Milestone Billing Reconciliation for IT Services Companies in India
A mid-size Indian IT services company with 40 active fixed-price contracts typically has 120 or more open milestones at any point — each at a different stage of deliverable completion, client sign-off, invoicing, and payment. The reconciliation challenge is not matching a bank credit to an invoice. It is tracing each milestone from the statement of work through delivery acceptance, invoice generation, TDS deduction by the client, and net cash receipt in the bank.
Multi-Currency Reconciliation for Indian IT Services Companies
Multi-currency reconciliation guides written for global companies miss the India-specific layers: FIRC matching against bank credits, SOFTEX declarations for STPI units, and RBI FEMA reporting for software export receipts. Indian IT services companies invoicing in USD, EUR, or GBP must reconcile not just the exchange rate variance but the regulatory trail that accompanies every foreign inward remittance.
SaaS Subscription Reconciliation in India: MRR, Deferred Revenue, and Cash Matching
Most Indian SaaS companies track MRR with precision but stop short of reconciling deferred revenue schedules against actual cash receipts. The gap between subscription invoiced, revenue recognised, and cash received produces three separate ledger views of the same customer — and when these diverge without a structured matching process, month-end close extends by days and Ind AS 115 audit queries multiply.
TCS on LRS and Overseas Tour Packages: Reconciliation for Indian Businesses
Foreign remittances under the Liberalised Remittance Scheme and overseas tour package sales both trigger TCS obligations under Section 206C(1G). For forex dealers processing hundreds of remittances per month, tracking cumulative PAN-wise thresholds across multiple slabs is the point where manual reconciliation fails and mismatches against Form 27EQ become systemic.
TCS on Luxury Goods Reconciliation in India: Section 206C Matching
Sellers of motor vehicles, scrap, minerals, and other specified goods must collect TCS under Section 206C and deposit it with the government. Matching what was collected from buyers against what was deposited via challan and reported in Form 27EQ is where reconciliation breaks — especially when cumulative thresholds per buyer must be tracked across the financial year.
Time-and-Material Billing Reconciliation for Indian IT Companies
At 200 consultants deployed across 15 clients, a time-and-material billing operation generates 3,000 or more billable line items per month — each combining a consultant's timesheet hours, a client-specific rate card, and a billing currency that may differ from the receipt currency. The reconciliation challenge is not the individual match. It is confirming that every approved timesheet hour was invoiced at the correct rate, received at the correct forex conversion, and reflected with the right TDS credit in Form 26AS.
Ayushman Bharat PM-JAY Claim Reconciliation for Empanelled Hospitals
At 50 claims per month, a district hospital can track PM-JAY settlements in a spreadsheet. At 500 claims across multiple treatment packages, with state-level rate variations and 30-to-90-day settlement cycles through the TMS portal, spreadsheet tracking produces systematic errors — missed claims, unreconciled bank credits, and package rate variances that go undetected until the quarterly audit.
Cashless Claim Settlement Reconciliation for Hospitals and Insurers
A cashless insurance claim involves at least three parties and four financial entries: the insurer's preauth approval, the hospital's final bill, the patient's co-pay, and the TPA's batch settlement. When any one of these amounts changes between preauth and discharge — and it almost always does — the reconciliation must track the variance across all four entries. This is where most hospital finance teams lose visibility.
CGHS Reconciliation: How Hospitals Match Central Government Health Scheme Claims
Empanelled hospitals treating Central Government Health Scheme beneficiaries face a reconciliation challenge that private insurance does not create: CGHS rates are fixed by the government, often lower than NABH or private rates, and settlements flow through city-wise CGHS offices with variable timelines. This guide covers how CGHS claim reconciliation works, where it breaks, and what the common dispute categories are.
ECHS Reconciliation: Ex-Servicemen Health Scheme Claim Settlement Matching
Empanelled hospitals treating Ex-Servicemen Contributory Health Scheme beneficiaries face settlement delays of 60 to 120 days, package rates that differ from both CGHS and private insurance schedules, and a referral chain that runs through military polyclinics and Station HQ approvals. This guide covers how ECHS reconciliation works, where claims get stuck, and how the process compares to other government health schemes.
Hospital Billing Reconciliation: OPD, IPD, and Patient Deposit Matching in India
Hospital billing reconciliation in India is structurally different from standard accounts receivable matching. A 200-bed hospital may process OPD cash and UPI collections across 8 counters, IPD advance deposits with partial consumption, pharmacy POS settlements from 3 terminals, and diagnostic lab payments — all hitting the same bank account as separate aggregated credits. Matching these to individual patient bills requires department-level data that the bank statement does not carry.
Hospital-Insurance Reconciliation: Multi-Payer Settlement Matching in India
Hospital-insurance reconciliation in India is not a single matching exercise. A 200-bed hospital typically deals with 5 to 15 insurance companies, each with its own TPA, rate schedule, preauthorisation process, settlement file format, and payment cycle. A single patient bill can involve three payers: the insurer covering the package amount, the patient paying the co-pay, and a corporate sponsor covering the balance. This guide covers how multi-payer settlement matching works and where revenue leaks.
IRDAI Compliance Reconciliation: Audit Trail and Claim Settlement Reporting for Hospitals
IRDAI compliance reconciliation is not an annual exercise. Every cashless claim settlement, every grievance filed on IGMS, every TPA rate dispute, and every preauthorisation decision carries a documentation requirement that must be traceable end-to-end. For hospitals dealing with 500+ insurance claims per month, the audit trail is either built into the reconciliation process or reconstructed under pressure when a regulatory query arrives.
TPA Settlement Reconciliation for Indian Hospitals
A single bank credit from a TPA covers 50 to 500 patient claims. The bank narration shows a batch reference and the insurer name — nothing about individual patients, claim amounts, or policy numbers. The actual claim-level breakdown exists only in the settlement sidecar file that the TPA sends separately, often in a different format for each of the 19+ TPAs operating in India. Reconciling TPA settlements means matching these two data sources for every batch, every week.
CARO 2020 and Bank Reconciliation: Audit Requirements for Indian Companies
Clause 3(ii)(b) of CARO 2020 requires auditors to report whether quarterly statements filed with banks agree with books of account for companies with working capital limits exceeding ₹5 crore. Finance teams that treat bank reconciliation as a month-end formality face audit qualifications, material weakness disclosures, and GST exposure from unreconciled bank credits.
GSTR-9C: The Three-Way Mismatch Trap Between Books, GSTR-2B, and GSTR-3B
GSTR-9C forces a three-way comparison that most finance teams run only at year-end: ITC per audited financial statements versus ITC per GSTR-2B versus ITC claimed in GSTR-3B. When these three numbers disagree, the consequence is not just an audit observation. It is interest at 18% per annum, penalties under Section 122, and potential prosecution under Section 132 for fraud cases.
Marketplace Fee Audit: Identifying Revenue Leakage in E-Commerce Settlement Reports
E-commerce sellers lose 2-3% of gross payment volume to fee errors that never get audited. Commission category misclassification, volumetric weight overcharges, incomplete return reversals, and incorrect TCS calculations compound silently across thousands of orders. For a seller processing ₹5 crore GMV per month, that translates to ₹10-15 lakh in annual leakage from settlement report discrepancies alone.
Rule 37 and Rule 37A: ITC Reversal When Your Supplier Defaults
Two GST provisions force the buyer to reverse legitimately claimed Input Tax Credit because of the supplier's actions. Rule 37 requires reversal if the buyer has not paid the supplier within 180 days of the invoice date. Rule 37A requires reversal if the supplier has not filed GSTR-3B by September 30 following the financial year. Both provisions carry interest implications, but unlike Section 16(4), both allow re-availment when the default is cured. The reconciliation challenge lies in tracking thousands of invoices against two independent clocks.
Section 16(4): The Permanent ITC Loss Deadline Every Finance Team Must Track
Section 16(4) of the CGST Act imposes the hardest deadline in Indian indirect tax. Input Tax Credit not claimed by November 30 of the financial year following the year of the invoice is permanently lost. Unlike TDS credits, there is no rectification, no condonation, and no updated return. The Finance Act 2022 shifted this deadline from September 30 to November 30, applied retrospectively from July 2017, but the fundamental risk remains: a single missed invoice can cost lakhs in irrecoverable credit.
Section 194T: The New TDS Obligation on Partner Remuneration, Interest, and Bonus
Every partnership firm and LLP in India has a new TDS obligation from April 1, 2026. Section 194T requires firms to deduct 10% TDS on salary, remuneration, commission, bonus, and interest paid to partners when the aggregate exceeds ₹20,000 in a financial year. Missing this deduction triggers assessee-in-default liability under Section 201(1) and a 30% expenditure disallowance under Section 40(a)(ia).
TDS Credit Recovery: Every Mechanism Available When Form 26AS Doesn't Match
When Form 26AS does not reflect the TDS your deductor claims to have deposited, the enterprise ends up paying tax twice on the same income. Deloitte's 2024 tax litigation survey found that 18% of corporate filers face at least one Form 26AS mismatch per assessment year. For an organisation with ₹100 crore in revenue, even a 2% credit loss translates to ₹20 lakh in unrecovered tax. This guide maps every recovery mechanism available under the Income Tax Act, in order of preference.
TDS Penalty and Interest: The Complete Multi-Layered Consequence Framework
A single TDS default in India triggers consequences under up to five separate provisions simultaneously: interest under Section 201(1A), assessee-in-default liability under Section 201(1), expenditure disallowance under Section 40(a)(ia), late filing fees under Section 234E, and criminal prosecution under Section 276B. For an organisation processing 1,000 payments per month, a systematic one-day delay in TDS deposit generates ₹36 lakh in annual interest liability alone.
AIS and TIS Reconciliation: How to Reconcile Annual Information Statement Before Filing ITR
The Annual Information Statement replaced Form 26AS as the primary tax credit and income disclosure document in November 2021, but most enterprise finance teams still limit pre-ITR reconciliation to Form 26AS. The gap matters: AIS contains 46 categories of financial information including SFT data, dividend reporting, and GST turnover — all of which now feed into Section 143(1) processing intimations. A mismatch between AIS reported income and filed ITR income triggers automatic notices even when the ITR figures are correct.
DRC-01B Notice: What It Means and How to Respond to the GST Liability Mismatch Notice
DRC-01B is an auto-generated GST notice issued when your GSTR-1 declared liability exceeds your GSTR-3B payment by more than the system threshold. You have seven days to reply on the GST portal. This guide covers the three reply options, when to make a voluntary payment via DRC-03, and how systematic reconciliation prevents these notices.
DRC-01C Notice: How to Respond to the GST ITC Mismatch Auto-Notice
DRC-01C is an auto-generated GST notice issued when Input Tax Credit claimed in GSTR-3B exceeds the ITC available in GSTR-2B by more than the system threshold. You have seven days to reply. This guide covers why legitimate ITC claims trigger DRC-01C, how to reply correctly, and how IMS actions prevent these notices before they are issued.
IMS vs GSTR-2B: The New Three-Way Reconciliation Indian Businesses Must Do
Finance teams that reconcile GSTR-2B against their purchase register without first completing IMS actions are working with an incomplete picture of their ITC. Since October 2024, GSTR-2B values are determined by IMS decisions — making a three-way reconciliation the minimum required process for accurate ITC claims.
GST Invoice Management System (IMS): How It Changes Your Reconciliation Workflow
The GST Invoice Management System went live on October 14, 2024, adding a mandatory review layer before invoices lock into GSTR-2B. Most finance teams are still running a three-step reconciliation that no longer matches how ITC is confirmed. This guide covers the new four-step workflow and where it breaks without structured tooling.
MSME 45-Day Payment Tracker: How to Reconcile Vendor Payables Under Section 43B(h)
The practical challenge of Section 43B(h) is not understanding the rule — it is tracking hundreds of MSME invoices across payment timelines at scale. For a company with 150 active MSME vendors, each generating 3 to 8 invoices per month, the compliance tracking requirement runs to thousands of data points per quarter. Manual spreadsheet management at this volume produces systematic errors. This guide covers what an MSME payment tracker must capture and how to connect it to bank payment records.
New Income Tax Act 2025: Complete TDS Section Mapping for Finance Teams
The Income Tax Bill 2025 renumbers every TDS section effective April 1, 2026. Section 194C becomes Section 393(1)(a), Section 194J maps to Section 393(1)(b), and the entire Chapter XX replaces the legacy TDS provisions. Finance teams need a mapping table, a TRACES update plan, and a cross-year reconciliation strategy before FY 2026-27 begins.
Section 393 Under the New Income Tax Act 2025: What It Means for TDS Reconciliation
Section 393 of the new Income Tax Act 2025 is the umbrella provision that consolidates what were previously separate TDS sections — 194C, 194J, 194H, 194I, 194A, and others — into a single section with sub-clauses. For reconciliation teams, this creates a dual-code operating environment from April 1, 2026: historical transactions carry old section codes, new transactions carry Section 393 sub-clauses, and cross-year matching must handle both simultaneously.
Section 43B(h): MSME Payment Reconciliation and Tax Disallowance Risk
Section 43B(h) of the Income Tax Act entered its second year of enforcement in AY 2025-26. Companies purchasing from Micro and Small enterprises that have not systematised vendor payment tracking are now exposed to real tax disallowance — not a theoretical risk. This guide explains the rule, who it covers, and the reconciliation process required to manage it.
TDS Correction Statement Deadline: March 31, 2026 Time-Bar for FY 2018–23
Five financial years of TDS data become impossible to correct after March 31, 2026. FY 2018-19, 2019-20, 2020-21, 2021-22, and 2022-23 correction statements are barred under the Section 200 limitation period. If your organisation has unresolved challan mismatches, PAN errors, or amount discrepancies for these years, the correction window closes in days.
Automating TDS Reconciliation: What the Process Looks Like End-to-End
Manual TDS reconciliation for a company with 60 active deductors takes 3 to 5 staff days per quarter. The process — downloading Form 26AS from TRACES, exporting the TDS receivable ledger from Tally or SAP, and matching row by row — produces systematic gaps at scale: wrong quarters, short deductions, PAN mismatches. This guide covers what automated TDS reconciliation looks like, where the logic differs from simple matching, and what it changes for a finance team's quarter-end cycle.
Financial Reconciliation Dictionary: Terms Used in Indian Finance Operations
A reference dictionary of 30 financial reconciliation terms for Indian finance operations — covering process concepts, transaction types, matching logic, and the reporting and control vocabulary that auditors and controllers use daily.
GST Reconciliation Glossary: Terms Every Finance Team Must Know
A working reference of GST reconciliation terms for Indian finance and tax teams — from GSTIN and ITC to IMS, GSTR-2B cut-off dates, and recipient mismatches — with practical context for each.
NACH and Payments Glossary: Key Terms for Reconciliation
A comprehensive glossary of NACH, ECS, mandate, and bulk payment terms for Indian NBFCs, lenders, and corporate treasury teams — including mandate types, return codes, reconciliation lag, and how NACH credits appear in bank statements.
Platform Settlement Glossary: Terms for E-Commerce and Payment Gateway Finance Teams
A reference glossary for platform settlement and payment gateway terms in India — covering MDR, TCS under Section 52, nodal accounts, chargeback, rolling reserve, and the tax treatment that makes settlement reconciliation in e-commerce uniquely complex.
TDS on ESOP Perquisites Under Section 192: Reconciliation Challenges
TDS on ESOPs is deducted at vesting under Section 192 — not at grant and not at sale. For finance teams, this creates reconciliation challenges: the timing of TDS events differs from ESOP accounting under IndAS 102, multiple vesting tranches generate multiple TDS entries, and cross-border grant structures add a Section 195 layer. This article covers the full reconciliation picture.
TDS Glossary: Essential Terms for TDS Reconciliation in India
A plain-language reference of every TDS term your finance team encounters — from TAN and TRACES to correction returns and Section 206AB — with India-specific context for reconciliation.
TDS on GST Component: How to Handle GST-Inclusive Invoices Correctly
A common error among Indian deductors is computing TDS on the total invoice value — base amount plus GST. CBDT Circular No. 23/2017 is unambiguous: TDS applies only on the base value excluding GST. This article covers how to handle both invoice scenarios, the reconciliation consequence of excess TDS, and the correction process.
TDS Reconciliation for IT Services Companies: 194J at Scale
For IT services companies with 50 or more active clients, TDS reconciliation under Section 194J is a quarterly exercise that routinely surfaces section mismatches, net-of-TDS payment gaps, and Form 26AS discrepancies that must be resolved before ITR filing.
TDS Reconciliation for NBFCs: Managing Section 194A at Scale
NBFCs operate on both sides of the TDS ledger simultaneously: deducting TDS from depositor interest under Section 194A while receiving TDS-deducted interest from banking partners. At scale, the reconciliation complexity compounds across thousands of depositors, multiple co-lending arrangements, and quarterly TRACES filing cycles.
Form 16A TDS Certificate: Reconciling Non-Salary TDS Deductions with Your Books
Form 16A is the non-salary TDS certificate issued by deductors for professional fees, rent, contract payments, interest, and commission. A service provider with 50 clients can receive up to 200 Form 16As in a year—one per deductor per quarter. Reconciling each against Form 26AS and the TDS receivable ledger is a quarterly obligation that directly affects the tax credit claimed in the ITR.
Form 15CA and 15CB: Reconciling TDS on Foreign Remittances for Indian Companies
Indian companies making foreign remittances — software subscriptions, professional fees, royalties, dividends to non-residents — must file Form 15CA before each remittance and obtain a CA-certified Form 15CB where required. Reconciling multiple 15CA filings against underlying payments, TDS challans, and Form 27Q entries across a financial year requires a structured tracking approach that most companies do not have in place.
TDS Compliance Calendar: Filing Deadlines, Reconciliation Windows, and Penalty Dates for FY 2025-26
TDS compliance in India runs on a fixed calendar of monthly deposit deadlines, quarterly return filing dates, and certificate issuance windows. Missing any one of them triggers interest under Section 201(1A) or penalties under Section 234E — at ₹200 per day. This guide maps every deadline for FY 2025-26, with the reconciliation windows that should run alongside each milestone.
TDS Demand Notice Under Section 200A: How to Reconcile and Respond
A TDS demand notice under Section 200A is generated automatically after the Income Tax Department processes a TDS return. It itemises short deductions, interest under Section 201(1A), late filing fees under Section 234E, and challan mismatches. Finance teams that have not reconciled their TDS records quarterly will find themselves compressing weeks of correction work into the notice response window.
Multiple Deductors, One PAN: Reconciling TDS from Multiple Sources in India
A consulting firm or professional receiving fees from multiple clients accumulates TDS entries across many deductors — each filing independently, each potentially applying a different section code, and each with their own filing timeline. Reconciling this against a single Form 26AS is a structured process that requires matching at the invoice level, not just at the aggregate tax credit level.
TDS PAN Validation Failures: How PAN Mismatches Trigger Higher Deduction Rates
When a deductee's PAN fails validation, Section 206AA mandates TDS at the higher of the applicable rate or 20% — regardless of the actual section rate. For Indian finance teams managing vendor payments, PAN mismatches range from inoperative status after the Aadhaar linking deadline to a single character error on an invoice. Each failure mode has a different fix, and all of them require resolution before the quarterly return is filed.
TDS Refund Reconciliation: Claiming and Tracking Excess TDS Deducted in India
TDS refund arises when the aggregate TDS deducted across all sources exceeds the total tax payable for the year — a common position for companies with losses, exempt income, or entities that hold a lower deduction certificate under Section 197 that was not submitted on time. Reconciling the expected refund against the intimation received under Section 143(1) and then tracking the bank credit is a three-stage process that most finance teams handle without a structured register.
Section 192: Reconciling Salary TDS Deductions with Form 16 and Form 26AS
Section 192 salary TDS does not follow a fixed rate—it varies by employee income slab, escalates in Q4 as adjustments for bonuses and perquisites are finalised, and must reconcile across three data sources: the payroll register, the TDS challan deposit record, and Form 26AS. For payroll teams managing hundreds of employees across multiple locations, each quarter end is a multi-source matching exercise with audit exposure if it fails.
Section 194: Reconciling TDS on Dividends for Indian Shareholders and Companies
Since 1 April 2020, dividend-distributing companies must deduct TDS under Section 194 at 10% for resident shareholders where annual dividend exceeds ₹5,000. Reconciling this across thousands of shareholders — each with different PAN, holding, and DTAA status — creates significant compliance risk. This guide covers both the paying company's and the investor's reconciliation process.
Section 194O TDS: Reconciling E-Commerce Operator Deductions for Indian Sellers
Section 194O places the TDS obligation on the e-commerce operator, not the seller—but it is the seller's finance team that must reconcile deductions across multiple platforms, match gross-basis TDS against net-of-GST revenue books, and resolve timing differences before the ITR deadline. For brands selling on two or more marketplaces, this is a quarterly exercise with material reconciliation risk.
Section 194S: Reconciling TDS on Virtual Digital Asset Transfers in India
Section 194S TDS on VDA crypto India applies to every transfer of a virtual digital asset—cryptocurrency, NFTs, and other notified digital assets. For crypto exchanges and corporate VDA traders, the reconciliation challenge is compounded by volatile asset values, multi-exchange deduction streams, and the interaction between TDS credit claims and the prohibition on offsetting VDA losses against other income.
Section 206AB and 206CCA: Identifying Non-Filers and Reconciling Higher TDS Rates
Section 206AB (effective 1 July 2021) requires TDS at twice the applicable rate — or 5%, whichever is higher — for vendors who have not filed income tax returns for two preceding financial years and whose TDS/TCS exceeded ₹50,000 in each of those years. For Indian finance teams, the practical challenge is not knowing the rule; it is identifying which vendors are 'specified persons' before each payment cycle and documenting the determination for audit.
Section 206C: Reconciling TCS Collected at Source for Indian Sellers and Buyers
Section 206C creates a dual reconciliation obligation: the seller must confirm that every rupee of TCS collected has been deposited and reported in Form 27EQ, while the buyer must verify that each TCS credit appears correctly in Form 26AS before claiming it in the ITR. For businesses dealing in scrap, motor vehicles, or overseas remittances, the volume and timing complexity of this matching exercise is significant.
TRACES Portal: How to Download and Reconcile TDS Data for Indian Finance Teams
TRACES (TDS Reconciliation Analysis and Correction Enabling System) is the Income Tax Department's central portal for every TDS function — from challan verification and Form 26AS to correction return filing and Section 206AB compliance checks. Finance teams that use TRACES only at year-end for ITR filing miss three quarterly reconciliation windows and accumulate discrepancies that deductors can no longer correct by the time they are found.
TDS Year-End Reconciliation: March 31 Close Checklist for Indian Finance Teams
March 31 closes the financial year but not the TDS cycle. The Q4 return is due 31 May, Form 16 by 15 June — yet the balance sheet must reflect TDS payable and receivable accurately at 31 March. For Indian finance teams, this gap between the book close date and the filing deadline creates specific reconciliation tasks that must be completed before accounts are signed off.
Best Reconciliation Software for Indian Businesses in 2025: A CFO Buyer Guide
The best reconciliation software for an Indian business is not determined by global feature rankings — it is determined by whether the platform handles India's compliance stack natively. TDS deduction chains, GSTR-2B ITC matching, NACH batch return classification, and UPI settlement netting each require specific matching logic that a generic reconciliation tool cannot configure without custom development. This guide helps CFOs and VP Finance evaluators ask the right questions before signing a contract.
How to Evaluate Reconciliation Software: A 10-Point Framework for Indian CFOs
Generic SaaS evaluation scorecards miss three structural requirements specific to India: statutory compliance handling for TDS and GST, support for Indian payment rails including NACH, UPI, and MT940 bank statements, and config-only deployment versus custom development. This framework gives CFOs and IT Heads the questions that surface these gaps before contract signature.
Excel vs Python vs Reconciliation Software: What Indian Finance Teams Should Use When
Choosing the wrong tool for reconciliation is not just an efficiency problem — it is a compliance risk. Excel works below 500 transactions per month. Python handles structured data but breaks on India statutory matching. Purpose-built software is the only viable option once volume, TDS, GSTR-2B, or audit trail requirements enter the picture.
How to Justify Reconciliation Software to Your Board: A CFO Playbook
Reconciliation software rarely fails on functionality — it fails to get approved because the business case is framed as an IT expense rather than a cost recovery exercise. Quantifying the four categories of reconciliation cost — staff time, statutory debt, audit risk, and close cycle delay — turns an intangible efficiency argument into a number the board can act on.
Reconciliation Software Implementation: What to Expect in 30-60-90 Days
A configuration-based reconciliation platform follows a predictable 30-60-90 day pattern from discovery to go-live. The milestones are data source mapping, matching rule configuration, parallel run, and sign-off — not build, test, and deploy. Understanding what each phase requires from the finance team makes the difference between a clean go-live and a delayed one.
Reconciliation Software ROI: How Indian Finance Teams Build the Business Case
ROI from reconciliation software is measurable through four cost categories that most Indian finance teams can quantify from existing data: staff hours spent on manual matching, reconciliation debt accumulated from unclaimed TDS and ITC, audit risk exposure from unreconciled compliance positions, and financial close delay caused by exception backlogs. This guide helps CFOs and Finance Controllers build the numbers before the board conversation.
Reconciliation Software vs ERP: Why Indian Finance Teams Need Both
The question finance teams ask when evaluating reconciliation software is usually some version of: 'We already have SAP — why do we need something else?' The answer lies in what an ERP is designed to do and what it is not. An ERP is a system of record for ledger entries. Reconciliation software is the matching layer that verifies what the ERP recorded against what banks, tax portals, and payment gateways actually processed.
15 Questions to Ask When Selecting a Reconciliation Vendor in India
Most vendor evaluation questionnaires for reconciliation software are generic SaaS checklists that miss the India-specific questions entirely. For Indian enterprises, 5 of the 15 questions on any evaluation scorecard must address TDS matching, GSTR-2B ITC reconciliation, NACH return code handling, data residency, and whether the vendor scopes the client's use case before configuring the engine.
SaaS vs On-Premise Reconciliation Software: What Indian Enterprises Should Choose
For most Indian enterprises, SaaS hosted on AWS Mumbai satisfies RBI data residency requirements, delivers a 2-to-4-week deployment, and shifts infrastructure maintenance to the vendor. On-premise or private cloud is the correct choice for a specific category of regulated entity — banks, insurance companies, PSUs with data sovereignty mandates — and a costly default for everyone else.
Security Checklist for Reconciliation Software: What Indian Enterprises Must Verify
Reconciliation software processes bank statements, TDS certificates, GST portal exports, and settlement reports simultaneously — the most concentrated set of sensitive financial data in an organisation. The security bar must match that data sensitivity, and for Indian enterprises, it must also satisfy RBI IT governance directions, SEBI cloud requirements, and DPDP Act 2023 obligations.
Advance Tax Reconciliation in India: Challan 280 Matching, CIN Tracking, and Form 26AS
Advance tax reconciliation connects four elements: the instalment amount calculated on estimated income, the Challan 280 payment made before the deadline, the CIN (Challan Identification Number) from the bank, and the credit that appears in Form 26AS. A shortfall at any instalment — or a Challan 280 that is not reflected in Form 26AS — has direct interest implications under Sections 234B and 234C. This guide covers the advance tax reconciliation process for Indian companies.
Bank Charges Reconciliation in India: Service Fees, GST on Charges, and Auto-Debit Matching
Bank charges — service fees, NEFT and RTGS transaction charges, cheque book charges, annual maintenance fees, and GST on all of the above — are among the most consistently mismatched items in Indian bank reconciliation. They arrive as auto-debits without prior invoice, carry GST at 18%, and must be allocated to the right expense ledger. This guide covers how bank charge reconciliation works in India and why it generates disproportionate exceptions.
Bank Statement Narration Patterns in India: How Reconciliation Systems Parse Them
Narration-based matching is the core challenge in Indian bank reconciliation. NEFT, RTGS, IMPS, UPI, and NACH credits each arrive with different narration structures from different banks — and none follow a single national standard. This guide covers the narration patterns from major Indian banks, how reconciliation systems extract match keys, and where narration parsing fails.
ECS to NACH Migration Reconciliation: Handling Dual-Running Periods and Mandate Transfer
When RBI mandated the migration from ECS (Electronic Clearing Service) to NACH, companies running large mandate books faced a dual-running period: ECS mandates still active, NACH mandates being registered, and both appearing in bank credits simultaneously. The reconciliation challenge during migration was matching collections that could arrive through either channel — with different file formats, different match keys, and different settlement timelines. This guide covers ECS to NACH migration reconciliation.
ESI Contribution Reconciliation in India: ESIC Challan Matching and Wage Month Verification
ESI contribution reconciliation requires matching the monthly ESIC challan payment — filed on the ESIC portal — to the bank debit and the ESI expense ledger, while verifying that covered employee headcount and wages align with payroll records. The threshold (employees earning ₹21,000/month or below) means the covered headcount changes every time an employee receives a salary revision, creating a moving match target that manual reconciliation handles poorly.
HDFC Bank Reconciliation: Statement Formats, CMS API, and Narration Patterns
HDFC Bank is the most widely used bank for enterprise current accounts in India. Its NetBanking, CMS (Cash Management Services), and MT940 export have specific narration formats and field structures that affect how reconciliation systems parse and match transactions. This guide covers HDFC Bank statement types, narration structures, CMS integration, and configuration details for automated reconciliation.
ICICI Bank Reconciliation: CIB Statement Format and Enterprise Account Matching
ICICI Bank's Corporate Internet Banking (CIB) platform has specific statement export formats and narration structures that affect enterprise reconciliation. ICICI's MT940 implementation uses /TXT/ prefix in the :86: tag — different from HDFC's /INF/ — and its NEFT/RTGS narrations follow a format that requires specific parser configuration. This guide covers ICICI Bank statement types, narration patterns, and what enterprise finance teams should configure for automated reconciliation.
MT940 Bank Statement Format in India: How It Enables Automated Reconciliation
MT940 is the SWIFT message format used by India's leading banks for enterprise statement export. Unlike PDF or CSV downloads, MT940 delivers structured, parseable transaction data that reconciliation engines consume directly — no screen-scraping, no manual field extraction. This guide covers how MT940 works, which Indian banks support it, and what it changes for automated bank reconciliation at scale.
NACH Mandate Management and Reconciliation: Active Mandates, Amendments, and Cancellations
NACH mandate management reconciliation is the process of keeping the mandate register — the internal record of all active mandates — aligned with NPCI's registered mandate database. A mandate that is active in the internal register but cancelled at NPCI generates a return code 25. A mandate that is registered at NPCI but missing from the internal register means EMI presentations are submitted without a valid mandate on file. This guide covers how mandate register reconciliation works.
NACH Reconciliation for NBFCs and Lenders: EMI Collection Matching and LMS Updates
For NBFCs and lenders, NACH reconciliation is not just a treasury function — it directly drives the loan management system (LMS) update that determines a borrower's Days Past Due (DPD) and NPA classification. A NACH return that is not reconciled and posted to the LMS within 24 hours means the DPD counter does not start, which understates portfolio risk. This guide covers NACH reconciliation for NBFCs, from batch submission to LMS update.
NACH Return Codes in India: Full Reference and Resolution Guide for Finance Teams
Every NACH debit return comes with a return reason code — a 2-digit number from NPCI that tells the presenting bank and the originator why the debit was rejected. The same return code drives the resolution action: code 01 (Insufficient Funds) is retriable, code 20 (Account Closed) is not. Finance teams that do not map return codes to resolution workflows manually work every return the same way. This guide covers the full NACH return code reference and the resolution logic for each.
Opening Balance Reconciliation in India: Resolving Month-Start Discrepancies
Opening balance reconciliation is the first control check of every new accounting period — confirming that the opening balance in the books matches the prior period's closing balance. For Indian companies running monthly reconciliation across multiple bank accounts, GST ledgers, and TDS receivables, opening balance discrepancies are the first detection point for prior-period errors that were not resolved. This guide covers the common causes and resolution sequence.
PF ECR Reconciliation in India: Matching EPFO Challan Returns to Books and Bank
Provident Fund reconciliation requires matching three sources: the ECR (Electronic Challan cum Return) filed on the EPFO portal, the bank debit for the PF challan amount, and the PF expense entry in the books. The TRRN (Transaction Reference Number) is the key that links all three. For companies with multiple establishment codes or employees on different wage structures, ECR reconciliation produces systematic exceptions that require structured resolution.
Salary and Payroll Bank Reconciliation in India: Bulk Transfer Matching and TDS Alignment
Salary disbursements generate some of the largest single-day bank debits for Indian companies — and some of the most persistent reconciliation exceptions. A bulk salary NEFT to 400 employees appears as a single bank debit but must align with an itemised payroll register that includes TDS deductions (Section 192), PF contributions, ESI deductions, and professional tax. This guide covers how salary payroll bank reconciliation works and where it breaks.
SBI Bank Reconciliation: Government Account Formats, YONO Business, and Statement Parsing
State Bank of India (SBI) is the primary bank for PSUs, government-linked companies, and many large Indian enterprises. Its YONO Business platform, CMP (Cash Management Product) service, and statement formats differ from private banks — particularly for government credits: PFMS disbursements, GST refunds, subsidy receipts, and TDS challan payments. This guide covers SBI bank reconciliation for enterprise finance teams.
Statutory Payment Reconciliation in India: Managing TDS, GST, PF, and ESI in One View
Indian companies make statutory payments to 5 or more authorities every month: TDS challan (TRACES), GST PMT-06 (GST portal), PF ECR (EPFO), ESI challan (ESIC), and advance tax (Income Tax). Each has a different portal, a different match key, and a different deadline. Without a single statutory payment register that tracks all five, the reconciliation function cannot confirm that every payment made was recorded correctly in every relevant ledger and portal.
Amazon Pay Settlement Reconciliation: Marketplace TCS, MDR, and Weekly Payouts
Amazon Pay settlement reconciliation differs depending on whether you are a third-party seller on Amazon's marketplace or a merchant using Amazon Pay as a checkout method on an external website. For marketplace sellers, the TCS deduction under GST Section 52 — applied at 1% on the taxable value of each transaction — creates a compliance reconciliation step that pure payment gateway settlements do not have. Both modes require reconciling a net settlement credit to transaction-level detail, but the data sources and compliance steps are materially different.
Bank Reconciliation Statement (BRS): Format and Preparation for Indian Companies
The Bank Reconciliation Statement is one of the oldest financial control documents — and one of the most frequently observed by statutory auditors. For Indian companies, the BRS must explain the difference between the cash book balance and the bank statement balance as at every period end. This guide covers the standard BRS format, the items that typically cause the difference, and the documentation standard required for statutory audit.
Cash Flow Reconciliation: Matching P&L to Actual Bank Movements
Cash flow reconciliation is the process of confirming that the cash movement shown in the cash flow statement — derived from the P&L and balance sheet — matches the actual bank movements recorded in the bank statements. Errors in underlying reconciliation (bank, AR, AP) propagate into the cash flow statement. This guide explains how to reconcile cash flow correctly for Indian organisations.
Cash-to-Bank Reconciliation for UPI and POS Transactions in India
UPI and POS collections have replaced cash for most Indian businesses — but they introduced new reconciliation complexity. UPI settlements are typically credited the next business day in bulk. POS terminal settlements arrive as a single daily batch with MDR deducted. Neither matches invoice-level data without a structured reconciliation process. This guide covers how to reconcile UPI and POS collections accurately.
Cashfree Settlement Reconciliation: T+1 Payouts and Exception Handling
Cashfree settlement reconciliation is the process of matching Cashfree's NEFT payouts — which arrive on a T+1 cycle as a standard feature — to individual orders in the settlement report. The faster settlement cycle creates a specific challenge: finance teams running day-old order exports against same-day bank credits find themselves reconciling against data that has not yet been consolidated. Cashfree also offers a separate Payouts product for bulk disbursements, which requires its own reconciliation track distinct from collection settlements.
Chargeback Reconciliation for Payment Gateways: A Finance Team Guide
Chargebacks are not just a customer service issue — they are a reconciliation issue. When a payment gateway deducts a chargeback from a future settlement, the finance team must match the deduction to the original transaction, reverse the revenue, and update the receivable. Unmatched chargebacks overstate revenue and distort cash. This guide covers how to reconcile chargebacks systematically for Indian businesses.
Chargeback reconciliation in India — matching disputes, deductions, and representment
Chargeback reconciliation in India requires matching each negative line item in a payment gateway settlement report to the original transaction, classifying it as a chargeback versus a refund or MDR adjustment, and tracking the dispute window and representment result. Finance teams at merchants operating across Razorpay, PayU, and Cashfree face this challenge every settlement cycle. Without order-level matching, chargeback deductions are routinely written off as unexplained variances.
Daily vs Monthly Reconciliation: When Each Approach Makes Sense
Daily reconciliation and monthly reconciliation are not interchangeable — they serve different risk profiles. A payment aggregator processing ₹10 crore in daily settlements cannot wait until month-end to discover a reconciliation error. A small manufacturer with 150 monthly invoices has no operational need for daily close. The right frequency depends on transaction volume, settlement timing, and regulatory exposure.
Debtors and Creditors Reconciliation: Ledger Matching Best Practices
Debtors and creditors reconciliation — matching your AR and AP ledgers against counterparty records — is the foundation of accurate financial reporting. In India, it is also a statutory audit requirement, a GST compliance check, and a TDS matching exercise simultaneously. This guide covers the process for both sides of the ledger.
Exception Management in Reconciliation: From Detection to Resolution
Most reconciliation processes are good at detecting exceptions — the items that did not match automatically. Fewer are good at resolving them systematically. An unresolved exception queue grows each month until it becomes the reconciliation backlog that consumes the team. This guide covers the full exception lifecycle: classification, routing, resolution, and prevention.
Fixed Asset Reconciliation: Register, Depreciation, and Physical Verification
Fixed asset reconciliation in India has three distinct components: reconciling the FA register to book value, reconciling the depreciation schedule to the Companies Act or Income Tax Act rates, and verifying physical assets against the register. Each has different data sources and different consequences when it fails. This guide covers all three.
Flipkart Seller Settlement Reconciliation: TCS, Fees, and Returns
Flipkart seller settlement reconciliation requires unpacking a single weekly bank credit into four separate deduction categories before any ITC or TCS adjustment can be claimed. Each category — marketplace commission, TCS under Section 52, return adjustments, and shipping charges — maps to a different ledger entry and a different compliance obligation.
Forex Reconciliation for Indian Companies: Matching Foreign Currency Transactions
Indian companies receiving or making foreign currency payments face a reconciliation challenge that domestic payments do not: the same transaction amount creates two different rupee values depending on whether you use the invoice rate, the bank's conversion rate, or the RBI reference rate. Exchange rate differences, forward contract settlements, and NOSTRO account balances all require separate reconciliation logic under FEMA.
Intercompany Reconciliation in India: Group Finance Complexity
Intercompany reconciliation in India is harder than in most markets because every transaction between group entities carries additional tax complexity: GST must be charged even on intercompany supplies, TDS applies to professional fees and contractor payments between related parties, and transfer pricing documentation must reconcile with the actual transaction amounts. This guide covers all three dimensions.
Invoice Matching With TDS: Net vs Gross Reconciliation for Indian Finance Teams
The most common Indian reconciliation failure is not a process breakdown — it is a matching logic error. When a client pays ₹90,000 against a ₹1,00,000 invoice after deducting 10% TDS, a generic matching tool flags a ₹10,000 mismatch. The correct logic matches the gross invoice against the net credit plus the TDS receivable. This guide explains how net-vs-gross matching works and why section-level rules are essential.
IPO Reconciliation: What Finance Teams Must Do Before Filing the DRHP
An IPO DRHP requires three years of restated financials — and each set of financials must pass scrutiny from SEBI, the merchant banker, and the statutory auditor. Reconciliation gaps that are tolerable in a private company become material disclosures in a public filing. This guide covers what Indian finance teams must reconcile before initiating the DRHP process.
Manual vs Automated Reconciliation: The True Cost Comparison
Most Indian finance teams know that manual reconciliation is slow. Fewer have calculated what it actually costs — in staff hours, missed ITC, unclaimed TDS credits, and GST penalties. This comparison covers the real numbers on both sides and the framework for deciding when automation pays for itself.
MDR fee reconciliation — verifying gateway charges against contracted rates
MDR fee reconciliation in India is the process of verifying that every Merchant Discount Rate deduction in a payment gateway settlement matches the contracted rate for that specific transaction type — credit card, debit card, UPI, net banking, or international card. MDR is not a single flat rate, and billing errors where the wrong rate is applied to a transaction type are a consistent source of recoverable cost. This guide covers the reconciliation workflow and the ITC implications of GST on MDR.
Meesho Seller Reconciliation: Handling High Return Rates and TCS Deductions
Meesho seller reconciliation is complicated by two factors that operate independently of each other: high return rates in fashion and lifestyle categories that can reduce weekly settlements to near-zero, and TCS deducted on forward sales that still appears in GSTR-2B even when the underlying order is returned. Tracking these two flows separately is the core of the reconciliation task.
Month-End Close Reconciliation Checklist for Indian Finance Teams
Month-end close in India requires completing four reconciliation workstreams in sequence — bank, TDS, GST, and platform settlements — before sign-off. Each has a different deadline, a different data source, and different consequences for delays. This checklist covers all four in the order they should run.
Multi-Bank Reconciliation in India: How to Manage Multiple Bank Accounts
Most Indian companies with annual turnover above ₹50 crore operate 5–15 bank accounts: current accounts with multiple banks, NACH collection accounts, salary disbursement accounts, GST refund accounts, and escrow accounts. Reconciling each account separately — bank by bank, team by team — creates a fragmented cash picture and a reconciliation process that grows linearly with account count. This guide covers how to structure multi-bank reconciliation for a unified cash view.
Netting Reconciliation in India: How to Handle Net Payments Between Counterparties
Netting — offsetting amounts owed between two parties and settling only the net difference — is common in group companies, marketplace platforms, and long-term client relationships. It simplifies cash flows but complicates reconciliation: a single bank credit of ₹45,000 may represent a gross receivable of ₹75,000 netted against a gross payable of ₹30,000. Reconciliation must handle both the individual transactions and the net settlement.
Nodal and Escrow Account Reconciliation: RBI Compliance for Indian Businesses
Nodal and escrow accounts carry regulatory obligations that ordinary bank accounts do not. RBI regulations for payment aggregators require that all buyer funds collected are held in a nodal account and settled to merchants within specified timelines. RERA regulations require 70% of home buyer payments to be held in an escrow. Both require reconciliation that is auditable not just internally — but by the regulator. This guide covers the reconciliation requirements for nodal and escrow accounts in India.
Partial Payment Reconciliation: How to Allocate and Match in Indian Finance
Partial payments — where a client pays less than the full invoice amount — are among the most common sources of AR reconciliation failures in Indian companies. The failure is not in identifying the payment; it is in allocating it correctly: which invoice does the partial payment apply to, does TDS apply to the full invoice or the partial amount, and how is the remaining balance tracked? This guide covers correct allocation logic for Indian AR teams.
PayU Settlement Reconciliation: Matching Nodal Bank Credits to Transaction-Level Payouts
PayU settlement reconciliation is the process of reconciling NEFT credits from PayU's nodal bank account to individual transaction records in the PayU settlement report. Every PayU settlement credit in your bank account represents a batch of captured transactions, net of MDR and GST on MDR — and the 18% GST charged on MDR is recoverable as ITC for registered businesses, but only if the settlement report is reconciled to the GST invoice PayU issues.
Reconciliation in PE-Backed Companies: Meeting Investor Reporting Standards
PE investors impose reporting standards that most Indian founder-led companies were not built for — monthly close in 5 days, board packs by the 10th, and clean audit trails for every number in the financial summary. Reconciliation is the bottleneck. This guide covers how PE-backed finance teams structure reconciliation to meet these demands without growing headcount proportionally.
Razorpay Settlement Reconciliation: Unpacking Net Payouts to Individual Orders
Razorpay settlement reconciliation is the process of matching a single NEFT bank credit — the net payout Razorpay sends every settlement cycle — back to the individual orders, fee deductions, and refund adjustments that constitute it. The settlement report, exported from the Razorpay Dashboard, is the primary document for this work. Without it, the bank credit is an opaque lump sum that cannot be posted to the correct revenue and expense accounts.
Reconciliation Audit Trail: What Regulators Expect in India
A reconciliation audit trail is not just a record of what matched — it is a queryable history of every matching decision, every exception classified, every override made, and every approver who signed off. Indian regulators under the Income Tax Act, GST framework, and Companies Act each have specific expectations for what this trail must contain and how long it must be retained.
Reconciliation Automation ROI: A Framework for Indian Finance Leaders
Building a business case for reconciliation automation requires three numbers: current cost, software cost, and payback period. For most Indian organisations processing 500+ transactions per month, the payback is 6–12 months. This guide provides the framework and the calculation methodology.
Reconciliation Benchmarks for Indian Finance Teams: What Good Looks Like
Most Indian finance teams do not know whether their reconciliation performance is good or poor — they have no external benchmark to compare against. This guide provides concrete reconciliation benchmarks for Indian businesses: match rates by reconciliation type, days-to-close, exception resolution time, and staff productivity ratios. Use these to assess current performance and set improvement targets.
Reconciliation Debt: What It Costs Indian Companies Every Year
Reconciliation debt is the accumulated backlog of unmatched transactions — TDS entries without Form 26AS credits, ITC claimed without GSTR-2B support, bank credits with no corresponding ledger entry. Unlike financial debt, it earns no interest in your favour. It costs interest, penalties, and write-offs. This guide explains how it builds and how to eliminate it.
Top 10 Reconciliation Errors That Trigger GST Notices
Most GST demand notices are not the result of intentional tax avoidance — they result from reconciliation errors. A GSTR-2B mismatch, a wrong TDS section rate applied to an invoice, or a platform settlement posted to the wrong period are the typical triggers. This guide covers the 10 errors most likely to generate a notice, and how to prevent each one.
Reconciliation Infrastructure vs Reconciliation Software: A Critical Distinction
Reconciliation software solves a specific matching problem: bank vs ledger, or TDS vs Form 26AS. Reconciliation infrastructure solves the class of problem: any financial matching requirement, across any data source, with India-specific rules configurable by preset rather than by custom code. The distinction matters when you are choosing between tools.
Reconciliation KPIs for Indian Finance Teams: Metrics, Targets, and Measurement
Reconciliation is one of the few finance functions that can be fully measured — every item either matches or it does not, every exception either resolves within SLA or it does not, every period closes by day 5 or it does not. Yet most Indian finance teams do not track reconciliation KPIs at all. The result: reconciliation quality is assessed retrospectively (at the audit) rather than proactively. These are the KPIs that change the dynamic.
What CFOs Get Wrong About Reconciliation: 7 Costly Misconceptions
Reconciliation misconceptions at the CFO level are more expensive than process failures at the analyst level — because misconceptions about what reconciliation is determine how much investment it receives and how the function is structured. These seven misconceptions are the most common reasons Indian companies carry unnecessary reconciliation debt and face preventable audit findings.
Reconciliation Patterns Indian CFOs Should Track
Reconciliation is a function that most CFOs review by exception — a demand notice arrives, an audit observation appears, and the reconciliation process is investigated. The CFOs who prevent these outcomes track reconciliation at the pattern level: match rates by type, exception aging by category, and debt accumulation velocity. These are the patterns that predict problems before they become demands.
Reconciliation in SAP vs Oracle vs Tally: What Finance Teams Need to Know
SAP, Oracle, and Tally are accounting systems — they record what happened. Reconciliation verifies that what happened matches external records: Form 26AS, GSTR-2B, bank statements. All three ERPs have built-in reconciliation capabilities, but all three have gaps that are specific to India's tax-at-source framework. This guide explains those gaps.
Refund reconciliation for payment gateways — matching deductions to credit notes
Refund reconciliation for payment gateways in India requires matching three simultaneous obligations: the negative deduction in the settlement report, the credit note issued to the customer under Section 34 of the CGST Act, and the proportional ITC reversal in GSTR-3B. Finance teams that treat gateway refunds as simple settlement adjustments miss the GST liability embedded in each refund. This guide covers the full matching workflow for full, partial, and gateway-initiated refunds.
10 Signs Your Reconciliation Process Is Broken
Reconciliation failures don't announce themselves — they accumulate quietly as missed deadlines, unexplained variances, and a finance team that never fully catches up. This guide covers the 10 indicators that identify a broken reconciliation process before the audit does.
Stripe India Settlement Reconciliation: Forex, FIRC, and Inward Remittance Matching
Stripe India settlement reconciliation involves three distinct tasks that standard accounts receivable workflows do not address: matching each Stripe payout_id to a bank SWIFT credit, reconciling the forex rate difference between invoice date and settlement date, and obtaining FIRC documentation for FEMA compliance on export proceeds. Each task requires a separate data source and a different reconciliation method.
TCS reconciliation for e-commerce sellers — GSTR-8 to GSTR-2B to GSTR-3B
TCS ecommerce reconciliation in India is a seller-side obligation that arises from Section 52 of the CGST Act: every rupee of Tax Collected at Source deducted by an e-commerce operator in the settlement report must reconcile against the GSTR-2B credit auto-populated from the operator's GSTR-8 filing. Sellers on Amazon, Flipkart, and Meesho cannot claim TCS credit in GSTR-3B without first confirming that the operator has filed and the correct amount appears in GSTR-2B. This guide covers the full three-source reconciliation workflow.
Tolerance Matching in Reconciliation: Setting Thresholds for Indian Finance Teams
Not every ₹1 difference in reconciliation needs a human reviewer. Tolerance matching — automatically resolving small variances that fall within pre-defined thresholds — is a standard practice that reduces exception queues by 15–30% without compromising control. The challenge is setting the right thresholds for Indian-specific reconciliation: TDS rounding, MDR calculation differences, and GST rounding rules all create predictable small variances that qualify for tolerance auto-resolution.
UPI Settlement Reconciliation — Matching High-Volume T+0 Transactions to Books
UPI settlement reconciliation India requires a different approach from batch gateway reconciliation: each transaction settles individually at T+0, generating its own bank credit line with a 12-digit UPI Reference ID. At scale, the volume of individual credits — not the complexity of any single transaction — is what makes manual matching unworkable and automated reconciliation necessary.
Virtual Account Reconciliation in India: How Auto-Matching Works
Virtual accounts solve one of Indian reconciliation's oldest problems: NEFT and RTGS payments that arrive without a clear invoice reference. By assigning each customer a unique virtual account number, incoming payments are automatically tagged to the right customer — eliminating the narration-parsing step that requires manual reconciliation. This guide covers how virtual account reconciliation works and where it fails.
What Is Financial Reconciliation? A Complete Guide for Indian Finance Teams
Financial reconciliation in India is not a single process — it is three overlapping processes running simultaneously: bank reconciliation, TDS reconciliation, and GST reconciliation. Each has different data sources, different timing, and different regulatory consequences when it fails. This guide explains all three and why they require a different approach in India.
What Is a Reconciliation Engine? How It Differs from Spreadsheet Tools
A reconciliation engine is not a faster spreadsheet. It is a different class of tool — one that applies configurable matching rules across multiple data sources simultaneously, classifies exceptions by type, and routes unmatched items to the correct reviewer. This guide explains the components of a reconciliation engine and when it becomes necessary.
Why Reconciliation Is Different in India: TDS, GST, and Platform Complexity
A bank reconciliation guide written for a US or UK business has one primary matching challenge: bank statement vs cash ledger. In India, the same process must handle TDS deductions, GST timing mismatches, platform settlement netting, and NACH batch disaggregation — simultaneously, with regulatory consequences for each. This guide explains the structural difference.
Year-End Reconciliation Guide for Indian Companies: FY Close Best Practices
India's financial year closes on March 31. For finance teams, the final 4–6 weeks are a race to resolve TDS mismatches, complete GST annual return reconciliation, and close books for statutory audit. This guide covers the critical reconciliation tasks — in sequence — for an orderly FY close.
Blocked ITC Under Section 17(5): What Cannot Be Claimed and Why
Section 17(5) of the CGST Act lists categories of inputs and input services where ITC is blocked regardless of how the expense is used in your business. Finance teams regularly claim credit on restaurant bills, employee cab services, and club memberships — only to face demand notices during audits. Understanding what is blocked, what exceptions apply, and how to reverse ineligible credit in GSTR-3B Table 4(B) is foundational to clean GST compliance.
E-Invoice Reconciliation in India: IRN, GSTR-1, and GSTR-2B Alignment
E-invoicing was supposed to make reconciliation automatic. In practice, it introduced a new set of mismatches: cancelled IRNs still appearing in GSTR-2B, invoices generated across multiple IRP portals, and amendments that require credit or debit notes because e-invoices cannot be modified after IRN generation. For businesses above the ₹5 Crore turnover threshold, e-invoice reconciliation is now a distinct workstream alongside conventional GST matching.
Form 16 vs Form 26AS: What to Do When They Don't Match
Form 16 and Form 26AS should show identical TDS figures for salary income, but they frequently diverge — with consequences that extend to demand notices after ITR filing. The discrepancy is almost always caused by an error in the employer's TDS return: a late filing, a PAN entry error, or a challan mismatch that prevents Form 26AS from reflecting what the employer has already certified in Form 16. Knowing the exact cause determines who to contact and how quickly it can be resolved.
GSTR-9 Reconciliation: Aligning the Annual Return With Monthly Filings
GSTR-9 reconciliation is not a single match — it is three layered comparisons run across 12 months of outward supply data, ITC claims, and tax payments. Filing errors discovered at the annual return stage are harder to correct than monthly mismatches, and for businesses with turnover above ₹5 Crore, differences between GSTR-9 and GSTR-9C attract auditor scrutiny and demand notices. Getting the annual return right depends on how cleanly the monthly cycle was managed.
GST Credit Note Reconciliation: Supplier Amendments and ITC Reversal
A GST credit note from a supplier triggers an ITC reversal obligation on the buyer's side. If the buyer misses the reversal — or posts it in the wrong month — the resulting GSTR-3B under-reversal becomes a demand in the next GST audit. The reconciliation task is matching every credit note that appears in GSTR-2B to a corresponding reversal in GSTR-3B Table 4(B), within the time limits imposed by Section 34.
GST Refund Reconciliation: Tracking Claims from RFD-01 to Bank Credit
A GST refund claim does not end at RFD-01 filing. The amount you claim, the amount the officer sanctions, the provisional credit released, and the final bank credit are four separate figures — and they rarely all agree. Reconciling each stage is essential for exporters, manufacturers with inverted duty structures, and businesses with excess cash ledger balances.
GST TCS Reconciliation for E-Commerce Sellers: Claiming the Credit
Every e-commerce seller in India receives settlement payouts net of TCS deducted under Section 52 of the CGST Act. That deduction does not disappear — it accumulates as an ITC credit in GSTR-2B. The reconciliation task is to verify that the credit deposited by the platform against your GSTIN exactly matches what you received, across every marketplace you sell on.
GSTR-1 vs GSTR-3B Reconciliation: Resolving the Output Tax Mismatch
GSTR-1 records every B2B and B2C invoice raised in the period, while GSTR-3B summarises the tax actually paid to the government. When these two returns disagree on output tax liability, GSTN flags the discrepancy and, in persistent cases, issues scrutiny notices. Reconciling them monthly — before scrutiny begins — is the first line of defence for any GST-registered business in India.
GSTR-2A vs GSTR-2B: Which Statement Controls ITC Claims?
GSTR-2A and GSTR-2B both show inward supply data, but they serve entirely different purposes. GSTR-2A is a live feed of supplier filings — useful for monitoring, but not the compliance document. GSTR-2B is the locked monthly snapshot that, since January 2022, determines exactly how much ITC a business can claim under Rule 36(4) of the CGST Rules.
IGST, CGST, and SGST Reconciliation: Managing Multi-State Tax Accounts
A business registered in five states runs five separate GSTR-3B filings, five electronic credit ledgers, and three tax head buckets — IGST, CGST, and SGST — each with distinct ITC set-off rules. The reconciliation problem is not just whether totals agree: it is whether the right tax head was charged on each supply, and whether the resulting ITC was applied in the legally correct offset sequence.
ITC Reversal Under Rule 42 and 43: How the Calculation Works
Rule 42 and Rule 43 of the CGST Rules require ITC to be partially reversed when inputs, input services, or capital goods are used for both taxable and exempt or non-business purposes. The calculation involves apportioning common credits using revenue ratios, reporting reversals in GSTR-3B Table 4(B) every month, and reconciling provisional monthly reversals against actual annual proportions in GSTR-9. Most mismatches originate in the common cost pool — electricity, rent, professional retainers — where purpose apportionment is genuinely difficult.
TDS Challan Mismatch: How to Identify and Resolve Errors
A TDS challan mismatch occurs when the challan details entered in a TDS return do not match the actual deposit recorded in OLTAS, blocking Form 26AS from updating for the deductee. Three error types — wrong BSR code, wrong serial number, and amount difference — account for the majority of delayed or missing TDS credits in Indian enterprise finance. Each requires a different detection approach and a C2 correction return filed by the deductor on TRACES.
TDS Correction Return: How to Fix Errors After Filing
Filing a TDS correction return on TRACES is the only way to fix errors in an already-submitted quarterly TDS return. There are five correction types — C1 through C9 — each targeting a specific class of error. Getting the correct type matters: using C2 when C1 is needed, or vice versa, results in a rejected correction and a longer resolution timeline. This guide covers when each type applies, how to prepare the corrected FVU file, and what to verify after submission.
TDS Lower Deduction Certificate Under Section 197: Process and Reconciliation
A lower deduction certificate under Section 197 is the legal mechanism by which a recipient demonstrates to their Assessing Officer that the standard TDS rate would result in over-deduction relative to their actual tax liability for the year. The certificate, once issued, must be furnished to every deductor who makes a payment to the recipient—and each deductor must independently verify it on TRACES before applying the reduced rate.
TDS Quarterly Return Reconciliation: Process and Common Errors
TDS quarterly return reconciliation requires matching three data sets in sequence: TDS deducted in the books, the return filed with the government, and the credits that appear in counterparty Form 26AS statements. When any of the three diverge, it generates either a compliance exposure for the deductor or a tax credit problem for the deductee. The Q4 return — due 31 May — is the highest-risk filing period because errors affect deductees' ITR season credits.
TDS Receivable Ledger Reconciliation: Matching Books to Form 26AS
The TDS receivable ledger records the tax deducted by clients and counterparties that the company expects to claim as a credit in its ITR. Reconciling this ledger against Form 26AS is not a year-end exercise — it is a continuous process that identifies missing credits, partial credits, and PAN errors before they create ITR filing problems. At scale, the match requires TAN-level matching logic and tolerance handling that manual spreadsheet approaches cannot provide reliably.
TDS Under Section 194A: Interest Income Reconciliation
Section 194A covers TDS on interest income from sources other than bank savings accounts. The threshold differs significantly between bank FDs and NBFC interest, and the deduction obligation often falls on the borrower rather than the lender. Finance teams in conglomerates with inter-company loans and businesses borrowing from NBFCs encounter distinct reconciliation challenges that this guide addresses.
TDS Under Section 194C: Contractor Payment Reconciliation
Section 194C governs TDS on payments to contractors and sub-contractors. Finance teams reconciling contractor bills frequently encounter rate mismatches, wrong TAN references, and multi-branch deduction chains that cause Form 26AS discrepancies. This guide explains where those errors originate and how to resolve them efficiently.
TDS Under Section 194H: Commission and Brokerage Reconciliation
Section 194H applies to TDS on commission and brokerage payments at a flat 5% rate. Real estate developers, insurance companies, and direct selling organisations encounter reconciliation complexity because commission amounts vary each month with deal volume. This guide explains the section, where Form 26AS matching breaks down, and how to resolve it.
TDS Under Section 194I: Rent Payment Reconciliation
Section 194I governs TDS on rent payments, with split rates for buildings versus plant and machinery. Corporate finance teams managing office leases across multiple cities encounter multi-TAN Form 26AS entries, co-working classification disputes, and the common error of deducting TDS on security deposits. This guide addresses each scenario with reconciliation steps.
TDS Under Section 194J: Professional Services Reconciliation
Section 194J covers TDS on professional fees and technical service charges. Since the Finance Act 2020 split the rate into 10% for professional services and 2% for technical services, misclassification has become the primary source of reconciliation discrepancies for IT services firms and management consultancies. This guide explains the distinction and how to close the gap.
TDS Under Section 194N: Cash Withdrawal Reconciliation
Section 194N is unusual in one structural respect: the bank—not the account holder—is the deductor. Finance teams at construction companies, logistics operators, and real estate developers who maintain large cash operations often discover 194N TDS debits in their bank statements without prior notice, and then face the task of matching those debits to Form 26AS Part A1 entries under the bank's TAN.
TDS Under Section 194Q: Purchase Reconciliation for Large Buyers
Section 194Q shifts the TDS obligation to the buyer—a reversal of the usual pattern where the payer of services deducts tax. For companies with annual turnover above ₹10 crore, every large goods supplier relationship must be tracked cumulatively across the financial year to identify the precise transaction where the ₹50 lakh threshold is crossed and deduction must begin.
TDS Under Section 194R: Benefit and Perquisite Reconciliation
Section 194R, effective from 1 July 2022, brought distributor gifts, dealer travel sponsorships, and high-value product samples into the TDS framework for the first time. The section requires the provider of the benefit—not the recipient—to deduct 10% TDS, and in cases where the benefit is non-cash, the deductor must gross up and pay the TDS from their own funds.
TDS Under Section 195: Non-Resident Payment Reconciliation
Every payment remitted to a non-resident is potentially subject to TDS under Section 195—there is no minimum threshold. The applicable rate depends on whether India has a Double Taxation Avoidance Agreement with the recipient's country, and reconciling these deductions across Form 26AS and foreign counterparty records adds a layer of complexity that domestic TDS sections do not have.
What Is a Reconciliation Statement? Definition and Types for Indian Finance Teams
A reconciliation statement is a formal financial document that compares two independent records of the same transactions — such as a bank statement against a ledger, or Form 26AS against TDS receivable — and documents every identified difference with its classification and resolution status. In Indian enterprise finance, reconciliation statements are both an internal control requirement and, in several cases, a statutory obligation.
What Is Automated Reconciliation? How It Differs from Manual Matching
Automated reconciliation is the use of software to ingest financial records from two or more data sources, apply configurable matching rules, identify matched and unmatched items, classify exceptions by variance type, and present a structured exception queue for human review. It replaces the manual process of opening two spreadsheets and performing VLOOKUP or visual comparison row by row — a method that becomes both unreliable and unsustainable above roughly 500 transactions per month.
What Is Bank Reconciliation? Definition and Process for Indian Finance Teams
Bank reconciliation is the process of comparing a company's internal cash ledger with the corresponding bank statement entries, identifying and explaining every difference. For Indian finance teams, the process extends beyond standard timing differences to cover UTR-based transaction matching, UPI references, and NACH batch credits — each requiring a distinct matching approach.
What Is Form 26AS? The Tax Credit Statement Explained for Indian Businesses
Form 26AS is the consolidated annual tax credit statement issued by the Income Tax Department of India, linked to a taxpayer's PAN. It consolidates TDS deducted by all deductors, TCS collected by sellers, advance tax paid, and refunds received — and serves as the primary document for reconciling TDS receivable in the company's books against credits actually deposited with the government.
What Is GSTR-2B? The Auto-Populated ITC Statement Explained
GSTR-2B is a static, auto-populated statement of available Input Tax Credit (ITC) generated for every GST-registered taxpayer from the 13th or 14th of the following month. Unlike GSTR-2A, which updates continuously as suppliers file, GSTR-2B is a fixed snapshot for the return period — and since January 2022, ITC claims are restricted to what appears in GSTR-2B under Rule 36(4), with no provisional buffer permitted.
What Is ITC in GST? Input Tax Credit Explained for Indian Businesses
Input Tax Credit (ITC) is the mechanism under India's GST framework that allows a registered business to offset the tax paid on purchases and inward supplies against the GST collected on its sales. The net difference — output tax minus eligible ITC — is the actual liability payable to the government. Since January 2022, ITC claims are restricted to amounts appearing in GSTR-2B, making supplier-level reconciliation a statutory requirement rather than an optional audit step.
What Is NACH in Banking? National Automated Clearing House Explained
NACH — National Automated Clearing House — is the centralised clearing infrastructure operated by NPCI that replaced the legacy Electronic Clearing Service system across Indian banking. It standardises recurring payment collection and disbursement through a single clearing hub with uniform file formats, UMRN-based mandate tracking, and T+1 return cycles.
What Is a Payment Gateway Settlement? How Online Payments Reach Your Bank Account
A payment gateway settlement is the process by which a payment aggregator collects customer payments, deducts its charges — MDR, GST on MDR, platform fees, TCS for marketplace operators — and transfers the net amount to the merchant's designated bank account. Settlement typically occurs on a T+1 to T+7 cycle depending on the gateway and merchant tier, and the settlement file provided by the gateway is the primary document for order-level reconciliation.
What Is TDS Deduction? How Tax Deducted at Source Works in India
TDS — Tax Deducted at Source — is a withholding mechanism under the Income Tax Act, 1961, where the entity making a payment deducts a prescribed percentage of tax before crediting the payee. The deducted amount is deposited with the government under the deductee's PAN, and the deductee claims it as a credit when filing the income tax return. PAN errors and deposit timing gaps are the two primary causes of TDS reconciliation mismatches.
What Is a UTR Number? Unique Transaction Reference in Indian Banking
A UTR — Unique Transaction Reference — is the payment-system-level identifier assigned to every interbank fund transfer in India. It is generated by the clearing infrastructure (NEFT, RTGS, IMPS, or UPI), not by the sending bank or application, making it the only reference that both the sender's and receiver's banks can independently verify for a given transaction.
TDS Reconciliation: Matching Form 26AS to Your Books
How Indian finance teams reconcile TDS deducted at source against Form 26AS — variance types, process steps, and where manual matching breaks at scale.
GSTR-2B Reconciliation: Claiming ITC Without the Risk
Step-by-step guide to reconciling GSTR-2B auto-populated data with your purchase register before claiming GST input tax credit.
Platform Settlement Reconciliation for D2C and E-Commerce
Aggregators pay net after deducting MDR, GST on MDR, TCS, and platform fees. Here is how to match every rupee back to the originating order.
Bank Reconciliation Process: What Changes at Enterprise Scale
Basic bank reconciliation works for small businesses. This article explains where the process breaks for enterprises and what a structured approach looks like.
NACH Reconciliation: Managing Batch Return Matching at Scale
NACH batch returns carry reason codes, partial settlements, and timing mismatches. How NBFCs and lenders build a structured reconciliation process.
See how TransactIG handles reconciliation for your industry
TransactIG is configurable for your ERP, your bank feeds, and your compliance requirements. Most implementations complete in 2–4 weeks without code development.