Vendor and Client Invoice Management as part of a CFO Retainer

Five regulatory frameworks touch every vendor invoice that flows through an Indian business: the GST e-invoicing mandate, the Invoice Management System on the GST portal, the Reverse Charge Mechanism, the MSMED Act 2006 payment rules, and the Income Tax Act 2025 TDS framework. Each has a specific penalty provision. Individually, most founders know they exist. Together, structured into a working control system, they are almost never set up correctly without a VCFO. This article maps how a VCFO retainer operationalises all five as a single invoice management framework: what the VCFO owns, what the accounts team executes, and what the cost of each gap is in rupees.

What does a CFO retainer cover for invoice management?

A VCFO retainer covers invoice management at the control and workflow design layer, not the data-entry layer. The VCFO owns the IMS review protocol (ensuring accounts teams act on vendor invoices before the GSTR-2B cut-off), the IRN validation gate at invoice receipt, the RCM register and self-invoice workflow, the MSME payable ageing tracker with acceptance-date discipline, the ISD assessment for multi-GSTIN businesses, and the TDS mapping table under the Income Tax Act 2025. Invoice posting, payment execution, and daily follow-up belong to the accounts team. The retainer exists to build the control layer that ensures the accounts team’s work is compliant, not to replace it.

The two-layer model: what the VCFO owns versus what the accounts team executes

The most expensive mistake in a growing finance function is assuming that because a VCFO reviews the books, someone is watching the invoices. No one is, unless the scope letter defines it explicitly.

The accounts team owns transaction execution: posting vendor bills, raising client invoices on schedule, running bank reconciliations, booking TDS entries at accrual, filing GSTR-1 with correct invoice data, and acting on IMS decisions once the workflow is set. These are daily and weekly tasks requiring accuracy, not financial judgement.

The VCFO retainer owns five control layers sitting above execution: designing the IMS review protocol so that no vendor invoice is deemed accepted by default on GSTR-2B without the accounts team checking it first; validating IRNs from e-invoice-mandated vendors before payment approval; maintaining the RCM register and reviewing self-invoice completeness monthly; running the MSME payable ageing tracker and flagging exposures before the 45-day statutory clock expires; and reviewing the debtor ageing report to set and enforce the escalation protocol.

When these layers collapse into each other (the VCFO chasing individual payments, the accounts team classifying RCM without guidance), the retainer is misused and compliance risk accumulates undetected.

Table: Responsibility split between VCFO retainer and accounts team

Activity	Accounts team	VCFO retainer
Posting vendor bills	Owner	Periodic exception review
Three-way match (PO, GRN, invoice)	Owner	Matching policy setter
IMS dashboard review before GSTR-2B cut-off	Executor	Protocol designer, escalation owner
IRN/QR validation for e-invoice-mandated vendors	Executor	Gate owner, exceptions queue reviewer
RCM classification per vendor category	Flags candidates	Final determination owner
Self-invoice issuance for RCM	Executor	Completeness reviewer
ISD invoice workflow for multi-GSTIN businesses	Executor	Applicability assessor, GSTR-6 overseer
MSME Udyam verification at onboarding	Executor	Process mandator, coverage reviewer
MSME 45-day ageing tracker (acceptance date)	Data input	Reviewer and payment-queue escalation
TDS rate mapping per vendor (ITA 2025, Section 393)	Reference	Owner, updated each April
TDS deduction and challan deposit	Owner	Quarterly spot-check before Form 140
GSTR-2B reconciliation vs purchase register	Owner	Exception sign-off
IMS rejection and dispute handling with vendors	Executor	Escalation decision
RCM ITC ageing tracker	Data input	Reviewer, window compliance
Client invoice raising and scheduling	Owner	Billing calendar and template review
Deferred revenue schedule	Owner	Monthly MIS reviewer
Debtor ageing report	Owner	Escalation protocol setter
LUT validity for export clients	Executor	Annual renewal trigger

How vendor invoice management works inside a VCFO retainer

