New apps every month Click through any of them before you spend anything

The pay runHR1 / 8

HR & PortalsPayLive

Payroll

Payroll is the one system where a quiet mistake becomes a very loud problem. This build puts the variance check before the payment rather than after, and then keeps the rest of the employee portal around it, because most pay errors start as an unrecorded contract change, a missed absence or a bank detail nobody chased.

From
$799
Function
28
Roles
4
Users
Unlimited

Next.js · TypeScript · PostgreSQL · Auth.js

Inside the app

What it does out of the box

28 connected functions on one schema, spanning four permission levels. Everything below is in the template before a line of customisation.

The pay run

Gross, net and employer cost, with every line drilling through to the elements that produced it: base, overtime, absence, deductions and contributions.

Variance check before payment

An unexplained variance over the threshold blocks approval. That is the whole reason the screen sits before the payment rather than after it.

Employee self-service

Their payslips, their leave balance, their hours, and the three things waiting on them. Most payroll tickets are questions this screen answers.

Attendance

In, out, hours and location. Hours feed the run for hourly contracts; for salaried staff they are a record of presence and nothing more is claimed.

Leave

Requests, approvals, balances and carry-over at risk, with unpaid and parental leave feeding the pay run rather than being retyped.

Employee records

One record per person carrying its own contract history. A part-time change made in 2024 is still visible years later.

Documents

Contracts, right to work and certificates with expiry dates and per-type visibility. Missing bank details are shown as blocking the first pay run.

Joining and leaving

Onboarding and offboarding as checklists, including the two tasks everybody forgets: equipment return and disabling the accounts.

Benefits and policies

Plans with employer and employee cost separated, and versioned policies where acknowledgement is against the version somebody actually read.

Requests and announcements

An HR help desk aged from when the person raised it, and announcements with per-person read counts and acknowledgement.

Reports

Headcount, turnover, absence and payroll cost by department, with annual leave excluded from absence because counting it makes the number meaningless.

What it is not

It does not calculate statutory tax for any jurisdiction. It holds what your payroll bureau or tax engine returns, and shows its working.

Permissions

Four roles, one build

An employee sees themselves. A manager sees their team, applied on the query rather than by hiding a menu. HR sees every record and runs the payroll. An admin owns the rules. Every level is included.

Employee7 functions

Their own record, and the answers

  • Payslips, P60 and pay history
  • Leave balance, requests and what was approved
  • Policies, benefits and the tools they need
  • Raise an HR or IT request and follow it
  • No sight of anybody else’s pay or record
Preview as an employee
Manager17 functions

Their own team, and only theirs

  • Attendance and leave for their team
  • Approvals, with the reason recorded either way
  • Employee records within their scope
  • Reports for their department
  • No payroll, no documents beyond their scope
Preview as a manager
HR16 functions

Every record, and the pay run

  • The pay run and the variance check
  • Every employee record and its contract history
  • Documents with expiries and blocking flags
  • Onboarding and offboarding checklists
  • Policies, benefits and announcements
Preview as HR
Admin27 functions

Everything, plus the rules

  • Everything HR can do
  • Users, roles and per-manager scope
  • Pay day, leave year and carry-over rules
  • Variance threshold and pay elements
  • An append-only log kept for seven years
Preview as an admin

The build

Every function in the box

28 functions, all of them live in the preview. Nothing on this list is a mockup or a roadmap item.

Access

  • Sign in

Pay

  • The pay run
  • Variance check
  • Payslips and history
  • Benefits

People

  • Overview
  • Employees
  • Attendance
  • Leave
  • Documents
  • Joining and leaving
  • Policies
  • Announcements

Support and admin

  • Employee self-service
  • Tools and links
  • Requests
  • Notifications
  • Reports
  • Users and roles
  • Audit log
  • Settings

What you get

Delivered as a repository, not a login.

Employers of 20 to 3,000 people who want payroll in the same system as their HR records.

  • 19 production functions spanning four permission levels
  • Full source code and PostgreSQL schema in your repository
  • Role-based access control, enforced server-side
  • Immutable audit log written on every change
  • Responsive layouts, usable on a phone, not just resized
  • CSV import and export on every core record
  • Deployment configuration for your cloud account
  • Twelve months of updates, and no per-seat charge ever

Access and evidence

Two people, every time

Payroll fraud and payroll error look identical until somebody checks. The controls that catch both are the same: unusual movements surfaced before the money leaves, and a second person approving what the first prepared.

  • A run cannot be approved by whoever prepared it
  • Variances above 15% must be explained or corrected before approval
  • Net pay is reconciled to a control total before the payment file is generated
  • A bank detail change holds the next payment for 24 hours
  • The employee is emailed whenever their bank details change
  • Employees can see their own record only, enforced at the row level
  • Every rate and element change is versioned and logged

Related

Apps that pair with this one

HR & PortalsSelf-service
Live

Employee Hub

Announcements that require an action, tracked per employee, with reach reporting for managers.

Next.js · TypeScript · PostgreSQL · Auth.js

Explore From $649
FinanceAccounting
Live

Finance Ledger

General ledger, payables, receivables and bank reconciliation on one double-entry schema.

Next.js · TypeScript · PostgreSQL · Recharts

Explore From $849
HR & PortalsTraining
Live

Learning Management

Courses, lessons, quizzes, assignments, a gradebook, live classes, cohorts and certificates, with completion records that survive an audit.

Next.js · TypeScript · PostgreSQL · MDX

Explore From $599

Questions

Payroll, in practical terms

Do I get the source code for Payroll?

Yes. The repository, application code, database schema, migrations, seed data and deployment configuration, is transferred to your organisation on delivery.

Does it file our statutory returns?

No, and this is the most important thing to be clear about. Payroll filing is jurisdiction specific, changes every tax year, and in most countries requires software recognised or accredited by the tax authority. This template calculates and records pay; it does not submit returns. Most clients run it alongside a recognised filing route, and a fitted build wires that up. Talk to your accountant before deciding.

Are tax and statutory rates kept up to date?

Rates live in configuration rather than in code, so they can be updated without a developer. Keeping them current is your responsibility once the code is yours, which is the trade-off of owning software rather than renting it. Ongoing rate maintenance is available as a support arrangement if you would rather not track it.

Why can't whoever prepares the run also approve it?

Because that single control catches both fraud and simple error, and both are expensive and public in payroll. Combined with variance checks that surface unusual movements before the payment file is generated, it is the cheapest protection available.

Can Payroll be changed to match our arrangements?

That is the usual route, and payroll is customised more than most. A fitted build sets up your pay elements, salary sacrifice arrangements, deduction order, pay calendar, payslip design, filing integration, branding and up to two integrations. Budget toward the upper end of the one to three week range.

What does it cost to run?

Hosting only, paid to your own cloud provider, roughly $50 to $200 a month. Payroll data is small but sensitive, so budget for solid backups and restricted access rather than scale.

Want Payroll shaped around your process?

A fitted build adjusts fields, stages, roles and integrations to how your team already works. One scoping call, a fixed price, one to three weeks.