The Mexico-United States corridor: payroll, suppliers and collections
The corridor is not one flow: it is three, and each breaks in a different place.
A Mexican company decides to "fix payments with the United States". It signs up for a tool, connects it, and three months later the project is half done: collections improved, supplier payments are unchanged and the payroll for the team in Texas was never touched. The diagnosis was not wrong. It was incomplete.
At Soulbit Academy we argue the mistake is treating the corridor as a single problem. It is three distinct flows, with distinct frictions and fixes that do not carry across. This article separates them and explains what changes in each. Soulbit is a stablecoin payments and treasury rail for businesses, not a bank, and you will see where its scope ends in each flow.
One corridor, three flows
When a Mexican company operates with the United States, money crosses the border in three logically distinct directions.
The first is collections: US clients paying dollar invoices for goods or services. The second is supplier payments: inputs, components, software and services bought from the north or from third countries and paid in dollars. The third is payroll and fees: people working for the company from another country, or from Mexico for a US parent.
All three are measured in dollars and all three pass through the international banking system, which is why they get conflated. But they break in different places. Collections stall on the client's vendor file and the banking timeline. Supplier payments stall on counterparty verification and the irreversibility of the transfer. Payroll stalls before any money moves, on the employment classification of each person.
What do they have in common, then?
The cost and opacity of the rail. The BIS cross-border payments programme exists because the G20 considers these payments slow, expensive and opaque, and the World Bank's Remittance Prices Worldwide series puts the average cost of sending money across borders at 6.36% of the amount, close to 15% through a bank channel. Those are remittance figures rather than B2B, but they describe the same plumbing all three flows travel through.
Flow 1: collecting from US clients
This is the flow with the biggest cash impact and the one most companies attack first, rightly.
The friction has two layers. The first is documentary: the client's accounts payable team opens a foreign vendor file and releases nothing until it is complete, typically with Form W-8BEN-E and the contractual support. The second is timing: the international transfer takes days and arrives with deductions nobody itemised.
Collecting in USDC attacks the second layer, not the first. The file still has to be assembled. What changes is that, once approved, every invoice travels with its payment link and settles in minutes with a verifiable identifier. The full procedure is in the guide to collecting from US clients in USDC, and the context behind the growth of these invoices in nearshoring and payments.
The honest condition: the client must be able to pay in USDC. Many US companies already hold stablecoin balances, but not all, and in large corporates the decision does not sit with procurement.
Flow 2: paying overseas suppliers
Here the friction changes nature. It is not somebody else's file, it is your own risk.
An outgoing payment is irreversible the moment it executes. That makes counterparty verification the critical control: validating the supplier's corporate details, verifying the destination through a channel other than the one it arrived on, and running a test transfer before the first full payment. A change of details communicated by email is the most common fraud vector in this flow, and it has nothing to do with the technology of the rail.
The second control is organisational: dual approval. Whoever prepares the payment should not be the one approving it, even when the finance team is two people.
What the company gains is predictability. The supplier confirms receipt in minutes and ships sooner, which shortens the whole purchasing cycle. And the amount arrives whole, with no correspondent chain deducting along the way.
| Flow | Where it breaks | What fixes it | What the rail does not fix |
|---|---|---|---|
| Collections from US clients | The client's vendor file and banking timeline | Payment link per invoice, settlement in minutes | The W-8BEN-E and the vendor file |
| Supplier payments | Counterparty verification and irreversibility | Verified record, test transfer and dual control | Internal discipline, which the company supplies |
| Payroll and fees | Employment classification by country | Recurring cycle and batch payments | The legal classification of each person |
| All three | Cost and opacity of the banking circuit | On-chain identifier and direct settlement | Taxes, which remain national |
Flow 3: payroll and fees
This is the flow that derails most projects, because the problem shows up before any money moves.
Before paying, you have to know what each person is. Employees and contractors are paid differently, with different documents and obligations, and that classification follows the facts rather than the name on the contract. The country-by-country analysis is in contractor vs employee in LATAM. Skipping that step and changing only the rail leaves the underlying risk intact and makes it more visible, because now there is an on-chain trace of every payment.
Once classification is settled, execution simplifies: a recurring cycle with a stable list, run from a single balance, with an identifier per line that supports same-day reconciliation.
What if the Mexican company pays someone working from Mexico for a US client?
Here it is worth recalling a rule that surprises many people: the IRS determines the source of personal services income by where the services are performed, regardless of where the contract was signed or where payment comes from. The rail does not alter that, and documentation remains mandatory at both ends.
The Mexican framework bounds the market, not the operation
One detail explains why the company does not find these services at its bank. In Mexico, Banco de Mexico's Circular 4/2019 lets banks and financial technology institutions operate with virtual assets only in internal operations and with prior authorisation, and requires them to keep the risk away from clients. It is a restriction on what supervised institutions may offer the public, not a prohibition on a non-financial company using the asset in its own operation. The detail is in Mexico's Fintech Law and crypto assets in business.
The practical consequence is that the digital dollar circuit and the peso banking circuit coexist. They do not replace each other.
What V1 covers in this corridor and what it does not
| Need in the corridor | Covered by V1? | How it is resolved |
|---|---|---|
| Collect invoices from US clients | Yes | Payment links and QRs per invoice |
| Pay suppliers in digital dollars | Yes | Individual or batch transfers from one balance |
| Pay teams in several countries | Yes | Recurring payroll and batch payments |
| Convert to fiat | Yes, in USD, EUR and GBP | Conversion by quote on request |
| Deposit in Mexican pesos | No | The company handles it with its bank |
| Classify people, calculate payroll or invoice | No | Stays with the company and its advisers |
Where to start
The practical recommendation, once the flows are separated, is to attack them in order of return and dependencies.
Collections first, because they improve working capital and depend mostly on a commercial conversation with the client. Suppliers next, because they require standing up counterparty verification and dual control, processes that serve everything else too. And payroll last, because it needs the labour analysis per country and consumes the most time.
There is a sequencing benefit that is easy to miss. The controls built for the supplier flow, counterparty verification and dual approval, are exactly the controls the payroll flow will need later. Standing them up once, on the flow where the amounts are largest and the discipline is most obviously justified, means the third flow inherits a process rather than inventing one. Companies that start with payroll because it feels most urgent usually end up building those same controls anyway, only under time pressure and with more people watching.
Attempting all three at once is the surest way to finish none. The country-level operating detail is in the crypto payments guide for Mexico.
Frequently asked questions
Why separate the three flows in the corridor?
Because they break for different reasons. Collections stall on the client's vendor file and the banking timeline; supplier payments stall on counterparty verification; payroll stalls on employment classification. A fix for one does not necessarily fix the other two.
Which of the three flows gives the best initial return?
Usually collections, because they affect working capital most and carry the fewest internal dependencies. Paying suppliers requires verifying counterparties and payroll requires a prior labour analysis per country. Starting with collections lets you learn the circuit at lower risk.
Can a Mexican company receive funds in pesos through Soulbit?
Not in V1. The only local banking rail is Colombia. A Mexican company holds balances in stablecoins such as USDC and USDT plus fiat in USD, EUR and GBP, and handles the step into pesos with its own bank or currency broker. Plan that leg from the start.
Does operating this corridor on another rail change anything on tax?
No. Taxes remain national at both ends. The Mexican company invoices and files under Mexican rules, and the US client keeps its own documentation and withholding obligations. The rail changes speed and cost, not the tax obligation.
Does the US counterparty need to operate in stablecoins?
For the collections flow, yes: if the client cannot pay in USDC, that invoice travels through the banking circuit. For suppliers and payroll, the decision sits with the Mexican company and its counterparties, who tend to be more flexible than a corporate accounts payable department.
Want your company to add stablecoins to its operations?
Join the Soulbit waitlist and start paying payroll, collecting and managing treasury without SWIFT.
Join the waitlist