A structured vendor invoice workflow under a VCFO retainer follows seven stages. Each stage has an owner and a compliance gate.

Stage 1: Receipt and three-way match

When a vendor bill arrives, the accounts team checks it against the purchase order and goods receipt note. The VCFO sets the matching policy at the start of the engagement: what tolerance is acceptable on quantity or value discrepancies, and what happens to a bill that fails the match. No bill enters the payment queue without a completed three-way match. The VCFO reviews the exceptions monthly.

This sounds basic. In practice, most businesses that arrive at a VCFO engagement without this structure have vendor bills approved and paid on the basis of verbal confirmation. When a GST audit requests purchase documentation, missing GRNs are the single most common reason ITC claims are challenged on procedural grounds under Rule 36(1)(a) of the CGST Rules 2017.

Stage 2: IMS review before GSTR-2B generation

The Invoice Management System (IMS) on the GSTN portal is the newest and most consequential change in the ITC ecosystem since 2017. From 14/10/2024, every B2B invoice saved by a supplier in GSTR-1, GSTR-1A, or IFF appears on the recipient’s IMS dashboard. From the October 2025 tax period, Section 38 of the CGST Act 2017 was substituted (by Notification 16/2025-Central Tax dated 17/09/2025) to make IMS the statutory basis for ITC. Only invoices the recipient accepts, or that are deemed accepted by inaction, flow into GSTR-2B and become eligible ITC.

The workflow mechanics are: the recipient can Accept, Reject, or mark Pending each invoice before the GSTR-2B generation date (the 14th of the following month). Accepted and deemed-accepted invoices populate GSTR-2B and auto-flow into GSTR-3B’s ITC table. Rejected invoices are excluded permanently. Pending invoices do not populate GSTR-2B for that cycle. From October 2025, credit notes and downward amendments can be held Pending for only one tax period.

The risk in “deemed acceptance” is not theoretical. An accounts team that does not review IMS before the 14th allows every invoice uploaded by every supplier (including invoices with wrong amounts, wrong GSTINs, or duplicate entries) to become eligible ITC by default. When such ITC is claimed in GSTR-3B and later challenged in assessment, reversal with 18% interest under Section 50 of the CGST Act 2017 is the consequence.

The VCFO retainer builds the IMS review protocol: a monthly workflow where the accounts team opens the IMS dashboard between the 11th and 13th of each month (after GSTR-1 is filed and before GSTR-2B is generated on the 14th), reviews each pending invoice against the purchase register, accepts matched invoices, rejects incorrect ones, and escalates disputed amounts to the VCFO. The VCFO reviews the exception report and makes the final decision on any invoice held as Pending before the GSTR-3B filing date. This protocol becomes a standing month-end task in the compliance calendar.

Stage 3: E-invoice IRN validation

IMS review and IRN validation serve different purposes. IMS checks whether a supplier’s invoice matches the purchase register. IRN validation checks whether the invoice itself is legally valid for ITC purposes.

For any B2B vendor whose aggregate annual turnover at PAN level has crossed ₹5 crore in any financial year from FY 2017-18 onwards, every invoice must carry a valid IRN and a digitally signed QR code issued by the Invoice Registration Portal (IRP). This is the e-invoicing mandate under Notification 10/2023-Central Tax, operative for FY 2026-27. The threshold is permanent once crossed: a vendor who touched ₹5 crore in FY 2021-22 and dropped to ₹4 crore since must still generate e-invoices.

A separate 30-day upload window has applied since 01/04/2025 for vendors with aggregate turnover above ₹10 crore: invoice data must be uploaded to the IRP within 30 days of the invoice date. An invoice uploaded after 30 days is rejected by the IRP and no IRN is generated. The buyer gets no ITC relief.

The VCFO retainer adds an IRN column to the AP register. Bills from e-invoice-mandated vendors that arrive without a valid IRN go into an exceptions queue. They are not approved for payment until the vendor provides a corrected e-invoice. The VCFO reviews the exceptions queue monthly and flags vendors with repeat IRN failures for escalation, including withholding payment as a contractual lever.

