Monday, October 5, 2026

GST 2.0: The Next Reform Is Not About Rates — It Is About Removing the Cost of Compliance

 By CA Surekha S Ahuja

From tax rates to tax friction: ITC, RCM, refunds, registration, exports, disputes and enforcement will decide the next phase of GST.

By CA Surekha S Ahuja
6 October 2026

The rate is what a business pays the Government. The cost of compliance is what it pays to prove that it paid.

The 57th GST Council meeting is scheduled for 8 October 2026, after more than thirteen months. The reported focus is not merely on rates, but on the machinery of GST — registration, returns, input tax credit, refunds, disputes and enforcement.

That is where the next GST reform needs to go.

After almost a decade of GST, the bigger question for a compliant business is no longer simply:

How much GST do I pay?

It is:

How much does GST cost me to comply with, reconcile, finance and defend?

GST 1.0 built the tax architecture.
GST 2.0 simplified the rate structure.
The next stage has to fix the operating architecture.

Same tax. Different cost.

Consider two businesses with identical turnover, identical GST liability and identical tax rates.

One receives its ITC smoothly, obtains refunds quickly, completes registration without repeated queries and closes its reconciliations through its accounting system.

The other has RCM transactions requiring separate identification, ITC blocked or disputed during departmental audit, refunds consuming working capital, repeated documentation queries and management time spent reconciling books with multiple GST records.

The tax may be identical. The business cost is not.

The statute sees the tax.

The profit and loss account sees the friction.

What has changed — and what is still open?

This distinction matters.

Several GST reforms are already part of the legal framework. Other issues are proposals, industry representations or reported areas of consideration. They should not be presented as though they are already law.

AreaWhat has changedWhat still needs attention
ITCRule 37A provides for reversal and subsequent re-availment in specified supplier-default situationsThe wider question remains: how should a genuine recipient be protected from supplier-side default?
RCM & ITCThe recipient pays RCM and, where otherwise eligible, may claim ITCClassification, documentation, eligibility and audit disputes can still arise over the same transaction
RefundsRisk-based provisional refund mechanisms have improved speed in specified casesBlocked credit and processing time can continue to impose working-capital costs
RegistrationRisk-based and simplified registration mechanisms have been introducedGenuine low-risk businesses should face proportionate verification and minimal delay
ReturnsGSTR-1A provides a mechanism for specified corrections before GSTR-3BBusinesses still reconcile data across multiple systems and periods
Services exportsChanges have addressed some intermediary-service issuesPlace of supply, overseas structures, realisation and documentation can still create uncertainty
Disputes & enforcementEnforcement and prosecution provisions have already been rationalised in certain areasThe system needs clearer differentiation between fraud, interpretation, reconciliation and procedural default

The principle is simple: a reported proposal becomes a compliance requirement only when it is legally implemented.

The GST pain businesses know: RCM paid, ITC still disputed

One of the most practical gaps in GST compliance is the treatment of reverse charge and the corresponding input tax credit.

RCM itself is straightforward in concept.

The recipient identifies the transaction, determines the liability and pays GST instead of the supplier.

But the compliance chain does not end with payment.

The business must establish:

Why RCM applies → taxable value → rate → time of supply → tax payment → reporting → ITC eligibility

During departmental audit, the same transaction may then be examined again from the ITC side.

Was the expenditure genuinely for business?

Is the credit blocked under section 17(5)?

Is proportionate reversal required?

Was the credit taken within the permitted time?

Is the documentation adequate?

Has the transaction been correctly classified?

Has the credit already been reversed or duplicated?

This can lead to an uncomfortable situation:

RCM tax has been paid, but the corresponding ITC is still questioned.

That does not necessarily mean there has been a revenue loss. The dispute may concern classification, documentation, timing, apportionment or eligibility.

RCM needs a complete audit trail

For every material RCM category, the system should be capable of answering five questions:

Why was RCM applicable?
What was the taxable value?
When was tax payable?
How was it paid?
Why is the corresponding ITC eligible?

Today, the answers may be spread across agreements, invoices, expense ledgers, RCM workings, payment records, GSTR-3B and the electronic credit ledger.

That fragmentation creates audit risk.

The better architecture is:

Transaction → RCM identification → tax payment → eligible ITC → reconciliation → audit trail

