Payroll gets calculated, the numbers are right, everyone’s due amount is locked in. Now someone has to actually get the money into people’s hands. And for a real chunk of the team at most Bangladeshi SMBs, that doesn’t mean a bank transfer. It means a mobile wallet.
Guards, delivery riders, junior staff, anyone whose job never came with a bank account attached. Mobile financial services (MFS) are how a huge share of Bangladesh gets paid outside the formal banking system, and that’s not a workaround, it’s just how payroll works here. The wallet itself isn’t the problem. What happens between “payroll is done” and “money is actually in the wallet” is where things go wrong.
The part that eats your payday
At most small businesses, this step is entirely manual. Whoever runs payroll opens the finalized sheet in one window and an MFS provider’s app or web portal in another, then goes down the list: pull an employee’s wallet number, type it into the transfer field, pull their salary amount, type that in too, confirm, next employee. Repeat for every single person on payroll.
For a team of ten, that’s tedious but survivable. For a team of forty or fifty, it’s an afternoon gone, and it’s an afternoon spent doing the single most sensitive kind of data entry a business does: moving real money to a real person based on a number typed by hand.
Where it quietly goes wrong
A wallet number is eleven digits with no built in check, unlike a bank account that at least gets validated against a name before a transfer clears. Get one digit wrong while copying it across by hand and the app usually won’t stop you. It just sends the salary to whichever wallet happens to be registered to that number, and that’s someone else’s money now, sitting in a stranger’s account.
The other common failure is simpler: losing your place in a long list mid-transfer, then either skipping someone entirely or paying them twice. Either way, nobody notices until an employee messages asking where their salary is, or a totally different employee mentions they got paid twice and isn’t sure if they should say anything. Untangling either situation after the fact takes far longer than the transfer itself ever did.
None of this is about anyone being careless. Type the same kind of information into the same kind of form a hundred times in a row and a mistake becomes close to guaranteed, not a fluke.
The fix isn’t a different payment method, it’s removing the retyping
The wallet stays the same. What actually needs to change is the step where a correct number, already sitting in your payroll system, gets manually copied into a second system by hand. That’s the only point in the whole process where a new mistake can get introduced, because the payroll numbers themselves were already right before anyone touched an MFS app.
The workaround that works is exporting the payroll run itself, in whatever format the MFS provider’s bulk disbursement portal accepts, and uploading that file directly instead of transferring employee by employee. The wallet numbers and salary amounts come straight from the payroll data that’s already been checked, so there’s no separate re-entry step sitting between “correct” and “paid” where a typo can sneak in.
Where Utso fits into this
This is exactly what Utso’s payroll module handles for salary disbursement: once a pay run is finalized, it generates a formatted bulk transfer export file, ready to upload directly to a mobile financial services provider’s bulk disbursement portal, instead of a manager retyping every employee’s wallet number and salary amount into an app one at a time. The payroll software page covers how this fits with the rest of the payroll run, from salary structure through the actual pay run.
It won’t stop an MFS provider’s own systems from having issues on their end, and it’s not a substitute for double checking a new employee’s wallet number when they first join. But it does close off the one failure point that’s entirely under your control: the manual re-entry step where a correct number quietly becomes a wrong one.
One more thing
Always confirm a new employee’s mobile wallet number directly with them before their first payday, and keep it on file the same way you would a bank account number. A clean export only helps if the number it’s built from was correct to begin with.