IMS and IRN validation are complementary: IMS confirms the invoice appears correctly in the GST system; IRN validation confirms the underlying invoice is legally authenticated. Both must pass for ITC to be secure.

Stage 4: Reverse charge mechanism register

RCM is the compliance layer accounts teams most consistently miss. Under Sections 9(3) and 9(4) of the CGST Act 2017, GST liability shifts from supplier to recipient in two categories.

Section 9(3) covers notified supplies regardless of supplier registration status. Common triggers for most businesses: legal services from individual advocates or law firms; goods transport agency services where the GTA has not opted for the 12% forward charge; and security services from individuals. When a business pays its lawyer or a freight provider, the vendor invoice carries no GST. The buying entity self-assesses GST at the applicable rate, pays from the electronic cash ledger (never from ITC), raises a self-invoice under Section 31(3)(f) of the CGST Act read with Rule 46 of the CGST Rules, and claims the ITC in the same GSTR-3B period.

Section 9(4) (for domestic unregistered suppliers) and Sections 5(3) and 5(4) of the IGST Act 2017 (for imports of services) cover payments to unregistered vendors and foreign vendors. Every payment to a foreign SaaS provider, cloud infrastructure vendor, or overseas consultant is an import of service attracting IGST at 18% under RCM, regardless of whether the foreign entity has any GST registration. The obligation arises at the earlier of payment or 60 days from the vendor’s invoice date under Section 13(2) of the CGST Act. Payment from the cash ledger, self-invoice issuance, and GSTR-3B Table 3.1(d) reporting are all mandatory.

The VCFO retainer builds an RCM register at onboarding: every recurring vendor categorised by GST status and supply type, with the applicable RCM provision noted. New vendors are classified before the first invoice is approved. RCM GST payable is included in the monthly payment run as a standing line item, not treated as an optional reconciliation task.

The ITC on RCM payments has a time-limited availing window. Under the current framework, ITC for a given period must be availed by the due date of the November GSTR-3B of the second financial year following the year of the invoice, or such extended date as notified. The VCFO retainer maintains an RCM ITC ageing tracker (structured like a receivable) so no month’s RCM ITC window expires unclaimed.

Stage 5: ISD workflow for multi-GSTIN businesses

From 01/04/2025, the Input Service Distributor mechanism is mandatory under Notification 16/2024-Central Tax (dated 06/08/2024) for any GST-registered entity that receives invoices for common input services at a central location on behalf of multiple branches with separate GSTINs under the same PAN. The ISD distributes ITC to branches via ISD invoices, filed monthly in GSTR-6 by the 13th.

Services typically centralised at head office that trigger ISD: audit fees, legal retainers, SaaS and software subscriptions, advertising, employee insurance, and management fees. A business with a Maharashtra GSTIN and a Karnataka branch GSTIN receiving software subscription invoices centrally must run ISD. Continuing cross-charge for externally procured services after April 2025 without ISD registration is non-compliant: ITC is disallowable at the branch level and penalties range from ₹10,000 to the full amount of ITC wrongly availed under Section 21 of the CGST Act.

The VCFO retainer assesses ISD applicability in the first 30 days of onboarding. For clients who need it and do not have it, the VCFO coordinates the registration, sets up the ISD invoice format in the accounting software, builds the proportional distribution formula, and integrates GSTR-6 into the monthly compliance calendar.

Stage 6: MSME exposure tracking

If a vendor holds a valid Udyam Registration Number, payment timing is governed by Section 15 of the MSMED Act 2006. No written agreement: payment due within 15 days of acceptance. Written agreement: payment due within the agreed period, capped at 45 days from acceptance. The cap cannot be contracted away: any agreement allowing 60 or 90 days to an MSME vendor is void to the extent it exceeds 45 days.