rather than requiring the taxpayer to reconstruct the entire chain years later during departmental audit.

“Ineligible ITC” is not one category

This is another area where GST 2.0 needs to move beyond mechanical matching.

An ITC disputed during audit may arise because:

  • the credit is specifically blocked under section 17(5);

  • expenditure has business and non-business use;

  • common credit requires reversal;

  • exempt supplies require proportionate reversal;

  • the statutory time limit is questioned;

  • invoice or receipt conditions are questioned;

  • supplier-side reporting creates a reconciliation issue;

  • the department adopts a different classification;

  • place-of-supply conditions affect eligibility;

  • credit is duplicated or already reversed; or

  • documentation does not sufficiently establish business purpose.

These are different legal and factual questions.

They should not automatically become one number called “wrong ITC.”

A clearly blocked personal expense is not the same as an RCM credit where tax has already been paid to the Government.

A duplicate credit is not the same as a genuine interpretational dispute.

A small reconciliation difference is not the same as structured fraudulent credit.

The response should therefore be proportionate to the nature of the risk.

Seven tests for the next stage of GST

1. ITC: from entitlement to usable and defensible credit

The real question is not merely how much ITC a business is entitled to claim.

It is:

How much credit is available, usable, correctly classified, reconciled and capable of surviving departmental audit?

Supplier default, RCM classification, section 17(5), common-credit reversal, place-of-supply issues, time limits and documentation disputes are different problems.

Test: How much ITC is blocked, disputed or under audit — and how much management time and financing cost does it consume?

2. Refunds: measure working-capital days

For an exporter, refund is working capital.

Every additional day between export, application, sanction and receipt has a financing cost.

Test: How many days does it take for export-related credit to reach the bank, and how much credit remains blocked?

3. Registration: prove the business once

The ideal sequence is:

Data verification → risk assessment → registration → start business

A genuine low-risk business should not experience the same friction as a high-risk applicant.

Test: How many days from application to the first legitimate invoice?

4. Returns: accounting output, not monthly reconstruction

GST returns should increasingly be an output of the accounting system rather than a monthly exercise in making multiple databases agree.

Test: How many people and hours are required simply to make GST data agree?

5. Services exports: ambiguity should not destroy export economics

India increasingly exports software, SaaS, consulting, engineering, professional, financial and specialised services.

Classification, place of supply, overseas structures, realisation and documentation can all affect export treatment.

Test: Can a procedural ambiguity convert a genuine export into a tax cost?

6. Disputes: proportionate treatment

Not every GST dispute represents evasion.

Some arise from interpretation, reconciliation, classification, documentation or small procedural defaults.

A minor mismatch should not necessarily travel through the same machinery as organised fraudulent credit.

Test: Does the cost of contesting a small demand exceed the demand itself?

7. Enforcement: distinguish error from fraud

Strong enforcement is necessary.

But credible enforcement also requires the system to distinguish:

honest mistake → correctable default → serious non-compliance → deliberate fraud

Test: Can the taxpayer understand where compliance risk ends and serious enforcement risk begins?

From officer-driven to system-driven GST

The next generation of GST should increasingly work like this:

Transaction
↓
System captures data
↓
Databases reconcile
↓
Low-risk transactions process automatically
↓
Exceptions are identified
↓
Human intervention focuses on genuine risk

This is particularly important for RCM and ITC.

The taxpayer should not repeatedly prove the same transaction to different parts of the system when the underlying data is already available.

What businesses should measure now

Businesses should move from measuring GST compliance to measuring GST friction.

AreaOld questionBetter question
ITCHow much credit was claimed?How much is usable, blocked or disputed?
RCMWas RCM paid?Can the complete RCM-to-ITC trail be defended?
RefundWas the refund filed?How many working-capital days are blocked?
RegistrationWas GSTIN obtained?How quickly could the business start invoicing?
ReturnsWere returns filed?How much manual effort is required?
ExportsWas the structure documented?Will the structure survive scrutiny?
LitigationHow much is disputed?How much money and management time is consumed?
ComplianceWhat was paid?What is the total cost of staying compliant?

The eight numbers every business should track

