P0502 Purpose Code: Receipts on account of construction works carried out abroad by Indian Companies

Purpose code P0502 is used when an Indian company is paid by an overseas client for construction work carried out abroad.

What is the P0502 purpose code?

Purpose code P0502 covers money an Indian company receives for building something outside India. It is the outward-facing half of the construction services pair, with its counterpart covering construction of projects here, so the location of the work is what separates the two. The receipt is payment for the construction itself rather than for goods supplied or for any investment in the project. Overseas construction contracts commonly sit within a project export approval framework carrying its own conditions, so confirm what applies to your contract before relying on this code alone. Under RBI FEMA guidelines, this inward payment is classified under Construction Services and reported accordingly.

When to use P0502 purpose code?

Use P0502 when your Indian company is paid by an overseas client for construction work performed abroad, whether that is a progress payment, a milestone certificate, or a final account settlement. It is the correct RBI receipt code for the construction work itself. Overseas projects run under a project export approval framework, so establish what your contract requires before the first payment rather than after it, since the code classifies the receipt but does not satisfy the approval.

When to use a different code:

• Use P0501 when the construction project is in India rather than abroad
• Use the export codes when the receipt is payment for goods supplied rather than for construction work performed
• Use the matching S-code when you are paying a foreign vendor rather than receiving money

Who typically uses P0502 purpose code

Indian construction, engineering and infrastructure companies executing projects outside India, including contractors on overseas civil works, engineering firms delivering built projects abroad, and specialist subcontractors working on foreign sites. The recipient is the Indian company being paid, since the code is declared on the money arriving here.

Examples of transactions covered under P0502 purpose code

• Progress payment received from an overseas client against a certified stage of works
• Milestone payment on an infrastructure project being built abroad by an Indian contractor
• Final account settlement received on completion of an overseas construction contract
• Payment for civil works executed at a foreign site by an Indian engineering firm

When NOT to use P0502 purpose code

• The construction project is in India rather than abroad (use P0501)
• The money is payment for goods exported from India to the project site rather than for construction work performed, which reports under the export codes
• The receipt is a return on an investment in the overseas project rather than payment for work done, which reports under the capital account codes
• You are paying a foreign vendor rather than receiving (use the matching S-code)

Documents required for P0502 purpose code

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

How is a P0502 Purpose Code declared?

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

1. Settle the approvals: Establish what the project export approval framework requires for your overseas contract before work begins.
2. Carry out the works: Execute the construction on the foreign site under the contract.
3. Raise your certificate or invoice: Bill the overseas client for the works completed in the period.
4. Declare the purpose: State the purpose of the inward remittance, on your bank's form or through your platform.
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 P0502 purpose code

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

1. Treating the code as covering the approvals: Assuming P0502 is all that governs an overseas project, when project export contracts carry their own approval conditions that have to be satisfied separately.
2. Coding goods supply as construction work: Applying P0502 to payment for materials or equipment exported to the site, when that is an export receipt and only the construction work itself belongs here.
3. Code and document mismatch: The code not matching what your payment certificate describes, which flags the payment.
4. Incomplete documents: Missing the contract or interim certificate, so the bank cannot tie the receipt to certified works 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 P0502 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 P0502 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.