FEMA for IT/Software Export Companies: SOFTEX, FIRC & Repatriation Compliance

Understanding the FEMA Framework for IT Exports

India’s IT and software export sector earns over USD 200 billion annually in foreign exchange, making FEMA compliance a critical regulatory obligation for every IT company engaged in cross-border service delivery. The FEMA framework for IT exporters is distinct from merchandise exporters in several important ways, and failure to comply can result in penalties, regulatory action, and complications with banking relationships.

At Virtual Auditor, we have built deep expertise in FEMA compliance for the IT sector, serving companies ranging from freelance developers to large IT services firms. Our experience reveals that even well-established IT companies often have significant compliance gaps in their FEMA reporting, primarily due to the complexity of the framework and the multiple agencies involved.

Key Regulatory References

The primary regulations governing FEMA compliance for IT exporters include:

• FEMA, 1999 (Act 42 of 1999): The parent legislation governing all foreign exchange transactions
• FEMA Current Account Transaction Rules, 2000: Rules governing current account transactions including service exports
• RBI Master Direction — Export of Goods and Services (2016, updated): Comprehensive guidelines on export procedures, realisation, and reporting
• SOFTEX Guidelines (RBI/STPI/SEZ): Specific procedures for declaring software export values
• EDPMS (Export Data Processing and Monitoring System): RBI’s automated system for monitoring export transactions
• Foreign Exchange Management (Manner of Receipt and Payment) Regulations, 2016: Regulations governing permitted modes of receipt for export proceeds

SOFTEX Form: The Foundation of IT Export Compliance

The SOFTEX (Software Export Declaration) form is the primary document for declaring the value of software exports from India. It serves a function analogous to the Shipping Bill for merchandise exports, but is specifically designed for software and IT service exports that are delivered electronically.

What is a SOFTEX Form?

SOFTEX is a declaration form prescribed by the RBI under the Foreign Exchange Management (Export of Goods and Services) Regulations, 2015. It captures details of software exports including:

• Exporter details (name, address, IEC, GSTIN)
• Buyer details (name, country, address)
• Invoice details (number, date, value in foreign currency and INR equivalent)
• Nature of software/IT service exported
• Mode of delivery (electronic/physical media)
• Payment terms and expected date of realisation

SOFTEX Filing Process

The SOFTEX filing process involves the following steps:

• Step 1 — Preparation: Compile export invoices, contracts, and supporting documentation for the reporting period
• Step 2 — Filing with designated authority: Submit SOFTEX forms to the jurisdictional STPI centre (for STPI-registered units) or Development Commissioner’s office (for SEZ units)
• Step 3 — Certification: The STPI/SEZ authority verifies the declared values against available benchmarks and certifies the SOFTEX form
• Step 4 — Submission to AD Bank: The certified SOFTEX is forwarded to the exporter’s Authorised Dealer (AD) bank for EDPMS reporting
• Step 5 — EDPMS entry: The AD bank creates an entry in RBI’s Export Data Processing and Monitoring System, linking the SOFTEX to expected remittances

SOFTEX Filing Timeline

SOFTEX forms must be filed within 30 days from the date of invoice or the date of export, whichever is later. However, in practice, STPI/SEZ authorities may accept filings with minor delays. We strongly recommend filing within the prescribed timeline to avoid compliance issues and potential RBI scrutiny.

Exemptions from SOFTEX Filing

Certain categories of IT exports are exempt from SOFTEX filing requirements:

• Individual transactions below USD 25,000: Exports valued at less than USD 25,000 (or equivalent) per transaction can be declared using a simple export declaration without a formal SOFTEX form
• Exports through the Government route: Software exports under bilateral government agreements may have separate reporting mechanisms

However, even for exempt transactions, the export must be reported to the AD bank and captured in EDPMS for monitoring of realisation.

FIRC and eBRC: Proof of Export Realisation

Foreign Inward Remittance Certificate (FIRC) and electronic Bank Realisation Certificate (eBRC) are the two key documents that serve as proof of export proceeds realisation. These documents are essential for multiple compliance purposes including GST refund claims, income tax benefits, and FEMA reporting.

Understanding FIRC

