Industries / Finance and business services / Payroll
Calculating pay
Calculating pay is the work of turning hours, pay rates, overtime, premiums and allowances into each person's gross pay, the amount before tax and other deductions, under the law and any union agreement that applies.
4
Milestones achieved, from 1938 to 2016.
2
To watch for: announced, not yet confirmed outside.
2
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
1938
Overtime pay by law
President Franklin Roosevelt signed the US Fair Labor Standards Act on 25 June 1938, effective 24 October 1938, with a maximum workweek of 44 hours in its final form, by the account of the Labor Department's historian. The act now requires pay of at least one and one-half times the "regular rate" for hours over 40 in a week, and the regular rate includes bonuses: in the Labor Department's own example, a $46 production bonus raises a $12-an-hour worker's regular rate to $13 and the pay for a 46-hour week from $588 to $637.
LessonOvertime is figured on the regular rate, so a payroll system that applies it to the base rate alone underpays.
Credit
US Congress; President Franklin D. Roosevelt
1954
Payroll moves to a computer
In February 1954 the British teashop and bakery firm J. Lyons and Co. began calculating its bakery staff's pay on LEO I, a computer it had built for its own office work. The LEO Computers Society calls it "the first payroll and the first major business application on a stored-program computer anywhere in the world". The Computer History Museum notes that Lyons first used LEO to value bakery output and added payroll later, and that a LEO II sold to the steelmaker Stewart & Lloyds ran that firm's payroll.
Credit
J. Lyons and Co.; David Caminer, who designed the Lyons payroll system and led its programming
2010
Queensland Health's failed payroll
On 14 March 2010, after ten aborted attempts, Queensland Health's new payroll system, built by IBM with SAP and Workbrain software, went live and failed; in the words of the later inquiry, employees endured months of hardship and uncertainty. The 2013 commission of inquiry led by Richard Chesterman found that the system that finally worked needed about 1,000 people to process data for each fortnightly pay, estimated it would cost about A$1.2 billion over the following eight years, and said it "may be the worst" failure of public administration in Australia. It found that user acceptance testing had covered only a sample of the system, so defects affecting pay were likely to remain in the parts not tested.
LessonA payroll system has to be tested against real pay scenarios across all its rules before launch, because untested rules fail on real paydays.
Credit
The Queensland Health Payroll System Commission of Inquiry, led by Richard Chesterman
2016
Phoenix fails federal workers
Canada's government set out in 2009, with a budget of $310 million, to replace the 40-year-old system that paid 290,000 employees in 101 departments, and launched Phoenix, a customized PeopleSoft system, in two waves on 24 February and 21 April 2016. Executives had cancelled a pilot in June 2015 because of major defects; of 111 required functions the Auditor General reviewed, 30 were missing at launch, among them retroactive pay, and 20% of the rest had failed testing and were not retested. By June 2017 there were 494,500 outstanding pay requests and $520 million in pay errors, and the Auditor General called the project "an incomprehensible failure of project management and oversight".
LessonThe government's own main lesson, the Auditor General reported in 2026, is to simplify and standardize pay rules before launching a new system.
Credit
The Office of the Auditor General of Canada, Spring 2018 Report 1, as quoted by the House of Commons Public Accounts Committee
Watch for
Phoenix's replacement, Dayforce
Canada plans to move its federal pay from Phoenix to Dayforce software. The Auditor General reported in spring 2026 that the first group, three departments, is planned to move in 2027; that the replacement will cost more than $4.2 billion; and that because the Treasury Board and the unions had not agreed simpler pay rules, Dayforce was being customized with three "cloud extensions" costing almost $4 million a year. On 30 September 2025 Phoenix still had a backlog of over 233,000 pay transactions affecting over 133,000 employees, and in January 2026 the department in charge shortened the move by about three years.
Achieved whenThe first departments have been paid by Dayforce for a full year and the Auditor General or another outside reviewer reports on the accuracy and timeliness of that pay.
Claimed by
Public Services and Procurement Canada, January 2026
Agents that check payroll
Workday said on 13 October 2026 that its Payroll Agent, already in use by customers, will gain an "autopilot" mode that keeps checking payroll and catches problems before payroll runs: for example, it can audit retroactive adjustments, flag anything outside set limits and draft notes to employees for the payroll team to review. Workday plans to offer it to early-adopter customers in early 2027 and says every action an agent takes is logged.
Achieved whenA customer or an outside auditor publishes how many seeded or real payroll errors the agent caught and missed over several pay cycles.
Claimed by
Workday, October 2026
Open
01
Public answer key, one agreement
A public answer key for the pay rules of one Canadian federal collective agreement, such as the Program and Administrative Services (PA) agreement between the Treasury Board and the Public Service Alliance of Canada. It holds at least 500 pay scenarios, each with the correct amount and the article it rests on, covering overtime (Article 28), shift and weekend premiums (Article 27), designated paid holidays (Article 30) and acting pay. Then write the rules as code that passes the key, and publish both.
The briefCredit · unclaimed02
Payroll math with answer keys
An automatically graded test of pay arithmetic built from the worked examples that regulators publish, starting with the US Labor Department's overtime rules in 29 CFR Part 778, where examples end in a dollar figure. Each case is a short pay situation with an exact answer to the cent and the section it comes from. Score AI models and open calculators on it.
The briefCredit · unclaimed
Open 01 · the brief
Public answer key, one agreement
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A public answer key for the pay rules of one Canadian federal collective agreement, such as the Program and Administrative Services (PA) agreement between the Treasury Board and the Public Service Alliance of Canada. It holds at least 500 pay scenarios, each with the correct amount and the article it rests on, covering overtime (Article 28), shift and weekend premiums (Article 27), designated paid holidays (Article 30) and acting pay. Then write the rules as code that passes the key, and publish both.
Why it is still open
The Auditor General reported in spring 2026 that pay rules had not been simplified before the move to Dayforce, so the government is paying for custom extensions to handle them. Two firms say they already turn collective agreements into executable rules: hazeydata.ai says its ACCORD engine covers about 150 federal agreements with more than a million scenarios validated, and Contract-as-Code sells checks of Dayforce, Workday, ADP and UKG results against agreements. Both are their makers' own claims, and neither publishes an answer key that anyone else can run.
Built with what exists
The agreement text on Canada.ca; AI coding agents that write the rules as code and are checked only against the answer key, as in the Note "Code no person read"; a model such as Claude Opus 5.5 to draft scenarios that people then check by hand.
First step
Write 25 overtime scenarios under Article 28 of the PA agreement, with the answers worked by hand.
Done looks like
At least 500 scenarios across at least six pay areas, each signed off by two reviewers with the article cited and released under an open license; rules code that passes all of them; at least one other engine run against the key, with every disagreement published.
Open 02 · the brief
Payroll math with answer keys
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
An automatically graded test of pay arithmetic built from the worked examples that regulators publish, starting with the US Labor Department's overtime rules in 29 CFR Part 778, where examples end in a dollar figure. Each case is a short pay situation with an exact answer to the cent and the section it comes from. Score AI models and open calculators on it.
Why it is still open
A Korean benchmark, KrRubberStamp, has 1,650 automatically graded office tasks that include payroll, but under Korean rules. Hendrika Maclean and colleagues (arXiv, January 2026) tested AI models on cases from a synthetic payroll system, from basic to complex, and found them "unreliable on exact numerical calculation"; their paper links no data. For US pay, the closest published test has ten tasks graded by hand (October 2026), and an open calculator for the federal overtime law covers only the weekly 40-hour rule and says state rules such as California's daily overtime are beyond it. This research found no automatically graded set built from the Labor Department's own examples.
Built with what exists
The text of 29 CFR Part 778 from Cornell's Legal Information Institute; Python; AI models from large to small, since cost per task matters for checks that run every pay cycle (see the Note "The jobs agents repeat").
First step
Turn the example in 29 CFR 778.110 into the first two cases: $588 for 46 hours at $12 an hour, and $637 for the same week with a $46 bonus.
Done looks like
At least 300 cases, each tied to a section of the regulation and checked by two people, graded automatically to the cent; published scores for at least three AI models and one open calculator, with each model run three times to show how stable its answers are.