International Payroll From Brazil: Paying Contractors Abroad

A group with a Brazilian entity pays a contractor in Bogotá, a developer in Mexico City, and a translator in Lisbon, every month, on the same date. The controller consolidating the group's numbers does not just need the wire to go out; they need a contract on file, the right withholding applied, a receipt that survives an audit, and a number that reconciles cleanly into the group's monthly close. Closing the FX trade is one step, not the whole process.

At Soulbit Academy we treat international payroll as a process, not a single transfer. Soulbit is a stablecoin payment and treasury rail for companies, not an accounting firm or a tax advisory, and this guide shows where that rail ends and where the work that stays with the company begins. We already covered paying contractors in USDC from Brazil in pay international contractors in USDC from Brazil; here the subject is different, the full end-to-end process, of which the payment instrument is only one step out of seven.

Classify the contractor before building any process

The first step of international payroll is classifying every paid person correctly, because that decision determines the paperwork, the taxes, and the settlement rail for the six steps that follow. A company that treats someone as a contractor when the relationship functions as employment takes on a risk that surfaces years later, and it is usually the country where the person works, not Brazil, that enforces that law.

In Brazil, article 3 of the Consolidação das Leis do Trabalho defines an employee as any individual who performs non-occasional services under the employer's dependency, in exchange for salary. Hiring someone outside Brazil does not switch off that same logic: most countries in the region apply an equivalent principle, that the facts of the relationship, not the label on the contract, decide the classification.

Does hiring a contractor abroad turn the Brazilian entity into an employer in that country?

It depends on the facts and the law of the place where the person works, not on the intent of the company that hired them. With subordination, fixed hours, exclusivity, and company-provided tools, many jurisdictions apply their own labor law regardless of the services contract signed. The full breakdown of that test, with the indicators Latin American courts use, is in contractor vs. employee in LATAM: how to pay each one.

The contract and the documents behind the first payment

A payment to a contractor abroad needs documentation in place before it leaves Brazil, and missing any one piece delays the payment or complicates the report later. No bank, exchange house, or payment platform clears recurring international payroll without this minimum set.

The services contract comes first, and it needs to spell out scope, value in foreign currency, frequency, and governing jurisdiction. Next is the company's own KYB dossier, which clears the account with the chosen institution; the full checklist is in KYB checklist: the documents they will ask for to open the account. The contractor supplies the invoice or receipt that supports the payment before the Receita Federal and, where a double-taxation treaty applies, a tax residency declaration. Finally, the FX transaction or settlement route generates its own proof, which feeds that month's reconciliation.

Document	Who provides it	What it supports
Services contract	Company and contractor	Formalizes scope, value, currency, and frequency
Company KYB dossier	Company	Clears the account with the institution moving the payment
Invoice or receipt	Contractor	Supports the payment before the Receita Federal
Tax residency declaration	Contractor	Allows the treaty rate to apply, where one exists
Proof of the FX transaction or settlement route	Authorized institution	Records the settlement and feeds the month's reconciliation
Proof of IRRF withholding	Company	Supports the tax paid before the Receita Federal

A generic services contract rarely fits every country: a clause that works for paying a contractor in Mexico may not hold up for one in Portugal, where a different tax regime applies. A country-specific contract costs one legal review; a generic one that fails costs a reclassification.

Closing the FX trade: exchange contract, authorized institution, and IOF

Every payment to a contractor outside Brazil goes through an FX contract signed with an institution authorized by the Central Bank, never directly with the counterparty abroad. Lei 14.286 of 2021, Brazil's foreign exchange framework law, kept that requirement while modernizing the rest of the market: banks, exchange brokers, and, within limits, payment institutions are the only parties authorized to close that operation.

Can a company pay a contractor outside Brazil without going through an authorized institution?

No, under no circumstance, whether settlement happens in converted reais or in stablecoin. The full mechanics of the exchange contract and the spread are in foreign exchange for companies in Brazil. On cost, the operation carries the federal IOF tax, currently 3.5% for most service payments abroad, broken down by purpose in Brazil IOF tax on foreign exchange for companies.

The taxes that appear on a payment abroad for services

A payment to a non-resident contractor for services can involve up to four federal taxes, one municipal tax, and the IOF. None depends on the settlement rail chosen: they appear on a traditional bank transfer and on a payment settled in stablecoin alike.