Before the next GST reform is announced, management should quantify:

  1. ITC blocked or disputed — with reasons.

  2. RCM exposure — category-wise, including corresponding ITC.

  3. ITC by source — inputs, input services and capital goods.

  4. Refund cycle time — export to actual receipt.

  5. Registration friction — queries, documents and delay.

  6. Reconciliation effort — people and hours spent each period.

  7. GST litigation inventory — substantive disputes versus procedural or reconciliation matters.

  8. Total GST compliance cost — staff time, professional fees, interest, blocked credit, financing cost and management time.

The eighth number is the one most businesses never calculate. It is also the number against which GST 2.0 should ultimately be measured.

CA S. Ahuja Perspective

The first generation of GST asked businesses to adapt to the tax system.

The next generation should make the system adapt better to legitimate business.

That does not mean weaker tax administration.

It means better tax administration:

  • less blocked capital;

  • faster legitimate refunds;

  • fewer repetitive reconciliations;

  • clearer treatment of RCM and ITC;

  • proportionate treatment of genuine errors;

  • less avoidable litigation; and

  • more targeted enforcement against deliberate fraud.

The real test of GST 2.0 is whether a compliant business can:

pay the right tax → claim the right credit → receive its legitimate refund → correct an honest mistake → and defend its position without disproportionate cost, time and uncertainty.

If that happens, GST reform has moved beyond rates into business efficiency.

If the tax is right but the cost of proving it remains high, the reform is incomplete.

A rate cut lowers the price of a product.
A compliance reform lowers the cost of doing business.

Important: The 57th GST Council meeting is scheduled for 8 October 2026. Reported proposals and industry representations should not be treated as law unless and until implemented through the appropriate statutory or administrative instrument.

Friday, October 2, 2026

SOFTEX to EDF: The Complete Exporter’s Guide, Compliance Calendar and FEMA SOP from 1 October 2026

 From SOFTEX to EDF, the form has changed. The compliance responsibility has not.

By CA Surekha S Ahuja 

From 1 October 2026, the export framework has moved to the common Export Declaration Form (EDF) framework. For software, SaaS, consultancy, professional services, BPO and other service exporters, the important change is not simply the replacement of SOFTEX by EDF. The real change is the need to control the complete FEMA life cycle, built into the monthly finance compliance calendar:

Export invoice → EDF → EDPMS → receipt → reconciliation → mark-off → closure

The 30/10 quick reference

Number

What the exporter should remember

1 October 2026

New export framework comes into force

30 days

Applicable monthly EDF filing period for software and services

5 working days

AD bank EDPMS entry timeline for the applicable service EDF

9 months

Normal export realisation period

12 months

Applicable period for exports invoiced or settled in INR

₹10 lakh

Simplified EDPMS closure facility for eligible exports

1 year

Threshold for consequences where proceeds remain unrealised beyond the applicable or extended period

3 times

Maximum penalty where the amount involved is quantifiable

₹2 lakh + ₹5,000/day

Maximum penalty where the amount cannot be quantified, plus the daily penalty for a continuing contravention

The FEMA clock

The realisation period does not begin from the same event for every export.

Export

The clock

Goods

Generally from shipment

Software and services

Generally from invoice

Goods sold from an overseas warehouse

From sale

Exports invoiced or settled in INR

12 months

Project exports

Applicable contractual/regulatory framework

 

Example. A service invoice dated 10 October 2026 will ordinarily have a nine-month realisation deadline of 10 July 2027. A commercial credit period agreed with the customer does not, by itself, replace the FEMA realisation requirement.

1. What has changed from SOFTEX to EDF?

The practical change is: SOFTEX process → common EDF framework → integrated FEMA export control. The exporter must not stop at declaration; the transaction must move through declaration, EDPMS, receipt, reconciliation and closure. The Authorised Dealer (AD) bank has an important operational role in extensions, reductions, set-offs, third-party receipts and closure.

One EDF does not mean one filing route.

Export

Broad route

Goods through EDI port

Shipping bill/customs route

Goods through non-EDI port

Customs route

Software from DTA

AD bank/STPI, as applicable

Other services from DTA

AD bank

SEZ exports

Development Commissioner/applicable SEZ route

 

For service and software exporters, the monthly invoice-to-EDF process is particularly important. October 2026 invoices enter the first monthly EDF cycle, and the filing should ordinarily be completed by 30 November 2026.

2. The FEMA export life cycle

The new compliance system should be designed around one simple chain.

