11.Purpose Codes Under FEMA — How to Select Correctly

Purpose codes under FEMA are regulatory classification tools prescribed by RBI to categorise every foreign exchange transaction. While they appear technical, their selection determines the legal nature of the transaction, applicable limits, and reporting obligations. Errors in purpose coding frequently result in compliance violations.

1. Introduction

Every foreign exchange transaction routed through an Authorised Dealer (AD) bank must be tagged with an RBI purpose code. This code determines:
  • whether the transaction is treated as capital or current account,
  • whether regulatory limits apply, and
  • whether post-transaction reporting is triggered.
Incorrect coding can alter the regulatory character of a transaction.
In FEMA, purpose coding determines compliance consequences.

2. Regulatory Basis of Purpose Codes

Purpose codes are notified by RBI to:
  • monitor cross-border transactions,
  • maintain statistical records, and
  • enforce compliance under FEMA regulations.
Banks are required to report remittances to RBI using these codes.

3. Capital vs Current Account Coding

Purpose codes broadly classify transactions into:
  • current account (trade, services, travel, maintenance), and
  • capital account (investment, loans, guarantees, acquisition of assets).
Capital account codes attract stricter regulatory oversight.
Misclassification can lead to regulatory re-characterisation.

4. Common Purpose Code Categories

Purpose codes typically cover:
  • import/export of goods,
  • professional and consultancy services,
  • royalty and technical fees,
  • education and travel expenses,
  • foreign direct investment (FDI),
  • overseas direct investment (ODI),
  • loans and borrowings.
Each category has a defined regulatory framework.

5. Frequent Errors in Purpose Coding

Common mistakes include:
  • classifying capital infusion as service income,
  • routing foreign share subscription as advance payment,
  • misreporting director loans as consultancy fees,
  • categorising property purchase under travel.
Such misclassifications often surface during audits or compounding reviews.
Incorrect purpose code converts a compliant transaction into a technical contravention.

6. Inward Remittances — Coding Sensitivity

Inward remittances require accurate coding for:
  • export proceeds realisation,
  • foreign investment receipts,
  • external borrowings,
  • gifts from non-residents.
Improper inward coding affects FDI reporting compliance.

7. Outward Remittances — LRS & Business Payments

For outward remittances:
  • individuals must ensure LRS eligibility and purpose alignment,
  • businesses must verify regulatory route before selecting capital codes.
Exceeding limits through incorrect coding increases risk exposure.

8. Impact on Reporting Obligations

Certain purpose codes automatically trigger:
  • FC-GPR filings,
  • FC-TRS filings,
  • ECB returns,
  • ODI reporting.
If coded incorrectly, reporting may not occur, resulting in independent contraventions.

9. Interaction with Tax and Regulatory Framework

Purpose coding may influence:
  • TCS applicability under LRS,
  • withholding tax determination,
  • transfer pricing documentation.
However, FEMA classification is independent of tax classification.

10. Practical Checklist for Correct Selection

Before selecting a purpose code, confirm:
    Residency status of both parties.
    Whether ownership or liability is created.
    Whether RBI approval is required.
    Whether sectoral caps apply.
    Whether reporting obligations are triggered.
Classification must be documented internally.

11. Bank’s Role vs Remitter’s Responsibility

Banks:
  • rely on documentation and declarations,
  • assign codes based on declared nature.
Customers:
  • remain legally responsible for correctness.
Bank processing does not validate regulatory interpretation.

12. Record Keeping and Audit Defence

Maintain:
  • remittance classification notes,
  • purpose code justification,
  • transaction agreements,
  • RBI filing acknowledgements (where applicable).
FEMA scrutiny may arise years after the transaction.

13. Practical Guidance for Businesses

Businesses should:
  • centralise FEMA review before remittance,
  • align accounting classification with purpose codes,
  • maintain a purpose-code tracker linked with reporting deadlines.
Structured review reduces compounding exposure.

14. Practical Guidance for Professionals

Professionals must:
  • independently verify classification,
  • not rely solely on invoice description,
  • document compliance opinion before remittance execution.
Professional diligence is key to regulatory defence.

15. CABTA Insight

“Purpose code is not procedural — it is regulatory positioning.”

Next Article