· 7 min read

Purpose code for SEO services in India: P1007, P0802, FIRC, and GST/LUT

A foreign client asking for SEO work can create a surprisingly practical question: what purpose code should you give the bank? The useful answer is not a magic code. It is a clean service description, invoice, bank-proof trail, and CA/bank confirmation.

This guide is for Indian SEO freelancers, consultants, digital marketing agencies, performance marketers, and small service exporters receiving money from foreign clients. It is not legal, tax, GST, FEMA, or banking advice. Use it as an operating checklist before you tell the client, payment rail, or bank which purpose-code context applies.

If you are still preparing the invoice itself, start with the foreign-client invoice guide. If the money has already reached the bank and is stuck, use the inward-remittance purpose-code checklist.

01 · Why the bank asks for a purpose code

A purpose code is the reporting bucket your authorised dealer bank uses to classify a foreign-exchange receipt. For a foreign client payment, the bank is not only asking whether money arrived. It is asking what the receipt is for: software services, advertising, consultancy, subscription, goods export, salary, gift, refund, or something else.

The code should follow the substance of your invoice and contract. If your invoice says "SEO services" but your declaration says a generic information-services or software code, the file may still be credited, but the paper trail can look weak later when your CA, AD bank, GST file, e-BRC work, or refund review asks what the export actually was.

Practical rule:treat the purpose code as a question to confirm with your bank or CA, not as a number to copy from another freelancer's Reddit comment.

02 · SEO is not always one code

"SEO" can mean different commercial work. One freelancer may be doing technical SEO on a SaaS site. Another agency may be running paid search campaigns, market research, reporting, and digital strategy. Another consultant may be advising a founder on content operations without touching the website implementation.

Those are not obviously the same service category. The invoice should therefore describe the actual work: technical SEO audit, website implementation support, digital advertising management, market research, content strategy, analytics/reporting, or business/marketing consultancy. The cleaner your words, the easier it is for the bank to choose the right reporting bucket.

03 · P1007, P0802, P1006, and P0806

RBI's published purpose-code material groups receipts by service type. Commonly discussed buckets around SEO and digital services include:

  • P1007. RBI describes this as advertising, trade fair, market research, and public opinion polling services. This is often the first code to ask about when the invoice is really advertising, digital marketing, campaign management, keyword research, or market research work.
  • P0802. RBI describes this as software implementation/consultancy, other than items covered in SOFTEX. Ask about this only where the SEO work is genuinely tied to software, website, analytics, integration, migration, or technical implementation work.
  • P1006. RBI describes this as business and management consultancy and public relations services. This can be relevant where the invoice is more strategy/advisory than execution.
  • P0806.RBI describes this as other information services, including subscriptions to newspapers and periodicals. Do not treat it as a generic "internet services" fallback without bank/CA confirmation.

The safe wording with your bank is: "My invoice is for [actual service]. Would you treat this under [candidate code], or do you need a different purpose code for this service description?" That keeps the bank accountable for the final reporting choice.

04 · Invoice wording that helps the bank

Avoid invoices that say only "SEO", "online work", "consulting", or "digital service". Those words may be true, but they force the bank or CA to infer too much.

Better invoice descriptions are more specific:

  • Technical SEO audit and implementation support.
  • Search-engine optimization consulting for client website.
  • Digital advertising campaign management and reporting.
  • Keyword research, content strategy, and analytics review.
  • Marketing strategy consulting for overseas client.

Keep the contract, statement of work, email scope, client approval, invoice, and bank credit together. If the bank asks why you chose a code, you should be able to point to one consistent service story.

05 · FIRA/FIRC, bank proof, and receipt trail

The purpose-code decision is only one part of the export file. You also need the receipt trail: remitter name, payment rail, bank credit, UTR or SWIFT reference, payment advice, FIRA/FIRC where available, and the invoice it closes.

If the client pays directly by SWIFT, the mapping is usually easier: client invoice to remitter to bank credit. If the money comes through PayPal, Wise, Skydo, Stripe, Upwork, Dodo, Paddle, or another intermediary, the sender visible to your bank may not be the final client. Keep platform statements and payout IDs so your CA can understand how the client payment became the Indian receipt.

If a receipt is already stuck or unclear, the bank follow-up checklist has the packet to collect before escalating.

06 · GST, LUT, and export-service records

Purpose code does not decide GST treatment by itself. A foreign client, foreign payment, and SEO invoice still need the broader export-of-services review: supplier, recipient, place of supply, payment route, relationship between parties, GST registration, and LUT position where applicable.

If your CA says the work is an eligible export of services under GST and you are using LUT, keep the Form GST RFD-11 acknowledgement for the financial year. If LUT is missing or output IGST was charged, understand the refund or ITC trail before sending the next invoice.

For the cash-flow side, read the LUT and IGST refund guide.

07 · Common mistakes to avoid

  • Using P0806 because it sounds broad. Its RBI wording is not a generic SEO bucket. Confirm before using it.
  • Calling everything software. Technical SEO may touch software systems, but ad management or content strategy is not automatically software consultancy.
  • Changing the invoice after the bank asks. Better to make the description accurate before payment.
  • Ignoring the payment rail. Platform payouts need platform proof, not just a bank statement line.
  • Separating GST/LUT from the bank file. Your CA will eventually need both the tax position and the remittance proof.

08 · Check before the client pays

Before the next foreign SEO payment, answer five questions. What exact service did you invoice? Which purpose-code bucket is your bank likely to use? Does the payment rail give usable proof? Does the bank credit map back to the invoice? Is GST/LUT treatment decided for this period?

If any answer is fuzzy, fix it while the transaction is fresh. The expensive part is not choosing between P1007 and P0802. It is trying to reconstruct the story six months later.

Check your purpose-code and bank-proof trail.

NiryatBox's free readiness checker asks a few questions about your export setup and flags LUT, e-BRC, EDPMS, purpose-code, FIRA/FIRC, and bank-handoff gaps. No bank login, no signup, and it gives you a shareable report for your CA.

Run the readiness checker →

Made in India. Questions: support@niryatbox.com.

Sources / further reading: RBI purpose-code reporting context; RBI Annexure II purpose-code list; RBI Master Direction on Export of Goods and Services; GST portal tutorial for furnishing LUT / Form GST RFD-11. Confirm your exact purpose code, GST registration, LUT treatment, FIRA/FIRC proof, and bank process with your CA and AD bank.