Dawmo 2026.9 is out — rendered payslips, a public API and calendar feeds. See what changed
For labour supply companies placing workers with clients across many sites, where the client is invoiced on hours worked, payroll runs to a large WPS file, and headcount moves with every contract.
Workers move between client sites during the month, and the hours each client owes for are pieced together from supervisors’ sheets.
How Dawmo handles it
Movement between sites is recorded as it happens rather than reconstructed at month end. Timesheets are kept per person, per site and per project, and export in the shape your client invoices want.
One wrong IBAN or salary card number in a file of hundreds of workers, and the whole file comes back from the bank.
How Dawmo handles it
The SIF is generated to your bank’s own layout and validated against it before you upload: IBAN checksums, salary card numbers, totals against headcount. An IBAN is checked when the employee enters it, not when the bank rejects the file.
A contract starts and two hundred people join. It ends, and everyone who leaves is owed a settlement worked out correctly.
How Dawmo handles it
Billing follows your active headcount, up and down. A resignation starts the clearance and the final settlement, with notice, leave balance, gratuity and deductions on one statement.
The rest of the platform switches on later, on the same employee record, with nothing to migrate.
Twenty minutes, on a call, with your payroll rather than our demo data. Bring last month’s run and we will compare it line by line.
In the call
No slides and no obligation. Book a time that suits you.