AWRA OpsHub Search

From a locked timesheet to a paid, reconciled payslip.

AWRA Payroll calculates every run over the locked, payroll-ready periods Attendance already produces — applying each region's statutory rules to gross pay, freezing a full payslip per employee, and posting the approved run straight into the ledger that already reconciles your vendor payments.

Runs

Calculate & review

Payslips

Every figure frozen

Statutory

Region-configurable

Ledger

One reconciliation surface

What's shipped

Everything from compensation to a posted payslip.

Payroll is deliberately the last HR module to ship, built on clean employee and attendance data — and it's live today, not a roadmap item.

Payroll runs

Create a run for a period, calculate gross-to-net for every employee in one pass, and recalculate freely before you approve.

Compensation & pay components

Model allowances, benefits and deductions per employee — fixed or a percentage of basic — each flagged taxable, pensionable and cash or non-cash.

Region-scoped statutory rules

Income tax, social security, health and local levies are versioned, effective-dated configuration per region — never hard-coded, so a rate change never rewrites a closed run.

Deterministic gross-to-net order

Basic is prorated for unpaid leave, cash allowances are added, statutory rules apply in a defined order against the right base, then voluntary deductions come off last.

Built on locked timesheets

A run only calculates from an approved, locked attendance period — payroll always reflects a signed-off record, never a live or disputed one.

Frozen payslips

Every figure on a payslip — basic, allowances, each statutory line and net — is a snapshot at calculation time, together with the exact rule-set version it depended on.

Encrypted bank & mobile-money details

Payout details are stored encrypted at rest, one record per method with a primary flag, ready to drive disbursement.

Posts to your existing ledger

An approved run posts as money-out into the same ledger and Payments Register that already reconciles vendor payments — one surface, not two.

Permission-gated & audited

Running, approving and posting payroll are distinct, granular permissions, and every calculation and state change is captured on the audit trail.

The moat

A run you can actually trust.

Every stage is explicit and auditable — from the locked period that feeds it, through a deterministic calculation, to the posting that closes the loop with finance.

1

Lock

Attendance period approved & locked

2

Resolve

Compensation & statutory rules resolved per employee

3

Calculate

Gross → statutory deductions → net, per person

4

Approve

Review payslips, then approve the run

5

Post

Approved run posts to the money-out ledger

Locking is the honest hand-off from Attendance: what payroll consumes is exactly what was signed off, so a run is never built on data that could still move underneath it.

Not a silo

The payoff for building HR in dependency order.

Fed by Attendance

Every run calculates from the locked, payroll-ready timesheets that Attendance & Time produces — no re-entry, no reconciliation gap.

Aware of Leave

Unpaid leave days prorate basic pay automatically, using the same approved leave records as the rest of HR.

One employee record

Compensation, bank details and payslips sit on the same profile as contracts, documents and attendance.

One money-out ledger

Payroll posts beside vendor payments in the same reconciliation surface your finance team already uses.

Granular permissions

Separate rights to run, approve and post payroll, layered on your existing roles.

Fully audited

Every run, recalculation, approval and posting is captured with who and when.

Questions

The practical details.

Which countries does payroll support?

Payroll is multi-jurisdiction by design: statutory rules are region-scoped, versioned, effective-dated configuration, not hard-coded logic — adding a region is a configuration exercise, not a rebuild.

How is net pay actually calculated?

Basic salary is prorated for unpaid leave days, cash allowances and benefits are added, statutory rules apply in a defined order against the correct base, and voluntary deductions come off last to reach net.

Can a run start from live, unlocked attendance?

No — a run only calculates against an approved and locked timesheet period, so payroll is always built on a signed-off record, never one that could still change underneath it.

What happens if a statutory rate changes?

A rate change is a new, versioned rule set. Once a payslip references a version it stays tied to it — a later correction never rewrites a run that already closed.

Are bank and mobile-money details secure?

Yes. Payout details are encrypted at rest, with access captured on the audit trail like every other sensitive HR field.

Where does payroll fit in the HR roadmap?

Payroll is live, alongside Employee Management, Leave and Attendance & Time — the final stage of the HR pillar, built deliberately on clean employee and time data.

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center