Consider a São Paulo-based B2B SaaS company — call it a vertical software operator in the agro-industrial sector, twelve full-time equivalent US engineers on service contracts, monthly combined invoices totaling around R$380,000 at mid-2024 BRL/USD rates. The company's two-person finance team runs the payroll cycle manually: approve invoices in the last week of the month, instruct the bank to convert BRL to USD and wire to each contractor's US account, reconcile whatever arrives in the contractors' accounts against what was sent.
On a good month, the process takes three days and about four hours of finance team attention. On a bad month — when one contractor's banking details are stale, or a SWIFT wire gets held at a New York correspondent bank, or the BRL rate moves 4% between approval and execution — it takes two weeks and a dozen email threads. This is not an exceptional scenario. It's the baseline for a growing Brazilian tech company that hasn't built dedicated infrastructure for US contractor payroll.
What follows is a complete walkthrough of the monthly payroll cycle for Brazilian companies paying US-based contractors: the steps, the decision points, the compliance touchpoints, and where the structural costs accumulate.
The Monthly Cycle: Before the First BRL Moves
The payroll cycle begins with the folha de pagamento (payroll register) — though for US contractors under service agreements rather than CLT employment contracts, the term is a slight misnomer. There is no folha in the CLT sense for independent contractors; you have a services payable register or invoice approval workflow. But the operational function is the same: by a defined date each month (typically the last business day or the 5th of the following month for accrual-basis companies), all contractor invoices need to be approved, amounts confirmed, and the payment instruction ready to execute.
The pre-execution checklist should include:
- Confirmed USD invoice amounts per contractor
- Current W-9 or W-8BEN on file for each contractor
- Verified US bank details — ABA routing, account number, SWIFT BIC if wire
- Calculation of total BRL equivalent at the expected FX rate, plus a buffer for rate movement
- Confirmation that the BRL balance in the operating account covers the payroll outflow plus the IOF (0.38% of the BRL conversion amount)
The last point catches companies off guard more often than expected. IOF is assessed on the BRL notional at the time of câmbio, not on the USD output. If you're converting R$380,000 to USD, the IOF is R$1,444 — a separate deduction from your BRL balance, not embedded in the USD amount received. Budget for it explicitly or your câmbio instruction will be short.
IOF Planning: The Structural Decision That Compounds Monthly
For our São Paulo operator running R$380,000 in monthly payroll FX, the IOF cost difference between a single-leg structure and a traditional two-leg structure is the difference between paying R$1,444 and paying R$2,888 — every month. Annualized, that's R$17,328 vs R$34,656 in pure IOF. At R$380,000/month payroll, that's not a rounding error; it's roughly equivalent to the cost of one month of a junior contractor's services, lost to tax structuring inefficiency each year.
The single-leg structure requires using a corridor operator whose infrastructure is designed to execute the entire BRL receipt → FX conversion → USD delivery as one BACEN câmbio event. Not every bank or FX operator supports this. Traditional Brazilian banks running standard SWIFT wires often generate two câmbio filings: one for the BRL-to-USD conversion, and one for the outbound international transfer classified separately. If your bank can't show you a single BACEN câmbio filing number covering the end-to-end transaction, you're likely on a two-leg structure.
FX Execution: Timing the Conversion
Once the BRL Pix instruction is ready and the IOF has been accounted for, the FX execution itself is the rate-sensitive step. The Banco Central's PTAX reference rate — published as a closing rate around 12:30-13:00 BRT on business days — is the benchmark most operators use for spread quoting. Submitting your conversion instruction before the morning PTAX inquiry (typically by 09:30 BRT) generally results in the most predictable rate, as afternoon trading sessions can move significantly on macro news.
For a company running payroll on a fixed monthly cycle, the discipline is simple: approve invoices on the 28th or 29th, submit the BRL Pix and FX instruction before 10:00 BRT on the 1st, receive the locked rate confirmation, and the USD delivery follows within the same business day or the next morning depending on corridor design. This is not exotic treasury management — it's basic cycle discipline that most growing companies implement once they've experienced one month of avoidable late payment.
The Cross-Border Send: What the US Contractors Actually See
From the US contractor's perspective, the payment arrives as either an ACH credit or an incoming wire to their US bank account. ACH credits typically show up with a generic descriptor and no clear originator name — this is a frequent source of confusion when contractors try to reconcile their accounts. A wire typically shows the originating party's name in the reference field, but SWIFT reference fields are limited in length and often get truncated.
The practical fix is simple: include the invoice number in the payment reference field, and tell your contractors in advance what the originator name will appear as in their bank statement. For companies using a corridor operator, the name on the wire may be the operator's legal entity, not your company's name. One email per contractor the first time they receive payment, explaining what name they'll see, eliminates 80% of "I haven't received my payment" queries.
If you're paying 12 contractors with different US banks, some payments will arrive faster than others. ACH credits to accounts at large US retail banks typically clear within one business day of the operator's outbound ACH submission. Wires to the same banks settle same-day if received before the bank's wire credit cutoff (typically 17:00-18:00 ET for most US banks). Payments to smaller regional banks or credit unions may take an extra business day. Build this variability into your communication to contractors rather than promising a specific arrival date.
Receita Federal and BACEN Reporting: The Compliance Trail
Every câmbio operation executed by a Brazilian authorized institution is reported to BACEN in real time through the SISBACEN system. Your company's CNPJ is associated with each operation, and the nature code (natureza) classifies the purpose of the remittance. For contractor service payments, the appropriate natureza typically falls under the services category in BACEN's câmbio classification table — but the specific code used by your operator matters for Receita Federal audit consistency.
Under the RFB's DIMOF (Declaração de Informações sobre Movimentação Financeira) framework, financial institutions report BRL cash movements above defined thresholds. The câmbio operations themselves are reported separately via the SISBACEN channel, but the combined reporting means the Receita Federal has a complete picture of your company's BRL outflows classified as international service remittances.
We're not saying this creates a compliance burden for companies paying contractors legitimately — it doesn't. The reporting is the operator's obligation, not the company's direct filing. The practical implication is that the nature code used on your câmbio filings should accurately reflect the services being procured. If your contractors are providing software development services, the remittance shouldn't be classified under a different natureza to obtain a marginally different treatment. The audit trail is complete and permanent.
What the Finance Team's Time Actually Costs
Returning to the São Paulo operator with 12 US contractors: on a well-structured corridor, the monthly payroll cycle for the finance team should require approximately 90 minutes of active work — invoice approval, BRL Pix submission, rate confirmation review, and a reconciliation check on T+1 to confirm USD arrivals. With API-level integration between the payroll operator and the company's accounting system, that shrinks further.
The version of this cycle that takes 10+ hours is characterized by: manual banking detail maintenance, no IOF pre-calculation, spot FX executed late in the day, SWIFT MT103 with no GPI tracking, and post-payment reconciliation done by email with contractors. Every one of those inefficiencies has a structural fix. None of them require exotic technology or large capital investment — they require picking a corridor infrastructure that treats payroll FX as an operational system rather than a series of one-off bank transactions.
The companies that get this right early — before they're at R$500,000+ in monthly payroll — build the discipline when the volume is manageable and carry it forward as headcount grows. The companies that don't are still running the same manual cycle at twice the volume, paying twice the IOF they should, and wondering why their US engineers keep asking whether their payments are coming on time.