Hiring and managing global contractors

Hiring a contractor in another country is the fastest way for a startup to add talent it cannot find or afford at home. The mechanics are simpler than employing someone abroad, but the discipline has to be real: the right classification, the right documents, a clean payment trail, and one directory that holds these people alongside your team. Get those four things right and cross-border work stops being a source of anxiety.

This guide covers when a contractor is the right structure, when it is not, how to onboard one properly, which documents to collect, how payment tends to work, and why the whole arrangement belongs in the same system as your employees.

Contractor, employee, or EOR

Three structures cover almost every case, and choosing wrongly is expensive in different ways.

A contractor is an independent business you engage for defined work. They control how they deliver, they invoice you, and they handle their own taxes in their own country. This is the lightest structure and the right default when the relationship genuinely fits it.

An employee works under your direction, on ongoing work, integrated into your team. Employment brings obligations that vary by country: payroll withholding, statutory contributions, leave, notice periods, and more. To employ someone in a country you usually need a legal entity there, which is a serious commitment.

An employer of record sits between the two. An EOR is a company that already has an entity in the target country and legally employs the person for you, running local payroll and compliance while the person works for you in practice. It gives you a real employee without opening your own entity, at a per-person cost that reflects the service.

The rule of thumb: engage a contractor when the work and the relationship are genuinely independent, use an EOR when you need a proper employee in a country where you have no entity, and open your own entity only when headcount in a country justifies it. The one thing you cannot do safely is call someone a contractor to avoid the cost of employing them when the relationship is really employment. That is misclassification, and the contractor versus employee guide covers why regulators care and how to keep your records clean.

Where the line falls also depends on the country, which is why the same arrangement can be comfortable in one place and precarious in another. In the Philippines, for instance, the statutory package that attaches to an employee is substantial enough that the classification is worth settling before the first invoice rather than after the first dispute.

Onboarding a contractor properly

The temptation with contractors is to skip the process, sign a one-line agreement, and start work. That is how you end up, a year later, without a signed scope, without tax forms, and without a clear record of what was agreed. Onboard a contractor with the same care you give an employee, minus the parts that do not apply.

A workable checklist:

• A written agreement that states the scope, the fee and how it is calculated, the payment schedule, who owns the work product, confidentiality, and how either side ends the arrangement.
• Identity and business details, so you know who you are paying and can show it later.
• The correct tax form for their situation, collected before the first payment.
• Bank or payment details captured once, in a place you can find them.
• Access to only the systems the work requires, and a record of that access so you can revoke it cleanly at the end.

The point of onboarding is not bureaucracy. It is that every fact you fail to capture at the start becomes a question you have to chase later, usually at the worst time.

The tax forms, and what they are for

Contractors handle their own taxes, but you still have a reporting and, in some cases, withholding role, and that starts with collecting the right form.

For US tax purposes, the common forms are the W-9, which a US person or entity provides, and the W-8 series, which non-US persons and entities provide to establish foreign status and any treaty position. Other countries have their own equivalents that serve the same purpose: identifying the payee and setting how their income is treated. The details depend on both countries, on any tax treaty between them, and on the nature of the work, so treat the specifics as something to confirm with a tax professional rather than something to guess.

What matters operationally is simpler. Collect the form before you pay, store it on the contractor’s record, and keep it current. A missing or stale form is the kind of gap that surfaces during due diligence or an audit, when it is hardest to fix.

Capstan’s contractor module collects these forms as part of onboarding and files them on the contractor’s record. It does not submit them to any authority on your behalf, and it gives no advice on which form applies. It holds the documents; the filing and the judgement remain yours and your advisers’.

How country rules should reach an invoice

This is worth a section of its own, because it is where most tools quietly overreach.

Withholding and tax lines on a contractor invoice depend on the jurisdiction, and jurisdictions change. There are two ways to build that. You can write the rules into the code, which means a rate change is a software release and every country you add is a branch somebody has to maintain. Or you can treat jurisdiction rules as versioned content that the software reads, which means a rate change is a new version of the content and the code never learns the name of a single country.

Capstan takes the second route, and the design is worth borrowing whoever you buy from. Jurisdiction content ships as a country pack: withholding rule templates, tax line templates and the documents a jurisdiction expects, published as data with a version on it. You adopt a pack for a jurisdiction and choose whether to follow the newest published version automatically or pin a specific one. When an invoice is raised against an engagement in that jurisdiction, the pack generates suggested tax lines on the draft, and every generated line records which pack version produced it, so you can answer “which rules were we running in March” without reconstructing anything.