Three statutory consequences attach to a missed deadline. Compound interest at three times the RBI bank rate under Section 16 of the MSMED Act (at a 6.5% bank rate, that is 19.5% per annum compounded monthly) begins accruing the day after the appointed day and is not deductible as a business expense under Section 23(4). Section 43B(h) of the Income Tax Act 1961, effective 01/04/2024 and continued under the Income Tax Act 2025, disallows the vendor expense in the year of accrual if payment was not made within the statutory period; the deduction falls into the year of actual payment. Companies (not LLPs) must file Form MSME-1 half-yearly with the Ministry of Corporate Affairs under Rule 2 of the Specified Companies Order 2019: the October to March period is due 30 April, the April to September period is due 31 October. Companies must disclose all outstanding MSME payables beyond 45 days.

The VCFO retainer builds a monthly MSME ageing tracker. Every vendor payable is tagged with Udyam status, acceptance date, and statutory deadline. The critical discipline is using acceptance date (the date of delivery or service completion), not the invoice date. If a vendor delivers on 01/08/2026 and invoices on 08/08/2026, the clock started on 01/08/2026 and the statutory deadline is 15/09/2026 (for a business with a written agreement allowing 45 days). A payment on 30/09/2026 is 15 days late, regardless of how many days have passed since the invoice date. Accounts teams that track from the invoice date systematically underestimate MSME exposure.

MSME-flagged invoices are surfaced in the weekly payment run as a priority queue, separate from the standard payment schedule, with the statutory deadline date shown alongside.

Stage 7: TDS mapping under the Income Tax Act 2025

From 01/04/2026, the Income Tax Act 2025 replaced the Income Tax Act 1961. All non-salary TDS provisions, previously in the 192 to 194T range, are now consolidated under Section 393. Salary TDS is Section 392. TCS is Section 394. TDS challans and quarterly returns filed from April 2026 must use new numeric payment codes (1001 to 1092) and new form numbers: Form 140 replaces Form 26Q, Form 138 replaces Form 24Q, Form 144 replaces Form 27Q, and Form 141 is the unified statement for TDS on rent, property, contractor, and virtual digital asset transactions. Using old section numbers (194C, 194J, 194I) on a return filed from April 2026 makes the return defective.

Operative thresholds under Section 393 for common vendor payments (legacy section in brackets for orientation):

• Professional services (formerly 194J): 10% TDS, threshold ₹50,000 per vendor per year (raised from ₹30,000 by Finance Act 2025, effective 01/04/2025)
• Technical services (formerly 194J): 2% TDS, same ₹50,000 threshold
• Contractor payments (formerly 194C): 1% or 2% depending on deductor type, threshold ₹30,000 per payment or ₹1,00,000 aggregate per year
• Rent on land/building/furniture (formerly 194I): 10% TDS, threshold ₹2,40,000 per year

TDS is deductible at the earlier of credit to the vendor’s account or actual payment. Credit means the accounting entry, not the bank transfer. A month-end accrual for an unpaid vendor bill triggers TDS at that point. TDS is deducted on the base taxable value only; where GST is separately stated on the invoice, TDS does not apply to the GST component.

The VCFO retainer owns the TDS mapping table, updated each April, and does a quarterly spot-check against the accounts team’s TDS entries before Form 140 is filed. Systematic errors (wrong rate, deduction on GST amount, missed accrual entries) are corrected before the return is filed, not discovered in a demand notice.

How client invoice management works inside a VCFO retainer

The accounts receivable side has a lower direct compliance exposure than vendor invoices, but the cash impact of poor controls is more immediate.

The accounts team raises invoices on the agreed schedule, records collections, and manages day-to-day follow-up. The VCFO adds four layers of oversight that accounts teams do not run independently.

GSTR-1 filing discipline and client ITC protection

When a business raises a tax invoice, that invoice must appear in the supplier’s GSTR-1 before the client can see it in their GSTR-2B and claim ITC. Under the IMS framework, a client who cannot find an invoice on their IMS dashboard cannot accept it or claim ITC for that period. If the supplier’s accounts team files GSTR-1 late, after the client has filed GSTR-3B, the client’s ITC for that invoice is delayed by a full month.

