SBI inward remittance stuck? Purpose code, invoice, and bank checklist for Indian freelancers

Indian freelancers and founders often discover export compliance only when a foreign payment gets stuck. The money is visible somewhere in the rail, but the bank wants context before crediting it or before issuing usable foreign-remittance proof. The words vary by branch: inward remittance, purpose code, invoice, FIRA, FIRC, payment advice, e-BRC, EDPMS. The practical problem is the same: the bank needs to understand the receipt.

This guide is not legal advice and it is not SBI-specific escalation magic. It is a practical checklist for Indian service exporters: freelancers, agencies, SaaS founders, consultants, and contractors receiving foreign client payments into India. If your receipt is personal remittance, NRE/NRO transfer, grant, salary, or investment money, your route may be different.

01 · First classify the receipt

Before chasing the bank, classify the money. A stuck transfer is easier to explain when you can say which bucket it belongs to:

• Service export receipt. Payment from a foreign client for software, consulting, design, development, marketing, support, or other services.
• Platform payout. Wise, Stripe, PayPal, Deel,Upwork, or another rail pooled or routed the payment before it reached your Indian bank.
• Personal remittance or salary. Money that is not against your Indian export invoice may need a different branch process and tax/compliance treatment.
• Grant, capital, or investment receipt. Do not force this into an export-service purpose code. Ask your CA or bank before choosing the route.

The wrong first classification creates the wrong paperwork. That is why a founder receiving USD for a SaaS invoice should not use the same explanation as an NRI moving money to an NRE account or a resident receiving a one-off family remittance.

02 · Why purpose code and invoice matter

SBI's own foreign inward remittance instructions includepurpose / invoice number in the standard telegraphic or wire transfer details. That is a useful clue: the bank is not only moving money. It is also recording why the money came in.

For export-service receipts, that "why" connects to purpose-code reporting, invoice matching, GST treatment, foreign-remittance proof, and sometimes downstream e-BRC or EDPMS cleanup. If your invoice says one thing, the platform payout says another, and the bank declaration uses a third category, the mismatch becomes expensive later.

03 · If the transfer came through Wise or a platform

Wise, Stripe, PayPal, Deel, Upwork, and other rails can make the bank trail less obvious because the name visible to the bank may not be your end customer's name. A client pays one system, the platform converts or batches funds, and your Indian bank sees a remittance that needs explanation.

In that case, collect two sets of records: the customer-side commercial record and the platform-side payout record. For example, keep the client invoice and contract, plus the Wise or platform transfer receipt, payout ID, remitter name shown to the bank, amount, currency, and date.

If you are choosing the payment stack itself, not only chasing a stuck remittance, compare the checkout and bank-proof tradeoffs in our Indian SaaS international payments guide.

If the platform is Dodo Payments or another Merchant of Record, the bank-proof question is even more specific: what is the payout route, what document is generated, and does your bank treat the credit as foreign inward remittance evidence? We mapped that separately in the Dodo/MoR FIRA/FIRC guide.

Do not assume the payout receipt alone is enough for tax or export-compliance evidence. It may help the bank trace the remittance, but your CA may still ask how it maps to your export invoice, LUT, GST, FIRA/FIRC, or e-BRC trail.

04 · Purpose codes for contractors and agencies

Purpose codes are bank reporting categories for foreign exchange transactions. The exact code depends on the real nature of the service, not just on the platform you used. RBI's purpose-code reporting material includes service receipt codes such as P0802 for software consultancy / implementation and P1006 for business and management consultancy / public relations services.

Use those examples carefully. A developer, product consultant, design agency, marketing freelancer, course creator, and SaaS founder may not all fit the same code. Ask the bank or CA which purpose code matches your actual invoice description and contract. The bank's reporting is the trail that later systems and compliance teams see. For a narrower marketing use case, see the SEO services purpose-code guide.

Primary-source context: RBI's Report of the Working Group on Balance of Payments Manual for India includes Attachment IV, New Purpose Codes for Reporting Forex Transactions.

05 · FIRA, FIRC, e-BRC, and EDPMS

When the remittance finally credits, the documentation work may not be over. For Indian service exporters, four records often get mixed together:

• FIRA / FIRC / payment advice is bank-side evidence that foreign money came into India.
• e-BRC is the DGFT-side realization certificate that may matter for export benefits or GST refund evidence.
• EDPMS is the RBI-side export-monitoring system where your AD bank handles export realization and closure workflows.
• GST/LUT records connect the export invoice to zero-rated supply treatment or refund work.

RBI's Master Direction on Export of Goods and Services says exporters must realize and repatriate the full value of goods, software, or services within the stipulated period. That does not mean every stuck inward remittance is an EDPMS problem on day one. It means the realization trail matters, and you should keep it clean before the quarter closes.

06 · What to send the bank

If an export-service receipt is stuck or unclear, prepare a single concise packet instead of sending scattered screenshots. Include:

• Bank account number, branch, and your registered business name.
• Expected remittance amount, currency, sender name, sender country, expected date, and UTR/SWIFT/reference if available.
• Client invoice with invoice number, date, service description, amount, and currency.
• Contract, statement of work, email confirmation, or platform order showing why the client paid.
• Wise/platform payout receipt, bank advice, or payment confirmation.
• Proposed purpose-code context, written as a question for the bank/CA to confirm rather than a blind assertion.
• GST/LUT context if this is an export of services under LUT or with IGST refund work expected.

SBI also describes an internet-banking flow for tracking and disposal of fresh remittance for NRO/NRE account use cases. If your account or receipt type is different, use that as a signal to ask the branch or trade services desk for the correct route rather than forcing the wrong workflow.

07 · Check before the next foreign payment

A stuck payment is a warning light. Even after the money credits, check whether your export setup is clean for the next receipt: invoice description, LUT, GST treatment, purpose code, FIRA/FIRC evidence, e-BRC path, and bank handoff.

If you receive foreign client payments repeatedly, do this before the next invoice, not after the bank has already asked for a missing document.

Sources / further reading: SBI foreign inward remittance information; SBI fresh remittance tracking/disposal FAQ; RBI Master Direction on Export of Goods and Services; RBI purpose-code reporting context. Confirm your exact remittance route, purpose code, GST treatment, and bank process with your CA / AD bank.