FEMA Compounding: When a Suo Moto Application Blocks 'Technical' Tag
Current · Source: Reserve Bank of India · RBI/2012-13/153 · issued 31 Jul 2012 · ~2 min read
Quick answerOnce an entity files a suo moto compounding application admitting a FEMA contravention, RBI will no longer treat it as 'technical' or 'minor'. The matter must then go through formal compounding under Section 15(1) of FEMA, 1999.
The rule, in the simplest words
If a bank or company files a suo moto (voluntary) application admitting they broke a FEMA (foreign exchange) rule, the RBI (Reserve Bank of India) will NOT call it a 'technical' or 'minor' mistake.
Once a suo moto application is filed, the RBI must start formal compounding (official penalty process) under Section 15(1) of FEMA, 1999.
If the RBI finds the mistake on its own or the company reports it without filing a compounding application, the RBI can still decide if it's technical/minor, material, or serious.
AD Category-I banks (banks allowed to deal in foreign exchange) must tell customers to think carefully before filing a suo moto application, because it removes the chance of a lighter warning.
How it plays out — a real example
A forex & trade-finance officer in Mumbai notices a customer accidentally exceeded the foreign exchange limit for a business trip. Before filing a suo moto compounding application, the officer advises the customer to first check with the bank's compliance team. They explain that if they file the application, the RBI will treat it as a serious violation and start formal penalties, instead of possibly just sending a warning letter.
What changed
RBI clarified that if a contravention is identified by the Bank or reported by the entity outside the formal compounding process, RBI retains discretion to classify it as technical/minor, material, or serious. However, once the entity files a suo moto compounding application admitting the contravention, RBI cannot treat it as technical or minor—compounding proceedings become mandatory.
What it means for you
Banks and their customers lose the chance for a lighter administrative resolution once they voluntarily file a compounding application. This increases the compliance burden and potential penalties for entities that self-report without first assessing whether the contravention could be resolved as technical/minor. AD Category-I banks must advise customers to carefully evaluate before filing suo moto.
What you must do
Advise customers that a suo moto compounding application waives the possibility of a technical/minor classification.
Train compliance teams to distinguish between technical/minor contraventions and those requiring formal compounding.
Update internal advisory materials to reflect the July 31, 2012 circular's stance on suo moto applications.
Ensure customers consult with AD banks before submitting a compounding application to avoid unintended escalation.
Who it affects
All AD Category-I banks, Entities dealing in foreign exchange under FEMA, Compliance officers handling FEMA contraventions
❓ Common questions
Can RBI still treat a contravention as technical if we file a compounding application later?
No. Once a suo moto compounding application is filed admitting the contravention, RBI will not consider it technical or minor. The compounding process under Section 15(1) of FEMA must be followed.
What happens if RBI identifies a contravention before we file anything?
RBI will decide whether it is technical/minor (administrative advice), material (compounding), or serious (referral to Enforcement Directorate). You can still get a lighter resolution if it qualifies as technical.
Does this circular change the compounding rules?
No, it clarifies the existing position from the 2010 circular and press release. The key change is that a suo moto application locks out the technical/minor route.
📜 Read the original circular — full text as issued by RBI
RBI/2012-13/153
A.P. (DIR Series) Circular No.11 July 31, 2012
To
All Category - I Authorised Dealer Banks
Madam / Sir,
Foreign Exchange Management Act, 1999 (FEMA)-
Compounding of Contraventions under FEMA, 1999
Attention of all the Authorised Dealer Category - I (AD Category - I) banks and their constituents is invited to A.P. (DIR Series) Circular no. 56 dated June 28, 2010 and the subsequent Press Release dated August 13, 2010, clarifying the position on ‘technical’ contravention and subsequent compounding thereof.
2. In this connection, it is clarified that whenever a contravention is identified by the Reserve Bank or brought to its notice by the entity involved in contravention by way of a reference other than through the prescribed application for compounding, the Bank will continue to decide (i) whether a contravention is technical and/or minor in nature and, as such, can be dealt with by way of an administrative/ cautionary advice; (ii) whether it is material and, hence, is required to be compounded for which the necessary compounding procedure has to be followed or (iii) whether the issues involved are sensitive / serious in nature and, therefore, need to be referred to the Directorate of Enforcement (DOE). However, once a compounding application is filed by the concerned entity suo moto, admitting the contravention, the same will not be considered as ‘technical’ or ‘minor’ in nature and the compounding process shall be initiated in terms of section 15 (1) of Foreign Exchange Management Act, 1999 read with Rule 9 of Foreign Exchange (Compounding Proceedings) Rules, 2000.
3. Authorised Dealers may bring the contents of this circular to the notice of their constituents and customers concerned.
4. The directions contained in this circular have been issued under sections 10 (4) and 11 (1) of the Foreign Exchange Management Act, 1999 (42 of 1999).
Yours faithfully,
(Dr. Sujatha Elizabeth Prasad)
Chief General Manager-in-Charge
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2012-13/153 · issued 31 Jul 2012. The plain-English explanation above is BankPulse’s own independent summary.
Advise customers that a suo moto compounding application waives the possibility of a technical/minor classification.
Update internal advisory materials to reflect the July 31, 2012 circular's stance on suo moto applications.
Ensure customers consult with AD banks before submitting a compounding application to avoid unintended escalation.
📜 Compliance
Train compliance teams to distinguish between technical/minor contraventions and those requiring formal compounding.
Grouped from the action items above — a single circular may involve more than one team.
Worked example & action-note template
Example: if you are an IT/Systems lead at a bank this circular applies to (All AD Category-I banks, Entities dealing in foreign exchange under FEMA, Compliance officers handling FEMA contraventions), your first concrete step on “FEMA Compounding: When a Suo Moto Application Blocks 'Technical' Tag” is: “Advise customers that a suo moto compounding application waives the possibility of a technical/minor classification.” (RBI issued this 31 Jul 2012).
Circular: RBI/2012-13/153 -- FEMA Compounding: When a Suo Moto Application Blocks 'Technical' Tag
Issued: 31 Jul 2012
Action required: Advise customers that a suo moto compounding application waives the possibility of a technical/minor classification.
Action required: Train compliance teams to distinguish between technical/minor contraventions and those requiring formal compounding.
Action required: Update internal advisory materials to reflect the July 31, 2012 circular's stance on suo moto applications.
Action required: Ensure customers consult with AD banks before submitting a compounding application to avoid unintended escalation.
Owner: ____________ Target date: ____________
Board/committee approval needed? Y / N
Evidence filed in compliance register on: ____________
Built only from this circular’s own published fields — not legal advice; always confirm against the official RBI source.
💬 Banker Discussion
Discuss this circular with fellow bankers — reply, upvote what helps, report what doesn’t belong. Be professional; no client data. Views are the commenter’s own, not BankPulse’s.
BankPulse Compliance Evidence Pack — generated 03 Aug 2026 · status cross-checked against RBI’s official withdrawal register (refreshed weekly). Official RBI source: https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=7485&Mode=0 — Plain-English summary by BankPulse (bankpulse.ai), reviewed by our expert reviewer, CA Amit Jain. Independent platform, not affiliated with the Reserve Bank of India; is our own plain-English paraphrase, not RBI’s original wording.
Help us keep this accurate
Found an inaccuracy or have an improvement? Tell us. Every report is reviewed by our team before any change is made — nothing goes live unverified.
Public beta — plain-English informational summaries. Always verify against the official RBI source (circular number cited on every page) before making compliance, credit, treasury, audit, or operational decisions. · Join our WhatsApp channel ↗
BANKPULSE · FREE DAILY BRIEF
Get RBI updates for your role
Every important RBI update, decoded in plain English — for your career, exams & financial awareness.
We collect only your email, name and role, used solely to send your brief — never sold or shared. Withdraw anytime via the unsubscribe link in any email. Independent platform, not affiliated with the RBI. Information, not legal advice.
REPORT AN ERROR · BETA
Spotted an error? Earn 500 BankPulse Credits
Help us stay accurate. If your correction is verified true and approved by our founder, you earn 500 BankPulse Credits — redeemable when the platform monetises.
Reviewed by a human before any credit is awarded. We never change the site from crowd input without verification.
WANT A NEW FEATURE · BETA
What would make BankPulse more useful for you?
Tell us what to build next — a tool, a data view, a role page, anything. We read every suggestion.
Thank you — your ideas directly shape what we build.