A FIRC is a document issued by an Authorised Dealer bank confirming the receipt of foreign exchange remittance from abroad. For IT exporters, FIRC serves as:

• Primary evidence of export realisation for FEMA purposes
• Supporting document for GST zero-rated export refund claims
• Proof for income tax deductions and exemptions related to export income
• Evidence for STPI/SEZ export performance compliance

Electronic Bank Realisation Certificate (eBRC)

The eBRC is the electronic version of the Bank Realisation Certificate, generated through the DGFT’s (Directorate General of Foreign Trade) system. It has largely replaced the physical BRC process and offers several advantages:

• Automated generation: eBRC is generated automatically when the AD bank reports the realisation to DGFT’s system
• Real-time availability: Available for download from the DGFT portal shortly after the bank reports the realisation
• Multiple uses: Can be used for DGFT schemes, FEMA compliance, GST refunds, and income tax purposes
• Reduced paperwork: Eliminates the need for physical bank certificates

Obtaining FIRC and eBRC

The process for obtaining these documents involves:

• FIRC: Request from AD bank upon receipt of foreign remittance. Banks typically issue FIRC within 3 to 5 working days of the remittance being credited
• eBRC: Generated automatically when the AD bank transmits realisation data to DGFT. IT companies can download eBRC from the DGFT portal using their IEC number

Common Issues with FIRC/eBRC for IT Companies

In our practice, we frequently encounter the following issues:

• Mismatch between SOFTEX value and FIRC amount: Due to exchange rate fluctuations, deductions by correspondent banks, or partial payments
• Delayed eBRC generation: When banks fail to transmit realisation data to DGFT promptly
• Multiple remittances against single SOFTEX: Requiring reconciliation of partial realisations
• Pooled remittances: Foreign clients making consolidated payments for multiple invoices, requiring allocation across SOFTEX entries

Repatriation of Export Proceeds

One of the most critical FEMA obligations for IT exporters is the timely repatriation (bringing back to India) of export proceeds. The RBI has prescribed specific timelines and procedures for this purpose.

Repatriation Timeline

Under the FEMA framework, IT export proceeds must be realised and repatriated to India within the following timelines:

• Standard timeline: 9 months from the date of export (date of invoice or SOFTEX, whichever is applicable)
• Extended timeline: Up to 15 months with prior RBI approval in exceptional cases
• Write-off provisions: Unrealised export bills can be written off under specific conditions prescribed by RBI, subject to AD bank approval

Monitoring Through EDPMS

The Reserve Bank of India monitors export realisation through the Export Data Processing and Monitoring System (EDPMS). Each SOFTEX entry creates a corresponding EDPMS entry that tracks:

• Export declaration details
• Expected realisation date
• Actual remittance receipts and their matching with export entries
• Overdue status and follow-up actions

Unmatched or overdue EDPMS entries trigger automatic alerts to both the AD bank and the RBI, potentially resulting in:

• Cautionary advices from the AD bank
• RBI scrutiny and potential investigation
• Restrictions on future export transactions
• Penalties under Section 13 of FEMA (up to thrice the amount involved)

Strategies for Timely Repatriation

We recommend the following practices for IT exporters:

• Clear payment terms in contracts: Specify payment milestones, due dates, and currencies in every client contract
• Regular follow-up mechanism: Implement a systematic follow-up process for outstanding invoices well before the 9-month deadline
• Currency hedging: Use forward contracts or options to manage exchange rate risk, which can otherwise delay payment decisions by foreign clients
• Escalation matrix: Define clear escalation procedures for overdue payments, involving finance, legal, and management teams
• Proactive EDPMS monitoring: Regularly reconcile EDPMS entries with actual remittances to identify and address mismatches early

Advance Remittance for IT Services

Many IT export contracts involve advance payments from foreign clients, whether as project mobilisation advances, subscription prepayments, or retainer fees. FEMA prescribes specific rules for handling advance remittances.

Rules for Receiving Advance Payments

Under the RBI Master Direction on Export of Goods and Services:

• Advance payment is permitted: IT exporters can receive advance payments from foreign buyers without RBI approval
• No interest obligation: Unlike advance payments for merchandise exports, service exporters generally do not face interest complications on advances
• Adjustment within export timeline: The advance must be adjusted against actual exports within the prescribed realisation period (9 months from the date of export)
• Refund of unutilised advance: If the export cannot be completed, the advance must be refunded to the foreign buyer through banking channels with proper documentation

