Question 1

We currently track attendance and leaves in spreadsheets. How disruptive is the switch?

Accepted Answer

The disruption is real but manageable — and it mostly happens during setup, not after. The biggest task is converting your existing leave policies, holiday lists, and attendance rules into the system's configuration. Once that is done, historical data can be imported and your team transitions to the self-service portal for requests and approvals. Most teams find the daily disruption drops significantly within the first two pay cycles, once employees understand they can check their own balances and managers have a leave calendar to work from.

Question 2

Our payroll has different salary structures for different employee types — fixed, variable, and contract. Can the system handle that without becoming complicated?

Accepted Answer

Yes, and this is one of the areas where configuration matters most. The system supports multiple salary structures running simultaneously — each with its own earning components, deduction rules, and formulas. Fixed employees, variable-pay roles, and timesheet-based contractors can all run through the same payroll cycle or separately, depending on how your pay periods work. The key during setup is mapping each structure accurately before the first payroll run — which is why previewing salary slips before finalising is built into the process.

Question 3

What does payroll actually look like on the day we run it — how long does it take and who needs to be involved?

Accepted Answer

Once the system is configured and attendance data is in, running payroll is a matter of applying filters for the period, previewing the salary register to check for anomalies, and submitting. For most teams of 10 to 150 employees, this takes under an hour when data is clean. The salary register report lets your HR or finance person catch discrepancies — a missing attendance entry, an unapplied bonus — before the run is finalised. Bank entries and general ledger postings are generated from the same process, so there is no separate reconciliation step needed.

Question 4

Our team includes employees on shift rosters — some rotating, some fixed. Can the attendance system handle that without manual workarounds?

Accepted Answer

Shift-based attendance is handled through a planning view that shows your roster visually — with drag-and-drop scheduling for swaps and adjustments. Each shift is configured with its own hours threshold, grace period, and late-entry rules, and attendance is marked automatically based on check-in data rather than manually entered. Employees can check in via the mobile app with geolocation captured, or through a biometric device if you have one integrated. If someone misses a check-in, they can submit an attendance regularisation request which goes through an approval workflow before the record is updated.

Question 5

What happens to our HR data if we need to change how something is configured after go-live — like updating a leave policy or revising a salary component?

Accepted Answer

Most configuration changes can be made without affecting historical records. Updating a salary component formula, for example, applies to future payroll runs — and you can synchronise existing salary structure assignments to pick up the change. Leave policy updates work similarly — you adjust the policy and the control panel lets you reassign it to relevant employee groups in bulk. The main area to be careful with is mid-cycle changes to tax configurations, where timing affects how deductions are spread across the remaining payroll periods. Your implementation team would map out the right sequence for any significant structural changes.

Question 6

Which members of our team actually need to use this system regularly, and what does that ask of them?

Accepted Answer

In a typical 10 to 150 person business, the HR manager or operations lead carries the heaviest load — managing configuration, running payroll, and handling exceptions. Department managers interact with it mainly for approvals — leave requests, shift changes, expense claims — which usually takes a few minutes at a time. Employees use the self-service portal for their own requests, payslip downloads, and attendance queries, which most pick up without training. Finance involvement is primarily at payroll close — reviewing cost centre entries and reconciling ledger postings. Most businesses find that one person can own the system operationally without it becoming a full-time role.

Question 7

We are planning to grow from 30 to 80 employees over the next two years. Will we need to reconfigure everything as we scale?

Accepted Answer

The system is designed to grow without requiring structural rebuilds. Adding employees means assigning them to existing salary structures, leave policies, and shifts — all of which can be done in bulk through the relevant control panels. New departments or cost centres can be added as they form, and approval hierarchies update as your reporting lines change. The areas that typically need revisiting as you grow are tax configuration — if you cross into new state or regional jurisdictions — and shift management, if your workforce model changes significantly. Neither requires starting from scratch; they are configuration updates to an existing working system.

When your people ops run the way your business needs

Leave approved without chasing anyone

Every employee record in one place

Payroll costs known before month closes

Compliance posture clear without last-minute scrambles

HR process survives when key people leave

New hires onboard without reinventing the process

Headcount grows, software cost stays flat

Payroll accuracy not tied to one person

Ownership was always the serious choice

Flat Cost Structure

No Renewal Pressure

Your Data, Your Server

Full Portability

Configuration Rights

Vendor Independence

Owning your software isn't a radical idea!

Your business equipment

Your software infrastructure

What running HR actually looks like, day to day

Employee checks leave balance without asking anyone

Leave request moves through approval without reminders

Manager sees team availability before scheduling anything

Payroll runs without last-minute reconciliation work

Salary costs tracked by department, not just total

New HR hire finds everything already documented in the system

Every HR function your business needs, where it belongs

People & Records

Attendance & Shifts

Leave Management

Payroll & Compensation

Tax & Compliance

Reporting & Visibility

Built around how your industry actually operates.

The people who feel HR and payroll most directly

Business Owner

HR Manager

Finance Manager

Department Manager

Team Member

Our Process

Fit conversation

Discovery & Research

Proposal and approval

Configure and Build

Training and handover

Support & documentation

What comes with every deployment

Consultation and configuration

Integrations scoped and built

Optional yearly support contract

... and HR & Payroll is just the beginning

CRM

ERP

Knowledge Base

HR & Payroll

Marketing Automation Tools

Learning Management System (LMS)

Business Insights

Helpdesk

Why businesses run on systems we've delivered.

Common Questions & Answers

We currently track attendance and leaves in spreadsheets. How disruptive is the switch?

Our payroll has different salary structures for different employee types — fixed, variable, and contract. Can the system handle that without becoming complicated?

What does payroll actually look like on the day we run it — how long does it take and who needs to be involved?

Our team includes employees on shift rosters — some rotating, some fixed. Can the attendance system handle that without manual workarounds?

What happens to our HR data if we need to change how something is configured after go-live — like updating a leave policy or revising a salary component?

Which members of our team actually need to use this system regularly, and what does that ask of them?

We are planning to grow from 30 to 80 employees over the next two years. Will we need to reconfigure everything as we scale?

Still have questions?

Meet our happy clients

Most good decisions start with one honest conversation.

Resources

Blog

Case Studies