Documents to retain
- legal issue memo
- transaction chronology
- forms and acknowledgements
- amount/delay calculation
- remediation and bank/RBI correspondence
- orders, appeals and closure certificate
The recurring governance model for finance and legal teams.
Building a FEMA Compliance Calendar and Control System is relevant for finance teams, compliance officers, company secretaries, lawyers and auditors. This guide explains the recurring governance model for finance and legal teams and converts the legal framework into a practical decision path.
| Step | Control |
|---|---|
| 1 | Identify the transaction and controlling legal instrument. |
| 2 | Separate substantive breach from reporting delay. |
| 3 | Quantify amount, delay and continuing element. |
| 4 | Complete administrative action and seriousness screening. |
| 5 | Choose LSF, RBI compounding, ED/adjudication or appeal route. |
| 6 | Close evidence, remediate controls and monitor recurrence. |
A group maintains separate spreadsheets for FDI, ODI, ECB and exports. A central event-and-source register reduces missed dependencies.
Identify the person, transaction date and exact legal event before applying a limit or form.
No. Operational acceptance does not cure an impermissible underlying transaction.
Keep the legal-source note, transaction documents, bank trail, valuation/approval where relevant, filing acknowledgement and closure evidence.
Refresh it when residence, ownership, control, amount, activity, instrument terms or law changes.
Do not begin with a form, portal or commercial label. Identify the person, purpose, instrument and transaction date; confirm the substantive route; complete payment, reporting and evidence; and refresh the analysis when facts or law change.
Back to Reporting, Enforcement and Case Law · All FEMA Pages