Remittances vs B2B Payments: Not the Same Market

A finance team shopping for a way to move money abroad keeps running into the same figure quoted twice: once for family remittances, once for company to company payments. The market lumps both under "cross-border payments," and that shared label suggests one provider can serve both. It rarely can.

At Soulbit Academy we separate what an aggregated figure hides. This article compares remittances and cross-border B2B payments across six concrete dimensions: who pays whom, average ticket size, frequency, channel cost, paperwork and the regulatory frame each one answers to. Every figure below cites its official source; where no verifiable figure exists, the difference is described qualitatively instead.

Remittances vs B2B payments: two categories the market adds into one figure

Remittances and B2B payments share exactly one trait: both move money across a border. The Committee on Payments and Market Infrastructures at the Bank for International Settlements (BIS) treats them as separate segments inside its G20 cross-border payments programme. The programme sets distinct cost and speed targets for retail, wholesale and remittance payments, precisely because they do not behave the same way.

That official distinction is this article's starting point. A "cross-border payments" figure that blends remittances and B2B payments without separating them hides a market running on two different business logics. What follows is the full comparison, dimension by dimension.

Dimension	Remittances	Cross-border B2B payments
Who pays whom	One individual to another, almost always a family member	One company to another, for a good or a service
Average ticket size	Tens or a few hundred dollars per transfer	Thousands to tens of thousands of dollars per transaction
Frequency	Monthly and recurring, tied to the sender's income cycle	Irregular, tied to each invoice's due date
Paperwork	None: no invoice, contract or withholding required	Invoice, often a contract, withholding tax when applicable, transfer pricing between related parties
Counterparty verification	KYC on the sending and receiving individual	KYB on the paying and collecting company

Who pays whom: individual to individual vs company to company

Who pays whom is the structural difference every other one flows from. A remittance is sent by one individual to another, typically a family member abroad, with no commercial obligation between them. A B2B payment is made by one company to another, to settle an invoice for goods delivered or a service rendered.

That difference in purpose changes what each payment is for. A remittance covers the receiving household's living expenses. A B2B payment settles a contractual obligation between two entities that, in most cases, will keep working together on a recurring basis. A channel optimized for the first purpose rarely serves the second well, because the verification, the paperwork and the service level each one needs are different from the start.

Ticket size, frequency and predictability

The average remittance runs tens or a few hundred dollars, while a B2B payment usually exceeds a thousand dollars and often reaches tens of thousands per transaction. The World Bank uses 200 dollars as its reference amount to measure remittance cost in its Remittance Prices Worldwide report, a figure that illustrates the real scale of an average remittance transfer.

Why does ticket size change how each payment's cost is structured?

Ticket size changes cost structure because fixed fees weigh very differently depending on the amount. A flat 5 dollar fee is a high percentage of a 200 dollar remittance and nearly negligible on a 50,000 dollar B2B payment. Comparing the percentage cost of a remittance to that of a B2B payment, without adjusting for this scale difference, produces a misleading read on which channel is actually cheaper for each case.

Frequency and predictability round out the difference. A remittance tends to repeat every month, for a similar amount each time. A B2B payment is irregular, tied to each invoice's due date and to the terms agreed with each supplier or client, which can run 30, 60 or 90 days.

Channel and cost: why the World Bank's 6.36% does not measure a B2B payment

The World Bank reports a global average cost of 6.36% for sending a remittance, rising to nearly 15% when the channel used is exclusively bank based, according to its Remittance Prices Worldwide report for the third quarter of 2025. That figure measures the cost of moving 200 dollars between individuals, the reference amount the report itself uses.

That methodological detail is the crux of this article: the 6.36% is not directly comparable to the cost of a five figure B2B payment, because fee structure changes with transaction size. The Financial Stability Board, which coordinates the G20 target, sets different cost goals per segment: a global average no higher than 1% for retail payments by 2027, versus no more than 3% for remittances by 2030. They are separate targets because they are separate markets.

