Purpose Code S0807 - Off-site software imports

The S0807 purpose code is for paying a foreign company for software delivered online, such as licences, downloads and SaaS subscriptions. Check when it applies, how it differs from S0802, and the tax points for this outward remittance.

The S0807 purpose code is used when an Indian business or individual pays a foreign company for software delivered from outside India. The RBI description is "off-site software imports". "Off-site" means the software reaches you online, not on a physical disc shipped through customs. It is a current account transaction, meaning a normal payment, not an investment. It sits in the RBI group for telecom, computer and information services. The main test is product versus service. If you pay for a ready-made tool, it is S0807. If you pay a firm to build or set up software for you, it is S0802. Some banks treat SaaS in different ways, so match the code to your invoice and ask your bank if in doubt.

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:

• SaaS subscriptions - Annual or monthly plans for design, CRM, project or analytics tools billed by a foreign company.
• Software licences - Perpetual or term licences for engineering, accounting or security software.
• Downloaded software - Tools and plug-ins bought from a foreign vendor's website.
• Seat renewals - Adding or renewing user seats on an existing foreign software plan.
• Developer tools and APIs - Fixed plans for code tools or software kits delivered online.

Do not use this code when:

• A foreign firm builds, customises or implements software for you (use S0802 instead).
• You pay usage-based hosting, storage or data processing charges (use S0803 instead).
• The fee is only for support or maintenance of software you own (use S0804 instead).
• The software comes on physical media shipped through customs (use S0102 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 "S0807 – Off-site software imports" on Form A2 or your bank's outward remittance screen.
2. Upload the vendor invoice and the order form or licence terms.
3. File Form 145 (earlier Form 15CA), with a CA's Form 146 (earlier Form 15CB) where needed, and deduct TDS only if it applies.
4. The bank checks the documents, books the FX rate and sends the payment.

Additional Notes:

• Under a 2021 Supreme Court ruling, fees for end-user software licences are generally not royalty under tax treaties (DTAA), so TDS is often nil. You need the vendor's TRC and Form 10F to rely on the treaty.
• The 2% equalisation levy on foreign digital services no longer applies, so it is not deducted on these payments.
• Keep licence and services lines separate on the invoice if a vendor sells both.

• 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