Accounting Treatment for Advance Remittances

Proper accounting treatment of advance remittances is essential for both FEMA compliance and financial reporting:

• Advances should be booked as “Advance from Customers” (current liability) until the service is delivered
• Revenue recognition must align with the delivery of services, not the receipt of payment
• Exchange rate differences between the date of advance receipt and service delivery date must be properly accounted for
• GST implications on advances must be evaluated — under GST, the time of supply for services is generally the date of invoice or payment, whichever is earlier

Deemed Exports and FEMA Compliance

Certain categories of IT service delivery may qualify as “deemed exports” for FEMA purposes, with specific compliance implications.

What Constitutes Deemed Export for IT?

In the FEMA context, deemed exports arise when IT services are delivered to entities within India but payment is received in foreign exchange or the ultimate beneficiary is a foreign entity. Common scenarios include:

• Services to Indian subsidiaries of foreign companies: Where the Indian entity bills in INR but the parent company pays in foreign exchange
• SEZ supplies: IT services provided by a Domestic Tariff Area (DTA) unit to an SEZ unit
• Projects funded by international organisations: World Bank, ADB, or UN-funded projects in India

FEMA Treatment of Deemed Exports

The FEMA treatment of deemed exports requires careful analysis:

• If payment is received in foreign exchange, standard export reporting (SOFTEX, FIRC, EDPMS) applies
• If payment is received in INR from an Indian entity, the transaction may not be classified as an export under FEMA, even if it qualifies as deemed export under GST or DGFT policy
• SEZ supplies require specific documentation under the SEZ Act and Rules, with separate FEMA implications

Foreign Currency Accounts for IT Exporters

IT exporters are permitted to maintain certain foreign currency accounts under FEMA to facilitate their export operations.

Exchange Earners’ Foreign Currency (EEFC) Account

IT exporters can retain a portion of their export earnings in an EEFC account maintained with an AD bank in India. Key features:

• Up to 100% of export earnings can be credited to the EEFC account
• The balance must be converted to INR within 30 days if not utilised for permissible purposes
• Permissible uses include payment for imports, travel expenses, and other current account transactions
• No interest is payable on EEFC account balances

Overseas Office Accounts

IT companies with overseas offices or branches can maintain foreign currency accounts abroad, subject to:

• RBI approval (automatic or specific route depending on the amount and country)
• Reporting to RBI through the AD bank
• Repatriation of surplus funds within prescribed timelines
• Annual certification by a chartered accountant

FEMA Penalties and Enforcement

Non-compliance with FEMA regulations carries significant consequences for IT companies:

Penalties Under FEMA

• Monetary penalty: Up to thrice the amount involved in the contravention, or ₹2 lakh where the amount is not quantifiable
• Continuing contravention: Additional penalty of ₹5,000 per day for each day the contravention continues beyond the initial penalty
• Compounding: FEMA contraventions can be compounded (settled) by paying a compounding amount to the RBI or the Directorate of Enforcement, avoiding adjudication proceedings

Common Contraventions by IT Companies

• Failure to realise export proceeds within the prescribed timeline
• Non-filing or delayed filing of SOFTEX forms
• Unmatched EDPMS entries due to reconciliation failures
• Unauthorised write-off of export receivables without AD bank approval
• Incorrect reporting of export values (mismatch between SOFTEX and actual invoices)
• Failure to maintain proper documentation for advance remittances

FEMA Compliance Checklist for IT Exporters

We recommend IT exporters maintain compliance with the following checklist:

• Monthly: SOFTEX filing for all export invoices raised during the month
• On receipt of remittance: Obtain FIRC from AD bank, download eBRC from DGFT portal
• Quarterly: EDPMS reconciliation — match all SOFTEX entries with actual remittances
• Monthly/Quarterly: Follow up on outstanding receivables approaching the 9-month deadline
• Annually: Review EEFC account balances and ensure compliance with utilisation norms
• Annually: Annual Performance Report for overseas offices/branches (if applicable)
• As applicable: Report significant transactions to AD bank within prescribed timelines

