Year-end accounts payable reconciliation in India is harder than any other month-end close because three compliance obligations, GSTR-2B vs books reconciliation, TDS closure, and MSME 43B(h) dues settlement, converge in the same two-week window. Each one draws on data the AP function owns, and each one exposes a different process gap that existed quietly throughout the year. Finance teams that find it manageable are not working faster in March; they are running cleaner AP the other eleven months.
The last two weeks of March look familiar in most AP functions: outstanding vendor statements piling up, a GSTR-2B mismatch that nobody flagged in November, TDS certificates that have not arrived, and a finance controller asking whether any MSME vendors are still unpaid. The pressure is real, but the source is not the calendar. It is the accumulated effect of process gaps that were invisible when transaction volumes were lower and the FY deadline was months away.
Year-end AP reconciliation in India is not a harder version of month-end close. It is a different category of work, one that surfaces three compliance obligations simultaneously, each with a different regulatory owner, a different data source, and a different consequence if missed.
Three year-end AP reconciliation obligations, one fortnight
The Indian financial year ends on March 31. AP teams are not unusually busy in the final two weeks because invoice volumes spike. Three distinct regulatory deadlines converge within that window, and each draws on data that only the AP function holds.
The first is GSTR-2B reconciliation. Under GST Rule 36(4), effective January 1, 2022, ITC can only be claimed in GSTR-3B to the extent it appears in GSTR-2B, the auto-populated purchase register generated from supplier filings. The provisional ITC allowance that previously permitted claims beyond matched amounts no longer applies. GSTR-2B is generated on the 14th of the following month, so a vendor who has not filed GSTR-1 for a given period leaves the corresponding ITC unclaimable until they do. AP teams must reconcile their purchase register against GSTR-2B before filing GSTR-3B each month. Teams that skip this monthly reconciliation arrive at March with twelve months of mismatches and no time to recover them.
The second is TDS closure. Finance teams processing vendor payments above threshold amounts are required to deduct tax at source, deposit it, and file Form 26Q quarterly. The fourth quarter covers January through March and closes after March 31. Late filing of Form 26Q attracts a fee of ₹200 per day under Section 234E, capped at the total TDS amount for the quarter, with an additional penalty of ₹10,000 to ₹1,00,000 possible under Section 271H. Interest on late deduction runs at 1% per month; on late deposit at 1.5% per month. Under Section 40(a)(ia), failure to deduct or deposit TDS can result in 30% of the related expense being disallowed in taxable income. Gaps in the vendor master, incorrect PAN data, or missed deductions produce errors that require form corrections after the quarter closes.
The third is MSME 43B(h) dues settlement. Section 43B(h), applicable from FY 2023-24 onwards, disallows a deduction in the current financial year for any payment to a Micro or Small Enterprise that exceeds the timeline set in Section 15 of the MSMED Act: 15 days where no written agreement exists, 45 days where one does. The disallowance reverses in the financial year in which the payment is actually made, regardless of accounting method. Unlike other provisions under Section 43B, there is no extension available by filing the return before the due date. Payment must clear within the prescribed window to be deductible in the current FY. The clause applies to Micro and Small enterprises engaged in manufacturing or services; dues to wholesale and retail traders are generally excluded. It applies only to invoices raised from April 1, 2023 onwards and does not extend to capital expenditure.
An example: an invoice dated March 1, 2024, under a 45-day agreement, has a due date of April 15, 2024. If payment is made in June 2024, the expense is disallowed in FY 2023-24 and allowed as a deduction in FY 2024-25. The same logic applies to any MSME invoice outstanding as of March 31, 2026 where the 15 or 45-day window has already passed.
These three obligations do not share data sources, regulatory timelines, or consequences. They share one thing: the data they depend on lives entirely inside the AP function.
What each obligation reveals
GSTR-2B mismatches at year-end point to one root cause: vendor GST filing behaviour was not monitored during the year. When a vendor files their GSTR-1 late or incorrectly, the buyer’s GSTR-2B does not reflect the corresponding invoice. AP teams that check GSTR-2B monthly catch this when it is still correctable. Teams that check it in March find months of accumulated discrepancies and no time to resolve them with vendors before the books close.
TDS reconciliation gaps point to a different problem: stale vendor master data. Missing PAN numbers, incorrect PAN-name combinations, and vendor category misclassifications produce TDS errors that surface during Form 26Q filing. Vendor master data is typically cleaned at onboarding and not refreshed after that. Without a structured annual verification process, the fourth quarter filing becomes a data correction exercise rather than a reconciliation.
MSME dues at year-end point to the most structural gap: the AP function did not know which vendors were registered MSMEs. The Udyam registration database is public, but AP teams do not commonly tag vendors by MSME status at onboarding or verify it annually. Without that flag, payment prioritisation cannot account for 43B(h) implications, and the finance team discovers the exposure only when preparing the year-end schedule. The operational detail on managing this throughout the year is covered in the MSME 45-day payment rule article. For how GSTR-2B matching requirements evolved between FY22 and FY26, see GST AP compliance changes FY22 to FY26.
Each of these is a March symptom of a year-round process design problem. Treating them as year-end tasks is the reason they accumulate.
What automation changes — and what it does not
AP automation does not make year-end reconciliation faster. It makes the work smaller by moving it out of March entirely.
GSTR-2B matching at invoice level, run continuously through the year, means mismatches surface when they are still correctable. A vendor who has not filed for two consecutive months is visible in October, not March. The AP team can follow up, withhold payment, or flag the ITC risk before it compounds.
Vendor master enrichment at onboarding, with annual verification, means Udyam registration status, PAN validity, and TDS applicability are maintained as live data rather than assumptions carried from the original setup. Payment workflows that apply MSME 43B(h) rules by vendor category remove the manual tracking burden and make the dues schedule a byproduct of normal payment processing, not a year-end exercise.
What automation does not change: the judgment calls. Disputed ITC claims require a CA to assess recoverability. TDS applicability on new payment categories, such as software subscriptions or cloud infrastructure costs, is not always settled and should not be automated without advice. The 43B(h) disallowance schedule requires sign-off from the statutory auditor and tax advisor. Automation handles data integrity and process compliance. It does not substitute for professional judgment on regulatory interpretation.
The process architecture for continuous compliance tracking across the full month-end close cycle is covered in month-end close automation for mid-market India. Finance teams evaluating whether their AP infrastructure can support this model can book a demo with IQInvoice to see how the reconciliation workflows operate in a mid-market environment.
Key observations
- Year-end AP reconciliation in India stacks three distinct compliance obligations in the same two-week window: GSTR-2B matching, TDS closure, and MSME 43B(h) dues settlement.
- Each obligation reveals a different structural gap: vendor GST filing behaviour unmonitored, vendor master data stale, MSME registration status untracked.
- Finance teams that experience March as a fire drill are not working on a volume problem; they are managing accumulated process debt from the preceding eleven months.
- AP automation reduces year-end reconciliation effort by distributing the work across the year, not by making the year-end task faster.
- Judgment calls on disputed ITC claims, TDS applicability on new payment types, and 43B(h) disallowance schedules require CA or statutory auditor sign-off and sit outside the scope of automation.