Human Resources — employee records, leave, attendance and time, payroll and payslips, and employee self-service.
AWRA Help Docs
The HR module manages the people side of your operations — employee records, leave, attendance and time, and payroll, with recruitment, onboarding and offboarding, performance reviews and expense claims around them — from the same workspace you already use for inventory, procurement, and sales.
AWRA Help Docs
The Projects module manages delivery — projects, tasks, planning, sprints and time — from the same workspace you already use for inventory, procurement, sales and HR. It is a delivery tool that is wired into the rest of the business, not a silo.
Asset Custodians & Custody Chain
A custodian is its own record rather than a user account, so drivers, site labourers, contractors, departments, vendors and visitors can hold assets with no login, no seat and no permissions. Six custodian types and four statuses including exited, so somebody who leaves stops receiving custody while every movement they were part of stays readable. Nine movement actions each carry their own permission, and every handover records the custodian, department, warehouse, location and condition at both ends, with an expected return date, optional photographs, optional GPS and a signature.
Attendance & Time
AWRA captures attendance three ways — a manual daily register, employee self-service clock-in/out, or CSV/biometric import — in one record. It adds shifts and weekly rosters, automatic late detection, overtime, correction requests, and timesheet approval and lock per pay period. Clock-in can be secured with device passkeys, GPS geofencing, and an office QR code.
AWRA Blog
Most board data policies cover laptops and email and never name the system holding payroll, supplier bank details and the asset register. Seven clauses that close the gap.
AWRA Blog
Fourteen tables point at the department list — payroll, budgets, purchase orders, assets, tickets, projects and the workflow queue. The record they point at holds two fields, the settings menu calls it a cost centre, and deleting one checks four of the fourteen.
AWRA Blog
Victoria wants a written incident record within 48 hours, on a form the Authority defines, kept five years and shown on request to people who do not work for you. Every report we make well is one you designed yourself.
AWRA Blog
Our public holidays repeat on the same date every year. Six of Japan's sixteen are not on a date at all — four are the nth Monday of a month and two are announced annually. The first year is correct, which is the problem.
AWRA Blog
End-of-service accrues from month one and nothing asks about it until somebody resigns. With a finance team of three, nothing that fails to raise an alert gets looked at.
AWRA Blog
A court has told member states to require a system that measures each worker's daily hours. Ours stored a 22:00 to 06:00 shift perfectly and reported its duration as empty — because clock-out is a time with no date, and six separate copies of the same arithmetic each decided an end before a start has no answer. Fixed the day this was published.
AWRA Blog
Most support portals fail because they ask people to create an account before they can complain. What makes an intake channel people actually use, and the honest limits of a portal.
AWRA Blog
Victorian payroll tax groups employers across company boundaries, makes the liability joint and several, and lets a grouping determination take effect from an earlier date. Our workspaces are built not to produce that figure — deliberately.
AWRA Blog
A certified payroll has a period of one week, a scope of one contract, and a signature attesting to three specific things. None is a cost figure — and its most unusual requirement is something this product already does, in the wrong module.
AWRA Blog
When a message to five people fails for two, the useful information is which two. Most integrations throw that away and report one reason — and the difference is a minute of work against an afternoon.
AWRA Blog
The kitchen loses money in percentages; the bar loses it in bottles. Nightly bottle math, pour discipline, empties fraud, and variance by shift.
AWRA Blog
For a firm that sells expertise, time is the only inventory — and the one form of stock that vanishes if you do not count it the same day. Utilisation, realisation, and where the hours actually disappear.
AWRA Blog
An employee's hour is recorded twice here — once as attendance that becomes pay, once as effort that becomes project cost. Linking the two, so you can compare what you paid for against what you billed, is an integration we can build into your workspace.
AWRA Blog
A smaller market with the same obligations as a larger one. Why the concentration problem — not fraud — is the real risk, and the five boring structural features that substitute for the people you do not have.
AWRA Blog
Four exclusions at the top rather than the bottom: no Revenue integration, no Irish payroll, no per-line VAT rate, no Irish reference customer. Then the questions worth asking everybody else.
AWRA Blog
Ask every vendor how many payroll runs their system accepts in one calendar month, and what reads a supplier certificate's expiry date at payment time. We publish our own answers, which are one and nothing.
AWRA Blog
Written by a vendor that does not file your return, has no UK payroll engine and no UK reference customer. Which is a strange sales position and a useful vantage point — there is nothing left to protect except the argument.
AWRA Blog
A church pays pastors, employs support staff, relies on volunteers and hands honoraria to visiting ministers. Four relationships that look alike on a bank statement and are entirely different in law.
AWRA Blog
The only pay basis held is a monthly salary. What actually works for harvest crews and fundis paid by the day, the two employment-type vocabularies that do not match, and the legal clock nobody is watching.
AWRA Blog
Getting an asset onto the register is the easy half. Five ways assets leave, why scrapping needs its evidence created before the item is gone, and the rule that keeps a register credible: retire, never delete.