The VCFO retainer sets a non-negotiable sequencing rule: GSTR-1 is filed before GSTR-3B, every month, without exception. Client invoices for the month are reconciled against GSTR-1 before filing to confirm every invoice is reported correctly. This protects the client relationship and prevents the supplier’s filing delays from creating ITC problems for buyers.

Revenue recognition and deferred revenue

When a client pays an advance retainer, the receipt is not revenue. Under Section 13(2) of the CGST Act 2017, GST liability on services arises at the earlier of invoice issuance or advance receipt. The GST is payable in the month of receipt, via a receipt voucher or tax invoice raised at that point. Revenue recognition is a separate matter governed by Ind AS 115 or AS 9: the advance is carried as deferred revenue (a current liability) until the service is delivered, and recognised on a straight-line basis over the service period.

In the first 30 days of almost every Treelife VCFO engagement, professional services clients show advance client receipts recorded as revenue at receipt. Two problems follow: the P&L is overstated for the period of receipt, and if no GST invoice or receipt voucher was raised at the time, the GSTR-3B for that month may have under-reported tax payable. The VCFO builds the deferred revenue schedule in month one and back-calculates any GST timing gaps.

Client invoice quality: GST fields that break ITC

Tax invoices issued to clients must carry the correct GSTIN (verified against the GST portal, not copied from a business card), the correct HSN or SAC code, the correct GST rate, and the correct place-of-supply classification: intra-state (CGST plus SGST) or inter-state (IGST). An incorrect place of supply means the client gets the wrong type of ITC. An incorrect GSTIN means the invoice does not auto-populate in the client’s GSTR-2B at all.

The VCFO conducts a one-time invoice template review at onboarding: GSTIN verification for all active client records, HSN/SAC mapping for all service categories, place-of-supply determination for inter-state clients, and LUT validity check for export clients. Export invoices must be zero-rated under a valid Letter of Undertaking and correctly reported in GSTR-1 Table 6A. The LUT renewal every April is added to the VCFO’s compliance calendar.

Debtor ageing and escalation

The VCFO produces a monthly debtor ageing report bucketed at 0-30, 31-60, 61-90, and 90+ days, with disputed invoices flagged separately. The escalation protocol is written into the engagement structure: receivables above a defined value that cross 60 days are flagged to the founder. Those crossing 90 days are assessed for provisioning under AS 9. The VCFO does not make collection calls; it ensures that the escalation triggers exist, are followed, and feed into the cash flow forecast.

Receivables ageing quality also has a direct cost-of-capital consequence. A business presenting to an NBFC or bank for invoice discounting with a high proportion of 60-plus-day receivables pays 14-18% per annum versus 9-11% for a book with mostly current, clean receivables.

What unstructured invoice management costs

Three loss categories recur. These are not estimates: they are the computations that come out of the vendor master audit in month one of most new VCFO engagements.

ITC at risk from IMS and IRN failures. At 18% GST on ₹1 crore of annual professional and technical service purchases, the ITC exposure is ₹18 lakhs. If vendor invoices are not validated through IMS and IRN checks, some portion of this ITC is disallowable under Section 16(2)(aa) of the CGST Act 2017, with interest at 18% per annum under Section 50 from the date the credit was claimed. A GST assessment three years later recovers principal plus accumulated interest.

Section 43B(h) disallowance on MSME payables. A business paying ₹60 lakhs per year to MSME vendors, with 20% of payments beyond the statutory window, faces ₹12 lakhs of disallowed deduction. At a 25% corporate tax rate, the additional tax is ₹3 lakhs per year. Without a MSME ageing tracker, this disallowance is only discovered when the ITR is scrutinised. At that point, the cash has already been paid to the vendor and the only relief is amendment of the prior year return under the permitted window.

Accumulated RCM liability. A business paying ₹12 lakhs per year to foreign SaaS vendors and ₹4 lakhs to its lawyers, without running RCM, accumulates ₹2.88 lakhs of unpaid GST per year (at 18% on the SaaS payments alone). Over two years, with 18% annual interest under Section 50(3) of the CGST Act, the liability is approximately ₹6.5 lakhs. The interest component is non-deductible and competes with operating cash flow.