Segment	G20 cost target	G20 speed target
Remittances (individual to individual)	Global average no more than 3% by 2030, no corridor above 5%	75% of payments available within one hour, in every corridor, by 2027
Retail payments (includes commerce and smaller B2B)	Global average no more than 1% by 2027, no corridor above 3%	75% of payments available within one hour by 2027
Wholesale payments (between financial institutions)	No cost target set	75% settled within one hour of the agreed time, by 2027

The channel also shifts by segment. Remittances typically rely on remittance operators and low value bank correspondence. B2B payments almost always run through international bank transfer and the same correspondent network, but at different volumes, with different controls and processing times tied to the size of each transaction.

The paperwork gap: invoice, contract and withholding vs nothing

A B2B payment normally requires an invoice to back the transaction, and in most Latin American countries also requires checking whether withholding tax applies to the payment abroad. Colombia, for instance, requires reviewing that withholding on every cross-border payment, as we detail in our guide on withholding tax on foreign payments. A remittance between individuals passes through neither filter.

What happens when the two companies paying each other are related parties?

When the two companies are related parties, the paperwork grows further: several countries in the region require a transfer pricing study showing the payment was made on market terms, not to shift profit artificially between jurisdictions. We cover that requirement in our analysis of transfer pricing for cross-border payments in Latin America. A personal remittance has no equivalent obligation, because there is no commercial relationship to audit.

The practical result is that a B2B payment leaves a full paper trail: invoice, contract when one exists, proof of withholding applied and, where relevant, transfer pricing support. That trail is exactly what an accounting team needs to reconcile the payment and defend it in a tax review. A remittance produces none of it, because it does not need to for its own purpose.

Regulatory frame and KYC vs KYB

The regulatory frame applying to a remittance and the one applying to a B2B payment share a common anti money laundering baseline, but differ in counterparty verification. A remittance operator runs KYC (Know Your Customer) on the sender: an identity document, personal data and, above a threshold, the source of that individual's funds.

A platform built for company to company payments runs KYB (Know Your Business) instead: it verifies the company's legal existence, identifies its beneficial owners, and reviews its declared business activity and source of funds as an entity, a process we cover in detail in what is KYB. The Financial Action Task Force (FATF) also requires, for virtual asset transfers, what is known as the travel rule: originator and beneficiary information that must travel with the transaction, under its guidance on Recommendation 16 as applied to virtual asset service providers.

That KYC versus KYB distinction is not a minor technicality: it determines which provider can legally process each type of payment with the due diligence it requires. A provider built for individual KYC does not have, by design, the process to verify beneficial owners or corporate structure, which is exactly what a B2B payment demands.

Why the confusion leads to bad decisions, and what Soulbit's V1 delivers today

Confusing remittances with B2B payments leads a finance team to pick a provider poorly matched to its own operation. A US company that needs to pay an overseas supplier and turns to a service built for family remittances discovers, too late, that it produces no invoice, no proof of the foreign exchange transaction, and no trail for withholding tax purposes.

Why does a remittance service rarely work for paying a business supplier?

A remittance service rarely works for that because its counterparty check is individual KYC, not company KYB, and its product is not designed to generate the paper trail a commercial payment requires. The typical outcome is manual reconciliation, with the accounting team rebuilding by hand what the channel should have produced on its own.

Soulbit is a B2B platform, not a remittance service. Its V1 requires company KYB to operate, not individual KYC for sending money to a relative. Today it lets a company hold a balance in USDC and USDT alongside fiat in USD, EUR and GBP, disburse payroll on a recurring or batch basis (the differentiator of its B2B leg), collect through payment links and QR codes, and request an OTC quote on request to convert between stablecoin and local currency, with a local banking rail available in Colombia. All of it runs under institutional custody with distributed signing (MPC), AML and KYT controls, and human support.

The V1 does not deliver a physical or virtual card, yield or APY on the balance, a native token, or direct API or SDK integration with an ERP system. None of that turns Soulbit into a remittance substitute, nor is it meant to: mass payroll disbursement in stablecoin and its B2B leg, which we already document in our analysis of global B2B stablecoin payment volume and our study of cross-border payroll growth in Latin America, are B2B use cases by design, with the paperwork and company verification that market requires. A finance team that understands this distinction picks the right provider the first time, instead of discovering the mismatch after processing the first payment.