Integration of FEMA with GST and Income Tax Compliance

FEMA compliance for IT exporters does not exist in isolation — it is deeply interlinked with GST and income tax compliance:

• GST refunds: FIRC/eBRC is required as supporting documentation for GST ITC refund claims by IT exporters
• Income tax: Export turnover certified through SOFTEX forms is used for computing deductions under Section 10AA (SEZ units) and other export-related benefits
• Transfer pricing: FEMA export valuations must be consistent with transfer pricing documentation for related-party transactions
• Form 15CA/15CB: Certain outward remittances by IT companies require chartered accountant certification under the Income Tax Act, with cross-references to FEMA approvals

Frequently Asked Questions

1. What is a SOFTEX form and when is it required for IT companies?

A SOFTEX (Software Export Declaration) form is a mandatory declaration prescribed by the RBI for reporting the value of software and IT service exports from India. It is required for all IT export transactions exceeding USD 25,000 per invoice and must be filed within 30 days from the date of export. The form is certified by STPI (for STPI-registered units) or the Development Commissioner (for SEZ units) and serves as the IT sector’s equivalent of a Shipping Bill for merchandise exports. Proper SOFTEX filing is the foundation of FEMA compliance for IT companies.

2. How do IT companies obtain FIRC for export remittances?

IT companies obtain FIRCs (Foreign Inward Remittance Certificates) from their Authorised Dealer (AD) bank upon receipt of foreign exchange remittance. The company should request the FIRC from the bank within a few days of the remittance being credited. Additionally, the electronic Bank Realisation Certificate (eBRC) is generated automatically when the AD bank transmits realisation data to DGFT and can be downloaded from the DGFT portal using the company’s IEC number. Both documents serve as proof of export realisation for FEMA compliance, GST refund claims, and income tax purposes.

3. What is the deadline for repatriation of IT export proceeds?

Under FEMA regulations, IT export proceeds must be realised and repatriated to India within 9 months from the date of export (invoice date). In exceptional circumstances, an extension of up to 15 months can be obtained with RBI approval through the AD bank. Failure to repatriate within the prescribed timeline constitutes a FEMA contravention, attracting penalties of up to thrice the amount involved. We advise IT companies to implement systematic follow-up mechanisms well before the 9-month deadline.

4. What happens if EDPMS entries remain unmatched?

Unmatched EDPMS entries — where SOFTEX filings are not reconciled with corresponding remittance receipts — trigger automatic alerts in the RBI system. This can lead to cautionary advices from the AD bank, RBI scrutiny of the exporter’s accounts, restrictions on future export transactions, and ultimately enforcement action with penalties. We strongly recommend quarterly EDPMS reconciliation to identify and resolve mismatches proactively, rather than waiting for regulatory intervention.

5. Can IT companies receive advance payments from foreign clients?

Yes, IT exporters are permitted to receive advance payments from foreign clients without requiring prior RBI approval. The advance must be adjusted against actual exports within the standard realisation period. If the export cannot be completed, the advance must be refunded through banking channels. Proper accounting treatment is essential — advances should be booked as current liabilities until service delivery, and GST implications on advance receipt must be evaluated under the time of supply rules.

6. How does FEMA compliance interact with GST refund claims for IT exporters?

FEMA and GST compliance are deeply interconnected for IT exporters. FIRC/eBRC documents serve as essential supporting evidence for GST ITC refund claims under Rule 89. The export turnover reported in SOFTEX forms must reconcile with the zero-rated turnover declared in GST returns (GSTR-1 and GSTR-3B). Discrepancies between FEMA export reporting and GST return filings can lead to rejection of refund claims and trigger cross-referral audits by both tax authorities.

7. What are the FEMA implications for IT companies with overseas offices?

IT companies maintaining overseas offices or branches must comply with additional FEMA requirements: obtaining RBI approval (automatic or specific route) for overseas direct investment, maintaining proper foreign currency accounts abroad, filing Annual Performance Reports with RBI through the AD bank, repatriating surplus funds within prescribed timelines, and obtaining annual chartered accountant certification. Non-compliance can result in enforcement action and restrictions on future overseas operations.