Common mistakes that create structural invoice compliance gaps

No IMS review protocol in the accounts team’s monthly workflow. The most common gap we see is a finance team that knows IMS exists but has no written protocol for when to review it, who does it, and what to do with disputed invoices. Inaction is deemed acceptance. An incorrect invoice accepted by default must be reversed later with interest. The VCFO retainer’s first task in month one is to write the IMS protocol, assign the account team member who owns it, and put the review date (between the 11th and 13th of each month) into the compliance calendar.

Running the MSME tracker from invoice date instead of acceptance date. This single mistake causes more Section 43B(h) disallowances than any other. Acceptance is delivery or service completion. The VCFO retainer requires vendors to note the delivery date on every bill, separate from the invoice date, and the ageing tracker uses that date, not the invoice date, for the 45-day calculation.

Treating the RCM register as a one-time exercise. Businesses build an RCM register at the start of the year and stop updating it. New vendors are onboarded without RCM classification. A new logistics vendor, a new foreign SaaS subscription, a new law firm: each of these is an RCM event if the category is notified or the supplier is unregistered. The VCFO retainer mandates RCM classification as a condition of vendor onboarding, enforced by the AP approval workflow.

Not updating the TDS mapping table after April each year. The Income Tax Act 2025 is in force. Old section codes in TDS returns filed from April 2026 produce defective returns. Beyond section codes, Finance Act changes alter thresholds and rates: the professional services TDS threshold changed from ₹30,000 to ₹50,000 in FY 2025-26. Accounts teams that were not told about this change either over-deduct TDS (annoying vendors and requiring correction) or under-deduct (creating short-deduction notices). The VCFO retainer updates the mapping table in April and briefs the accounts team before the first payment run of the new financial year.

Raising client invoices after the 20th of the month. Under Section 31 of the CGST Act 2017, a tax invoice for continuous supply of services must be raised on or before the last day of each calendar month. A September retainer invoice raised in October does not move the GST obligation. The tax was due in September’s GSTR-3B. Interest under Section 50 starts from the September due date. The VCFO retainer sets a billing calendar with a hard cut-off, typically the 25th of each month, so the accounts team can raise all invoices, reconcile with GSTR-1, and file before the 11th.

How the VCFO retainer phases in invoice management controls

Treelife’s VCFO retainer rolls out invoice management infrastructure across the first 60 days.

In the first 30 days, the VCFO runs a vendor master audit covering: GST registration and e-invoice threshold status for each vendor; IMS review protocol design and insertion into the monthly compliance calendar; RCM classification for every recurring vendor; Udyam Registration verification for all vendors above ₹3 lakhs per year in spend; TDS category mapping under Section 393 of the Income Tax Act 2025; and ISD applicability assessment for any client with multiple GSTINs. The current GSTR-2B is reconciled against the purchase register to surface existing ITC mismatches, and the existing RCM register (if any) is reviewed for gaps.

From day 31 to 60, the MSME ageing tracker is built with acceptance-date fields. The payment approval matrix is formalised: authorisation thresholds, payment run frequency, separate queues for MSME-deadline-flagged and RCM-flagged invoices. The IMS exception escalation process is agreed with the founder. The debtor ageing format and escalation protocol are finalised. The billing calendar is set and the LUT renewal date for export clients is added to the compliance calendar.

From month three onwards, invoice management is a standing section of the monthly MIS pack: a single-page AP and AR summary showing total payables outstanding, MSME exposure approaching the 45-day limit, ITC on hold pending IMS action or IRN validation, RCM paid in the period with ITC claimed, and debtor ageing bucketed at 30/60/90/90+ days. This goes to the founder alongside the P&L and cash flow statement every month.

What the VCFO does when invoice management is already broken