Title: Figure 1. The FEMA export life cycle - Description: Figure 1. The FEMA export life cycle

Figure 1. The FEMA export life cycle

EDF filing is only one event in the FEMA life cycle; it is not the closure of the export transaction. An exporter can have an invoice, an EDF and a bank receipt while the corresponding EDPMS item remains open. The internal control should therefore continue until the applicable FEMA closure is completed.

3. Put EDF into the monthly compliance calendar

This is the most important operational change. FEMA export compliance should not be left to the annual audit or year-end receivable review.

Timing

Compliance action

At invoice

Classify export and calculate FEMA dates

Monthly internal cut-off

Reconcile invoices with books and GST returns (GSTR-1 and GSTR-3B)

Within applicable EDF period

File EDF

After bank processing

Verify EDPMS entry

Monthly

Match receipts with export invoices

At 6 months

Review ageing and problem receivables

Before FEMA due date

Ensure receipt or initiate permitted remedy

After receipt

Obtain mark-off/closure

Quarterly

Review eligible ₹10 lakh closure cases

Monthly/quarterly

CFO review of exceptions

 

Keep statutory and internal dates separate. 30 days and nine months are regulatory timelines. A 15th-of-the-month reconciliation target or a six-month warning is an internal control designed to give time for corrective action.

Why six months? At six months, management can still ask:

•     Is payment actually expected? Is there a customer dispute?

•     Is a short receipt likely? Is third-party payment involved? Is set-off relevant?

•     Will an extension or other permitted remedy be required?

The objective is simple: find the FEMA problem while there is still time to solve it.

4. The CFO FEMA register

Every exporter should maintain one central register rather than separate spreadsheets for Accounts, Treasury and FEMA.

Field

Purpose

Field

Purpose

Customer/country

Counterparty

Receipt

Date and amount

Export category

Goods/software/services

Difference

Short receipt/charges/claim

Invoice/date/value

Underlying transaction

Extension/reduction

Approval/details

GST return

GSTR-1 period; LUT or IGST

Set-off

Details

EDF

Filing date/reference

Third-party receipt

Details

EDPMS

Entry/status

Mark-off

Date

FEMA due date

Realisation deadline

Closure

Final status

 

The monthly reconciliation should be:

Books ↔ Invoice register ↔ GST returns ↔ EDF ↔ Bank ↔ EDPMS

Any unexplained break should become an exception, with an identified owner and action date.

5. Match the EDF with GST returns

The same export invoices are reported under GST and under FEMA, so the two sets of figures should agree every month before the EDF is filed.

GST record

What to match with the FEMA record

GSTR-1, Table 6A (exports)

Invoice number, date and value agree with the EDF for the same month; shipping bill details for goods

GSTR-3B, Table 3.1(b) (zero-rated supplies)

Monthly export turnover agrees with the EDF total and the books

LUT or IGST payment

Each export invoice is identified as supplied under LUT or with IGST paid

Refund claim

Realisation evidence filed with the refund claim (FIRC/BRC) ties to the receipt marked off in EDPMS

Annual return (GSTR-9)

Export turnover for the year agrees with EDFs filed and the books

 

Why it matters. For services, receipt of payment is part of the GST definition of an export of services, so an unrealised invoice is a GST exposure as well as a FEMA one. For goods, rule 96B of the CGST Rules requires a refund to be repaid with interest where proceeds are not realised within the FEMA period, including any extension. The nine-month FEMA date is therefore also a GST date.

Expected differences should be explained, not ignored: exchange-rate differences, credit notes, amendments made in a later GSTR-1, and advances.

6. Realisation ageing: six months is the warning, nine months is the normal period

A service invoice raised on 10 October 2026 may have a normal FEMA realisation deadline of 10 July 2027. The control should operate as follows.

Title: Figure 2. Realisation ageing control - Description: Figure 2. Realisation ageing control

Figure 2. Realisation ageing control

Do not wait for the deadline to expire before approaching the AD bank where regulatory action is required. A longer contractual credit period does not automatically extend the FEMA period.

7. Rs.10 lakh: simplified closure, not blanket exemption

For eligible export entries within the prescribed limit, a simplified declaration-based EDPMS closure mechanism is available. But ₹10 lakh should not be treated as a blanket exemption from FEMA export compliance. Always ask two separate questions: Was EDF required? and Is the transaction eligible for the ₹10 lakh closure facility? These are different compliance questions.

