Payroll that runs itself, correctly, every time
No spreadsheet formulas, no adding things up by hand, no month-end scramble. Payroll runs as a scheduled process behind the scenes for every company on Utso, calculated the same correct way every time, on whatever frequency each company actually pays its people.
Pay as often as you like
Daily, weekly, bi-weekly, and monthly pay cycles are all supported in the same platform, a rare combination in the Bangladesh market, where most software picks one frequency and expects every business to fit it. A factory floor paying daily wages, a project team paid bi-weekly, and a head office running standard monthly salaries can all sit inside the same company account, each on its own schedule, without exporting data between separate systems to make it work.
Each company sets its pay frequency once, and a daily check looks at every company and fires a pay run automatically whenever that company’s date is due, whether that is every single day or once a month. Nobody has to remember when payday is coming or manually start the run. If a company later changes its pay frequency, for example moving a team from weekly to monthly as it grows past its early hiring stage, the new schedule takes effect from the next cycle without disturbing past payroll history.
Raises and back pay
Increments can be entered one employee at a time or as a batch across a whole team, which matters when a raise applies to a whole department at once rather than one person. Every increment moves through the same three steps, drafted, then approved, then applied, so a raise is never live in payroll before someone has actually signed off on it.
Back pay is where this saves the most manual work. When an approved increment is effective from an earlier date rather than the current cycle, Utso works out the arrears automatically and generates the back pay entry, instead of leaving HR to calculate the difference by hand for every affected employee. The increment history stays attached to each employee’s record, so there is always a clear trail of what changed, when it took effect, and when it was actually approved.
A separate database for every company
Payroll data gets a stronger guarantee than the rest of the platform. Every company’s HR and CRM records already live apart from every other company’s, but payroll goes one step further: each company’s salary data sits in its own separate database, not a shared database with a filter deciding what you are allowed to see.
That distinction matters more than it sounds. Row-level filtering depends on every query in the system getting the filter right, every single time, forever. Physical database isolation removes that dependency: there is no shared table for a bug, a misconfigured report, or a future integration to leak from. For salary figures, arguably the single most sensitive number attached to any employee, that is the strongest level of separation Utso offers anywhere on the platform, applied by default to every company, not sold as a paid upgrade.
Allowances, deductions, and adjustments before you lock the run
A payroll run is rarely just base salary. Named allowances, house rent, conveyance, and any custom allowance a company wants to define, are configured per employee and included automatically every run instead of added back in by hand every month. Deductions work the same way: TDS, leave deductions calculated from approved leave records, and any custom deduction a company needs, all apply automatically once they are set up.
Real payroll always has exceptions, though, so ad-hoc adjustments are supported too: a one-off addition or deduction for a single employee that applies before that pay run closes, with no separate off-cycle process needed for something small. Once a run has been reviewed and is correct, it can be marked as paid in bulk for the whole company in one action, rather than confirming payment employee by employee.
Payslips that generate and deliver themselves
Once a run is complete, every employee’s payslip is generated automatically as a PDF, with no separate export-and-format step for HR to run every month. Payslips can be downloaded in bulk as a single ZIP file for record-keeping, emailed directly to each employee, or pulled by employees themselves from self-service whenever they need one, for a loan application or a visa file, without asking HR to dig it up.
Employees are not left waiting for payday to know what is coming, either. A next salary preview shows the projected upcoming amount ahead of the actual pay run, calculated from the same attendance, leave, and increment data payroll itself will use, so there are no surprises between what someone expects and what actually lands.
Paying people through mobile financial services
Most Bangladeshi employees are paid through a mobile financial service rather than a traditional bank transfer, and Utso generates a disbursement file formatted for exactly that, ready to hand to whichever mobile wallet provider your company already uses for bulk payment. HR does not have to reformat a spreadsheet by hand into whatever layout the provider expects, or split one company-wide payment into a separate bank-transfer batch and a separate mobile-wallet batch.
The export is generated from the same completed, approved pay run as everything else on the platform, so the amount going out to a mobile wallet always matches the payslip the employee sees, not a second figure recalculated somewhere else.
Payroll that already knows your HR data
Because payroll sits in the same platform as HR, attendance, and leave, it does not start from a blank spreadsheet every cycle. Approved leave already carries the right deduction into payroll without anyone re-entering it, and a new hire added to the employee directory has payroll set up for them automatically as part of that one action, so payroll is never a separate second step after the HR paperwork is done. Compare that to running payroll in a spreadsheet or a standalone tool like Tally, where every attendance exception, leave day, and new joiner has to be typed into payroll by hand, a second time, by someone hoping the two records still agree.
Fast even when every company pays on the same day
Payroll is its own service, separate from HR, CRM, and the rest of the platform, and it scales on its own. When every company’s pay run fires on the same day, for example the start of the month, when most offices in Bangladesh pay their staff, that spike in payroll processing does not slow down attendance, leave approvals, or anything else your team is doing in Utso at the same time. Each part of the platform grows independently, so adding more employees, or more companies, to payroll does not make everything else slower to compensate.
Physical database isolation. Your salary data lives in its own separate database, physically apart from every other company on Utso, not a shared database with a filter deciding what you can see. It is the strongest level of data isolation the platform offers, applied by default.
Nobody has to start it. Payroll runs on its own: a daily check fires each company’s pay run automatically whenever its schedule is due, whether that company pays daily, weekly, bi-weekly, or monthly.
Built around Bangladesh Labour Rules. TDS and leave deductions are computed to match Bangladesh Labour Rules, not a global payroll engine adapted after the fact, and leave data feeds straight into the same run so deductions reflect what was actually approved.
BDT pricing. Your subscription is priced and billed in taka, with no USD conversion friction or exchange-rate guesswork on your invoice.
Start with the free HR tier and add payroll when you’re ready, with a 2-month free trial included. No payment details required to register your company.