What Happens If You Use the Wrong Purpose Code on an Inward Remittance?
- Author:
- Manoj Sharma
- Verified by:
- Editorial team
- Published:
- Last modified:
Short answer
A wrong purpose code misstates why money came into India in the bank's FETERS report to RBI. For an exporter, a wrong code can stop the receipt matching the export entry, block eBRC generation and weaken GST refund records. Your AD bank can amend the code, so ask for a correction as soon as you notice it.
| Applies to | Governed by | Deadline | Penalty | Last verified |
|---|---|---|---|---|
| Anyone receiving foreign currency into India, with the largest impact on exporters of services, software and goods, including freelancers | Regulation 18(2), FEMA (Export and Import of Goods and Services) Regulations, 2026; RBI A.P. (DIR Series) Circular No. 84 (2012) on FETERS purpose codes | No fixed deadline to correct a purpose code; the export realisation period of nine months (Regulation 5) keeps running while a receipt stays unmatched | No separate penalty for a wrong code in the 2026 Regulations; a resulting FEMA contravention can attract a section 13 penalty of up to three times the sum involved | 8 Oct 2026 |
What does a wrong purpose code change in RBI reporting?
A wrong purpose code changes how RBI records the payment, because banks report every foreign trade transaction in FETERS with a purpose code. Under Regulation 18(2) of the 2026 Regulations, an Authorised Dealer must report all foreign trade transactions in the Foreign Exchange Transaction Electronic Reporting System (FETERS) as per RBI guidelines.
- RBI data: Since April 2012, banks report every foreign exchange transaction under a purpose code from the revised list in A.P. (DIR Series) Circular No. 84. A wrong code places your receipt in the wrong purpose group in the data your bank reports to RBI.
- EDPMS: Banks must enter inward remittances for all exports in EDPMS and mark off the export entry once the value is realised, under Regulation 18(1)(e) and (g). A receipt coded as a non-export purpose may not be linked to your export entry.
- Bank checks: Under Regulation 4(2), a bank credits an export receipt only after it is satisfied the transaction is genuine. A code that does not match your invoice or business profile can lead to a query or a request for documents.
- eBRC: The bank sends an Inward Remittance Message (IRM) carrying the purpose code to DGFT. The DGFT eBRC rules restrict which codes can produce an eBRC for each export type.
- GST papers: A GST refund claim for export of services needs a statement of invoices with the matching BRC or FIRC under Rule 89(2)(c) of the CGST Rules. A certificate showing a non-export purpose is weaker evidence for that claim.
A wrong purpose code is usually a reporting error that the bank can fix. The real risk comes from leaving it uncorrected while export deadlines and refund claims depend on the record.
Who is affected by a wrong purpose code on an inward remittance?
Exporters are affected most by a wrong purpose code, because their receipts must close export entries and support GST and eBRC records. People receiving personal transfers face fewer follow-on effects, though the bank's report to RBI is still wrong.
| Receiver | Main impact | Why | Best for |
|---|---|---|---|
| Freelancer or consultant exporting services | High | Receipt must match the invoice and EDF entry in EDPMS and support GST refund or LUT records | Individuals billing foreign clients |
| Software or SaaS exporter | High | DGFT allows only P0802, P0803, P0807 and P0103 for eBRC under Services > IT | IT services and software businesses |
| Goods exporter | High | Receipt must close the shipping bill entry in EDPMS; P0101 and P0108 cannot be used for eBRC | Merchant and manufacturer exporters |
| Exporter receiving an advance | Medium | An advance is reported under P0103 and must be routed through the same AD bank as the later export proceeds under Regulation 10(1), unless both banks are told of a change | Businesses taking upfront payments |
| Individual receiving a family transfer or gift | Low | No export entry to close, but the FETERS report is still wrong | Residents receiving personal remittances |
How do you correct a wrong purpose code after the money is credited?
You correct a wrong purpose code by asking the bank that handled the remittance to amend it. DGFT's eBRC FAQ says exporters must contact the bank to change a purpose code, and that banks have the authority to amend the IRM and send the updated details.
- Compare the code on your credit advice, FIRA or FIRC with your invoice and contract, and identify the code that describes the service or goods. The RBI purpose codes list groups codes by type.
- Write to your AD bank (or the bank branch that received the money) with the transaction reference, date, amount, remitter name, the code shown and the code you want.
- Attach the invoice, the contract or engagement letter, and the EDF if one was filed under Regulation 3(2).
- Ask the bank to amend the IRM sent to DGFT, as DGFT FAQ 28 says banks can do.
- Ask for a revised inward remittance certificate or advice showing the corrected code, and keep the bank's written confirmation with the invoice.
- Check that the export entry in EDPMS is marked off against the receipt, and regenerate the eBRC on the DGFT portal if needed.
What should you do if the bank refuses or ignores a purpose code correction request?
If the bank refuses or ignores the request, use its grievance route. Regulation 19(2) requires every AD bank's export policy and SOP to include an escalation process for customer grievances and an appeal handled at a higher internal level.
- Regulation 19(4) requires the bank to publish its policy and the main features of its SOP on its website.
- Regulation 19(1)(a) requires the policy to list the documents, timelines and charges for each process.
- Keep a copy of every request and reply in case you need to escalate.
Can a bank charge a penalty for a purpose code error made by the exporter?
A bank cannot charge you a penalty for a regulatory delay or violation on your part. Regulation 19(3) says an AD bank shall not levy charges or penalty on its exporter, importer or merchant trader constituent for any regulatory delay or violation, and that its charges must be reasonable and proportional.
- The bank may still apply its normal published service charges for processing an amendment, if its SOP lists one.
How does a purpose code correction affect the eBRC on the DGFT portal?
A purpose code correction reaches DGFT through an amended IRM from the bank. Under DGFT FAQ 17, exporters must choose the SAC code that corresponds to the purpose code, so a wrong code can leave no matching SAC option for your invoice. Read more in the eBRC on DGFT guide.
- DGFT rule 12 lets service exporters attach only invoices whose SAC codes match the description of the same services.
- DGFT rule 9 allows only P0103 (advance) to be clubbed with another purpose code in a single eBRC.
Which records does a wrong purpose code affect, and what documents fix each one?
A wrong purpose code can affect five records: the FETERS report, the EDPMS entry, the eBRC, GST refund papers and the LUT position. The table below shows what each record needs and which document helps put it right.
| Record | What can go wrong | Document to fix it | Best for |
|---|---|---|---|
| FETERS report to RBI | Receipt classified under the wrong purpose group | Bank's written confirmation of the amended code | All receivers of foreign currency |
| EDPMS export entry | Receipt not linked to the invoice or shipping bill, so the entry stays open | Invoice, EDF and amended remittance advice; for invoices up to Rs 10 lakh, your realisation declaration under Regulation 4(2) | Service and goods exporters |
| eBRC on DGFT | eBRC blocked or SAC mismatch | Amended IRM from the bank | Exporters claiming FTP benefits or proving realisation |
| GST refund claim | Certificate does not show an export receipt for the invoice | Revised FIRC or BRC listed against each invoice under Rule 89(2)(c) | Exporters claiming ITC refunds |
| LUT export of services | Payment not shown as received against the export invoice | Revised certificate showing receipt within the Rule 96A(1)(b) period | Exporters supplying under LUT without IGST |
What happens if a wrong purpose code is never corrected?
If a wrong purpose code is never corrected, the export can look unpaid in the bank's records even though the money arrived. That can trigger realisation follow-ups, restrictions on future exports, a GST demand under the LUT and a weaker refund claim.
- Open entry: Banks must follow up on outstanding EDPMS entries under Regulation 18(1)(f), so an unmatched receipt can lead to repeated requests for documents. See EDPMS for service exporters.
- Realisation: Export value must be realised within nine months from the invoice date for services, or twelve months if invoiced or settled in rupees, under Regulation 5. A receipt that is not linked may leave the export showing as unrealised. See the export realisation period.
- Advance only: If export proceeds remain unrealised for more than one year beyond the due or extended date, Regulation 13 allows further exports only against full advance or an irrevocable letter of credit.
- GST under LUT: Under Rule 96A(1)(b), an exporter under LUT must pay the tax with interest if payment for services is not received within one year, or the FEMA period with any RBI-permitted extension, whichever is later. Records that do not show the receipt make this harder to prove.
- FEMA penalty: Under section 13(1) of FEMA, as restated in RBI's Master Circular on Compounding, a contravention can attract a penalty of up to three times the sum involved where quantifiable. The 2026 Regulations set no separate penalty for a wrongly declared code.
- Income tax: The Income-tax Act, 2025 replaced the 1961 Act from 1 April 2026. A purpose code that conflicts with your books and invoices can raise questions, so keep invoices and bank records consistent.
Ask your AD bank in writing to amend the purpose code and the IRM, attach the invoice and contract, and get a revised certificate. Then check that the EDPMS entry is marked off and regenerate the eBRC. The step-by-step correction guide covers the request in more detail.
Which RBI and DGFT rules govern purpose code reporting and correction?
Purpose code reporting rests on RBI's FETERS circular of 2012 and Regulation 18(2) of the 2026 Export and Import Regulations, in force from 1 October 2026. Correction runs through the bank, as DGFT's eBRC FAQs confirm. Circular No. 20 of 16 January 2026 superseded the old Master Direction on export from the same date.
| Circular or regulation | Clause | Date | Plain meaning | Best for |
|---|---|---|---|---|
| A.P. (DIR Series) Circular No. 84 | Para 3 | 29 February 2012 | Banks report all foreign exchange transactions under the revised purpose code list from April 2012 | Understanding where purpose codes come from |
| FEMA (Export and Import of Goods and Services) Regulations, 2026 | Reg 18(2) | In force 1 October 2026 | Banks report all foreign trade transactions in FETERS | Exporters checking current rules |
| FEMA (Export and Import of Goods and Services) Regulations, 2026 | Reg 4(2) and 18(1)(e), (g) | In force 1 October 2026 | Bank checks genuineness, credits the receipt and closes or updates the EDPMS entry | Exporters with open EDPMS entries |
| FEMA (Export and Import of Goods and Services) Regulations, 2026 | Reg 19(2), (3) | In force 1 October 2026 | Bank must offer grievance escalation and cannot penalise you for your regulatory delay or violation | Exporters whose correction request stalls |
| DGFT eBRC FAQs | Q17, Q25, Q28 | March 2024 | Purpose code maps to SAC; ask the bank to change a code; banks can amend the IRM | Exporters generating eBRCs |
| DGFT self-certified eBRC guidelines | Rules 3, 9, 10, 12 | 10 November 2023 | Lists which purpose codes can produce an eBRC and how invoices must match | Software and service exporters |
What are the common purpose code mistakes made by Indian exporters?
- Personal code: Picking a personal transfer code such as P1301, which RBI's purpose code list describes as "Inward remittance from Indian non-residents towards family maintenance and savings", for client fees. The receipt is then reported as a personal transfer.
- Wrong group: Choosing P1006 ("Business and management consultancy and public relations services") for software development, or P0802 ("Software consultancy/implementation (other than those covered in SOFTEX form)") for marketing work. Compare similar codes in P0802 vs P0807.
- Advance code: Using P0103 for a payment that is not an advance. RBI describes P0103 as "Advance receipts against export contracts, which will be covered later by GR/PP/SOFTEX/SDF – other than Nepal and Bhutan".
- Late check: Noticing the code only when filing a GST refund or generating an eBRC months later, when the bank needs more time to trace and amend the transaction.
- No paper trail: Asking for a correction by phone only. A written request and the bank's written reply are the records you will need for GST and EDPMS.
- Invoice mismatch: Describing the service one way on the invoice and choosing a code for a different service. Banks compare the two, and DGFT matches SAC codes to the purpose code.
How did we verify this?
Every rule, deadline and form on this page is linked to its official source, checked on the dates below.
- Foreign Exchange Management (Export and Import of Goods and Services) Regulations, 2026, Notification FEMA 23(R)/2026-RB dated 13 January 2026, amended up to 22 September 2026, Regulations 1(2), 3(2), 4(2), 5(1), 10(1), 13, 18(1)(e) to (g), 18(2), 19(1) to (4); footnotes on FEMA 23(R)/(1)/2026-RB (checked 8 Oct 2026)
- RBI A.P. (DIR Series) Circular No. 84 dated 29 February 2012: Compilation of R-Returns, Reporting under FETERS, Paragraph 3: report all foreign exchange transactions as per the revised purpose code list from April 2012 (checked 8 Oct 2026)
- RBI A.P. (DIR Series) Circular No. 20, RBI/2025-26/194, 16 January 2026: Export and Import of Goods and Services, Paragraphs 4 and 7: Master Directions on export and import and listed circulars superseded from 1 October 2026 (checked 8 Oct 2026)
- RBI FETERS purpose code list (attachment to A.P. (DIR Series) Circular No. 84 dated 29 February 2012), Receipt purpose codes P0101, P0103, P0108, P0802, P0803, P0807, P1006, P1301 (checked 8 Oct 2026)
- DGFT FAQs (Self-Generation of eBRC), Version 1.0, March 2024, Q4, Q17, Q25, Q28 (checked 8 Oct 2026)
- DGFT Self-Certified eBRC Generation Guidelines, Version 1.0 (10 November 2023), Rules 3, 9, 10 and 12 (checked 8 Oct 2026)
- Integrated Goods and Services Tax Act, 2017: Section 2 (Definitions), CBIC tax information portal, Section 2(6): definition of export of services (checked 8 Oct 2026)
- Central Goods and Services Tax Rules, 2017: Rule 89 (Application for refund), Rule 89(2)(c): invoices with relevant BRCs or FIRCs for refunds on export of services (checked 8 Oct 2026)
- Central Goods and Services Tax Rules, 2017: Rule 96A (Export under bond or LUT), Rule 96A(1)(b) (checked 8 Oct 2026)
- RBI Master Circular No. 9/2014-15 on Compounding of Contraventions under FEMA, 1999 (1 July 2014, updated 16 October 2014), Para 1.1, restating FEMA section 13(1) (checked 8 Oct 2026)
- Income Tax Department e-filing portal: Objective and scope of the New Act, Q2: Income-tax Act, 1961 repealed on 01.04.2026 (checked 8 Oct 2026)
Frequently asked questions
Can a wrong purpose code be changed after the FIRA or FIRC is issued?
Yes, a wrong purpose code can usually be changed after the FIRA or FIRC is issued. DGFT's eBRC FAQ says exporters must contact the bank to request a purpose code change, and banks can amend the IRM. Ask the bank for a revised certificate that shows the corrected code and keep its written confirmation.
Does a wrong purpose code make an export of services lose GST zero rating?
A wrong purpose code does not by itself remove zero rating. Section 2(6) of the IGST Act sets five conditions for export of services, and none of them names a purpose code. The code still matters as evidence, because refund claims need FIRCs or BRCs matched to each invoice under Rule 89.
Is there a time limit to correct a wrong purpose code with the bank?
No time limit for correcting a wrong purpose code appears in DGFT's eBRC FAQ, which only says to contact the bank. In practice, correct it well before the nine-month realisation period ends and before you file any GST refund claim. Check your AD bank's published SOP for its own timelines.
Can a bank hold or query an inward remittance because of a wrong purpose code?
A bank can hold or question a credit when the purpose code does not fit the payment, because Regulation 4(2) lets it credit an export receipt only after it is satisfied the transaction is genuine. Respond quickly with your invoice and contract. See why banks return inward remittances.
Will RBI penalise an exporter for a wrong purpose code?
The 2026 Export and Import Regulations set no separate penalty for a wrong purpose code. FEMA section 13 penalties apply to contraventions, such as failing to realise export proceeds in time. Correcting the code promptly helps prevent a reporting error from turning into an unrealised export on the bank's records.
Which purpose code should a freelancer use instead of P1301 for client payments?
A freelancer should use the purpose code that describes the service billed, in place of P1301, which covers family maintenance and savings from Indian non-residents. For example, P0802 is "Software consultancy/implementation (other than those covered in SOFTEX form)". The right code depends on the work. The purpose code for freelancers guide lists common codes.
Does a wrong purpose code block eBRC generation on the DGFT portal?
A wrong purpose code can block eBRC generation. DGFT's rules allow only P0802, P0803, P0807 and P0103 for Services > IT, bar P0101 and P0108, and require the SAC code to correspond to the purpose code. Ask your bank to amend the IRM, then generate the eBRC again.