8. The three common exceptions

Exception

The issue

Control

Short receipt

Example: export value ₹12 lakh, receipt ₹10 lakh. The difference may arise from bank charges, exchange differences, discount, rebate, customer claim or another commercial adjustment. The accounting entry does not itself determine the FEMA treatment.

Export value → receipt → difference → FEMA treatment → closure

Third-party receipt

Payment comes from someone other than the overseas customer.

Establish the identity of the payer, the relationship with the customer, the reason for payment, the underlying transaction and compliance with applicable FEMA conditions.

Set-off

An export receivable and import payable may appear commercially capable of set-off. But commercial set-off is not automatically FEMA-permitted set-off.

Check and document the applicable conditions and the AD-bank procedure.

9. AD bank and EDPMS controls

The exporter should obtain the AD bank’s current operating procedure for EDF submission, software/service exports, EDPMS entry, extension, reduction, set-off, third-party receipts, mark-off and closure.

One control should be non-negotiable: EDF submitted ≠ EDPMS updated. The EDPMS reference/status should be verified and retained. Legacy open EDPMS entries should also be reviewed.

10. What happens when export proceeds remain unrealised?

If proceeds remain unrealised beyond the applicable or extended period, the matter should immediately move from routine ageing to FEMA exception management. Where the prescribed period remains exceeded by more than one year, the Regulations provide for restrictions on further exports, including the prescribed full advance payment or irrevocable Letter of Credit requirement, subject to the applicable provisions.

FEMA ageing is therefore not merely an accounts-receivable report. It is a regulatory-risk report.

11. Penalties and regularisation

A contravention can attract penalty under section 13 of FEMA. Where the amount involved is quantifiable, the penalty can extend to three times the sum involved. Where it cannot be quantified, the penalty can extend to ₹2 lakh. A continuing contravention can attract an additional penalty of up to ₹5,000 per day. These are statutory maximums, not automatic penalties in every delayed case.

The practical response is:

Identify → document → regularise → obtain AD-bank treatment → close

Compounding may be available in appropriate cases under section 15 of FEMA.

12. Six controls that prevent most FEMA export problems

#

Control

What it means

1

Separate the three dates

Maintain separately: EDF filing date, FEMA realisation date and EDPMS closure date.

2

Start ageing at invoice level

Do not wait for the balance-sheet date.

3

Trigger review at six months

Six months is the management warning; it is not the statutory deadline.

4

Escalate exceptions before the due date

Short receipt, dispute, third-party payment, set-off or expected delay should be identified early.

5

Reconcile EDPMS monthly

EDF filing alone is not sufficient evidence of closure.

6

Give every exception an owner

A FEMA register without an accountable person is only a spreadsheet.

October 2026: implementation checklist

#

Every exporter should now

Done

1

Replace the old SOFTEX SOP wherever applicable.

 

2

Obtain the AD bank’s current EDF/EDPMS procedure.

 

3

Create one central FEMA export register.

 

4

Load current and legacy open export entries.

 

5

Add FEMA due dates to receivable ageing.

 

6

Introduce a six-month warning trigger.

 

7

Reconcile invoices, GST returns, EDF, bank receipts and EDPMS monthly.

 

8

Identify short receipts and other exceptions.

 

9

Initiate permitted remedies before the deadline where required.

 

10

Assign an owner to every open FEMA exception.

 

11

Include FEMA ageing in the monthly CFO review.

 

12

Complete the first applicable October 2026 monthly EDF cycle by 30 November 2026.

 

The CA S. Ahuja Perspective

SOFTEX was a form. EDF is a system. The real compliance change from 1 October 2026 is not simply the replacement of one declaration with another. It is the need to control the complete export life cycle shown in Figure 1, from invoice to closure. And the management system should operate before the regulatory deadline:

When

What it is

6 months

Warning

9 months

Normal realisation period

Before due date

Remedy where required

Overdue

Immediate exception management

 The safest FEMA export system is not the one that remembers the deadline. It is the one that raises an exception before the deadline arrives.

The simplest management rule: every export invoice should have a FEMA due date, an owner, an EDPMS status and a closure status. That is the practical discipline that replaces the old SOFTEX mindset.