Compliance Deadline Countdown Widget for Indian Finance Teams

Section 16(4) of the Central Goods and Services Tax Act 2017 imposes a hard time bar on the availment of Input Tax Credit: a registered taxpayer cannot claim ITC in respect of any invoice or debit note relating to the supply of goods or services after the 30th of November of the year following the financial year to which the invoice / debit note pertains, or the date of filing the annual return for the said FY, whichever is earlier. As standardised post the 2022 amendment, the 30 November following FY-end is the operative outer date. This is not a late-filing penalty and it is not an interest-with-grace-period regime: it is a substantive, non-restorable extinguishment of the ITC right. Once the 30 November window closes, the ITC on the missed invoice is permanently lost - there is no restoration mechanism under the CGST Act, no discretionary relief under any circular, no appellate re-opening. The financial impact is direct: the missed ITC becomes an out-of-pocket cost recognised as expense in the P and L (grossed up if the vendor's invoice included the tax component in the base cost). For a mid-market company with a 5 to 15 crore rupee annual ITC pool, a routine 2 to 5 per cent leakage against the 30 November deadline is a 10 lakh to 75 lakh rupee permanent-loss line item that shows up as a variance in the annual close. This is why the widget flags Section 16(4) as the single most critical annual compliance deadline: every other deadline (tax audit, ITR, GSTR-9, CARO) triggers penalty, interest, additional fees or an adverse audit remark - all recoverable, all curable - but Section 16(4) triggers permanent loss with no cure. The reconciliation implication is that the GSTR-2B vs GSTR-3B vs purchase-register reconciliation must be closed on a rolling monthly basis (14th IMS action window) and the residual mismatch swept up in an October / November sprint before the 30 November wall closes; leaving the reconciliation to the GSTR-9 filing exercise in December is too late.

DRC-01B and DRC-01C are the two automated GST intimations introduced under Rules 88C and 88D of the CGST Rules 2017 respectively, representing the current backbone of the GST department's data-driven compliance enforcement. DRC-01B (Rule 88C, notified January 2023) is auto-issued through the GST portal when the tax liability declared by the taxpayer in GSTR-1 for a tax period exceeds the tax liability declared in GSTR-3B for the same period by a specified threshold (currently 20 per cent and 25 lakh rupees). The taxpayer must respond within 7 days of receipt of the intimation, either by paying the differential with interest under Form DRC-03 or by furnishing an explanation in Part B of the DRC-01B form on the portal. Missing the 7-day window means the intimation converts into a formal show-cause notice under Section 73 or Section 74, with recovery proceedings, interest under Section 50 at 18 per cent p.a., and potentially a penalty in the 10 per cent to 100 per cent range depending on whether the department invokes Section 74 (fraud). DRC-01C (Rule 88D, notified August 2023) is auto-issued when the ITC availed by the taxpayer in GSTR-3B exceeds the ITC auto-populated from GSTR-2B by a specified threshold (currently 20 per cent and 25 lakh rupees). The response window is 15 days from receipt of the intimation - either pay the differential ITC with interest through DRC-03 or explain the difference in Part B of the DRC-01C form. Missing the 15-day window triggers ITC blocking under Rule 86A of the CGST Rules and formal recovery proceedings. Both windows are notice-triggered rather than calendar-based because the timer starts when the specific taxpayer receives the specific intimation on the GST portal - which can happen on any day of the year - not on a fixed statutory date. The widget therefore takes the notice-receipt date as a user input and computes the 7-day (DRC-01B) or 15-day (DRC-01C) countdown from that date. Reconcile against the Terra Insight DRC-01B 72-hour triage playbook (7-day window compresses to 3 working days once weekend and holidays are stripped) and the DRC-01C ITC-mismatch response playbook before the response is filed.

The 31 March 2027 date on the widget is the operative deadline for filing TDS correction statements against the historic TDS returns of FY 2018-19 to FY 2022-23 - a five-year window that has been the accumulated reconciliation debt for most Indian corporates that filed with rate errors, PAN errors, deductee-name mismatches, challan-mapping errors or classification errors during the multi-year run of Section 194 amendments (Section 194N cash withdrawal from 2019, Section 194O e-commerce operator from October 2020, Section 194Q purchase of goods from July 2021, Section 194R benefit / perquisite from July 2022, Section 194S virtual digital asset from July 2022). Under the Central Board of Direct Taxes' consolidated procedural direction and Rule 31A read with the current Form 27B / Form 26Q / Form 27Q / Form 27EQ mechanic, TDS correction statements must be filed within a maximum window from the end of the FY to which the underlying return relates. The 31 March 2027 date represents the outer boundary for corrections to FY 2018-19 (the oldest year in the correctable range) and by extension the same window closes progressively for the intervening years. What makes this deadline irreversible - and why the widget flags it as critical alongside Section 16(4) - is the downstream deductee impact: once the correction window closes, the deductee (vendor, contractor, employee) can no longer claim the corresponding TDS credit against their tax liability because their Form 26AS cannot be updated to reflect the corrected TDS entry. The deductor is left with the tax gross-up cost (Section 40(a)(ia) disallowance of the underlying expense at 30 per cent, plus the substantive TDS liability that cannot be recovered from the deductee). The Terra Insight TDS backlog correction sprint playbook (linked below) is the operational blueprint - inventory the 5-year backlog, prioritise by deductee-value and error type, run reconciliation against the deductor-deductee matching in the department's back-office (which is what generates the correction opportunity in the first place), and close before the 31 March 2027 wall.

No, and this is a deliberate design choice with a workaround. The widget shows the standing statutory calendar as prescribed in the underlying Act, Rule or notification - the 7th, 11th, 14th, 20th, 22nd, 24th, 25th of the following month for the recurring GST and TDS deadlines; the 15th of June, September, December and March for advance tax; the 30th of September for tax audit; the 31st of October for the income tax return; the 30th of November for the Section 16(4) ITC time bar; the 31st of December for GSTR-9 and GSTR-9C. CBDT and CBIC routinely issue circular-based due-date extensions during a specific year (COVID-era extensions in FY 2019-20 through FY 2021-22, the July 2024 extension of the ITR filing date to 15 August 2024 for individual assessees, the December 2024 extension of the GSTR-9 date, etc.) - these are announced by circular typically 1 to 4 weeks before the original date, are unpredictable in timing and are typically taxpayer-category-specific (individual vs corporate, small vs large, particular audit-firm capacity constraints). Baking these into a widget that must remain stable across the FY would create a rolling-updates burden that the widget cannot deliver reliably. Similarly, the General Clauses Act 1897 automatic rollover of a due date falling on a Sunday or a declared public holiday to the next working day is state-specific (the declared holiday list differs by state under the Negotiable Instruments Act 1881 read with the state government's annual holiday notification) and cannot be resolved without knowing the taxpayer's state of registration. Workaround: every card includes an 'Add to calendar' .ics download - once in the finance team's Outlook / Google Calendar / Apple Calendar, the day-of-week is visible immediately, and any CBDT / CBIC extension circular issued during the year is applied by the CA firm and manually reflected by shifting the calendar entry. The widget is a working-aid dashboard for the finance team, not a substitute for the CA firm's compliance memo or the Company Secretary's statutory calendar.

Form 168 is one of the quarterly TDS-upload forms introduced under the CBDT's 2026 procedural migration to the new tax-year architecture (the migration package that also introduced the current payment-code series 1001 through 1092 for the various TDS heads under the amended and re-codified Chapter XVII-B of the Income-tax Act 1961). It became live from April 2026 onwards, with the first Form 168 quarterly upload against Q1 FY 2026-27 (April to June 2026) due 31 July 2026, and the recurring quarterly due dates thereafter following the same 31 July / 31 October / 31 January / 31 May cadence as the parallel Form 141 quarterly TDS return series. Form 141 is the quarterly return of TDS deducted under the general chapter, replacing the historic Form 26Q (payments to residents other than salary) and Form 27Q (payments to non-residents) in the post-migration nomenclature. Form 168 is the corresponding quarterly upload for the specialised TDS heads that were introduced in the 2020 to 2024 amendment stream (Section 194O e-commerce operator, Section 194Q purchase of goods, Section 194R benefit / perquisite in kind, Section 194S virtual digital asset transfer) and consolidates the upload architecture for these specialised heads that were previously handled through amended versions of Form 26Q. Both Form 141 and Form 168 carry the same late-filing consequences: late-fee under Section 234E at 200 rupees per day of default (capped at the aggregate TDS amount in the return), and separately a penalty under Section 271H in the range of 10,000 rupees to 1 lakh rupees leviable by the AO for late filing of the return or for filing an incorrect return (mitigated if the return is filed within one year of the due date and the TDS with interest has been deposited). The widget shows both Form 141 and Form 168 as separate quarterly deadline cards because they are separate return filings on the TIN NSDL / income tax portal with separate reconciliation and error-correction workflows for the finance team, even though the underlying calendar dates coincide.

The FY-end toggle in the control bar affects only the subset of deadlines that are keyed to the company's own accounting-year-end - specifically, the Section 43B(h) Income-tax Act 1961 MSME 45-day payment disallowance trigger (which crystallises on the last day of the FY, so 31 March for a standard Indian FY or 31 December for a Dec-FY foreign-holding subsidiary), the Section 135 Companies Act 2013 CSR spend obligation crystallisation (last day of the FY), the Section 135(5) Unspent CSR Account transfer for ongoing projects (within 30 days of FY-end, so 30 April for March-FY or 30 January for December-FY), and the Section 135(5) Schedule VII fund transfer for non-ongoing project unspent (within 6 months of FY-end, so 30 September for March-FY or 30 June for December-FY). All other Indian statutory tax and GST deadlines remain calendar-based per the Indian tax code regardless of the company's accounting-year-end selection: tax audit report under Section 44AB is 30 September following the Indian FY 2025-26 close (i.e. 30 September 2026) for every Indian assessee irrespective of whether the assessee also reports internally on a Dec-FY basis for consolidation with a US or European parent; income tax return under Section 139(1) is 31 October, Section 16(4) ITC time bar is 30 November, GSTR-9 and GSTR-9C are 31 December, monthly and quarterly TDS and GST deadlines are calendar-based. This design reflects the underlying statutory reality: the Indian income tax and GST framework is hard-wired to the April-to-March Indian FY for return filing, tax audit and annual return purposes, and does not defer to the assessee's internal reporting calendar for a Dec-FY foreign-holding subsidiary. The FY-end toggle is therefore a limited tool - it aligns the FY-end-relative internal deadlines (43B(h), CSR crystallisation and transfer) with the company's own reporting calendar while leaving the statutory tax and GST calendar unchanged. A foreign-holding subsidiary running a Dec-FY internal reporting alongside a March-FY Indian tax reporting will effectively see two overlapping compliance calendars; the widget surfaces the Dec-FY side of the split for the internally-relative deadlines and the March-FY-anchored calendar for the statutory ones.

The .ics calendar export runs entirely inside the browser - no data is sent to Terra Insight, no data is sent to any third party, no cookies are dropped, no analytics event is fired against the deadline data. When the user clicks the 'Add to calendar' link on a deadline card, the widget's client-side JavaScript constructs an RFC 5545 iCalendar (ICS) format text string in memory (the standard BEGIN:VCALENDAR / BEGIN:VEVENT / DTSTART / DTEND / SUMMARY / DESCRIPTION / END:VEVENT / END:VCALENDAR skeleton), wraps it in a Blob object, generates an in-memory object URL via URL.createObjectURL, and triggers a download by programmatically clicking a synthetic anchor tag with the download attribute set to a filename derived from the deadline name and date. The browser then hands the resulting .ics file to the user's default calendar application (Microsoft Outlook, Google Calendar via the browser-native web app, Apple Calendar, Mozilla Thunderbird, etc.). All computation - the days-to-go arithmetic, the colour-band decision, the sort by proximity, the .ics generation - runs in the browser's JavaScript engine against the base date input, the FY-end toggle and (where entered) the notice-date inputs. The base date defaults to today (from the browser's local time zone) and the notice-date inputs default to blank. The widget uses no fetch calls, no XHR, no WebSockets, no third-party CDN scripts and no image beacons for the deadline computation. The only network calls that Terra Insight (or Terra Insight's static-hosting provider, AWS CloudFront) can see are the initial page load (HTML, CSS, JS bundled at build time - the same as any other page on this site) and the standing site-wide anonymous analytics event that all Terra Insight marketing pages fire on load. No deadline-specific event, no input-value event, no calendar-export event is transmitted anywhere. The widget is safe to use with the company's actual notice-receipt dates (which may be sensitive information under the company's data-handling policy) - none of it leaves the browser.