How to Pay Contractors and Employees in India from a US Company
Paying people in India from a US company sounds like a solved problem until the first payout stalls in a correspondent bank, the contractor asks why the amount they received is lower than the invoice, or the finance team realizes the monthly wire fee is quietly the second biggest line item after the actual salary. The mechanics of moving USD into an Indian bank account or UPI ID are well understood, but the choices around compliance, structure, and channel make the difference between a payroll that runs itself and one that consumes a few hours every cycle.
This guide covers what US companies actually need to know when paying India-based contractors and employees: the practical difference between the two categories, the compliance basics that show up on both sides of the corridor, how batch and recurring payouts work in practice, why speed and cost matter more than they look on paper, and how to pick a payout method that keeps up as the India headcount grows.
Contractor Versus Employee: The Structural Difference That Drives Everything Else
The first decision a US company makes when hiring in India is not which payment app to use. It is whether the person is a contractor or an employee, because the payout structure, the compliance posture, and the tax treatment on both sides follow from that classification.
An India-based contractor invoices the US company for services rendered, typically in USD or INR depending on how the engagement is priced. The company pays the invoice, the contractor receives the funds in their Indian bank account or UPI-linked account, and the contractor is responsible for their own income tax filings in India under the Indian Income Tax Act. From the US side, the contractor is a foreign vendor and the company issues a 1099 only if it is required under US rules (typically not, for services performed entirely outside the US by a non-US person). Withholding is generally not required by the US company, though the specific facts matter and companies should confirm with a tax advisor.
An India-based employee is a materially different setup. If the US company hires the person directly as a US-payroll employee working remotely from India, the company has to think about India tax residency, permanent establishment risk, and social security obligations, all of which usually push companies toward one of two structures instead: hiring through a local India entity the US company owns, or hiring through an Employer of Record (EOR) that becomes the legal employer in India while the person works day-to-day for the US company. Both structures shift the payroll rails to INR paid from an Indian entity, which is a domestic Indian payment rather than a cross-border transfer.
For most US companies with a small India team, the practical reality is that contractors are paid via cross-border USD to INR transfer, and full employees are paid via a local India entity or EOR. The payment mechanics discussed below apply to both, but the compliance layer is different.
Compliance Basics: TDS, FEMA, and Proper Invoices
Compliance is where cross-border payroll gets a reputation for being harder than it needs to be. In practice, the requirements are a short list.
On the US side, the company treats the payment as a foreign vendor invoice or intracompany transfer, retains the invoice or engagement contract as documentation, and follows its usual US tax and audit rules. There is no US regulator that oversees the specific corridor; the compliance is at the entity level.
On the India side, three things matter. First, the payment has to be received into a proper account: a regular resident savings or current account for a contractor, or the salary account of the Indian entity for a payroll employee. Second, TDS (Tax Deducted at Source) may apply on the Indian side if the payer is an Indian entity making payments to another Indian party, but for a direct cross-border payment from a US company to an Indian contractor, TDS is not withheld by the US payer. The contractor pays income tax on the received amount when filing their annual return. Third, FEMA (Foreign Exchange Management Act) governs how the inbound foreign currency is received; the receiving bank handles the FEMA reporting on behalf of the recipient as part of the standard inbound remittance workflow, and no separate filing is required from the contractor for typical amounts.
For proper documentation on both sides, three items are usually sufficient: a written engagement contract or scope of work, an invoice per payment cycle referencing the engagement, and the transfer confirmation from whichever payment channel is used. That trio is what a US audit or an Indian tax authority is likely to ask for, and keeping it filed by cycle is faster than reconstructing after the fact.
Batch and Recurring Payouts
A one-off payment to a single contractor is straightforward on any channel. The volume problem shows up when a US company is paying ten, fifty, or a few hundred people in India every month.
Batch payouts let the finance team upload a single file (usually a CSV with recipient details and amounts) and initiate the entire cycle in one action rather than clicking through each transfer individually. Every serious cross-border payment platform supports this on the sending side. The differences between platforms show up in how the recipient side is handled: whether each payment lands correctly matched to the right person on the first try, how failed payments (wrong account number, closed UPI ID) are handled, and how the reconciliation report gets fed back to the sender.
Recurring payouts, meaning the same amount to the same recipient every month, are simpler still: most platforms let the sender save recipient details and repeat past transfers with two taps rather than re-entering everything. The reconciliation report at month-end should show which payments cleared, which failed, and which are pending, so the finance team can close the cycle without chasing individual confirmations.
The practical upgrade for a US company managing India payroll from a few people to a few dozen is not switching tools; it is turning on the batch feature that was already available on the current tool.
Speed and Cost: Where the Numbers Actually Land
The visible cost of an India payout has two components: the transfer fee on the sending side and the FX markup baked into the exchange rate. The transfer fee is usually the smaller number, but it is the one that appears on the invoice line and gets the attention. The FX markup is the larger number, hidden inside the exchange rate the platform quotes.
A US bank wire to India typically charges USD 25 to USD 50 per outbound wire plus a 2 to 4 percent FX markup above the mid-market rate. On a USD 5,000 monthly payout, the all-in cost lands in the USD 100 to USD 250 range, most of which sits in the FX spread. Settlement takes 1 to 3 business days.
A general-purpose remittance app or business payments platform typically charges a lower flat or percentage fee and a tighter FX markup. Depending on the platform, the all-in cost on the same USD 5,000 payout lands anywhere from USD 15 to USD 80. Settlement can be same-day or next-day.
Sliq Pay is one of the platforms in this second category, built specifically for US-to-India flows. The pricing published on the marketing site is a 0 percent FX markup on mid-market (Google/Reuters) rates and a 0.3 to 0.5 percent transfer fee, with settlement instant on the India-side rails within the per-rail caps (up to 200,000 INR instantly via UPI, up to 500,000 INR instantly via IMPS, and settlement within hours for larger amounts). For a US company running monthly cycles, both the total cost and the speed matter: the transfer that lands the same day is one that finance does not have to reconcile the following week.
The right question is not “what is the cheapest platform” in the abstract. It is “what is the all-in cost on my typical payout size, and how fast does it settle end-to-end”. Both answers should come from a test payout, not from a marketing page.
Comparison of Common Payout Channels
| Channel | Typical Fee | FX Markup | Settlement | Batch Support | Fit |
|---|---|---|---|---|---|
| US Bank Wire | USD 25 to 50 per wire | 2 to 4 percent | 1 to 3 business days | Limited | Occasional large payouts |
| General remittance app (personal accounts) | Low to medium | 0.4 to 1.5 percent | Minutes to 1 day | Rarely, or manual | Not a fit for business volume |
| Cross-border business payments platform | Low percentage or flat | 0 to 1.5 percent | Same-day to next-day | Yes | Most US companies with India headcount |
| Local India entity payroll (INR) | Domestic rates | Not applicable | Same-day domestic | Yes | Full-time employees on India books |
The pattern that repeats across most US companies is a hybrid: contractors paid via a cross-border business payments platform on a monthly cycle, and any full-time employees paid domestically in INR from a local India entity or EOR.
Reality Check: Three Things That Look Fine Until They Are Not
Three quiet problems account for most of the payroll friction US companies hit as their India team grows.
The first is treating an ongoing engagement with a single contractor as a series of one-off invoices without a written contract. This is fine until something goes wrong (a payment gets stuck, the scope becomes ambiguous, the relationship ends messily) and there is no document to point at. A short engagement contract signed once, referenced by each subsequent invoice, saves the same conversation from being had three months later.
The second is using a US bank wire as the default because it is the tool the CFO already has open. For amounts above USD 50,000 or for a first-time payment where compliance may need attention, the bank has value. For a USD 3,000 monthly payout to a contractor, the bank wire quietly costs USD 100 more than it needs to and takes two extra days.
The third is picking a payment tool that works fine at ten contractors and starts creaking at fifty. The migration cost of switching platforms mid-scale (updating contractor bank details, retraining finance, reconciling two months of reports across two tools) is significant, so choosing a tool that has clear batch payout, an API or CSV workflow, and a public roadmap of enterprise features saves a re-platform later.
Travel Tip: For Founders Visiting India to Meet Their Team
The team-payment side of the corridor is the formal payroll flow. The other side, which usually surprises US founders on their first India trip, is that day-to-day spending in India runs on UPI QR codes rather than on cards or cash. Most cafes, auto-rickshaws, hotels, and even street vendors accept UPI and often prefer it over cash. US-issued credit and debit cards often get declined at smaller merchants, and ATM withdrawals carry foreign transaction and ATM fees on top of the FX markup.
Sliq Pay supports UPI-based QR payments in India from a US-linked bank account, without needing an Indian bank account or local SIM. For a founder or team member visiting India for a week of offsites, that means the meal, the ride, and the coffee are paid the way the merchant expects to be paid, at a mid-market FX rate with no card decline. The tool that runs monthly payroll is the same tool that pays for the trip. That is a small quality-of-life upgrade that adds up across a week of meetings.
Frequently Asked Questions
Do I need to withhold US tax when paying an India-based contractor?
Generally, a US company paying a non-US person for services performed entirely outside the US does not withhold US federal income tax and does not issue a 1099. The specific facts of the engagement matter, and companies should confirm with a US tax advisor. The contractor is responsible for their own Indian income tax filings on the received amount.
Does the contractor pay tax on the money in India?
Yes. An India-resident contractor treats the received payment as business or professional income under the Indian Income Tax Act and pays income tax when filing their annual return. TDS is not withheld by the US payer on cross-border payments; the contractor manages their tax obligations directly.
Can I hire someone in India as a full US-payroll employee?
Technically yes, but it usually creates India tax residency and permanent establishment questions that most companies avoid by either setting up a local India entity or hiring through an Employer of Record. Both structures shift the payroll to a domestic INR payment from an Indian legal entity, which is a different flow from the cross-border contractor payment.
What is the fastest way to pay a contractor in India?
Same-day or instant, using a platform that settles on India’s UPI or IMPS rails. Up to 200,000 INR per transfer settles instantly via UPI and up to 500,000 INR settles instantly via IMPS. Amounts above the instant caps settle within hours through the standard rails.
How much does it actually cost to pay someone in India from the US?
On a typical USD 3,000 to USD 10,000 payout, a US bank wire runs USD 100 to USD 400 all-in, most of which is FX markup. A cross-border business payments platform runs USD 10 to USD 100 all-in on the same payout. Ask any platform for the all-in cost on a specific payout, not just the fee, before switching your cycle over.
Can I batch pay multiple contractors in one action?
Yes, on any platform built for business payouts. Upload a CSV with recipient details and amounts, initiate the batch once, and reconcile through the returned report. The batch workflow is table stakes for a company running a monthly cycle for more than a few people.
What documentation should I keep for each payout?
A written engagement contract or scope of work signed once, an invoice per payment cycle referencing the engagement, and the transfer confirmation from the payment channel. That set is usually sufficient for US audit and Indian tax questions.
How do I handle payments if my India headcount grows to fifty or more people?
The workflow does not change materially: batch payouts on a monthly cycle, reconciliation through the platform’s report, and separate handling for any full-time employees hired through a local India entity. The tool choice matters more at scale because migration costs are meaningful, so pick a platform with clear enterprise features rather than growing into a consumer app.
A Final Word
Paying people in India from a US company is a two-part problem: getting the classification right (contractor versus employee, direct versus EOR) and picking a payout channel that keeps up with the volume. The compliance is short but non-negotiable; the mechanics are simple once the channel is chosen; the cost is mostly in the FX spread rather than the fee.
For most US companies with a growing India team, the practical setup is a cross-border business payments platform for contractors and a local Indian payroll rail for employees, reviewed once a year as the headcount changes. Getting the channel choice right on the way in is a lot cheaper than switching after the fact.
Disclaimer
The information provided on this blog is for general informational purposes only and does not constitute legal, financial, tax, or professional advice. Product features, pricing, eligibility, and availability may vary by country, user type, regulatory requirements, and are subject to change.
Please refer to Sliq Pay’s Terms of Use and official product pages for the most accurate and up-to-date information. Sliq Pay makes no representations or warranties regarding the completeness, accuracy, or reliability of the content.
