Every dollar has a trail.

FairSlip reconstructs what MOM's and CPF Board's published rules say a month should have paid, from a payslip and a roster a worker already has. The same rules read an employer's payroll file the day before payday.

AI reads. Code calculates. You confirm.

Check my pay Check payroll before payday

Worker

after payday

Reconstruct the month from evidence you already have.

Employer

before payday

Catch the difference while it is still free to fix.

One rule engine

MOM's Employment Act rules and CPF Board's published rates, in code

How a figure is arrived at

Documents
A payslip, a roster, the terms you agreed to.
Two readers
Two models from two vendors read the same images, separately.
Established facts
A field counts only if both agreed, or you confirmed it.
Published rules
Code does the arithmetic, and refuses inputs it cannot use.
Money
Every amount keeps the facts it was built from.
Difference
What the rules give, against what reached the bank.

This is the actual path a number takes through FairSlip, and it is the same diagram the worker screen draws with your own figures on it.

Worked examples

Three invented months, run through both engines just now. The third is refused on purpose: its overtime hours were not established, so nothing is calculated for it.

Fictional data. No real worker's document or information appears in FairSlip.

Loading fixtures…