The first is IRRF, governed by Instrução Normativa RFB No. 1,455 of 2014, which consolidates the withholding income tax rules on income remitted to legal entities domiciled abroad. Historically the rule applies a general rate and a heavier one for beneficiaries in a low-tax or favorable-regime jurisdiction; the exact figure depends on the nature of the service and on any applicable double-taxation treaty, and a wrong reading here creates a retroactive liability.

Next come PIS/COFINS-Importação, on the service import itself, and, when the contract transfers technology or technical assistance, CIDE-Remessas. At the municipal level, ISS can apply to the service received, at a rate each municipality sets within the bounds of federal complementary law. No rate is pinned down here on purpose: each depends on the exact nature of the service, and a generic number is worth less than your accountant's confirmation for your specific contract.

Does paying in USDC or USDT change any of these taxes?

No. Switching the settlement rail changes the speed and traceability of the payment, not the nature of the operation before the Receita Federal. A service import remains a service import, and the taxes levied on it are the same, whatever instrument moves the money.

BCB Resolution 561 changes one route, not the whole payroll process

BCB Resolution 561 closes, starting October 1, 2026, one specific route inside the eFX service, not international payroll as a whole. The rule, published April 30, 2026, amends Resolution 277 and bars a Brazilian eFX provider from settling with its counterparty abroad using virtual assets.

The change speaks to the eFX provider, not directly to the company that hires that service. If a group's international payroll depends on an eFX provider that settles the offshore leg in stablecoin, ask that provider, before October, which route replaces that settlement. If the company buys and transfers the stablecoin directly, without an eFX provider, the operation stays under the broader framework of Resolutions 519, 520, and 521, not 561. The full breakdown is in BCB Resolution 561: what changes in international payments.

The monthly calendar: closing, receipts, and reconciliation for group reporting

The monthly cycle of international payroll has seven fixed milestones, from the period cutoff to the report that feeds group compliance. Each milestone has an owner and a timing relative to the committed pay date. Treating these milestones as a calendar, not as loose tasks, is what separates predictable international payroll from one that slips every month, and it is what a controller needs to consolidate the group's numbers on time.

Each milestone depends on the one before it: the calculation only starts after the cutoff, the FX trade only closes after the calculation, and reconciliation only happens after payment and after receipts are filed. Treating this sequence as a fixed calendar, with a buffer before the pay date, avoids the most common failure: closing the FX trade too late and racing the settlement window of the chosen rail.

Milestone in the monthly cycle	Owner	Timing relative to payment
Period cutoff and batch definition	Finance or HR	Several days before the pay date
Calculating the amount per contractor	Finance, based on contract and invoice	After cutoff, before closing the FX trade
Closing the FX transaction or settlement route	Finance and authorized institution	With buffer, per the rail's settlement window
Payment to contractors	Finance	On the date committed to each contractor
Issuing and filing receipts	Finance	Same day as payment
Accounting reconciliation	Accounting	Days following payment
Report to relevant authorities and group compliance	Accounting or compliance	Per each obligation's own calendar

Why does reconciling international payroll take longer than reconciling a single supplier?

Because the number of receipts grows with the number of contractors, not with the total amount paid. Reconciling one large payment to a single supplier takes minutes; reconciling fifteen small payments, each with its own exchange rate, its own receipt, and its own settlement date, takes hours, and that administrative time is part of the real cost of international payroll.

What Soulbit V1 delivers in this process, and what it does not

Soulbit V1 delivers the payment step of the international payroll process, with balances in stablecoins, USDC and USDT, and in fiat limited to dollar, euro, and pound. After KYB verification, the platform runs recurring and batch payroll, the Soulbit Salaries module, converts between stablecoin and fiat at an on-request quote (eOTC), keeps institutional custody and AML/KYT monitoring, and issues an on-chain identifier per payment, useful in the reconciliation described above.

What the V1 does not do is equally central to this article. Soulbit does not classify the relationship between the company and the contractor, does not calculate the payroll amount or the applicable taxes, and does not withhold or file anything with Brazilian authorities: those tasks stay with the company and its accountant. One point specific to Brazil deserves to be stated plainly: Soulbit has no local banking rail in the country. The V1's only local banking rail is Colombia; in Brazil, the final conversion to reais still depends on an authorized institution, outside the platform. The V1 also offers no cards, no yield on balances, no proprietary token, and no native mobile app.

In practice, Soulbit covers one of the seven steps, moving the money after the company has already classified the contractor, closed the contract, calculated the amount, and decided how it will close the FX trade. The other six steps stay with the company, its accountant, and the financial institution that closes the exchange operation.