P0809 Purpose Code: Satellite services including space shuttle and rockets, etc.

Purpose code P0809 is used when an Indian business receives payment from abroad for satellite services or related space services.

What is the P0809 purpose code?

Purpose code P0809 covers money received from abroad for satellite services, and the description extends that to space shuttle and rockets. Those are not communications services in the ordinary sense, so the code reaches further than its group name suggests: it covers satellite capacity and the space activity that supports it, including launch. What separates it from its neighbour is the medium rather than the service, since terrestrial telecommunication reports under P0808 and satellite-based provision reports here. Under RBI FEMA guidelines, this inward payment is classified under Telecommunication, Computer & Information Services and reported accordingly.

When to use P0809 purpose code?

Use P0809 when your Indian business is paid from abroad for satellite services, whether that is transponder capacity, ground segment services, or the space services the description names alongside them. It is the correct RBI purpose code for the satellite side of the group. Because the description reaches into launch and space activity without setting out where that stops, confirm with your bank where your work is a space service rather than a communications one.

When to use a different code:

• Use P0808 when the service is terrestrial telecommunication rather than satellite-based
• Use P0803 when the payment is for processing data received via satellite rather than for the satellite service itself
• Use the matching S-code when you are paying a foreign vendor rather than receiving money

Who typically uses P0809 purpose code

Indian satellite operators, ground segment and teleport providers, and organisations providing space services to overseas customers, including capacity leasing and launch-related work. The recipient is the Indian business being paid, and the sector is small but growing.

Examples of transactions covered under P0809 purpose code

• Transponder capacity fees received from an overseas broadcaster or telecom operator
• Ground segment and teleport services billed to an international satellite customer
• Payment from a foreign customer for satellite-based communication capacity
• Fees received from abroad for space services of the kind the description names

When NOT to use P0809 purpose code

• The service is terrestrial telecommunication rather than satellite-based (use P0808)
• The payment is for processing or analysing data that arrived by satellite rather than for the satellite service (use P0803)
• The work is technical or scientific services outside what this description names, in which case confirm the correct code with your bank
• You are paying a foreign vendor rather than receiving (use the matching S-code)

Documents required for P0809 purpose code

To receive a payment under P0809, keep the following documents ready so your bank or platform can verify the transaction and report it correctly under FEMA.

How is a P0809 Purpose Code declared?

Declaring the code is pretty straightforward. Here's how the payment gets tagged and reported.

1. Provide the service: Deliver the satellite capacity, ground segment work, or space service under your agreement.
2. Raise your invoice: Bill the overseas customer for the capacity or services provided in the period.
3. Declare the purpose: State the purpose of the inward remittance, on your bank's form or through your platform.
4. Submit supporting documents: Provide the service agreement and invoice so the bank can verify the transaction.
5. Get your FIRA: Once processed, your FIRA is issued as proof and the payment is reported under FEMA.
6. With a traditional bank you handle each step of your payment journey. But with a platform built for cross-border payments, you can preselect a default purpose code so that the payments land smooth.

Common mistakes to avoid while using P0809 purpose code

A few common slips can hold up your payment or cause compliance issues. Here's what to watch for.

1. Choosing between P0808 and P0809 by service rather than medium: Treating all communications revenue as one code, when terrestrial telecommunication and satellite-based provision are split between the two.
2. Coding downstream data work as a satellite service: Applying P0809 to processing or analysing data that arrived by satellite, when the processing is a data service and only the satellite provision belongs here.
3. Code and invoice mismatch: The code not matching what your service agreement describes, which flags the payment.
4. Incomplete documents: Missing the capacity agreement or usage statement, so the bank cannot establish what was provided and holds funds until provided.
5. Missing PAN or KYC: Incomplete verification stops the bank from releasing the payment.
6. Using an inward code for an outward payment: Applying a receipt code to money you're sending out instead of the matching outward code.

How Skydo simplifies inward remittance under P0809 Purpose Code

With a bank, you declare the purpose code on your own for every single payment. With Skydo, you can preselect your code once and every payment gets tagged automatically.

1. Preselect the code once: Set P0809 as your default and Skydo tags every incoming payment for you, so there's no form to fill on each one.
2. No repeat declarations: A bank makes you restate the purpose for every remittance. Skydo does it in the background, the same way each time.
3. Instant, free FIRA: Your remittance proof is generated and stored on every payment, ready for your CA, GST, and audits, with no request and no fee.
4. Zero FX markup: You get the live mid-market rate with a flat, visible fee, instead of a markup hidden inside the bank's rate.
5. Settled in 24 hours: Your payment reaches your Indian bank within a day, fully reported and compliant.