.png)
How to Pay Indian Freelancers from Abroad: FEMA Rules
- Saransh Garg
- 2 days ago
- 11 min read
Under the Foreign Exchange Management Act (FEMA) 1999, every payment made to an Indian freelancer from a foreign company is classified as an inward remittance and must be routed through an Authorised Dealer (AD) bank in India. This is not optional paperwork. It is a statutory requirement. If the Indian freelancer cannot produce a FIRC (Foreign Inward Remittance Certificate) or an equivalent bank credit memo, they cannot legally recognise the income for GST purposes, and your company may face scrutiny under FEMA Section 10(6) during audits.
When you need to pay Indian freelancers abroad, FEMA rules dictate not just how the money moves, but what documentation must exist on both ends of the wire. The permitted channels, the GST reverse-charge question, the Form 15CA/15CB requirement, all of it is non-negotiable. We have seen this exact problem derail engagements with three mid-sized European SaaS companies in the past 18 months. Most foreign finance teams discover these requirements only after the first payment is already flagged.
Why Most Foreign Companies Violate FEMA Rules When Paying Indian Freelancers
Every month, our team fields calls from finance controllers and legal ops leads at US, UK, Dutch, and German companies who have already been paying Indian contractors for 6 to 18 months via PayPal, Wise, Deel, or direct SWIFT, and have suddenly been asked by their Indian counterpart to produce documentation that was never generated.
The core confusion is structural. India treats inward remittances to individual freelancers differently from remittances to registered Indian companies. When you pay an Indian software house, the receiving entity raises a GST-compliant invoice, exports the service under LUT (Letter of Undertaking), and receives the funds through a normal export proceeds account. The paperwork is standard.
When you pay an individual Indian freelancer, someone working as a sole proprietor, a gig contractor, or an unregistered professional, the compliance chain has more links. The freelancer must receive the funds in an Indian bank account and not a foreign wallet. The bank must classify the credit under the correct purpose code. The freelancer must file the income under Schedule FSI in their Indian ITR. If the annual payment to a single Indian individual exceeds a threshold that triggers TDS obligations, the question of whether the foreign company has a "permanent establishment" risk in India gets activated.
We placed a team of seven backend engineers as individual contractors for a mid-sized Irish fintech in 2022. The client's finance team was wiring payments directly to each engineer's Wise account. Eighteen months in, two engineers were denied FIRC documentation by Wise India for a portion of their income, because Wise's AD bank category classification in India did not cover all purpose codes for professional services. The engineers could not reconcile their income for GST filing. We had to restructure the entire engagement onto an EOR model mid-contract.
The problem is not malice. It is that the rules governing how companies pay Indian freelancers abroad under FEMA rules are scattered across RBI Master Directions, FEMA Notification No. 14(R)/2016-RB, and GST Circular No. 56/30/2018. Foreign finance teams have no reason to know these exist unless someone tells them.
What FEMA 1999 Actually Requires When You Pay Indian Freelancers from Abroad
FEMA 1999, administered by the Reserve Bank of India (RBI), classifies all cross-border payments into Current Account and Capital Account transactions. Payments to Indian freelancers for services rendered to foreign clients fall under Current Account Transactions, specifically under the category of "invisible receipts" related to software and professional services exports.
Here is what that means in practice for your finance team.
Permitted payment channels: Funds must flow through SWIFT to an Indian bank account held at an RBI-designated Authorised Dealer bank. State Bank of India, HDFC, ICICI, Axis, Kotak, and most scheduled commercial banks qualify. Payments via PayPal are legally permissible only if PayPal settles the funds into the freelancer's linked Indian bank account within the RBI-stipulated timeline, currently 9 months for export proceeds, though this is practically settled within days. Wise operates as a payment intermediary and not an AD bank, so the final credit must still land in an Indian bank account to generate a valid FIRC.
Purpose codes: Every inward remittance must be tagged with an RBI purpose code. For software and IT services, the correct codes are typically P0802 (software consultancy) or P0699 (other professional services). If the bank tags the payment under an incorrect purpose code such as P1301 (personal remittances), the freelancer's export income classification breaks down and they lose access to GST zero-rating on their services.
GST implications: Indian freelancers exporting services to foreign clients are eligible for zero-rated GST (0%) under the IGST Act, provided they receive payment in convertible foreign exchange and satisfy the "export of services" conditions under Section 2(6) of the IGST Act. The foreign company does not pay Indian GST, but the freelancer must maintain proof of foreign exchange receipt (FIRC) to claim the zero-rating.
Form 15CA and 15CB: If your annual payment to a single Indian freelancer exceeds Rs. 5 lakh (approximately USD 6,000 or EUR 5,500 at current rates), the remittance triggers Form 15CA, which is a declaration filed by the Indian recipient or remitter, and in some cases Form 15CB, which is a certificate from a Chartered Accountant. As a foreign payer, you are not responsible for filing these, but your Indian contractor is. If they cannot produce them during an RBI or IT Department inquiry, it creates a retroactive compliance gap in your engagement.
FEMA Compliance Checklist: Every Step a Foreign Company Must Follow Before the First Payment
This is the framework our legal and ops clients at AnjuSmriti Global Recruitment Solutions use before the first payment is initiated. Screenshot and adapt it for your internal payment SOP.
Compliance Step | Who Is Responsible | Document Required | Timing |
Verify freelancer has an Indian bank account (not wallet) | Finance Team | Bank account proof from contractor | Before onboarding |
Confirm payment channel is SWIFT or RBI-approved | Finance Team | Internal check | Before first payment |
Correct RBI purpose code tagged by sending bank | Finance Team / Bank | Payment instruction to bank | At each wire |
Freelancer registers for GST (if turnover exceeds Rs. 20L or Rs. 10L for services) | Freelancer | GST registration certificate | Before first invoice |
Freelancer raises invoice with "Export of Services" declaration | Freelancer | Invoice copy | Per payment cycle |
FIRC or bank credit memo obtained by freelancer | Freelancer | FIRC from AD bank | After each receipt |
Form 15CA filed (if annual remittance exceeds Rs. 5L) | Freelancer with CA | Form 15CA acknowledgement | Before or at remittance |
Contract reviewed for PE risk triggers | Legal / Finance | Signed contract | Before engagement starts |
DTAA applicability checked for your country and India | Legal | Tax treaty text | One-time at setup |
Annual reconciliation of foreign income in freelancer's ITR | Freelancer | ITR Schedule FSI | At Indian tax filing time |
Two things most foreign companies miss. First, they never ask for the FIRC. They assume the bank generates it automatically and the contractor manages it. In practice, freelancers, especially those working with foreign clients for the first time, do not know to request it until something goes wrong. Build FIRC submission into your quarterly invoice approval workflow. Second, they use contract templates that include clauses like "dedicated resource" or "full-time availability," language that is innocuous in a US staffing context but creates PE exposure in an India cross-border engagement.
Our team works on offshore recruitment practice reviews both the payment structure and the contract language before any contractor engagement goes live. This dual-check has caught PE risk triggers in roughly one in three contracts that clients bring to us pre-signed.
How AnjuSmriti Structures FEMA-Compliant Payments for Foreign Companies: Process and Proof
When a foreign client comes to us wanting to engage Indian contractors directly rather than through an EOR, our compliance intake covers five areas before we make a single introduction: entity type of the Indian professional, payment channel viability, contract language review, GST status, and purpose code verification with the client's bank.
Our typical timeline for structuring a compliant direct freelancer engagement runs 10 to 14 days. Two days for compliance intake, three days for contract drafting with an empanelled Indian CA firm, three days for the freelancer's GST registration if not already in place, and two to four days for the client's bank to confirm purpose code capability.
For clients who want to engage remote contract professionals from India across multiple roles simultaneously, we also run a payment dry-run before the first live wire to confirm the purpose code flows correctly end to end.
The engagement that nearly collapsed: In late 2023, a 40-person US legal-tech company approached us to place three senior data engineers as independent contractors. The client's finance team was based in Austin. They had already drafted a contractor agreement using a US-standard template that included an exclusivity clause and a fixed monthly retainer structure.
We flagged the PE risk immediately. The client's legal counsel initially pushed back, arguing that because the engineers were in India and the client had no Indian entity, there was no Indian tax exposure. We brought in an Indian tax advocate who outlined the CBDT Circular on PE determination. The client's counsel revised the contract within a week.
What almost went wrong: the client's bank, a mid-tier US regional bank, did not support RBI purpose codes in their SWIFT message fields. The first wire would have arrived in India with no purpose code, causing the receiving bank to hold the funds under the RBI's "purpose unknown" queue. We caught this during the dry-run payment test we always run before the first live remittance. The client switched to their international treasury account at JPMorgan, which supported full MT103 field population.
Outcome: Three engineers placed, all payments flowing correctly for 14 months, FIRCs being collected quarterly, and no PE risk exposure. The client's finance team now uses our FEMA compliance checklist as their internal SOP for all India contractor engagements.
Cost of Paying Indian Freelancers Abroad FEMA Rules: Direct vs EOR vs Non-Compliant
Many finance teams assume that paying Indian freelancers directly is the lowest-cost option. It often is, but the cost comparison needs to include the compliance infrastructure and not just the contractor rate. Understanding what it truly costs to pay Indian freelancers abroad under FEMA rules helps finance heads budget accurately from day one.
Here are realistic all-in numbers for three seniority levels of Indian IT contractors with compliant payment structures.
Role Level | Freelancer Rate (USD/month) | EOR Fee (if used) | Direct Compliance Cost (CA, GST, contract) | Total Monthly Cost |
Mid-level (3 to 5 years) | USD 2,200 to 2,800 | USD 300 to 450 | USD 80 to 120 (amortised) | USD 2,580 to 3,370 |
Senior (6 to 9 years) | USD 3,500 to 4,800 | USD 350 to 500 | USD 80 to 120 (amortised) | USD 3,930 to 5,420 |
Lead or Architect (10 or more years) | USD 5,500 to 7,500 | USD 450 to 600 | USD 80 to 120 (amortised) | USD 6,030 to 8,220 |
For comparison, equivalent roles in the US market via a staffing firm run USD 12,000 to 22,000 per month at senior and lead levels, inclusive of employer costs.
Direct freelancer engagement works best when your legal team has reviewed the contract for PE risk, your bank supports purpose code tagging, and the contractor is GST-registered. The compliance overhead runs approximately USD 80 to 120 per contractor per month when handled by an Indian CA on retainer.
EOR model: where we employ the contractor in India and you pay us, eliminates the FEMA documentation burden entirely from your side. The Employer of Record structure shifts all Indian payroll, PF, and compliance obligations to us. It costs more per head, but your finance team's liability surface drops to zero. For companies placing more than five contractors, the EOR model also enables global payroll consolidation through a single invoice. For companies expanding operations in India more broadly, we also help structure the full business expansion in a compliant and cost-effective way.
What clients typically reinvest the savings into: expanded team size, which is the most common use, tooling and infrastructure for the distributed team, and in several cases a dedicated India operations lead to manage the growing contractor base.
Conclusion
Over the next 12 to 18 months, we expect the RBI to tighten purpose code enforcement for inward remittances, particularly as India's gig economy international and the IT Department increases scrutiny of foreign income declarations in individual ITRs. The recent CBDT guidance on PE determination for remote workers signals that this space is getting more regulated, not less.
In live mandates right now, we are seeing more European and US companies proactively asking about how to pay Indian freelancers abroad under FEMA rules at the onboarding stage, rather than after a compliance issue surfaces. That shift is meaningful. When you pay Indian freelancers abroad, FEMA rules are not a back-office afterthought. They are the foundation of a sustainable engagement model.
If your finance or legal ops team is setting up or auditing an India contractor programme, we are happy to walk you through the payment architecture, contract review, and CA referral in a single intake call.
Interesting Reads:
FAQs
1. Does FEMA 1999 apply to payments via Deel or Remote.com?
Yes, FEMA applies to the transaction, not the platform used. If Deel or Remote acts as an EOR, compliance shifts to their Indian entity. If they are only intermediaries, the freelancer must handle FIRC, RBI purpose code, and GST export rules. Always confirm the platform’s exact role before onboarding. This directly affects compliance responsibility and documentation flow. Ignoring this can lead to delays in payment classification. It may also create issues during audits.
2. What is the correct RBI purpose code for IT freelancer payments?
Common purpose codes include P0802 for software services and P0801 for IT-related work. For AI, analytics, or consulting services, P0802 is typically appropriate. If the code is missing, banks may assign a default classification. This can impact export reporting and income categorisation. It’s best to confirm the code during onboarding. Freelancers should verify with their authorised dealer bank. Including this in contracts avoids confusion later.
3. When does hiring an Indian freelancer create PE risk?
Permanent Establishment risk arises when the engagement resembles employment. Red flags include exclusivity, fixed monthly payments, and direct control over work. Terms like “full-time” or “dedicated resource” increase scrutiny. This may result in Indian tax liability for the foreign company. Structuring contracts with output-based deliverables helps reduce risk. Multi-client clauses also strengthen compliance. Regular legal review of contracts is strongly recommended.
4. Does an Indian freelancer need to charge GST to foreign clients?
Export services are zero-rated under GST if conditions are satisfied. No GST is charged under LUT, or it is refunded if applied. However, GST registration becomes mandatory once turnover crosses the threshold. Without registration, compliant export invoices cannot be issued. This can disrupt FIRC and documentation chains. Proper invoicing ensures smooth foreign remittance processing. It also supports audit and tax filings.
5. What if payment is made to a PayPal wallet instead of a bank account?
PayPal operates as a payment aggregator, not an authorised dealer bank. Funds are not treated as export proceeds until settled into a bank account. Without this transfer, FIRC cannot be issued. This affects GST compliance and FEMA reporting. Delayed withdrawal may raise regulatory concerns. Freelancers should move funds to their bank quickly. Keeping records of each transfer is also important.
6. Does a foreign company need to deduct TDS?
In most cases, TDS does not apply if the company has no presence in India. Section 195 applies only to payments made from within India. However, if a Permanent Establishment exists, TDS obligations may arise. Involvement of an Indian entity can also trigger withholding requirements. This makes PE risk a critical factor in tax planning. Companies should assess structure carefully. Professional tax advice is advisable for complex cases.
7. What is Form 15CA and who handles it?
Form 15CA is filed by the Indian recipient or their representative. It is used to report foreign remittances under tax rules. The foreign company is not responsible for filing it. However, contractors may request company details to complete the form. Form 15CB may be required for higher-value transactions. Providing a standard information sheet simplifies this process. It ensures faster and accurate compliance.
8. Can a foreign company pay an Indian freelancer in INR?
Payments must be made in foreign currency to qualify as export of services. INR payments are treated as domestic transactions. This removes GST zero-rating and FIRC eligibility. It also affects tax benefits available on export income. If paid via an Indian entity, the structure changes entirely. The engagement becomes domestic in nature. In such cases, different compliance rules apply.
Comments