Who this is for
Office manager or finance lead who prepares payroll inputs each period and wants a second check before submission.
A payroll error: a leaver paid, a duplicate employee line, or hours beyond contract that nobody noticed.
The result
You receive a checker workbook or script that you run on your own payroll input file. It checks hours against contract, rate changes, duplicate employee ids, leavers with hours and missing fields, and lists what it notices for your payroll person to review. We build and test it on synthetic files only and never receive real payroll data.
What is included
- A checker built from your list of checks, as a workbook with formulas or a script you own
- Built and tested on synthetic payroll-style files that we make from your column names
- Checks you choose from: hours against contract, rate change without a note, duplicate employee id, leaver with hours, missing required field, pay above a ceiling you set
- A results sheet that lists each item noticed with its row and the rule
- Rules do the checking: no language model ever sees your file
- A run book for running it yourself
You receive
- The checker workbook or script
- Synthetic test files and results
- Run book
- List of checks and thresholds
What is not included
- Processing payroll, producing payslips or submitting anything to a tax authority
- Receiving, storing or opening real payroll data
- Advice on pay, tax, leave or entitlement
- Decisions about individual employees
- Accounting, tax, audit, legal or financial advice: a named person at your business decides every money question
- Filing, submitting, approving, posting or paying anything in any system
- A statement that your figures are correct, complete or ready for audit
What we need from you first
- The column names of your payroll input file, as text
- The checks you want and your thresholds
- Who will run it. No payroll data of any kind in the first enquiry
Never send passwords, keys, customer records or confidential code in the first enquiry. Secure handover is agreed after scoping.
How we check it is done
- On synthetic files that we plant with at least one problem for every check you chose, every planted problem is listed with the right row and rule; because we plant them, this is a smoke test
- You add 5 problem rows of your own to a copy of a synthetic file and run the checker yourself; it lists all 5 with the right rule
- On a clean synthetic file, false items stay at or under the count agreed in advance
- You run the checker yourself on a synthetic file and get the same results
- The deliverables contain no real payroll data, and the checker sends nothing anywhere
You re-run the acceptance test with the steps we hand over, check the results and sign off in writing. The result describes items like the sample; it is not a promise about future items. Payment follows sign-off.
When we would stop or decline
- You want us to see real payroll files
- You want payroll processed for you
- You need the checks to decide about individual employees automatically
- You want the system to post, send, file or pay by itself, without a person at your business approving each action
Questions
Is this AI?
No. Rules do the checking, and no language model sees your file. It is listed here because it is the safe, checkable form of payroll checking.
Will you process my payroll?
No. We do not process payroll or submit anything to a tax authority.
Do you need a sample payroll file?
No. We write synthetic files from your column names.
Price and terms
£245 · untested offer price. £245 after the agreed acceptance test is passed and you sign off. No payment before sign-off.
This is a new service with no published client results. The price is a starting point we have not yet tested with buyers. Nothing is ordered or charged by the enquiry. The full specification is on the Synthetic Industry catalogue.