Systems We've Built
Working Client Implementation

Payroll Automation

A custom payroll workflow that reconciles Zenoti payroll and attendance exports, surfaces exceptions for human review, handles multiple compensation paths, and turns reviewed data into payroll-ready outputs.

Built for Polish Nail Lounge & Co. to put structure, exception handling, and human verification around a multi-step weekly payroll process.

The Operating Problem

Payroll was not one file, one rule, or one clean handoff.

The weekly process depends on more than a payroll export. Attendance can contain missed checkouts or unusually short shifts. Different roles follow different compensation paths. Front-desk coverage can add another pay component. Cash payroll needs a separate review. The final handoff still has to be organized for the people responsible for payroll and internal records.

O2S built one operating workflow around those moving parts instead of asking an operator to reconcile them across files and notes by hand.

What O2S Built

Two source files become one controlled payroll workflow

The system combines the payroll export with the attendance log, checks for exceptions, gives the operator a place to review or correct them, incorporates additional pay paths, requires pre-submit verification, and generates the outputs used to finish the payroll process.

Payroll Export
Attendance Log
Exception Review
Cash Payroll
Front-Desk Hours
Verification
Process
Outputs
How It Works

The automation handles the math. The operator handles the judgment.

01

Bring in both sources

The production system reads a Zenoti payroll export and the daily attendance log.

02

Compare what happened

Attendance is checked for missed checkouts and suspiciously short shifts that may make reported hours unreliable.

03

Review exceptions

Flagged hours are surfaced for a human to investigate and, when appropriate, override before processing.

04

Handle different pay paths

Cash payroll, commissions, hourly roles and additional front-desk coverage are handled inside the same workflow.

05

Verify before processing

Required review checkpoints keep the Process Payroll action disabled until the operator confirms the necessary checks.

06

Generate the handoff

The reviewed data becomes payroll-processor and internal-record outputs instead of another manual rewrite.

The money moment
The files disagree.
The system does not silently choose a number. It surfaces the exception so a person can review the underlying record before the corrected value reaches the output.
Exception Handling

A discrepancy becomes a review step, not a hidden payroll error.

In the public demo, the payroll export reports 28.50 hours for a sample technician while the attendance log contains a missed checkout. The workflow flags the record. The operator can review it, apply the verified 34.25-hour correction, and then see that corrected value carry into the final payroll output.

Payroll export
28.50 hours
Human-reviewed correction
34.25 hours

All people, rates, hours and amounts in the public demonstration are fictional.

Interactive Demo

Follow the payroll workflow end to end

This public version uses synthetic employees, synthetic pay data and a preloaded sample instead of accepting real payroll uploads. It preserves the operating sequence that matters: reconcile, review, verify, process and produce outputs.

Public demo · synthetic payroll data · no employee informationClick “Load Sample Payroll” to trigger an intentional missed-checkout discrepancy, review the correction, verify the inputs and process the sample payroll.
System Controls

Automation with visible checkpoints

Two-source reconciliation

The payroll export and attendance log serve different purposes and are brought together before processing.

Exception flagging

Missed checkouts and unusually short shifts are surfaced instead of being buried in a final total.

Manual correction

The operator can override a flagged hour total after reviewing the underlying attendance issue.

Multiple compensation paths

Hourly, commission, cash and front-desk coverage logic can coexist in the same controlled workflow.

Pre-submit verification

Required checks keep payroll from being processed before the operator confirms the necessary review steps.

Purpose-built outputs

The same reviewed dataset drives downstream handoffs instead of requiring the numbers to be re-entered for each audience.

Production Outputs

One reviewed dataset, several usable handoffs

The working implementation produces different views for different parts of the payroll process. The public demo previews the same output categories using fictional data.

XLS

Payroll handoff

A clean spreadsheet for the direct-deposit payroll handoff.

XLS

Internal full report

A more detailed internal workbook with corrections, commissions and additional pay components.

TXT

Copy / email summary

A formatted text summary that can be copied or used to prepare the payroll email handoff.

PDF

Cash payroll record

A separate cash-payroll summary for recordkeeping and distribution review.

Human in the Loop

The system does not decide why a time record is wrong.

It identifies the condition that needs attention, gives the operator the context and a correction point, and then carries the reviewed decision forward consistently.

1

System

Reads the two source datasets, calculates the routine pieces and flags conditions that deserve review.

2

Human

Checks the attendance issue, confirms any correction, reviews cash and additional hours, and completes the verification gate.

3

System

Uses the reviewed values to produce consistent payroll outputs for the next step in the process.

Intentional Boundaries

It supports payroll operations without pretending payroll should run unattended.

The implementation is deliberately bounded around review, preparation and handoff.

No silent correction of flagged hours
No automatic payroll submission
No automatic movement of employee funds
No creation of employees missing from the source system
No payroll data stored between browser sessions
What This Demonstrates

The system is payroll-specific. The capability is operational.

O2S took a recurring process with multiple files, exception conditions, different compensation rules, manual review and several downstream handoffs and turned it into one purpose-built operating workflow. That same systems approach can apply anywhere a business is repeatedly reconciling inputs, making controlled decisions and rebuilding the same outputs by hand.

DiagnoseMapBuildControlImplementRefine
Start With the Process

What recurring workflow are you still rebuilding by hand?

Start with the operating problem. O2S can help determine whether the answer is a workflow improvement, automation, AI, a custom internal tool—or something simpler.