P0802 Purpose Code: Software consultancy and implementation

P0802 is the RBI purpose code for: Software consultancy/implementation (other than those covered in SOFTEX form). It sits in group 08, Telecom, Computer and Information Services, of the receipt purposes RBI uses to classify foreign exchange coming into India.

P0802 at a glance

CodeP0802
RBI wordingSoftware consultancy/implementation (other than those covered in SOFTEX form)
RBI group08, Telecommunication, Computer & Information Services
StatusIn RBI's receipt purpose list
eBRC on DGFTYes, Services > IT
Who attaches itThe AD bank that receives the payment

Can a P0802 remittance become an eBRC?

Yes. DGFT's guidelines name P0802 as one of only four purpose codes that apply to an eBRC for Services > IT: P0802, P0803, P0807 and P0103. It generates an eBRC on its own; only P0103 may be clubbed with another code. For a service export DGFT also shows only the invoices whose SAC code matches the description of the service.

The rule is DGFT’s, from its General Guidelines for Generating eBRC (last updated 26 March 2024). The full list, and what each rule means when you map remittances, is in how to generate an eBRC on the DGFT portal.

What this code says about the money

A purpose code is your bank speaking, not you. When a foreign payment reaches your account, the AD bank reports it with a purpose code that states the RBI classification of the transaction, and that report is the Inward Remittance Message, the IRM. A remittance carrying P0802 has been classified as: Software consultancy/implementation (other than those covered in SOFTEX form).

In FETERS reporting

FETERS is the Foreign Exchange Transactions Electronic Reporting System, the system under which Authorised Dealer banks report their foreign exchange transactions to the RBI, and its receipt purpose list is where P0802 is defined. That list, Annex I to A.P. (DIR Series) Circular No. 84 dated 29 February 2012, places P0802 in group 08, Telecommunication, Computer & Information Services, and describes it as: Software consultancy/implementation (other than those covered in SOFTEX form). That is the wording a bank’s reporting desk works from, so it is the wording to match when you ask the bank what a remittance was reported as.

P0802 or a neighbouring code

The codes below are the ones most easily confused with P0802. The difference is in RBI’s wording, so the table quotes it, with what DGFT allows for each.

CodeRBI wordingeBRC on DGFT
P0802Software consultancy/implementation (other than those covered in SOFTEX form)Yes, Services > IT
P0807Off-site Software ExportsYes, Services > IT
P0803Data base, data processing chargesYes, Services > IT
P1006Business and management consultancy and public relations servicesService export, not named

If the code on your remittance looks wrong

The code is attached at reporting time by the bank, so the fix runs through the bank, not through DGFT. Ask the AD branch that received the payment to confirm the classification; an amended report shows up as a revised IRM. What each IRM status means, and what you can do with a remittance in each state, is in the IRM explainer, and the errors DGFT returns when a code does not fit the filing are in IRM mapping errors on DGFT. Exporters who agree the purpose code with their buyer's bank once, at onboarding, rarely meet this page twice.

Other codes in group 08

All 9 Telecom, Computer and Information Services purpose codes

P0802 is an RBI purpose code for an inward remittance, and it classifies the payment as: Software consultancy/implementation (other than those covered in SOFTEX form). It sits in group 08, Telecom, Computer and Information Services, of the receipt purposes Authorised Dealer banks report to the RBI.

Yes. DGFT's guidelines name P0802 as one of only four purpose codes that apply to an eBRC for Services > IT: P0802, P0803, P0807 and P0103. It generates an eBRC on its own; only P0103 may be clubbed with another code. For a service export DGFT also shows only the invoices whose SAC code matches the description of the service.

Your AD bank does, not you. When a foreign payment reaches the account the bank reports it to the RBI with a purpose code, and that report is the Inward Remittance Message, the IRM. The code arrives already attached, which is why a code that looks wrong is corrected through the bank rather than through DGFT, before the remittance is mapped to an eBRC.

In RBI's FETERS receipt purpose list, Annex I to A.P. (DIR Series) Circular No. 84 dated 29 February 2012, P0802 sits in group 08, Telecom, Computer and Information Services, and reads: Software consultancy/implementation (other than those covered in SOFTEX form). FETERS is the Foreign Exchange Transactions Electronic Reporting System, under which Authorised Dealer banks report their foreign exchange transactions to the RBI.

They describe different payments. P0802 means: Software consultancy/implementation (other than those covered in SOFTEX form). P0807 means: Off-site Software Exports. P0803 means: Data base, data processing charges. For an eBRC under DGFT's guidelines: P0802: Yes, Services > IT; P0807: Yes, Services > IT; P0803: Yes, Services > IT. The AD bank picks the code that describes the payment, from the 9 codes in group 08 and the rest of RBI's list.

Get started

The code arrives with the money. So can the certificate.

The eBRC exporter app is free at any volume. No certificate limit, no card required.