A wrong purpose code on a foreign inward remittance rarely causes a problem on the day the money lands; it causes problems months later, when your bank tries to match the credit to your EDF, when an eBRC fails to appear, or when a GST officer asks why an "export" receipt is coded as something else. The fix is simple if you catch it early: check the code on every FIRA or payment advice and ask your bank, in writing, to correct any mistake while the transaction is fresh. Prevention is even simpler.
Key takeaways
- A purpose code is the RBI code that describes why foreign money came into India; your bank records it when crediting the remittance.
- Common mistakes: a non-export code on an export receipt, the wrong service category, and codes chosen by the payer's bank without context.
- Consequences include EDPMS matching delays, eBRC trouble, GST refund queries and classification questions.
- Correct errors quickly with a written request, invoice and contract attached.
- Prevent them by telling your bank and clients the right code up front.
What a purpose code does
Every foreign inward remittance credited to your account is tagged with a purpose code. For service exporters, that code is meant to show that the money is payment for a specific category of service exported. Examples from RBI's list include:
| Code | Category |
|---|---|
| P0802 | Software consultancy / implementation |
| P0807 | Off-site software exports |
| P1004 | Legal services |
| P1005 | Accounting, auditing, bookkeeping and tax consulting |
| P1006 | Business and management consultancy and public relations |
| P1007 | Advertising, trade fair, market research |
| P1008 | Research and development services |
| P1009 | Architectural, engineering and other technical services |
Always confirm the right code with your bank; the list is long, and categories have nuances. Our purpose code finder helps you shortlist.
The mistakes that cause the most trouble
1. A non-export code on an export receipt
The worst mistake is a business receipt coded as something that is not a service export at all, for example a personal transfer category. It can happen when funds arrive without a clear description, or when a payment service or the remitter's bank selects a default. Your FIRA then does not support the receipt as export proceeds.
2. The right family, the wrong category
Software firms sometimes see P0802 where P0807 fits better, or vice versa. Consultancies see P1007 (advertising) where P1006 (consultancy) was right. These look minor but create inconsistencies between your invoice, your EDF description and the bank's records. Our explainer on P0802 vs P0807 unpicks the most common software confusion.
3. One code for everything
If you provide several kinds of service, say software development and marketing, a single code across all remittances may misdescribe some of them. Ask your bank how to handle mixed receipts.
4. Advances coded without context
Advance payments for future services can arrive before an invoice exists. Without supporting information, the bank may code them generically. Send the proforma invoice or contract when you expect an advance.
What the consequences look like
| Where it shows up | What happens |
|---|---|
| EDPMS matching | Bank hesitates to match a credit coded as non-export against your EDF invoice |
| eBRC | Realisation may not be reflected cleanly, delaying the certificate |
| GST refund (IGST-paid exports) | Officers may question whether payment was received as export proceeds |
| LUT exports | Mismatches between export invoices and receipts can prompt queries |
| Income tax and audits | Auditors may ask why receipts are classified differently from invoices |
| Future remittances | A pattern of inconsistent codes can draw extra questions from your bank |
None of these is a disaster on its own, but they compound. A misclassified receipt from November can turn into a refund delay the following summer.
A worked example
Cedar Lane Engineering Pvt Ltd in Pune provides structural design for a client in Canada. In November 2026 it received CAD 18,000 against invoice CLE/EX/112. The FIRA showed purpose code P1006 (business and management consultancy). Cedar Lane's work is engineering design, for which P1009 (architectural, engineering and other technical services) is the natural fit.
Cedar Lane caught the error during its monthly FIRA check, eight days after the credit. Its accountant wrote to the bank using our purpose code correction letter, attaching the invoice, the engineering services agreement and a short description of the work, and asked for a revised advice. The bank corrected the code and reissued the advice. Cedar Lane noted the revised reference in its EDF register against the November EDF row.
Had the error surfaced only at year-end, the same correction would have required digging through old emails, and the bank may have needed more justification.
How to correct a wrong code
- Check every FIRA within a week of the credit. Make it part of your monthly routine.
- Write to your bank with the remittance date, amount, currency, remitter, the code shown and the code you believe is correct.
- Attach evidence: the invoice, contract or statement of work, and a brief description of the service.
- Ask for a corrected FIRA or advice, and record the new reference.
- Follow up if you hear nothing; keep copies of all correspondence.
Banks decide whether and how they can correct codes, especially for older transactions, so speed helps.
How to prevent mistakes in the first place
- Tell your bank your usual purpose code when you start exporting, and ask it to note it for your account.
- Put a clear service description on every invoice, matching your EDF description.
- Ask clients to reference the invoice number and service in their payment instructions.
- For payment platforms, check how they describe payouts, and confirm with your bank what code it applies.
- Use consistent SAC codes on invoices and EDFs; mismatched descriptions invite mismatched codes.
This article is general information, not legal or tax advice.
Frequently asked questions
What is a purpose code on a foreign remittance?
It is an RBI code that describes the reason foreign money is coming into India, such as P0802 for software consultancy or P1006 for business consultancy. Your bank records it when it credits the remittance, and it appears on your FIRA or payment advice.
Who decides the purpose code on an inward remittance?
The bank crediting the money records the code, often based on information from the remitter and from you. That is why giving your bank and clients the correct service description in advance matters.
Can a wrong purpose code be corrected?
Usually yes, if you ask your bank promptly with supporting documents such as the invoice and contract. Banks decide how they handle corrections, and older transactions may need more justification, so check each FIRA soon after the credit.
Does a wrong purpose code affect my EDF?
It can complicate matching the remittance to your EDF invoice in EDPMS, especially if the code suggests the money is not export proceeds. Correcting the code helps the bank close the entry and keeps your records consistent.
Can a wrong purpose code affect GST refunds?
It can raise questions about whether payment was received as export proceeds, which matters for refund claims on exports with IGST paid. Keeping codes correct and consistent with invoices avoids avoidable queries.
Bottom line
Purpose code errors are cheap to fix in week one and expensive in month twelve. Check every FIRA as it arrives and use our purpose code correction letter the moment something looks wrong.
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.