How Do You Correct a Wrong Purpose Code or FIRA After Payment?
- Author:
- Manoj Sharma
- Verified by:
- Editorial team
- Published:
- Last modified:
Short answer
You correct a wrong purpose code after payment by asking the bank that credited the money to amend it. DGFT says exporters must contact the bank for a purpose code change. The bank can amend the inward remittance message (IRM) sent to DGFT. The bank also reissues any FIRA or FIRC it issued.
| Applies to | Governed by | Deadline | Penalty | Last verified |
|---|---|---|---|---|
| Any exporter or freelancer in India whose foreign payment was credited with the wrong purpose code, or whose FIRA or FIRC shows wrong details | Regulation 18(2) of the FEMA (Export and Import of Goods and Services) Regulations, 2026 (FETERS reporting); A.P. (DIR Series) Circular No. 84 of 29 February 2012 (purpose codes); DGFT eBRC FAQs (IRM amendment) | No official time limit for a purpose code change is published; ask as soon as you spot the error, and well before EDF, eBRC or GST refund filings that rely on the record | Not applicable: no specific penalty for a purpose code error is published; the practical risk is a mismatch across bank, DGFT and GST records | 8 Oct 2026 |
What does correcting a purpose code or FIRA after payment involve?
Correcting a purpose code after payment means asking your AD bank to change how it classified and reported a foreign payment it has already credited. The bank reports foreign trade transactions in FETERS (Regulation 18(2)), using RBI purpose codes (Circular No. 84), and sends the remittance details to DGFT as an IRM.
- Purpose code: A five-character code that tells RBI why money came in, such as a software or consulting service. AD banks report all foreign exchange transactions with a purpose code under A.P. (DIR Series) Circular No. 84. See what an RBI purpose code is.
- IRM: The Inward Remittance Message is the bank's reference for an inward remittance, shared with DGFT and used to generate an eBRC (DGFT eBRC FAQs, Q2 and Q29).
- FIRA or FIRC: The advice or certificate your bank gives you for an inward remittance. The bank issues it, so only the bank can reissue it with corrected details. See FIRC vs FIRA vs e-BRC.
- eBRC: The electronic Bank Realisation Certificate issued by DGFT as confirmation that the exporter has received payment (DGFT eBRC FAQs, Q1). Exporters now generate it themselves from the IRM (Q48).
One error can sit in three places at once: the bank's FETERS report, the IRM at DGFT and the FIRA in your files. A complete fix covers all three.
Who needs to correct a purpose code or FIRA after payment?
Any exporter whose payment was credited under the wrong purpose code needs a correction, especially if the record is used for eBRC, EDPMS or GST refunds. Freelancers who received service fees under a non-export or generic code are the most common case.
| Situation | Correction needed | Why | Best for |
|---|---|---|---|
| Service fee credited under a non-export code | Yes | The record no longer shows an export of services, which can block eBRC generation and confuse GST evidence | Freelancers and agencies paid by foreign clients |
| Wrong code within the right group, such as two software codes | Usually yes | DGFT allows only P0802, P0803, P0807 and P0103 for eBRC under Services > IT, and codes must map to your SAC code | Software and IT service exporters |
| Advance received, coded as advance | Usually no | DGFT's eBRC rules treat P0103 as the advance payment code and let it be clubbed with other codes when generating an eBRC | Exporters paid before invoicing |
| FIRA shows wrong name, amount or date | Yes | GST refund claims for services rely on the bank's remittance certificate details | Exporters claiming IGST or ITC refunds |
| Payment received through a cross-border payment aggregator | Depends | The aggregator provides documents to your AD bank for EDPMS closure; ask who reported the code | Sellers using a regulated PA-CB |
How do you correct a wrong purpose code after payment?
You correct a wrong purpose code by making a written request to the AD bank that credited the payment, with your invoice and the correct code. DGFT's answer is that exporters must contact the bank to request changes in purpose code (DGFT eBRC FAQs, Q25). The bank then amends its records and the IRM.
- Find the transaction details on your bank advice or FIRA: date, amount, currency, bank reference number and the purpose code applied.
- Work out the correct code from RBI's purpose code list. The RBI purpose codes list for exporters and purpose code for freelancers pages can help you shortlist.
- If you will generate an eBRC, check the DGFT purpose code to SAC code mapping, since exporters must choose the SAC code that corresponds to the purpose code (DGFT eBRC FAQs, Q17).
- Write to your branch or trade services desk asking for the purpose code to be changed. Attach the invoice, the contract or engagement email, and a short note on the service you provided.
- Ask the bank to confirm three things in writing: the code is corrected in its records, the IRM sent to DGFT is amended, and a corrected FIRA or FIRC will be issued.
- Log in to the DGFT portal and check that the IRM now shows the new code before you generate the eBRC.
- If you already generated an eBRC from the wrong IRM, cancel it on the DGFT portal and generate a fresh one. You can cancel it yourself only within 120 days of generation; after that, your bank flags it and cancels it on your request (DGFT eBRC FAQs, Q80 and Q81).
- Keep the request, the bank's reply and the corrected FIRA with your export records for GST and audit.
How does a bank amend the IRM after a purpose code correction?
The bank amends the IRM by sending a new record with an amendment flag that overwrites the earlier entry (DGFT eBRC FAQs, Q63 and Q67). Each IRM message carries a status of F for fresh, A for amendment or C for cancelled. DGFT confirms that banks have the authority to amend the IRM for incorrect purpose codes (Q28).
- The bank reference number can stay the same across fresh, amended and cancelled messages.
- The technical transaction ID changes with each amended or cancelled message.
- You cannot generate an eBRC without an IRM, so wait for the amended IRM before generating one.
How do you get a corrected FIRA or FIRC from the bank?
You get a corrected FIRA or FIRC by asking the same AD bank to reissue it after the purpose code or other details are fixed. No RBI rule sets a format or deadline for reissue. Each bank follows its own process, so ask your bank for its procedure and any charges in writing.
- Ask for the reissued document to show the same bank reference number as the original, so it matches your books.
- Ask whether the old document is withdrawn or marked as superseded.
- If you hold an eBRC issued by the bank under the older system, only the bank can cancel and reissue it (DGFT eBRC FAQs, Q49 and Q50).
How do you correct a purpose code on a payment received through a payment aggregator?
You correct a purpose code on an aggregator payment by first asking the aggregator and then your AD bank. A cross-border payment aggregator (PA-CB) must give the documents your AD bank needs to close the EDPMS entry (Master Direction on Payment Aggregators, para 11(h)). Every PA must name an officer and an escalation matrix for merchant issues (para 8(d)).
- Ask the aggregator which code was applied and which bank reported the transaction.
- Ask for a corrected statement or advice that your AD bank can rely on.
- Use the escalation matrix shown on the aggregator's website if the first request is not answered. See RBI PA-CB guidelines.
Which documents and deadlines matter when correcting a purpose code after payment?
The documents that matter are the invoice, the contract and the bank's original advice. No official deadline exists for the correction itself. Other deadlines run on the same payment: the EDF for services is due within 30 days from the end of the invoice month (Regulation 3(2)), and realisation within nine months of the invoice date (Regulation 5).
| Item | What to check | Deadline or rule | Best for |
|---|---|---|---|
| Export invoice | Service description matches the code you ask for | Keep with the request; no RBI format | Every correction request |
| Contract or engagement email | Shows the client is abroad and what you supplied | Supports the bank's genuineness check | Banks that ask for proof of the service |
| Original FIRA or bank advice | Wrong code or detail, bank reference number | No published time limit for a purpose code change | Identifying the transaction |
| DGFT IRM record | Code shown after the bank's amendment | Bank sends an IRM with status A | Exporters generating eBRC |
| EDF for services | Invoice value and the entry in EDPMS | Within 30 days of the end of the invoice month; AD bank may extend | Service exporters filing EDF |
| EDPMS entry | Remittance linked to the right invoice | Bank enters service EDF details within five working days of receipt | Exporters with open entries |
| GST refund file | Invoice numbers and FIRC or BRC details | Rule 89(2)(c) statement for export of services | Exporters claiming refunds |
What happens if a wrong purpose code or FIRA is not corrected after payment?
If a wrong purpose code is left uncorrected, your bank, DGFT and GST records describe the payment differently. That can stop an eBRC, slow EDPMS closure, and weaken evidence for a GST refund. No RBI penalty specific to a wrong purpose code is published.
- eBRC blocked: DGFT accepts only certain codes for eBRC. It does not allow eBRC for P0101 and P0108, and allows only four codes under Services > IT (eBRC generation guidelines, rules 3 and 10).
- GST evidence: A refund claim for export of services needs a statement of invoices with the relevant BRC or FIRC (CGST Rule 89(2)(c)). A FIRA with wrong details weakens that file.
- EDPMS gaps: The AD bank must enter inward remittances for exports in EDPMS and close entries once export value is realised (Regulation 18(1)(e) and (g)). A payment coded as non-export may not be matched to your invoice. See EDPMS closure.
- Data quality: RBI uses purpose codes reported in FETERS to classify foreign exchange transactions (Circular No. 84, paragraph 3). A wrong code misstates what you earned.
Ask the bank in writing as soon as you see the error, get the IRM amended, regenerate any eBRC, and file the corrected FIRA. Read what happens if you use the wrong purpose code for more detail.
Which RBI rule says how a purpose code is corrected after payment?
No RBI rule sets out a stand-alone correction procedure for purpose codes. The bank's reporting duty comes from Regulation 18(2) of the 2026 regulations and Circular No. 84. DGFT's eBRC FAQs describe the IRM amendment. Regulation 19 requires each AD bank to publish a policy with an escalation and appeal route.
| Circular or regulation | Clause | Date | Plain meaning | Best for |
|---|---|---|---|---|
| FEMA (Export and Import of Goods and Services) Regulations, 2026, FEMA 23(R)/2026-RB | Regulation 18(2) | In force 1 October 2026 | AD banks report all foreign trade transactions in FETERS under RBI guidelines | Understanding who reports the code |
| Same regulations | Regulation 19(1), (2) and (4) | In force 1 October 2026 | Each AD bank needs a documented policy and SOP, an escalation and appeal process, and must disclose the policy on its website | Exporters whose request is ignored or refused |
| Same regulations | Regulation 19(3) | In force 1 October 2026 | Bank charges must be reasonable and proportional to the service | Checking a fee for reissue |
| A.P. (DIR Series) Circular No. 84 | Paragraph 3 | 29 February 2012 | AD banks report all foreign exchange transactions with the revised purpose codes | Finding the official code list |
| A.P. (DIR Series) Circular No. 20 | Paragraphs 4 and 7 | 16 January 2026; effective 1 October 2026 | Supersedes the old Master Directions on export and import from 1 October 2026 | Readers following older guidance |
| DGFT FAQs on Self-Generation of eBRC | Q25, Q28, Q63, Q67 | March 2024 | Contact your bank for a code change; banks amend the IRM with status A | Exporters who use eBRC |
| Master Direction on Payment Aggregators | Paragraphs 8(d) and 11(h) | 15 September 2025 | PA escalation matrix; PA-CB gives documents to the exporter's AD bank | Sellers paid through an aggregator |
What are common mistakes when correcting a purpose code after payment?
- Verbal requests: Asking at the branch counter without a written request, so there is no reference number to escalate later.
- Half fixes: Getting a new FIRA while the IRM at DGFT still shows the old code, so the eBRC still fails.
- Stale eBRC: Leaving an eBRC generated from the wrong IRM in place instead of cancelling it and generating a new one.
- Code guessing: Picking a code from memory without checking the RBI list and the DGFT purpose code to SAC mapping.
- Wrong bank: Writing to a bank that only forwarded the funds, when the bank holding the account that received the remittance reports the IRM (DGFT eBRC FAQs, Q45 and Q56).
- Skipping escalation: Giving up after one refusal, when every AD bank must offer an escalation and appeal route (Regulation 19(2)) and the RBI Ombudsman route exists.
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, as amended by FEMA 23(R)/(1)/2026-RB dated 22 September 2026, Regulations 3(2), 5, 18(1)(b), 18(1)(e), 18(1)(g), 18(2), 19(1) to 19(4) (19(4) inserted by the 22 September 2026 amendment) (checked 8 Oct 2026)
- RBI A.P. (DIR Series) Circular No. 20, RBI/2025-26/194: Export and Import of Goods and Services (16 January 2026), Paragraphs 4 and 7 (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: purpose codes for all foreign exchange transactions reported in FETERS (checked 8 Oct 2026)
- DGFT, FAQs (Self-Generation of eBRC), Version 1.0, March 2024, Q1, Q2, Q17, Q25, Q28, Q29, Q45, Q48, Q49, Q50, Q56, Q59, Q63, Q67, Q80, Q81 (checked 8 Oct 2026)
- DGFT, Self-Certified eBRC Generation Guidelines, Version 1.0 (10 November 2023), Rules 3, 4, 5, 9 and 10 (checked 8 Oct 2026)
- RBI Master Direction on Regulation of Payment Aggregator (PA), RBI/DPSS/2025-26/141 dated 15 September 2025, Paragraphs 8(d) and 11(h) (checked 8 Oct 2026)
- RBI, Frequently Asked Questions, Reserve Bank - Integrated Ombudsman Scheme, 2026, Q1 (in force 1 July 2026, replaces RB-IOS 2021), Q16, Q17 (checked 8 Oct 2026)
- Central Goods and Services Tax Rules, 2017: Rule 89 (Application for refund), Rule 89(2)(c) (checked 8 Oct 2026)
- Integrated Goods and Services Tax Act, 2017: Section 2 (Definitions), Section 2(6), export of services (checked 8 Oct 2026)
Frequently asked questions
Is there a time limit to correct an RBI purpose code after payment?
DGFT was asked about a procedure and time limit for a purpose code change, and its answer only says exporters must contact the bank (Q25). No published RBI or DGFT time limit applies. Ask early, since EDF, eBRC and GST refund filings that rely on the same payment have their own deadlines.
Can an exporter change the purpose code on the DGFT eBRC portal directly?
No published DGFT process lets an exporter change a purpose code on the portal. The bank that reported the IRM amends it by sending an amended record that overwrites the earlier entry (DGFT eBRC FAQs, Q67). The exporter can then cancel any eBRC made from the old IRM and generate a new one.
What should a request letter to the AD bank for a purpose code change include?
A purpose code change request should include your account number, the remittance date, amount, currency and bank reference number, the code applied, and the code you want. Attach the invoice and contract. Ask the bank to amend the IRM sent to DGFT and to reissue the FIRA or FIRC.
Does a wrong purpose code make a payment ineligible as export of services for GST?
The GST definition of export of services in IGST Act section 2(6) lists five conditions, including payment in convertible foreign exchange or permitted rupees. A purpose code is not one of those conditions. A wrong code can still create inconsistent records, so correct it before relying on the FIRA for a refund.
What can an exporter do if the AD bank refuses or ignores a purpose code correction?
First escalate inside the bank, using the escalation and appeal process each AD bank must have under Regulation 19(2). If the bank does not reply within 30 days or you are unhappy with it, you can complain to the RBI Ombudsman within 90 days of that period ending or the bank's last reply, whichever is later (RB-IOS, 2026 FAQs, Q17).
Does correcting a purpose code change the FIRA number or bank reference number?
DGFT says the bank reference number can stay the same across fresh, amended and cancelled IRM messages, while the technical transaction ID changes (DGFT eBRC FAQs, Q59). Whether your bank gives the reissued FIRA a new number depends on its own process, so ask the bank to confirm.
Can the P0103 advance payment purpose code stay as it is after the invoice is raised?
DGFT's eBRC rules treat P0103 as the advance payment code. DGFT allows P0103 to be used alone or clubbed with other codes to generate an eBRC, but the invoice date must be on or after the remittance date (eBRC generation guidelines, rules 4, 5 and 9). A change is usually not needed.