The whole list, marked honestly

Eleven steps in the order they actually depend on each other, each one saying how long it takes and why it is needed before you start it.

Four questions at the start change the checklist. Say this is your first payroll and a fifteen-minute step disappears entirely.

Real addresses offered while you type, then verified as deliverable against the postal service rather than merely tidied up.

Upload it once and it appears everywhere the company does — the switcher, the sidebar, and every document that carries your name.

Not a shrunken desktop. Every screen is built for a 390-pixel phone first, because that is where a lot of this actually gets done.

Pick the first period and the first pay day; every date after it is worked out for you, including the deadline to approve by.

Money takes business days to move, so every pay date carries the date you have to approve by, worked backwards through weekends and non-banking days.

Salaried staff monthly and hourly staff fortnightly, in the same company.

Every figure opens into the arithmetic behind it, and nothing is submitted until you approve exactly what you were shown.

The whole run — review, the arithmetic behind each number, and the approval — on a phone, with the same password re-entry as anywhere else.

A bonus, a correction or a final pay outside the normal schedule.

A nudge before an approval deadline, and a nudge to your team before an enrolment window closes, so nobody has to chase anybody.

Filed on time from the figures you approved, through a licensed filing partner. Acting as your reporting agent is a status granted by the tax authorities, not something software can assert.

Tax figures come from an authoritative provider under contract. We will never guess at a rate, and a rate we cannot verify is shown as unavailable rather than estimated.

Prepared, filed and delivered to the people they belong to.

People working in more than one state, recorded properly from the start.

What an owner-operator should pay themselves, shown with the reasoning and the sources rather than as a number to take on faith.

The election itself, the deadlines attached to it, and the owner self-pay that has to follow from it.

Choose a plan that fits your budget and headcount, enrol your team, and have the deductions come out of payroll on their own.

Set up through a licensed provider, enrolled from the same screen as everything else, deducted from payroll automatically and reconciled against the ledger.

The owner-only plan, with employee and employer contributions both handled, and the deduction flowing straight through payroll.

Reimburse premiums and medical costs without running your own scheme.

If you already offer benefits, the plan moves with you rather than being rebuilt.

Hours recorded once and carried into the run, with no re-keying and nothing to import.

Nobody can approve their own hours, a rejection has to say what to fix, and hours a pay run has taken stop being editable.

Requests, approvals and balances, with accrual that matches what you actually promised.

For field and site teams: a clock-in that records where it happened, so hours for work done away from a desk are verifiable without a second product bolted on.

Hours attributed to the job they were worked on, and carried into your accounts.

You send an invitation; they fill in their own name, address and emergency contact, and you are told when they are done. The link works once and expires, and it opens nobody else's record.

Set who somebody reports to, and their timesheets go to that person rather than to every administrator. A reporting line that would loop back on itself is refused, and it names the line to change.

A new starter walked through their own first week, without a folder of paperwork.

Documents signed and stored where they belong, rather than emailed round and lost.

Everything about a person, in one place, for as long as you have to keep it.

Salaried, hourly and contract arrangements side by side in one list, each with their own classification and rate. Nothing assumes a company has one kind of worker.

A raise closes the old rate and opens a new one rather than overwriting it, so re-running an old payroll still gives the old answer. The reason is required.

Up to 500 people at a time from a CSV, with a dry run naming the line and column of every problem. If any row is wrong, nothing is written.

Payslips, tax documents, time off and a change of address — done by the person themselves, which is fewer emails for you and faster for them.

Available the moment they exist, and explained rather than merely itemised.

Performance and pay decisions in the same place as the pay itself, rather than in a separate product that has to be reconciled by hand.

Through a licensed money-movement partner. Moving money needs a licence, not more code, and nothing here moves until that is signed.

Unlimited, with 1099s prepared and filed at the end of the year.

Send an invoice and pay a bill without leaving the thing that already knows your books.

Paid in their own currency, with the paperwork their country expects.

Actual employees abroad, not just contractors — the thing every US payroll product tells you to go and buy somewhere else. The architecture carries country packs from the first line of code.

Headcount by every split that changes what is owed, what the pay on file adds up to, and hours recorded against hours approved. Exporting is its own permission.

Registers, contributions, agency payments, bank transactions and year-to-date figures — all of which come out of a completed pay run.

Journals that match your chart of accounts, out of a ledger that already balances.

Accounting, time, and the tools your team is already in.

Every integration we build is built on the same public API you get. If we have not connected the tool you use, you are not stuck waiting for us to.

A bookkeeper who can see payroll but not approve it; a manager who only sees their own team.

So a borrowed open laptop is not enough to pay somebody or change where pay goes.

Handbooks, contracts and forms, filed against the company or one person. Encrypted at rest, served only as downloads, and archived rather than deleted.

Who changed what, when, and from where. It cannot be quietly edited afterwards.

Balance enforced by the database rather than by the code writing to it, in whole cents throughout.

Switch between them without signing out, with nothing shared across the boundary.

Plain answers, including the uncomfortable ones, and a refusal to guess where we are not qualified — worker classification, or whether a threshold applies to you.

On every plan, including the free one.

The same one each time, who already knows your set-up.