Some engagements start with an invoice backlog: months of vendor bills without IRN validation, no RCM payments made, MSME vendors paid late, an IMS dashboard full of unreviewed invoices that are now deemed accepted, and a GSTR-2B reconciliation gap sitting unresolved. The VCFO’s first task is triage.

The priority sequence is: identify any Section 43B(h) exposure in the current ITR and clear MSME payables before the return is filed if the year is still open; quantify ITC at risk from IMS and IRN failures and determine whether reversal under Rule 37A of the CGST Rules is required or whether vendor correction is achievable; calculate the RCM liability and interest outstanding and file voluntary payment before a notice issues; and assess any ISD non-compliance and co-ordinate registration and retrospective distribution with the GST consultant.

Cleanup follows triage in correct accounting periods, co-ordinated with the statutory auditor so corrections are reflected consistently in the books and filings.

Frequently asked questions

Q: Is vendor invoice management included in a standard VCFO retainer scope?
A: It depends on how the scope letter is drafted. Most retainers include accounts payable financial controls (IMS protocol, IRN validation, RCM register, MSME ageing tracker, TDS mapping, and GSTR-2B reconciliation sign-off) as part of the core control layer. Transaction-level data entry, payment execution, and daily follow-up stay with the accounts team. Confirm the scope explicitly before signing.

Q: What is the IMS and why does it matter for vendor invoice management?
A: The Invoice Management System is a GST portal module where every B2B invoice uploaded by your supplier in GSTR-1 or IFF appears on your dashboard. From the October 2025 tax period (under Section 38 of the CGST Act 2017 as substituted by Notification 16/2025-Central Tax), IMS is the statutory basis for ITC. You must Accept, Reject, or keep Pending each invoice before GSTR-2B is generated on the 14th. Inaction equals deemed acceptance. Accepting a wrong invoice, or having a wrong invoice deemed accepted by inaction, means you claim incorrect ITC that must later be reversed with 18% annual interest under Section 50 of the CGST Act.

Q: What happens if my vendor does not generate an IRN?
A: If the vendor’s aggregate annual turnover has exceeded ₹5 crore in any year since FY 2017-18 and they issue a standard tax invoice without an IRN, that invoice will not flow correctly into GSTR-2B. ITC on it is disallowable under Section 16(2)(aa) of the CGST Act 2017. Your options are: reject the invoice in IMS, request the vendor raise a corrected e-invoice, and re-accept in IMS before the next GSTR-2B cycle. Building IRN validation into your payment approval gate (no IRN, no payment) is the only structural protection.

Q: What is Section 43B(h) and how does the VCFO manage it?
A: Section 43B(h) of the Income Tax Act 1961, effective 01/04/2024 and continued under the Income Tax Act 2025, disallows an expense paid to a micro or small enterprise in the year it is accrued if payment was not made within the period under Section 15 of the MSMED Act 2006: 15 days with no written agreement, up to 45 days with one. The expense is deductible only in the year of actual payment. The VCFO manages this through a monthly MSME ageing tracker that uses the acceptance date (not the invoice date) as the clock-start and flags payables approaching the limit in the weekly payment run.

Q: Which vendor payments attract RCM under GST?
A: The main Section 9(3) triggers for most businesses: legal services from individual advocates or law firms; goods transport agency services where the GTA has not opted for 12% forward charge; security services from individuals. All imports of services from foreign vendors (SaaS subscriptions, cloud infrastructure, overseas consulting) attract IGST under RCM via Sections 5(3) and 5(4) of the IGST Act 2017. In each case, the buyer self-assesses GST, pays from the cash ledger, raises a self-invoice, and reports in GSTR-3B Table 3.1(d).

Q: What is the MSME acceptance date and why does it matter?
A: Section 15 of the MSMED Act 2006 starts the statutory payment clock at the date of acceptance of goods or services (the date of delivery or service completion), not the invoice date. A vendor who delivers on the 1st and invoices on the 8th has already been running the clock for seven days. Accounts teams that track from the invoice date systematically miscalculate MSME exposure and book Section 43B(h) disallowances they could have avoided.

