Wrong Purpose Code Used for Inward Remittance: How to Correct It
TL;DR - Summary
- What is a purpose code for an inward remittance? - A purpose code is a short alphanumeric code that identifies the nature of a foreign exchange transaction, and Authorised Dealer (AD) banks report it to RBI as part of Balance of Payments (BoP) reporting, so every inward remittance must be tagged with the correct code when it is credited.
- What happens if you use the wrong purpose code on an inward remittance? - When you use the wrong purpose code, the payment is still credited to your Indian bank account, but the transaction is reported to RBI under the wrong category and stays in RBI's BoP data unless a formal amendment is made through your AD bank.
- How do you correct a wrong purpose code with your AD bank? - You correct a wrong purpose code in five steps: identify the incorrect code, determine the correct code, contact your AD bank, submit supporting documents, and get written confirmation that the code has been updated.
- How does a wrong purpose code affect your FIRC, eBRC, and compliance records? - A wrong purpose code can affect the accuracy of your FIRC/FIRA, complicate eBRC generation, and cause reconciliation issues for GST refunds or income-tax filings, and correcting the code at the bank does not automatically update an eBRC that has already been issued.
What Is a Purpose Code?
A purpose code is a short alphanumeric code that identifies the nature of a foreign exchange transaction, such as whether a payment received from abroad is for software services, goods export, consultancy, or another category. In India, Authorised Dealer (AD) banks collect purpose codes and report them to the RBI as part of Balance of Payments (BoP) reporting, so every inward remittance must be tagged with the correct code at the time it is credited.
Take a Bengaluru-based freelancer who receives $3,000 from a US client for IT consulting. That payment must carry the correct service-export purpose code. If it carries the wrong one, an incorrect transaction type shows up in RBI's records as well as in the bank's internal ledger. You can read more about the RBI purpose code for inward remittance in our separate guide.
⚠️ COMMON MISCONCEPTION
Many freelancers think purpose codes only affect the bank's internal records. In reality, AD banks submit these to RBI's BoP reporting system, so an error persists in regulatory filings unless it is formally corrected.
What Happens If You Use the Wrong Purpose Code?
Using the wrong purpose code does not block the payment, and the money is still credited to your Indian bank account, but the transaction is reported to RBI under the wrong category. Because AD banks submit purpose-code data to RBI's BoP reporting system, the error enters a regulatory filing. It can create mismatches in export reporting, affect the accuracy of your FIRC/FIRA, complicate Electronic Bank Realisation Certificate (eBRC) generation, and cause reconciliation issues when your income is scrutinised for GST refunds or income-tax filings.
Leaving a wrong code uncorrected leaves the incorrect category in RBI's BoP data permanently, unless a formal amendment is made through the AD bank.
Here is how that can play out.A Bengaluru freelancer codes an IT support payment as P0807 (Off-site software exports) instead of P0803 (Data base, data processing charges). The reported category no longer matches the actual service provided, which may cause issues with GST refund eligibility.
💡 QUICK INSIGHT
The payment credit and the regulatory reporting are two separate events. Money reaching your account does not mean the purpose code was recorded correctly.
How to Correct a Wrong Purpose Code
To correct a wrong purpose code, you work through five steps in order: identify the incorrect code on your remittance advice, determine the correct code, contact your AD bank, submit supporting documents, and get written confirmation that the code has been updated.
Step 1: Identify the Incorrect Code
Check the remittance advice or credit advice from your bank. The purpose code that was reported should be visible on this document. Confirm the code that was actually used and note the transaction or UTR reference number.
Step 2: Determine the Correct Purpose Code
Work out the actual nature of the payment: goods export, software services, IT-enabled services, consultancy, royalty, and so on. Then cross-check it against the RBI master list of purpose codes to find the exact applicable code. Do not pick a code that merely sounds similar.
These are commonly confused purpose-code pairs for Indian freelancers and exporters:
| Purpose code | Transaction type |
|---|---|
| P0807 | Off-site software exports |
| P0803 | IT-enabled services (ITeS) |
| P1004 | Management consulting |
| P0899 | Other business services |
Step 3: Contact Your AD Bank
Write to the branch or relationship manager handling your foreign-currency account and ask them to amend the purpose code for the specific inward remittance. Give them the transaction reference number, the incorrect code that was reported, and the correct code you are requesting.
Step 4: Submit Supporting Documents
Attach the documents the bank asks for to show the nature of the payment. The full list is in the documents section below.
Banks have no standardised correction form. Some require a letter on company letterhead, while others use an internal format, so ask your relationship manager what the bank requires before you draft anything.
Step 5: Get Written Confirmation of the Correction
Ask the bank to confirm in writing that the purpose code has been updated in its records. Check whether the correction also requires an amended FIRC/FIRA or an updated eBRC, and keep all confirmation documents on file.
⚠️ COMMON MISCONCEPTION
Sending an email to your bank's general inbox is not enough. A purpose-code amendment is a formal request that must be routed through your AD branch with supporting documents attached.
Can a Bank Change the Purpose Code After the Payment Is Credited?
Yes. Crediting the payment to your account and reporting the purpose code to RBI are two separate processes, so the reported code can be amended even after the money has been received. Whether your bank can make the change depends on its internal procedures and how far the transaction has progressed in downstream reporting.
Not all banks handle this the same way. The exact process, and whether the amendment is possible at all, depends on the bank, the transaction date, and the stage of RBI reporting. There is no universal rule.
The bank will typically require supporting documents that prove the actual nature of the transaction before it makes any amendment. If a FIRA or FIRC has already been issued, the bank will need to assess whether the correction also requires re-issuance of that document, so ask your relationship manager about it explicitly.
✅ PRO TIP
Check your purpose code at the point of receiving payment, not after. Correcting it post-credit requires a formal bank request and supporting documents.
Documents You May Need for Purpose-Code Correction
AD banks typically ask for some or all of these documents when processing a purpose-code correction: the invoice, the contract or agreement, the remittance or credit advice, the UTR or transaction reference number, the FIRA or FIRC, shipping or export documents where the payment relates to goods exports, and a written declaration or correction request. Not every bank asks for all of them.
| Document | Why it may be needed |
|---|---|
| Invoice | Establishes what the payment was actually for |
| Contract / agreement | Supports the nature of the underlying transaction |
| Remittance / credit advice | Identifies the transaction and the code originally reported |
| UTR / transaction reference number | Helps the bank locate the specific payment in its system |
| FIRA / FIRC | Helps reconcile the reported inward remittance with bank records |
| Shipping / export documents | Relevant where the payment relates to goods exports |
| Written declaration / correction request | Explains the error and the amendment being requested |
The exact list depends on the bank's internal process and the nature of the transaction, so confirm with your relationship manager before you start gathering documents.
⚠️ COMMON MISCONCEPTION
A FIRA or FIRC alone is not proof of the correct purpose code, because it reflects whatever code was originally reported. You still need the invoice or contract to substantiate the amendment.
What If the Wrong Purpose Code Has Already Been Used for eBRC?
If an eBRC has already been generated with the wrong purpose code, the underlying inward remittance record that feeds the eBRC may need to be corrected first. The eBRC is generated from the realisation data the bank submits to DGFT, so a wrong code in that data carries forward into the eBRC. Ask your AD bank explicitly whether the eBRC needs to be amended or reissued after the purpose-code correction.
- Check before you approach the bank: see whether an eBRC has already been generated for that transaction. If it has, say so in your correction request so the bank can advise on both steps together.
- Do not wait for the bank to flag it: not all banks proactively flag the eBRC, and the responsibility to check falls on you as the exporter.
- Expect bank-specific answers: the bank's ability to amend an eBRC depends on its internal system and the stage at which the eBRC was generated. There is no standardised national process for eBRC correction, so the bank's guidance is the authoritative source.
Skydo's P1401 purpose code guide covers that code in detail.
⚠️ WATCH OUT
Correcting the purpose code at the bank level does not automatically update an already-issued eBRC. You must separately confirm with your AD bank whether the eBRC also needs to be reissued.
Common Purpose-Code Correction Scenarios
Three scenarios come up for freelancers and exporters: a service export reported under the wrong service category, an export payment reported under an incorrect broad category, and a payment received through a payment platform that is classified incorrectly. In each case the fix runs through your AD bank, with documents that show what the payment was actually for.
- Wrong service category: a freelancer providing IT-enabled services receives a payment that is logged under P0802 (Software product exports) instead of P0806 (IT-enabled services). The distinction matters for GST refund eligibility and RBI sector reporting, so the freelancer must approach the AD bank with the invoice and service agreement to get the code amended.
- Incorrect broad category: an Indian exporter of professional services receives a payment that is accidentally tagged under a goods-export code. Goods and services codes sit in entirely different categories in the RBI master list, so the mismatch is more likely to surface during export reconciliation or eBRC generation, which makes correction more urgent.
- Payment platform classification: a freelancer receives payment through a cross-border payment platform, and the platform or the AD bank defaults to a generic or incorrect code rather than the one that matches the actual service. The freelancer must check the remittance advice immediately after credit and raise a correction request if the code does not match the invoice.
The most common mix-up for Indian freelancers is between P0802 and P0806. They sound similar but sit in different regulatory categories, with different implications for GST and export reporting. Our P0807 purpose code guide covers another code in detail.
You can also avoid the correction hassle upstream. Skydo shows you the purpose code at the point of receiving payment, so you can confirm it is correct before it enters your AD bank's records. Skydo also issues a free FIRC/BIRC for every transaction, so there is no ambiguity in the remittance documentation from the start.
Pricing is a flat $19 for payments under $2,000, a flat $29 for payments from $2,000 to $10,000, and 0.3% above $10,000. There are no monthly fees.
Picking a purpose code that's merely close to your actual transaction isn't a safe shortcut. Each code maps to a specific regulatory category, so an approximate match means the transaction gets classified wrong.
How Long Does Purpose-Code Correction Take?
There is no fixed or guaranteed turnaround for a purpose-code correction. Processing time varies by bank, transaction, and how complete your documentation is.
The timeline depends on three variables:
- Your documents: how quickly you submit complete supporting documents.
- The bank's process: the bank's internal amendment process.
- Downstream records: whether records such as the FIRA/FIRC or eBRC also need correction alongside the purpose code.
If a FIRA or eBRC amendment is needed in addition to the purpose-code change, the overall process takes longer because it involves additional verification steps within the bank.
In practice, raise the correction request as early as possible and submit all required documents in one go. Incomplete submissions are the most common cause of delays, and every additional document exchange adds days. Follow up with your relationship manager proactively, especially if an eBRC or FIRC amendment is also involved.
Will a wrong purpose code get my account flagged by RBI?
A wrong purpose code creates a misclassified entry in RBI's BoP reporting system, and whether it triggers scrutiny depends on the nature and size of the mismatch and how it is handled. Proactively correcting the code through your AD bank is the recommended approach, because it puts a formal amendment on record rather than leaving an unexplained discrepancy.
Can I correct the purpose code after the FIRC has already been issued?
Does a wrong purpose code affect my GST refund?
How long does the bank take to process a purpose-code correction?
Do I need a special form to request a purpose-code correction?
What documents does the bank need for a purpose-code correction?
What happens if the wrong purpose code has already been used for eBRC?
Can a payment platform user correct a purpose code, or does it have to go through the AD bank?
