Wrong Purpose Code On An Inward Remittance: What Happens And How To Fix It
Quick answer
A wrong purpose code either holds your payment for clarification or stamps the wrong tag on your e-FIRA. You fix it by asking your bank’s forex desk to amend the code and reissue the e-FIRA, with your invoice and contract as proof.
Most freelancers never actually chose the purpose code sitting on their foreign payments. The bank tagged it automatically, or the platform hardcoded one, and it went unread until a GST refund or a CA’s question made it matter.
That’s the quiet trap: the wrong code is rarely a typo you made, it’s usually a default you inherited. Upwork locks its withdrawals to a fixed code whether it fits your work or not, and a bank left to decide for itself will often drop a foreign inflow into a generic or personal bucket. So fixing it comes down to two jobs: noticing it, then getting the bank to change it.
Key Takeaways
- A wrong purpose code shows up two ways: a payment held for clarification before it lands, or the wrong tag already baked into an e-FIRA you already hold.
- You fix both the same way, by asking your bank’s forex desk to amend the code and reissue the e-FIRA, with your invoice and contract as the proof.
- Left alone, a personal or mismatched code can put your GST export refund and a clean ITR at risk, which is why it’s worth chasing.
- The sooner you raise it the easier it clears, so the real move is to check the code on your last payment today.
What actually happens when the purpose code is wrong?
A purpose code is the label your bank reports to the RBI for every bit of foreign money you receive, part of the wider system that governs how money reaches you from abroad and how it’s tracked under FEMA. Inward codes are a P followed by four digits. When the code matches your work, the payment clears quietly. When it doesn’t, one of two things happens, and they are not the same problem.
The first is a payment held before it reaches you. The bank spots a mismatch, or the sender gave no clear purpose, and it pauses the credit to ask what the money is for. You get an email or a call from the branch. This one is almost good news, because you’re being asked before anything is finalised. Reply with a plain service description and your invoice, and it usually releases within a day or two.
The second is quieter and far more common: the money already landed, but the code stamped on it is wrong. Maybe the bank defaulted it to a personal transfer code, the sort meant for an NRI sending money home to relatives (P1301, family maintenance and savings), which has nothing to do with a client paying you for work. Maybe a platform hardcoded something that doesn’t fit. Nothing looks broken. The rupees are in your account. The problem only surfaces later, when your e-FIRA shows a personal code against what was plainly business income, and a CA or a GST officer notices it.
So why can’t the bank just edit a number and move on? Because it has already reported that code to the RBI through the foreign-exchange transaction reporting system (FETERS). Changing it means filing a correction, which is why the bank asks for documents instead of taking your word. The paperwork isn’t there to slow you down, it’s what lets the bank justify the amendment on record.
How do you actually get a wrong purpose code fixed?
The correction runs through your own bank. Not the RBI, not your client, not the platform. Work through it in order:
- Confirm the mismatch. Pull the e-FIRA or bank credit advice for that payment and read the actual code against the work you did. Working out which code you should have had is its own question, so settle that first, before you email, so you’re requesting a specific correct code and not just flagging a vague problem.
- Assemble the proof. Your invoice, the contract or scope of work, and anything that ties the payment to a real service: client emails, a project brief, platform screenshots. The aim is to leave zero doubt about what the money was for.
- Write to the forex or remittance desk. Email the branch that holds your account and ask for two specific things: amend the purpose code to the correct one, and reissue the e-FIRA showing the corrected code.
- Follow up and keep the trail. Corrections often clear in a few working days, though it varies bank to bank. Reference your first email when you chase, and save every reply.
Your correction email should leave nothing to interpretation. Include your name and account number, the UTR taken from your Indian bank statement rather than the platform’s internal reference, the amount and currency, the credit date, the wrong code currently showing, the correct code you’re requesting, and a one-line reason for the mismatch. Attach the invoice and the credit advice. Add a plain line confirming everything else about the transaction stays the same. Banks amend faster when the request reads like it came from someone who knows exactly what they’re asking for.
One honest limit here. The correction request is yours to make, and it’s straightforward. But whether a code change means revisiting a return you’ve already filed is a question for your CA, not for me.
What does leaving the wrong code cost you later?
The wrong code is invisible until it isn’t, and where it bites is money. Export of services is zero-rated under GST, which lets you claim a refund on the tax you paid on your inputs, but that claim leans on proof the payment came in as an export. An e-FIRA carrying a personal or family-transfer code is weak proof of exactly that. A refund officer who sees business income tagged as a personal remittance has every reason to hold the claim up.
The same mismatch resurfaces at income tax. A personal-transfer code sitting against what your ITR reports as professional income is the kind of inconsistency that invites a closer look you don’t want. None of this is a guaranteed disaster. It’s a stack of small, avoidable frictions that all arrive at the worst possible moment, mid-filing or mid-refund, when you least want to be reconstructing a payment from months back. The e-FIRA is the document your CA leans on to prove your foreign income, and it’s only as clean as the code printed on it.
Is there a deadline to fix a purpose code?
Sort of, and it’s the reason not to sit on this. Banks report these codes to the RBI in cycles, so a correction is simplest while the payment is still recent and gets more awkward the longer it’s been sitting reported. A correction on last month’s payment is routine. One on a transaction from a couple of years back can take longer, or run into a branch that no longer wants to touch it. The exact window varies bank to bank, so if a payment is already a few months old, ask your branch how far back they’ll amend rather than assuming it’s fine.
So the age of the payment matters almost as much as the error itself. If you’ve spotted a wrong code, don’t spend a week researching the perfect fix. Raise the request while the transaction is still recent enough to be easy.
Frequently Asked Questions
Can I change a purpose code after the money has already been credited?
Yes. You request a purpose code amendment from your bank’s forex desk, attach your invoice and contract, and ask for a reissued e-FIRA showing the corrected code. The money stays in your account; only the reported code changes.
Who fixes the code, my bank or my client’s bank?
Your own bank, the one where the money landed. It made the report to the RBI, so it makes the correction. Your client and their bank play no part in an Indian purpose-code amendment.
Will a wrong purpose code affect my GST refund?
It can. A personal or mismatched code on your e-FIRA weakens the proof that the payment was an export of services, which is what a zero-rated GST refund claim relies on. Correcting the code before you file keeps that proof clean.
What documents does the bank need to amend a code?
Usually your invoice, the contract or scope of work, the bank credit advice showing the UTR, and a short declaration of the correct purpose. Client emails or platform screenshots help where the sender’s name doesn’t obviously match yours.
Do this today: Open your last foreign payment’s e-FIRA or bank credit advice and find the purpose code, a P followed by four digits, printed near the transaction description. If it’s a personal or family code, or anything that doesn’t match the work you actually delivered, email your bank’s forex desk now with the invoice attached and ask for an amendment, before it’s sitting on a filing your CA has to explain.
Reviewed and updated: August 2026
Sources and official verification
- Reserve Bank of India. “Annexure II: New Purpose Codes for Reporting Forex Transactions (Receipt Purposes).”
https://www.rbi.org.in/upload/notification/pdfs/52220.pdf. - Reserve Bank of India. “Foreign Exchange Transactions Electronic Reporting System (FETERS).”
https://www.rbi.org.in/upload/ERSystem/FETERSV62New.doc. - Central Board of Indirect Taxes and Customs. “IGST Act, 2017: Section 16, zero-rated supply (export of services).”
cbic-gst.gov.in.
Ritesh Yengkhom
I'm Ritesh — I've freelanced for over five years, largely through Upwork, and I'm the writer behind WealthWali. I have a B.Com from Delhi University, but most of what's on this site came from somewhere else: chasing late invoices, guessing at tax, and learning the hard way what nobody tells you about freelancing in India. Everything here is what I've actually used, paid for, or gotten wrong myself. Where something needs a CA or a lawyer, I'll say so plainly instead of pretending I know more than I do.
View Author Profile