Q: What is ISD and does my business need it?
A: The Input Service Distributor mechanism under Section 2(61) of the CGST Act 2017 is mandatory from 01/04/2025 (Notification 16/2024-Central Tax) for any GST-registered entity with multiple GSTINs under the same PAN that receives common service invoices (audit fees, SaaS subscriptions, legal retainers, insurance) at a central GSTIN. The ISD distributes ITC to branches via ISD invoices and files GSTR-6 by the 13th monthly. Without ISD registration, ITC on those shared services is disallowable at branch level.

Q: How does TDS work on vendor invoices under the Income Tax Act 2025?
A: From 01/04/2026, all non-salary TDS is consolidated under Section 393 of the Income Tax Act 2025. Old section codes (194C, 194J, 194I) no longer exist in filed returns from April 2026 onwards; use numeric payment codes and new form numbers (Form 140 replaces Form 26Q). Rates are largely unchanged. Professional services: 10% on amounts above ₹50,000 per year. Technical services: 2%, same threshold. Contractor payments: 1-2%, threshold ₹30,000 per payment or ₹1,00,000 aggregate. TDS is deducted at the earlier of accounting credit or payment, on base value only, not on the separately stated GST component.

Q: What is Form MSME-1 and when must it be filed?
A: Form MSME-1 is a half-yearly MCA return for companies (not LLPs or proprietorships) disclosing outstanding payments to MSME vendors beyond 45 days. April-September period: due 31 October. October-March period: due 30 April. Filed under Rule 2 of the Specified Companies Order 2019. The VCFO retainer includes it in the compliance calendar, drawing data from the MSME ageing tracker.

Q: Does GST apply when a client pays a retainer in advance?
A: Yes. Under Section 13(2) of the CGST Act 2017, GST liability arises at the earlier of invoice issuance or advance receipt. An advance received for a six-month retainer triggers GST in the month of receipt. A receipt voucher or tax invoice must be raised and the GST paid in that month’s GSTR-3B. Revenue recognition is separate: the advance is deferred revenue on the balance sheet, recognised as income as the service is delivered.

Q: What happens to IMS for RCM, ISD, and import-of-goods invoices?
A: RCM invoices, ISD-distributed invoices, and GSTR-5 records (non-resident taxable persons) do not pass through IMS. They appear directly in GSTR-2B without requiring an Accept/Reject/Pending action. Import of goods (Bill of Entry) has a separate section in IMS from October 2025. The VCFO retainer reconciles both streams separately: the IMS-based stream for domestic forward-charge invoices, and the direct-GSTR-2B stream for RCM, ISD, and imports.

Q: How quickly can a VCFO retainer set up invoice controls from scratch?
A: The full framework (IMS protocol, vendor master audit, IRN validation gate, RCM register, MSME ageing tracker with acceptance dates, ISD assessment, TDS mapping table under ITA 2025, billing calendar, and debtor ageing protocol) is built within the first 30 to 60 days. The timeline depends on vendor count, the state of existing vendor master data, and the accounting software in use.

Regulatory references:

• Section 38, CGST Act 2017 (as substituted by Notification 16/2025-Central Tax dated 17/09/2025): statutory basis for ITC through IMS
• Section 9(3) and 9(4), CGST Act 2017: reverse charge on notified supplies and unregistered suppliers
• Section 5(3) and 5(4), IGST Act 2017: reverse charge on import of services
• Section 13(2), CGST Act 2017: time of supply for services, GST liability on advance receipts
• Section 16(2)(aa), CGST Act 2017: ITC allowable only for invoices in GSTR-2B
• Section 31(3)(f), CGST Act 2017: self-invoice obligation for RCM recipients
• Section 50, CGST Act 2017: 18% annual interest on short-paid GST
• Section 73, CGST Act 2017: penalties for non-fraud tax shortfall
• Section 2(61) and Section 20, CGST Act 2017: ISD definition and ITC distribution
• Rule 36(1)(a), CGST Rules 2017: documentary conditions for ITC (purchase documentation)