P0802 Purpose Code: Software consultancy and implementation

Purpose code P0802 is used when an Indian business or freelancer receives payment from a foreign client for software consultancy and implementation services.

What is the P0802 purpose code?

Purpose code P0802 is used when an Indian business or freelancer receives money from abroad for software consultancy and implementation services. This covers work like custom software development, system implementation, technical consulting, and related software delivery for a foreign client. It applies specifically to software services not covered under a SOFTEX filing, packaged or off-site software product exports use P0807 instead. Under RBI FEMA guidelines, this inward payment is classified under computer and information services and reported accordingly.

When to use P0802 purpose code?

Use P0802 when you receive money from a foreign client for software services provided from India. It is the correct RBI purpose code for software consultancy, development, and implementation work that is not filed under SOFTEX. P0802 applies to the service itself, whatever your business structure.

When to use a different code:

• Use P0801 when the payment is for hardware consultancy or installation
• Use P0803 when the payment is for data processing, hosting, or database services
• Use the matching S-code when you are paying a foreign vendor rather than receiving money

Who typically uses P0802 purpose code

Software service exporters, IT consultants, and freelance developers in India who bill foreign clients for building or implementing software. It applies whether you invoice as an individual freelancer, a proprietorship, or a registered company.

Examples of transactions covered under P0802 purpose code

• Payment for developing a custom web or mobile application for an overseas client
• Fees for implementing or configuring software at a foreign company
• Retainer for ongoing technical consulting on a software project
• Milestone payment for a software delivery contract with an international client

When NOT to use P0802 purpose code

• The payment is for hardware consultancy or installation (use P0801)
• The payment is for data processing, hosting, or database services (use P0803)
• The payment is a small-value receipt below the freelancer threshold (use P1590 where applicable)
• You are paying a foreign vendor rather than receiving (use the matching S-code)

Documents required for P0802 purpose code

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

How is a P0802 Purpose Code declared?

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

1. Raise your invoice: Bill your foreign client for the software service, clearly describing the work.
2. Receive the payment: The client sends the money to your bank or receiving account.
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 invoice, contract, and KYC 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.

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 P0802 purpose code

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

1. Using a closely related code: Tagging a transaction with this code when it actually belongs under a similar, adjacent code.
2. Code and invoice mismatch: The code not matching what your invoice describes, which flags the payment.
3. Incomplete documents: Missing invoice, contract, or KYC, so the bank holds funds until provided.
4. Missing PAN or KYC: Incomplete verification stops the bank from releasing the payment.
5. Ignoring small payments: Assuming low-value receipts don't need the correct code, which invites scrutiny.
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 P0802 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 P0802 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.