Purpose Code S0802 - Software consultancy/implementation

The S0802 purpose code is for paying a foreign firm or freelancer for software consultancy, development or implementation. Check when it applies, how it differs from S0807, and the tax forms and documents your bank needs for this outward remittance.

The S0802 purpose code is used when an Indian business pays a foreign firm or developer for software services. The RBI description is "software consultancy / implementation". It covers people's time and expertise: planning, building, setting up or integrating software for you. It is a current account transaction, meaning a payment for services, not an investment. It sits in the RBI group for telecom, computer and information services. The main test is service versus product. If you pay for work done for you, such as a custom app or an ERP rollout, it is S0802. If you pay for a ready-made licence or subscription, it is usually S0807.

This Purpose Code should be used only where the transaction fits its defined regulatory scope. Here's when you should and shouldn't use this code:

You should use this code when:

• Custom software development - An overseas agency builds a web app, mobile app or internal tool to your brief.
• ERP or CRM implementation - A foreign partner configures and rolls out a platform such as an ERP for your company.
• System integration - A specialist connects your payment, inventory and accounting systems.
• Software architecture advice - A consultant reviews your tech stack or plans a cloud migration.
• Freelance developers - Hourly or milestone payments to a developer based abroad.

Do not use this code when:

• You are buying an off-the-shelf licence or SaaS subscription (use S0807 instead).
• You are paying for hosting, database or data processing charges (use S0803 instead).
• The payment is for ongoing repair, support or maintenance of existing software (use S0804 instead).
• The advice is about business strategy, not software (use S1006 instead).

RBI purpose codes are mandatory under FEMA to classify the nature of cross-border transactions entering or leaving India. They allow banks and regulators to accurately track foreign exchange flows and apply the correct regulatory, tax, and reporting treatment.

For individuals, businesses and institutions, correct purpose code usage:

• Ensures transactions are classified correctly under FEMA.
• Enables accurate reporting to the RBI and other regulators.
• Reduces delays caused by compliance checks or misclassification.
• Supports clean audit trails and tax reconciliation.

Bottom-line:

Using the correct purpose code helps ensure smooth processing, regulatory compliance, and faster credit of funds.

1. Select "S0802 – Software consultancy / implementation" on Form A2 or your bank's outward remittance screen.
2. Upload the contract or statement of work and the vendor's invoice.
3. File Form 145 (earlier Form 15CA), with a CA's Form 146 (earlier Form 15CB) where needed, and deduct any TDS due.
4. The bank checks the documents, books the FX rate and sends the payment.

Additional Notes:

• Software consultancy fees are often treated as fees for technical services. Some tax treaties (DTAA) tax them only if the know-how is passed on to you, so the TDS answer depends on the vendor's country.
• Keep the vendor's TRC and Form 10F on file if you apply a DTAA rate.
• If one invoice covers both licences and services, ask for a split so each part gets the right code.

• Using a generic or incorrect purpose code instead of the exact RBI-prescribed purpose code can lead to misclassification of the transaction under FEMA and trigger additional compliance checks by the bank.
• Mismatch between purpose code, invoice, and remittance narration may place the transaction on hold until clarification is provided.
• Submitting unclear or incomplete supporting documents that do not clearly describe the nature of the transaction often result in delays, as banks rely on documentation to validate FEMA compliance.
• Missing mandatory PAN or incomplete KYC documentation can prevent banks from releasing funds until verification is completed.
• Using service-related purpose codes for non-service transactions like capital receipts, investments, gifts, or refunds can result in incorrect regulatory treatment and potential reporting issues.
• Assuming small or recurring transactions do not require accuracy and repeated misclassification can attract regulatory scrutiny over time.

Cross-border payments require accurate purpose code selection and complete compliance documentation. Xflow helps businesses and individuals receive international payments while staying aligned with RBI and FEMA requirements.

With Xflow, you can:

• Select the correct purpose code with clarity
• Organize and maintain supporting documents
• Reduce compliance back-and-forth with banks
• Support FEMA compliant inward remittances