Dawmo 2026.9 is out — rendered payslips, a public API and calendar feeds. See what changed
The parts nobody asks about until procurement does, and then they decide the deal on their own.
The full list is below. These are the one or two claims the module is actually bought on, with the mechanism behind each one drawn rather than described.
Isolation
Tenant isolation here is a policy on the table rather than a filter somebody remembered to add to a query. A group with eleven companies sees its own eleven; a mistake in application code cannot leak a row across that boundary, because the row never leaves the database. Procurement asks this question and decides the deal on the answer.
One table, three companies
A mistake in application code cannot leak a row across the boundary, because the row never leaves the database.
11 capabilities, switched on per company
Multi-company & branch
Several companies and branches in one group, with data and approvals scoped to each company, branch and department.
Row-level tenant isolation
Separation enforced by the database itself, not by a filter in the application that one missing clause would defeat.
Approval engine
One engine behind every request type, so a policy change is configured once.
Eight languages, Arabic and Urdu right to left
Set right to left rather than flipped, in the app and in the documents it generates.
Public API
Documented, versioned, and the same API the app itself uses.
Roles & permission scopes
What a branch manager sees is a scope, not a screen someone remembered to hide.
Notifications
Push, email and in-app, with the noise level set per person rather than per company.
Audit & privacy
Every change to a record, every ID reveal and every bank-file export written to a log you can query.
Reporting & exports
Your data out in a shape you can use, without asking for it.
Import / export
Bulk changes staged, validated and previewed before they are applied.
Module & subscription controls
Modules toggled per company, which is what makes the pricing honest.
All of the above is machinery under one thing: the employee record every module reads. Core HRMS is where that record is kept, and the isolation, the roles and the approval engine exist to protect it.
The employee record
There is no export, no nightly sync and no reconciliation step, because there is no second copy to reconcile.
Each one is switched on per company, on the same employee record. Take this module on its own, or run it with the rest and stop reconciling two systems.
Where the employee record starts
Recruitment
Requisitions, a candidate pipeline with optional AI screening, your own careers page and offer letters from your template. The accepted offer becomes the employee record, so nobody types the new joiner in twice.
See RecruitmentCapture that works where the signal doesn’t
Time & Attendance
The strongest thing Dawmo does that imported HR software does not: record a shift on a site, on a bus or in a camp, on whatever hardware is already there.
See Time & AttendancePayday, without the spreadsheet
Payroll & WPS
Leave, overtime, claims and loans arrive in the run on their own. The bank file is generated in your bank’s format and validated before you upload it, not after it bounces.
See Payroll & WPSTasks, goals, reviews and promotions
Performance & growth
Tasks with owners and due dates, goals, review cycles, promotions and benefits, kept on the same record as the contract and the salary, so a promotion is decided on evidence rather than memory.
See Performance & growthPart well, and settle right
Offboarding
A resignation starts the clearance, the exit interview and the final settlement, each desk signing off its own part, with the gratuity basis shown on the settlement.
See OffboardingVehicles, drivers and what they cost
Fleet
Mentioned on the home page and sold here: if you run vehicles, the tolls and fines are already arriving against people whose attendance you are tracking anyway.
See FleetYour field team is already on this app
Mini CRM
Not sold as a CRM, but as the reason your salespeople’s visits are recorded at all. They are already opening Dawmo to punch in; the visit takes one more tap.
See Mini CRMFrom purchase request to goods received
Procurement
Purchase requests with quotes, approved on your own route. Each approved request becomes one purchase order, issued as a PDF with the VAT and the supplier's TRN, and deliveries are booked in against it. It stays light on purpose: no tenders, budgets or invoice matching.
See ProcurementBring a real month of your own and we will run it through this module on the call rather than walking you through a standard tour.
In the call
No slides and no obligation. Book a time that suits you.