When a foreign payment lands in your account under the wrong purpose code, the fix is a short letter asking your bank to reclassify that specific remittance, backed by the invoice and contract that show what the payment was really for. Send it as soon as you spot the error, ideally within days of the credit, because a wrong code flows into your FIRA, your bank's export records and potentially your GST paperwork. The letter itself takes ten minutes; the documents you attach are what persuade the bank.
Key takeaways
- Purpose codes are RBI codes that classify why foreign money came in, for example P0802 for software consultancy or P1007 for advertising and market research.
- A wrong code can complicate matching your payment to the EDF, the issue of eBRCs and your GST export records.
- The correction letter should identify the remittance precisely, state the wrong and correct codes and explain why.
- Attach the invoice, a contract or statement of work extract and the original FIRA or credit advice.
- Banks decide what they accept and how fast. Ask, follow up and keep the corrected FIRA.
Why the code matters
Every inward remittance carries a purpose code that tells the bank, and RBI's reporting systems, what kind of transaction it was. For a service exporter, the code is meant to reflect the service invoiced.
Problems arise when the code says one thing and your paperwork says another. A payment coded as a family remittance or a loan, rather than a service export, may not be treated as realisation of your export invoice. Even a mismatch between two service codes, say consulting instead of software, can raise questions when the bank matches the payment to your EDF or when a GST officer checks your refund claim.
| Example of a mismatch | Why it matters | Likely correct code (confirm with bank) |
|---|---|---|
| Software development paid under a consulting code | Inconsistent with invoice and SAC 998314 | P0802 or P0807 |
| Market research fee coded as management consultancy | Wrong service category on FIRA | P1007 |
| Engineering drawings coded as "other business services" | Vague; may not support export records | P1009 |
| Bookkeeping for a foreign client coded as legal services | Wrong category | P1005 |
| Export fee coded as a personal or non-trade remittance | May not count as export realisation | The relevant service code |
Use our purpose code finder to shortlist the right code before you write.
When to send the letter
- Immediately after the credit, when you receive the FIRA or credit advice and see the wrong code.
- Before closing EDPMS entries, if you are about to send matching instructions for an invoice above ₹10 lakh.
- Before a GST refund claim, if the FIRA will be part of your evidence.
- At a periodic review, if you discover older errors. Late corrections are still worth asking for, but banks may need more explanation.
Better still, prevent the problem: tell your client what to put in the payment reference ("Payment for software development services, invoice NL/26/045") and, if your bank lets you, confirm the code when it contacts you about the incoming payment.
Sample letter format
[On letterhead]
To The Branch Manager / Trade Services Desk [Bank name], [Branch]
Date: [DD Month YYYY]
Subject: Request for correction of purpose code on inward remittance dated [date], reference [remittance reference]
Dear Sir or Madam,
We received an inward remittance in our current account no. [XXXXXXXX4321] as follows:
- Date of credit: [date]
- Remitter: [client name], [country]
- Amount: [currency and amount]
- Remittance / FIRA reference: [reference]
- Purpose code applied: [wrong code and description]
This remittance is payment against our export invoice no. [number] dated [date] for [description of services], which is an export of services. The correct purpose code is [correct code and description].
We enclose (1) a copy of the invoice, (2) an extract of the contract / statement of work, and (3) the FIRA / credit advice showing the code applied. The invoice has been declared on our EDF for [month].
Kindly correct the purpose code and issue a revised FIRA / advice. Please let us know if you need anything further.
For [Company name] [Authorised signatory name and designation]
Our free purpose code correction letter tool fills this in from your details.
A worked example
Copperleaf Insights Pvt Ltd, a Gurugram research firm, invoiced a Canadian client CAD 14,200 on 6 October 2026 for a consumer survey. The payment arrived on 4 November. The FIRA showed P1006, business and management consultancy.
Copperleaf's finance lead compared it with the invoice (SAC 998371, market research) and the statement of work, which described survey design and fieldwork. She wrote to the bank on 6 November using the format above, asked for P1007 and attached the invoice, the SOW extract and the FIRA. The bank asked one follow-up question about whether any consulting was included, she replied with the SOW scope, and the revised FIRA arrived. She then used it in the matching instructions to close the EDPMS entry for that invoice.
What to attach, and why
- The invoice: shows the service and links the payment to a specific EDF row.
- Contract or statement of work extract: proves the nature of the service independently of your invoice wording.
- Original FIRA or credit advice: shows the code the bank applied.
- Client's payment confirmation (optional): helpful if the client's bank used an odd description.
- EDF reference (optional): shows the bank the invoice is already declared.
Avoid over-explaining. One paragraph and three attachments is usually enough. This is general information, not legal or tax advice; the bank's own rules decide whether and how it can correct a code. Our article on purpose code mistakes that cause trouble later covers prevention.
Frequently asked questions
Can a bank change the purpose code after the money is credited?
Banks can often correct a purpose code on request when the documents support it, but each bank has its own process and limits. Ask promptly and provide the invoice and contract.
What happens if I leave a wrong purpose code uncorrected?
It may complicate matching the payment to your EDF, closing the EDPMS entry, getting an eBRC and supporting GST export records. Small errors are easier to fix early than at year end.
Which documents prove the correct purpose code?
The export invoice, a contract or statement of work describing the service, and the original FIRA or credit advice. Together they show what the payment was really for.
Should I mention the EDF in the correction letter?
It helps. Stating that the invoice has been declared on the EDF for a particular month shows the bank the payment relates to an export already on record.
Bottom line
A wrong purpose code is a small error with outsized consequences, but a clear letter with three attachments usually fixes it. Act within days and keep the corrected FIRA with the invoice. Draft yours now with our free purpose code correction letter generator.
This guide is general information for Indian businesses, not legal or tax advice. Rules and bank processes change — confirm specifics with your AD bank or chartered accountant.