Purpose Code S0809 - Satellite services including space shuttle and rockets

The S0809 purpose code is for paying a foreign provider for satellite capacity, satellite links or launch services. Check when it applies, the tax points and the documents your bank needs for this outward remittance.

The S0809 purpose code is used when an Indian business pays a foreign provider for satellite services. The RBI description is "satellite services including space shuttle and rockets etc.". It covers the use of satellite capacity and the service of putting a satellite into orbit. 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. S0809 pays for the service, not the hardware. If you import a satellite dish, terminal or the satellite itself, that is a purchase of goods under the import codes.

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:

• Transponder capacity - A TV channel or DTH operator leases capacity on a foreign satellite.
• Satellite uplink and downlink - A broadcaster pays for links to send live feeds across countries.
• Launch services - A space startup pays a foreign launch provider to carry its satellite on a rocket.
• Maritime and in-flight connectivity - A shipping or airline firm pays for satellite internet on ships or aircraft.
• Satellite phone and data plans - A business pays for satellite airtime for remote sites or field teams.

Do not use this code when:

• You are buying satellite hardware, dishes or terminals (use S0101 or S0102 instead).
• The service is ordinary telecom, email or bandwidth not carried by satellite (use S0808 instead).
• You pay for space research, testing or other scientific work (use S1023 instead).
• You are buying satellite images or data sets for analysis (use S0803 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 "S0809 – Satellite services including space shuttle and rockets etc." on Form A2 or your bank's outward remittance screen.
2. Upload the capacity lease, launch contract or service agreement and the 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:

• Transponder lease payments have a long tax dispute history on whether they are royalty. The answer depends on the law, the contract and the DTAA, so a CA's view is needed.
• Launch contracts are often paid in milestones. Match each payment to the milestone invoice.
• Space and satellite users may also need sector approvals, which are separate from the bank's FEMA checks.

• 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