Two properties matter more than the machinery. The first is that the pack is a default and your accountant is the authority: the suggested lines are ordinary editable draft rows, and they are edited before the invoice is submitted, not after. Re-running the suggestions clears the pack’s own lines and regenerates them while leaving anything entered by hand untouched. The second is that adopting a pack is reversible. Withdrawing an adoption stops future suggestions for that jurisdiction and leaves the tax lines already on existing invoices exactly where they are.

The honest limit, stated because it belongs in the same paragraph as the capability: a published pack is content, and content has to be reviewed by someone qualified in that jurisdiction before it is trusted in a live filing. Capstan ships the mechanism and treats jurisdiction review as a gate on the content, not as a box the software ticks for you. Today the only pack authored is for India, and it covers contractor invoice withholding and tax lines rather than employee payroll. Everywhere else, the module holds the engagement, the invoices and the documents, and you and your accountant supply the tax treatment.

Two calculators help you compare the options with your own numbers rather than a rule of thumb. The contractor cost calculator takes a rate, a basis, the currency conversion margin and any fixed extras and gives you an all-in monthly and annual figure. The employee cost estimator does the same job for a hire, with blank employer-cost lines you name and value yourself, because those rates are local and we will not guess them for you.

Paying contractors across borders

Cross-border payment has more moving parts than a domestic bank transfer: currency conversion, fees on both ends, and a paper trail that has to match your books.

A few habits keep it clean. Agree the currency in the contract, so nobody argues about exchange rates after the fact. Decide who bears transfer fees and write it down. Keep every payment tied to an invoice and a reference, so each payout can be traced to specific work. And keep the record of what you paid separate from the mechanism you paid with, because payment rails change and your record should not depend on any one of them.

On this point, be precise about what a system of record does and does not do. Capstan records contractor payouts by reference only. It does not hold a payment rail and never moves money. You pay through your bank or a payment provider, then record the payout against the contractor so your record and your books agree. The money moves through your chosen channel; Capstan keeps the record that ties it to the person and the work.

The invoice itself has a stated lifecycle rather than a status field somebody edits: draft, submitted, then either rejected with a mandatory reason or approved for payment. A contractor can submit their own invoice through their portal, or an administrator can record one on their behalf, and the invoice remembers which of the two happened. The payable amount is derived from the line subtotal plus added tax lines minus withheld ones every time it is read, rather than stored as a number that can drift away from the lines that make it up.

Keep everyone in one system

The recurring mistake is structural. Employees go in the HR tool, contractors go in a spreadsheet, and the two never quite match. Someone leaves and their access lingers. A contractor converts to an employee and their history starts over. A report of headcount depends on which document you happened to open.

One system that holds employees and contractors removes all of this. Each person has a record, the right documents sit on it, onboarding and offboarding run the same way, and a single view tells you who is working, in what capacity, from where. That is the case for keeping contractors in the same HRIS as your team rather than in a parallel system you maintain by hand.

Two boundaries are worth knowing before you assume it is all one thing. A contractor holds a genuinely separate kind of identity from an employee: tenant-linked, bound to one contractor record, and structurally unable to become an employment or hold a member role. That is enforced in the database rather than in application code, which is why a contractor never quietly accumulates employee-shaped access, and why a contractor never counts toward your employee headcount or your seat count. And the module itself is a paid one. Contractors in your records are part of the free core; the portal, the invoicing, the country packs and the payout register arrive with Contractor Management, and like every module it needs a paid plan under it before it can be switched on.

The real cost of hiring in a second country is rarely in the contract. It is in the things that quietly go plural once there are two: the holiday calendar, the leave policy, the handbook, the currency the record is kept in, and the assumption that a working day means the same thing everywhere.

Where to go next

If the person you have in mind is in India and the relationship really looks like employment rather than a contract for services, hiring employees in India sets out what that commits you to, from the contract and notice terms to the identifiers you collect on day one.

If you are weighing whether a specific role should be a contractor or an employee, read the contractor versus employee guide next, because the classification is a legal judgement and getting it wrong is costly. If you are hiring in India specifically and want to understand how statutory payroll fits together for employees there, the orientation to statutory payroll in India sets out the components without pretending the numbers stay still.

You can also look at the product directly. The core HRIS is free up to twenty active employees and holds contractor records alongside your team. The contractor module adds the portal, the invoice lifecycle, the tax-form collection, the country packs and the payout register on top, and it needs a paid plan under it, which is stated on the pricing page rather than discovered at the enable button.