Purpose Code P0809 - Satellite services

The P0809 purpose code is for payments received from foreign clients for satellite services, including launches, satellite capacity and related space services. Check when it applies, how it differs from P0808 and P1022, and the GST points for this inward remittance.

The P0809 purpose code is used when an Indian company receives money from abroad for satellite services. The RBI description is "satellite services including space shuttle and rockets, etc.", so it covers launch work as well as services delivered through satellites. Typical users are launch providers placing a foreign customer's satellite in orbit, operators leasing satellite capacity, and firms running tracking or ground support for foreign missions. It is a current account receipt for a service export. It sits in the RBI group for telecom, computer and information services.

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:

• Satellite launch services - A foreign company pays an Indian launch provider to carry its satellite to orbit on an Indian rocket.
• Satellite capacity leasing - A foreign broadcaster or telecom firm pays for transponder or bandwidth capacity on an Indian satellite.
• Tracking and ground station support - Fees for tracking, telemetry and command support for a foreign satellite or mission.
• Satellite imagery and data services - A foreign client pays for earth observation data supplied from an Indian satellite.
• Launch-related mission services - Payload integration and launch campaign support billed as part of a foreign launch contract.

Do not use this code when:

• You provide ordinary telecom, internet or voice services over ground networks (use P0808 instead).
• You provide space research, scientific testing or technical studies, not satellite services (use P1022 instead).
• You repair or maintain a foreign rocket or space vehicle (use P1602 instead).
• You sell satellite parts or hardware that is shipped abroad (use the goods export codes 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 P0809 (Satellite services) when your bank asks for the purpose of the inward remittance.
2. Upload the launch or service agreement and the invoice raised on the foreign client.
3. Give a FEMA declaration where the bank asks, confirming the service provided.
4. The bank checks the documents, converts the funds and credits your account.

Additional Notes:

• Launch contracts often pay in milestones. Report each milestone receipt under P0809 and keep the matching invoice.
• Keep the bank's FIRC or e-FIRA. It is your proof of foreign inward remittance for GST refunds and eBRC.
• If one contract mixes services and hardware sales, ask the client to invoice them separately.

• 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