Case study: a BPO with agents in four countries unifies payroll

A US company that outsources customer support to a BPO in Latin America rarely asks how payroll gets built. It asks a simpler question: will the vendor's service hold up this month, or will an agent walk off mid-shift because a bonus was paid wrong again. Behind that question sits a payroll operation processing hundreds of lines every two weeks, across four countries, with a headcount that never looks the same twice.

At Soulbit Academy we present this as a synthetic, realistic example, not a real client. A related case, a small startup with a clean monthly cycle, is in case study: a startup with a remote team in 5 countries pays all payroll in USDC. That one is a small team on a stable monthly rhythm. This one is different: the challenge here is not the number of countries, it is agent volume, shifts that change weekly and turnover that reshapes the payroll every cycle.

The vendor profile (illustrative case)

Meridiano BPO is an illustrative case: a contact center legally based in Bogota that runs customer support, technical support and collections for telecom and retail clients, including US-based accounts.

Meridiano runs 340 agents across four countries: 180 in Colombia, where headquarters and most of the operation sit; 90 in Mexico; 45 in Peru; and 25 in Argentina. The operation works three shifts, morning, afternoon and night, to cover coverage windows that stretch into the early hours depending on the client and campaign.

Payroll is run by a four-person team reporting through a coordinator to the CFO. The goal was not to cut headcount or exit a country. It was to get a payroll batch that closed without rework and gave the CFO a number he could trust every two weeks before approving payment.

The problem: volume, shifts and a payroll that never closes the same way twice

Meridiano's real problem was batch variability. With 340 payment lines spread across four countries, every cycle arrived with a different headcount and different shift amounts. Bonuses changed with the prior month's performance results. The cost of moving money mattered too: as a public reference, the World Bank's Remittance Prices Worldwide series puts the average cost of cross-border transfers at 6.36% of the amount, and close to 15% through a bank channel.

Before the change, the team built each country's batch separately, with its own calendar, its own bank upload format and its own data checks. Consolidating four countries into one report for the CFO took two to three full days, and any last-minute fix, a mid-cycle departure or a miscalculated bonus, forced the whole country batch to reopen.

Turnover and shifts: why a BPO payroll never closes the same way twice

In contact centers that run night shifts like the one in this case, staff turnover tends to be higher than in a standard office role. At Meridiano, each cycle brought in an average of 15 to 22 new agents and lost 12 to 18, concentrated mostly in the night shift and the most demanding campaigns.

That turnover is not a side detail for the payroll team, it is the reason no batch resembles the last one. Every new hire needs identity and payment details verified before the first cycle, and every departure has to be removed from the next batch and settled according to that country's law, something Soulbit does not calculate.

Why does monthly turnover complicate payroll more than total headcount does?

Because headcount is a stable number that changes little, while turnover changes what is inside the batch every cycle. A BPO with 340 fixed agents and zero turnover builds nearly the same batch every two weeks. One with the same headcount and this case's turnover builds, in practice, a different batch each time: a different line count, different settlement amounts and different payment checks.

Variable pay adds another layer. Base salary is predictable, but night differentials, overtime and performance bonuses are not: they depend on the shift assigned that month and on metrics like average handle time or client satisfaction. No BPO can treat the agent layer and the variable-pay layer as one and the same.

How the biweekly cycle ended up organised

With the process redesigned, Meridiano's payroll cycle moved from a manual four-country consolidation to a single batch reviewed in one morning.

Dimension (illustrative case)	Before	After
Batches built per cycle	4 separate batches, one per country	1 consolidated batch with 4 local breakdowns
Consolidation time for the CFO	2 to 3 full days	Half a day
Lines checked manually for shift variation	Every line, one by one	Only lines flagged as exceptions
New hires added to the running cycle	Only in the next full cycle	Same cycle, if verified in time
Traceability per agent	Scattered bank receipts by country	On-chain identifier per line
Local currency payment	Depends on each country's bank	Only Colombia via local rail; elsewhere each agent handles it

The procedure they adopted follows the same pattern as any recurring payroll batch: settle in each country's system, build a consolidated batch, validate every line against the agent's verified record, fund the total including fees, approve under dual control and execute. The full operational detail is in how to schedule recurring payroll in stablecoin.

