Run cockpit
Blockers, variances and approvals sit on one board, so a run does not hide surprises.
Run payroll with built-in statutory rules, two-person approval and clean books.
Payroll takes people, pay and approved hours through to approved runs, payslips, statutory files, bank payments and ledger postings. India and the UAE run on a built-in engine whose rules are dated data with citations, and other countries can run through a partner. Every run needs a second person to approve it and pay data stays hidden from administrators and the assistant.
Blockers, variances and approvals sit on one board, so a run does not hide surprises.
The preparer can never approve, enforced in the database.
Rates and slabs carry a source and an effective date, so you can see why a figure is what it is.
You compare against your current payroll person by person before you rely on the new one.
Returns, the salary file and the bank instruction come from the same approved run.
Search or filter. Planned items are labelled; everything else is available now.
Pay groups, periods and cut-off dates that drive every run.
6 featuresA built-in engine for Indian statutory payroll, driven by dated rule data.
10 featuresNative payroll for the United Arab Emirates, as researched.
9 featuresOne screen to take a run from inputs to approval, with separation of duties built in.
10 featuresProve the new payroll against your current one before you rely on it.
3 featuresBranded payslips that employees can read in their own language.
7 featuresFiles and challans prepared on the right dates, ready for upload.
8 featuresPay people and post the books without re-keying.
7 featuresThe tax paperwork and exits that make payroll messy, handled in one place.
5 featuresOther hubs feed pay lines automatically and once only.
5 featuresPayroll through a partner where a native engine is not the right choice.
5 featuresReady reports for payroll, HR and finance.
3 featuresIt prepares the work. A person confirms it.
The same four building blocks, specific to Payroll.
Reopening a run, running off-cycle, settlements and break-glass access go through workflow with a second approver.
Registers, variances and statutory dues with dashboards for the payroll administrator, HR and finance.
Datasets
Dashboards
Payroll reads people, hours, incentives, expenses and benefits by event and posts to the ledger and payments.
/v1 payroll resources
Events
Connectors
AI Migrate brings pay structures and history in alongside a parallel run. Payroll vendor packs are planned.
Employees see payslips and submit investment declarations on the phone. Approvers handle payroll requests from the phone.
Pay, bank and identifier data and pay revisions come from the worker record
Approved hours become pay inputs
Approved incentive batches arrive as pay lines
Approved reimbursements are paid with salary
Bonuses and benefit deductions arrive as lines
Payroll journals and provisions post to the ledger
Tax deducted at source figures feed tax
Bank files and remittances are paid through the payment process
India and the UAE run on the built-in engine. The United States is planned through a partner. Other countries are planned.
From dated rule packs with citations. Your organisation reviews and acknowledges a pack before it is used.
No. The database records the approver as a different person from the preparer.
Yes. A parallel run compares results person by person, and the built-in engine can be held from paying until one passes.
It prepares the files and challans. Upload to the portals and the UAE salary file submission need your own registrations and logins.
Only people with explicit access. Administrators and the assistant cannot read pay results by default, and break-glass access is logged.
No. It explains and prepares. People approve runs, pay and file.