How it works
From a sentence to the next pay run.
Five steps, about an afternoon. The thing you approve at the end is not code. It is the short list of what the app may write to payroll.
- 01Describe itA sentence, or a template you change
- 02Three questionsWhich code, who approves, which sites
- 03See it runningSandbox, on your own employees
- 04Approve the writesThe only way it reaches payroll
- 05DeployOne company, or a provider's whole book
Steps 1 to 3 take minutes. Step 4 is the one a payroll admin signs off, once per app. Step 5 is versioned, so any deploy rolls back as a unit.
The step that matters is the one you approve.
The writes screen
Before anything deploys, you see every path the app has asked for, who approves each one, and whether it can be reversed. Nothing deploys until each line is approved, and an app can never ask for a path that is not on this list.
- Earnings importPayroll admin approves · reversible until the run
- Time entriesManager approves · raw hours only
- DeductionsNot available to apps
What happens on pay day
Entries from an app are staged, not committed. They sit on the pay run where your payroll admin can see them, change them or throw them away. They become real when the pay run is approved, and the audit entry records the app, the version, the payload and the person who approved it.
Overtime, rounding, break rules and taxability are computed by the payroll engine, never by the app. That is deliberate: an app that could do its own overtime math would be a liability.
Every app starts already knowing how you pay people.
Other builders hand you an app and an empty database. Here the record is already there, so there is nothing to integrate and nothing to re-key.
Employee record
Everyone, every location, every status
Pay calendar
Schedules, cutoffs, open and closed runs
Earning and deduction codes
With their taxability and overtime treatment
Tax rules, 50 states
Daily overtime, tip credit, prevailing wage, per diem
Roles and approvals
Managers see their crew, employees see themselves
GL and job costing
Sage, Viewpoint, Dynamics, QuickBooks
Audit trail
Every write, who approved it, how to reverse it
Employee center
Your app appears as a tile, on the web and on a phone
An app is not a separate website nobody logs into.
It mounts inside the product people already use, in the place that matches the job.
A page in the admin console
For the office: full-width, built for a desk and a keyboard.
A tab on the employee record
Credentials, equipment, per diem history: all on the person.
A tile in the employee center
On a computer at the office and on a phone in the field, same tile.
What it will not do
The promise is any HR app connected to payroll, not anything. The boundary is published, on purpose, because a payroll system that can be talked into anything is not one you should trust.
- No app writes deductions or garnishments. Those stay with the engine.
- No app computes its own overtime. It sends raw hours; the engine does the math.
- No app reads another company's data, ever, under any circumstance.
- No app calls the outside internet. It talks to the record and nothing else.
- No app ships without passing the rule checks for the states you operate in.