What changed was not the obligation to calculate each item, which stays with the payroll team and its local software in each country. What changed was the final step: instead of four separate payment processes on four bank calendars, the team executes one batch and each agent gets paid through whichever route exists in their country.

Colombia, Mexico, Peru and Argentina: one batch, four different regimes

Consolidating the batch does not erase the legal differences between the four countries, it makes them visible in one place. Each country brings its own shift calendar, its own hiring rules and its own enforcement authority.

In Colombia, Ley 2466 de 2025 amended article 160 of the Código Sustantivo del Trabajo and moved the start of the night differential from 9:00 p.m. to 7:00 p.m., in force since December 25, 2025. For a BPO running extended hours, that two-hour shift in the night window directly affects the cost of every cycle, even though the differential rate itself did not change and remains at 35%.

In Mexico, hiring call center agents cannot be resolved through personnel outsourcing, because the reform banning it explicitly excludes cases where a provider supplies workers who perform the client's core activity, exactly what telephone operators do. The Registro de Prestadoras de Servicios Especializados u Obras Especializadas, run by the Secretaría del Trabajo y Previsión Social, only covers services outside that core activity, so Meridiano hires its 90 Mexican agents directly, a nuance related to what we cover in payroll for remote workers in Mexico and the CFDI.

Why does adding a country to the operation involve more than opening a bank account?

Because every country brings its own pay calendar, its own definition of a shift and its own enforcement authority. In Peru, the Ministerio de Trabajo y Promoción del Empleo and SUNAFIL oversee working hours and rest periods, with rules that do not match Colombia's or Mexico's. In Argentina, the tax authority is ARCA, the successor to AFIP under Decreto 953/2024, and its usual pay calendar differs from the biweekly one Meridiano uses in the other three countries.

Country (illustrative case)	Agents	Key shift or hiring detail	Local banking rail in V1
Colombia	180	Night differential from 7:00 p.m. (Ley 2466 de 2025)	Yes
Mexico	90	Agents hired directly; outsourcing rules do not apply to core operations	No, agent converts independently
Peru	45	Working hours and rest periods overseen by the MTPE and SUNAFIL	No, agent converts independently
Argentina	25	ARCA is the tax authority; pay calendar differs from the other three	No, agent converts independently

Outside Colombia, each agent receives stablecoin and handles the conversion to local currency independently, because V1's local banking rail exists only in Colombia. Meridiano communicated this from the first cycle, using the same approach as the remote-team case: anyone who prefers to keep getting paid by traditional transfer in their country can do so.

What Soulbit Salaries automates here, and what stays with the payroll team

Soulbit Salaries disburses the payroll batch once it is calculated, it does not calculate it. Meridiano's payroll team keeps settling every line in its own system or in each country's local software: base salary, night differential, overtime and performance bonus are determined before the batch reaches the platform.

What Soulbit handles is the next step: loading a batch with hundreds of lines, each carrying a different amount, validating every destination against the already verified KYB and KYC record, funding the total including fees and executing under dual-control approval. What that verification file requires is covered in what is KYB.

Beyond that, Soulbit V1 does not run payroll, does not calculate contributions or social benefits, and does not report to any authority. It also does not resolve hiring compliance in any country, such as Mexico's outsourcing restriction, nor does it replace the labour counsel Meridiano keeps in each of the four countries. Any BPO weighing this path should check with counsel whether its hiring structure in each jurisdiction is correct before touching the payment side.

What another multi-country BPO can take from this

Three conclusions travel well to another BPO with a similar structure.

First: separate calculation from disbursement. Consolidating payroll into one batch does not mean calculating each item once for all countries, it means no longer repeating the payment process four times at the same pace the calculation repeats.

Second: turnover is managed through a hire and departure process, not by reopening the whole batch. Meridiano stopped reopening the entire batch for every last-minute change and instead treated each hire and each departure as an individual line inside the next cycle.

Third: the real cost of a BPO's cross-border payroll is not only in transfer fees, as the analysis of the true cost of international payroll by bank transfer explains, it is in the hours the payroll team spends consolidating manual reports. Meridiano did not measure fees saved, it measured how many hours the team stopped spending reconciling four countries by hand, and that was the number that convinced its CFO, and reassured its US clients that the service would not slip.