RBI Purpose Code: Full List and How to Use It in 2026

Every foreign payment credited to your Indian bank account carries a three-to-five character code that tells the RBI exactly what you were paid for. Called a purpose code, it feeds directly into India's Balance of Payments data and sits on the FIRC or eFIRA your bank issues after each transfer. Get it wrong and your GST export refund stalls, your SOFTEX filing breaks, or your payment sits in limbo while your bank requests additional documents. This guide covers the full list, the codes that matter most by business type, and how to submit them correctly.

A purpose code is a short alphanumeric identifier that AD (Authorised Dealer) banks record for every inward or outward foreign exchange transaction under the RBI's FETERS (Foreign Exchange Transactions Electronic Reporting System) framework. Inward remittance codes begin with "P"; outward remittance codes begin with "S." Banks must capture and report the code before crediting your account. The governing document is RBI Master Direction No.18/2015-16 on Reporting under FEMA, 1999, updated June 24, 2026. Over 150 distinct codes exist across inward and outward categories.

This is the most common compliance error among IT and software exporters. P0802 covers software consultancy, development, and implementation when the receipt is not SOFTEX-reportable. P0807 applies to off-site software exports that must be declared through the SOFTEX mechanism to the relevant Software Technology Parks of India (STPI) or SEZ authority.

If your agency files SOFTEX declarations, use P0807. If it does not (which covers the majority of IT services firms billing on time-and-materials or fixed-fee contracts without SOFTEX), use P0802. Applying P0802 to a SOFTEX-reportable export, or vice versa, creates a mismatch between your SOFTEX filings and your bank records, which can trigger queries during tax assessments and income tax return processing.

Consultancy, BPO, and KPO work that does not involve software development belongs under P1006, not P0802.

Outward remittance codes begin with "S" and must be quoted on Form A2 for every payment sent abroad. The following codes cover the most common outward business transactions, sourced from RBI FETERS V6.2.

• S0001-S0009: Capital account transactions (Indian investment abroad in equity, debt, or real estate; FDI repatriation)

• S0101-S0108: Import of goods (covering advance payments, sight payments, and usance bills)

• S0802-S0804: Outward payments for software consultancy and maintenance

• S1101-S1103: Royalties, license fees, and franchise payments

Most Indian exporters encounter S-codes only when making outward payments for software licenses, imported inputs, or overseas office expenses. The inward P-codes above are the primary concern for businesses collecting payments from foreign clients.

The process is straightforward, but the timing matters.

1. Raise an invoice that clearly identifies your service or goods category.

2. Share the correct purpose code with your overseas client and ask them to include it in SWIFT message fields 70 or 72 when initiating the transfer.

3. When your AD bank receives the funds, confirm the purpose code before the bank processes the credit. Banks typically send a query message if the code is missing.

4. Provide supporting documents alongside the code: your invoice, signed contract, and purchase order where available.

5. The purpose code is then recorded on your FIRC or eFIRA, which serves as your proof of foreign inward remittance.

Under FEMA 1999, you must retain FIRA documents, invoices, contracts, and bank advices for at least five years. If your bank credits your account with an incorrect code, request a correction in writing with your invoice as supporting evidence; AD banks can update purpose codes post-credit.

The consequences range from administrative inconvenience to formal penalties. An incorrect purpose code can cause your bank to hold the payment pending clarification, block GST export refunds (since the refund process cross-references FIRC purpose codes), and create mismatches in your SOFTEX filings or income tax returns.

Under FEMA 1999, Section 13, deliberate misreporting attracts penalties of up to three times the transaction amount. For inadvertent or technical errors, the RBI amended its Master Directions on Compounding of Contraventions under FEMA, 1999 on April 22, 2025, introducing a cap of ₹2,00,000 for certain technical contraventions, including incorrect purpose codes. Before this amendment, no upper cap existed for such violations. Incorrect purpose codes are among the highest-volume compounding categories under FEMA, according to analysis by Cyril Amarchand Mangaldas.

The practical takeaway: first-time or inadvertent errors now carry defined maximum financial exposure, but prevention remains far simpler than correction.

Selecting and submitting the right RBI purpose code is easier when the platform handles the documentation layer automatically. Jio Payment Solutions, an RBI-regulated payment aggregator with a PA-CB (Cross Border) license, issues an automated eFIRA for international payments received, with the purpose code captured as part of built-in FEMA reporting. This removes the manual step of chasing your bank for FIRC documentation and reduces the risk of code mismatches sitting undetected on your records.

For IT exporters billing recurring clients, the platform supports both one-time and standing instruction payments, with settlement designed for faster processing than traditional international wire arrangements. Jio Payment Solutions also provides transparent fees, so businesses can understand the applicable costs before using the service.

Purpose codes are not paperwork for its own sake; they determine whether your GST refunds clear, your SOFTEX filings reconcile, and your FEMA record stays clean. The two decisions that catch most exporters off guard are the P0802/P0807 split for IT exporters and the importance of confirming the code with your bank before, not after, the credit lands.

Check your last five inward payment FIRCs or eFIRAs today. Verify the purpose codes against the RBI FETERS Annexure II. If any are wrong, contact your AD bank with the correct invoice to request an amendment.