| Point | Detail |
|---|---|
| Point 1 | FEMA is the Indian law that regulates foreign exchange transactions |
| Point 2 | FEMA affects cross-border payment projects in concrete ways that must appear |
| Point 3 | The Liberalised Remittance Scheme, known as LRS |
| Point 4 | The documentation a BA must capture for a FEMA compliant project starts |
| Point 5 | FEMA and RBI regulations are related but not identical |
FEMA Compliance for Payments IT Projects
What you will learn
Your objective. By the end of this lesson, you will be able to explain fema compliance for payments it projects. FEMA is the Indian law that regulates foreign exchange transactions, and its core principle is that foreign exchange can only be dealt with through authorised persons, such as banks licensed as authorised dealers, and.
Why it matters. A customer who has already remitted 240,000 dollars cannot remit a further 20,000 dollars in the same financial year.
Chapter objective: Learner explains Indian payment systems in depth, including NACH, BBPS, and FEMA rules, and applies them to recurring collections, bill payments, and cross-border transfers from India. Learner practises this skill on realistic banking cases, explaining the reasoning clearly and using correct terminology throughout the work.
Key learning points
- FEMA: Indian law
- FEMA: concrete effects on projects
- Without that matrix
- BA must specify how the cumulative total
- System must store these documents
- FEMA permissions and RBI directions
Key terms
Purpose code: A code that states the commercial reason for a payment, such as supplier payment, salary or goods. Purpose codes are taken from an ISO external code list and support regulatory reporting, screening...
Capture: The step in a card transaction where the merchant collects the authorised amount from the issuer, usually when goods are shipped.
Scheme: A card or payment network that sets the rules, standards and fees for transactions between issuers and acquirers.
Regulatory comparison showing FEMA Compliance for Payments IT Projects.
Practise this lesson
Exercise
Decide which settlement model fits the scenario in this lesson and explain why.
Use the settlement models, the liquidity trade-off and the finality rules in this lesson.
- What to do. Name the model, state when settlement becomes final, and explain what happens if the sending bank does not have enough liquidity.
Correct result. Real time gross settlement settles each payment individually in central bank money with immediate finality, but it needs liquidity for every payment. Deferred net settlement nets payments and settles the net position, which needs less liquidity but leaves settlement risk until the net settles.
Why. Settlement is where money actually moves. The model decides the risk, the liquidity need, and when the payment is truly final.
Check your understanding
Practice question
Which of the following best describes fema compliance for payments it projects?
Takeaway and next step
What to remember
The BA should never design a flow that allows a customer to send foreign exchange for a purpose that FEMA does not permit.
Follow 240,000 dollars through every stage, from instruction to beneficiary credit, and note where it can stop.
Open the Payment Lifecycle Simulator →
Builds on "UPI Architecture in Depth: VPA, PSP Apps and the NPCI Switch".
Transcript and full text
Show transcript
FEMA is the Indian law that regulates foreign exchange transactions, and its core principle is that foreign exchange can only be dealt with through authorised persons, such as banks licensed as authorised dealers, and only for permitted purposes. The Act replaced the earlier FERA, which was more restrictive, and it introduced a framework where current account transactions, such as trade payments, travel and education, are generally permitted, while capital account transactions, such as investments abroad, are subject to limits and conditions. A BA working on a cross-border payments project must know which category a transaction falls into, because the documentation, the approval and the reporting differ. The BA should never design a flow that allows a customer to send foreign exchange for a purpose that FEMA does not permit. FEMA affects cross-border payment projects in concrete ways that must appear in the requirements. Every outward remittance must capture the purpose code, the beneficiary details, the source of funds, and the declaration that the customer has made under FEMA, and the system must validate the purpose against the permitted list before the payment is released. The system must also check the customer limits, screen the beneficiary and the destination country against sanctions lists, and store the declaration and the supporting documents for audit. A BA should work with the compliance team to produce a purpose code matrix that maps each purpose, such as education, medical treatment or family maintenance, to the documents required, the limit that applies, and the approval workflow. Without that matrix, the development team will build a generic remittance screen that compliance cannot approve. The Liberalised Remittance Scheme, known as LRS, is the framework that allows a resident Indian individual to remit up to 250,000 US dollars per financial year for permitted current and capital account transactions. The limit is per person per financial year, and it covers purposes such as travel, education, medical treatment, gifts, maintenance of relatives abroad, and investment in foreign shares and property. The system must track the cumulative remittances of each customer across the financial year and block any remittance that would exceed the limit, and it must report the remittances to the Reserve Bank of India. A BA must specify how the cumulative total is calculated, how it handles remittances made through other banks, and what the customer sees when the limit is reached. A customer who has already remitted 240,000 dollars cannot remit a further 20,000 dollars in the same financial year. The documentation a BA must capture for a FEMA compliant project starts with the customer declaration, usually in the form of an A2 form or an online equivalent, where the customer states the purpose, the amount and the beneficiary, and declares that the remittance is within the LRS limit and for a permitted purpose. The BA must also capture the PAN of the remitter, the supporting documents such as a university admission letter for education or a hospital estimate for medical treatment, and the tax collected at source where applicable. The system must store these documents with the transaction, link them to the purpose code, and retain them for the period required by the regulator. The requirements should also define the maker checker process, one user enters the remittance, another approves it, and the system records both identities with timestamps. FEMA and RBI regulations are related but not identical, and a BA should be able to explain the difference in a meeting. FEMA is the Act passed by Parliament that sets the legal framework for foreign exchange, while the RBI issues the regulations, directions and master directions that implement FEMA in practice, such as the Master Direction on Liberalised Remittance Scheme and the Master Direction on Export and Import of Goods and Services. In other words, FEMA says what is permitted, and the RBI directions say how it must be done, what forms to use, and what reports to file. A BA should cite the specific RBI Master Direction in the requirements document, include the version and date, and maintain a change log so that when the RBI updates a direction, the impact on the requirements can be assessed quickly and accurately.
FEMA is the Indian law that regulates foreign exchange transactions, and its core principle is that foreign exchange can only be dealt with through authorised persons, such as banks licensed as authorised dealers, and only for permitted purposes. The Act replaced the earlier FERA, which was more restrictive, and it introduced a framework where current account transactions, such as trade payments, travel and education, are generally permitted, while capital account transactions, such as investments abroad, are subject to limits and conditions. A BA working on a cross-border payments project must know which category a transaction falls into, because the documentation, the approval and the reporting differ. The BA should never design a flow that allows a customer to send foreign exchange for a purpose that FEMA does not permit.
FEMA affects cross-border payment projects in concrete ways that must appear in the requirements. Every outward remittance must capture the purpose code, the beneficiary details, the source of funds, and the declaration that the customer has made under FEMA, and the system must validate the purpose against the permitted list before the payment is released. The system must also check the customer limits, screen the beneficiary and the destination country against sanctions lists, and store the declaration and the supporting documents for audit. A BA should work with the compliance team to produce a purpose code matrix that maps each purpose, such as education, medical treatment or family maintenance, to the documents required, the limit that applies, and the approval workflow. Without that matrix, the development team will build a generic remittance screen that compliance cannot approve.
The Liberalised Remittance Scheme, known as LRS, is the framework that allows a resident Indian individual to remit up to 250,000 US dollars per financial year for permitted current and capital account transactions. The limit is per person per financial year, and it covers purposes such as travel, education, medical treatment, gifts, maintenance of relatives abroad, and investment in foreign shares and property. The system must track the cumulative remittances of each customer across the financial year and block any remittance that would exceed the limit, and it must report the remittances to the Reserve Bank of India. A BA must specify how the cumulative total is calculated, how it handles remittances made through other banks, and what the customer sees when the limit is reached. A customer who has already remitted 240,000 dollars cannot remit a further 20,000 dollars in the same financial year.
The documentation a BA must capture for a FEMA compliant project starts with the customer declaration, usually in the form of an A2 form or an online equivalent, where the customer states the purpose, the amount and the beneficiary, and declares that the remittance is within the LRS limit and for a permitted purpose. The BA must also capture the PAN of the remitter, the supporting documents such as a university admission letter for education or a hospital estimate for medical treatment, and the tax collected at source where applicable. The system must store these documents with the transaction, link them to the purpose code, and retain them for the period required by the regulator. The requirements should also define the maker checker process, one user enters the remittance, another approves it, and the system records both identities with timestamps.
FEMA and RBI regulations are related but not identical, and a BA should be able to explain the difference in a meeting. FEMA is the Act passed by Parliament that sets the legal framework for foreign exchange, while the RBI issues the regulations, directions and master directions that implement FEMA in practice, such as the Master Direction on Liberalised Remittance Scheme and the Master Direction on Export and Import of Goods and Services. In other words, FEMA says what is permitted, and the RBI directions say how it must be done, what forms to use, and what reports to file. A BA should cite the specific RBI Master Direction in the requirements document, include the version and date, and maintain a change log so that when the RBI updates a direction, the impact on the requirements can be assessed quickly and accurately.
Full lesson text (all scenes)
Completing a lesson updates your progress dashboard on the homepage.
Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.