A contractor of record (CoR) is the party that holds the direct contractual relationship with an independent contractor on a client's behalf. The client gets the developer's work; the contractor of record holds everything on paper — the contractor agreement, the identity and tax documentation, the invoicing, and the payment relationship. The client never contracts the individual.
Not legal or tax advice. This guide is a layperson-readable overview of an engagement structure. Classification and cross-border questions have real legal edges — consult a qualified attorney or CPA before relying on any of this for a particular engagement.
The definition, unpacked
When a company works with an independent contractor directly, it carries the whole administrative and contractual relationship itself: drafting the contractor agreement, verifying identity, collecting the right tax form, paying an individual (often across a border), and keeping the records straight. Multiply that by a few contractors in a few countries and it becomes a genuine operations function.
A contractor of record absorbs that function. The CoR signs the contractor agreement with the individual, collects and reviews the tax documentation, runs the payments, and keeps the records — while the client holds one commercial contract with the CoR and receives one clean monthly invoice per contractor. The term comes from the same family as "employer of record," and the one-word difference is the entire point.
Contractor of record vs. employer of record
| Contractor of record (CoR) | Employer of record (EOR) | |
|---|---|---|
| The worker is | An independent contractor | A full-time employee |
| Legal counterparty to the worker | The CoR, via a contractor agreement | The EOR, as the legal employer |
| Payroll, benefits, statutory compliance | None — the contractor invoices and files their own taxes under their country's contractor regime | Run by the EOR: local payroll, benefits, employment-law compliance |
| The client holds | One commercial contract with the CoR; one US-dollar invoice per developer | A service agreement with the EOR, plus employment-shaped costs |
| Fits when | You want senior, project-directed capacity month-to-month | You want the person on your org chart — benefits, equity, reviews — without opening a local entity |
Neither shape is "better." They solve different problems, and the honest question is which relationship you actually want with the person. If the answer is an employee in everything but the entity paperwork, an EOR is the right tool — our comparison with Near walks through exactly that trade. If the answer is senior contract capacity that integrates with my team, a contractor of record keeps the structure aligned with the reality.
Why the distinction matters for international developers
Engaging a developer in another country directly means becoming, in a small way, a cross-border contracting operation: the agreement, the tax form (a W-8BEN, in the common case), the international payment rail, and the record-keeping all land on you. The contractor-of-record structure moves that whole surface to a party built for it — and keeps the legal relationships clean. The developer is contracted to the CoR, not to you, so you don't accumulate contracting relationships with individuals across jurisdictions.
It also keeps the money simple: one US-dollar invoice per developer, from one US counterparty, whatever currency the developer is ultimately paid in.
How sourceBOLD implements it
sourceBOLD acts as the contractor of record on every engagement — it's built into the engagement model rather than sold as a separate service:
- You sign an MSA + SOW with sourceBOLD. The Master Services Agreement covers the commercial relationship; a Statement of Work per developer names the person, the start date, and the monthly Service Fee. That's the entirety of what you sign to start an engagement.
- sourceBOLD signs the Independent Contractor Agreement with the developer. The contract that makes the developer an independent contractor exists between sourceBOLD and the developer — you never contract the individual.
- Identity and tax documentation are collected and reviewed before anyone is paid. Government-ID verification and the applicable tax form (W-9 for US persons; W-8BEN or W-8BEN-E for foreign individuals and entities) are hard gates in the platform — a developer without an approved tax form on file cannot be paid, by system rule.
- Payments run through the platform, funding-gated. The developer is paid in their primary currency after your invoice settles — the funding gate is enforced in code: the platform refuses to dispatch a developer payment until the linked invoice has settled.
The result, from your side of the table: you carry no employment relationship and no cross-border employment exposure, and the day-to-day is just a senior developer in your standups and your repos.
When a contractor of record is the wrong fit
If you want the developer as a full-time employee — your benefits package, your equity pool, your performance-review ladder — a contractor of record isn't the right structure, and stretching it that far is how classification problems start. Use an employer of record, or hire directly. We'd rather say that plainly than win an engagement shaped wrong.
For the numbers underneath the model, What it costs publishes the per-developer pricing. For the placement process end to end, How it works walks from scoping to first standup. And for how the structure compares against specific providers, the head-to-head comparisons name names.