By KYN AI Advisory Team — AI implementation specialists, Singapore
An AI agent can prepare payroll: collect the month's inputs, apply the CPF rules, produce a draft payslip for every employee and flag anything unusual. It should not approve the run, release the bank file or file with CPF. Those steps move money and carry legal liability, so a named person does them. The split is simple: the agent computes and checks, the person decides and pays.
What does payroll prep involve?
Payroll for a Singapore SME has six stages. The agent takes stages one to four and part of five. The person keeps the rest.
- Collect inputs. New hires, leavers, salary changes, overtime, unpaid leave, claims, bonuses and allowances for the month.
- Classify wages. Split each pay item into ordinary wages and additional wages, because CPF treats them differently.
- Compute. Apply CPF rates by age and residency status, apply the wage ceilings, and compute net pay.
- Check. Compare against last month and against rules. Flag differences.
- Approve and pay. A person reviews exceptions and approves. The bank file is generated and released.
- File and remit. CPF contributions are paid and records kept.
Which CPF rules does the agent need to apply?
The engine encodes rules as data, with an effective date, so a rate change is a new row, not a code change.
- Contribution rates by age band. For employees aged 55 and below who are citizens or in their third year or later as permanent residents, the CPF Board lists an employer rate of 17% and an employee rate of 20% from 1 January 2026, per the CPF Board employer contribution page. Rates step down in older age bands and differ for first and second-year permanent residents. Do not hard-code one number.
- Ordinary Wage ceiling. The CPF Board states the ceiling reached S$8,000 a month in 2026. See What is the Ordinary Wage ceiling. Contributions on ordinary wages are computed on wages up to that ceiling.
- Additional Wage ceiling. The CPF Board sets this at S$102,000 less the ordinary wages subject to CPF in the year, per What is the Additional Wage ceiling. The agent has to track year-to-date ordinary wages per employee to compute the room left for a bonus.
- Rounding. The CPF Board publishes rounding rules for the employee and employer shares. Encode them exactly and test them, because a one-dollar difference across 40 people becomes a recurring correction.
The agent should refuse to run if the rate table has no row effective for the pay month. A silent fallback to last year's rates is the failure to avoid.
What can the agent check that people miss?
Computation is the easy part. Checks are where an agent earns its cost.
| Check | What it catches | |---|---| | Month-on-month net pay change above a threshold | Typing errors, a missed leaver, a duplicate allowance | | New name on the list with no contract on file | A ghost employee or a missing document | | Leaver still being paid | A missed termination | | Bank account changed since last run | Payment redirection | | Wages near the ceiling | A wrong split of ordinary and additional wages | | Age band or residency change this month | Wrong rate after a birthday or PR milestone | | Claims paid twice (payroll and expenses) | Duplicate reimbursement | | Gross-to-net does not reproduce | A formula or rounding error |
Each flag should name the employee, the field, the old value, the new value and the rule that fired. A reviewer who sees "net pay up 38% against last month; new allowance of S$900 added on the 12th by user X" resolves it in seconds.
What stays with a person?
- Approving the run. Pay is a money movement and an employment obligation. One named approver signs off the final figures.
- Releasing the bank file. The agent generates the file. A person uploads or releases it. Separation of duties: the person who changes bank details does not release the payment.
- Filing and paying CPF. Payment and submission to the CPF Board are done by an authorised person.
- Judgement calls. Whether an allowance is ordinary or additional wage when the contract is unclear, how to treat a termination payment, whether a contractor is in fact an employee. The agent can list the facts. It should not choose.
- Employee questions. A person answers "why is my pay lower this month".
- Anything new. A new type of pay item, a new rule, a new entity. The agent marks it "unclassified" and stops.
Payroll data is personal data. The PDPC governs how Singapore organisations protect it. In practice that means restricted access, logging of who viewed or changed a record, and no payroll data in prompts sent to a service you have not assessed. Row-level security in the database, named accounts and no shared logins are the controls. See security.
How do you roll it out safely?
- Parallel run. For two or three months, run the agent's draft beside your normal process. Compare every employee, every line.
- Fix by class. When a difference appears, find out whether it is a rule error, a data error or a human error. Fix the class, not the single case.
- Golden test set. Keep a set of tricky employees (age band change, PR year change, bonus across the ceiling, mid-month joiner, unpaid leave) and run it before every rules change.
- Cut over with approval. The agent's draft becomes the starting point. The approver still signs.
- Review every rule change. Rates change. Someone owns watching for them and recording the effective date.
What does a draft payroll check look like?
A draft run goes through the same checks every month. Here is an illustrative example for a team of 25.
| Check | Result (illustrative) | Action | |---|---|---| | Headcount against last month | 25 vs 24 | One new hire: confirm contract and start date | | Salary changes | 2 | Confirm approval document for each | | Pay above or below last month by more than a set share | 3 | Explain: bonus, unpaid leave, correction | | Employee missing a bank account | 0 | None | | Leavers in the month | 1 | Confirm last day and final pay | | CPF total against sum of employee lines | Match | None |
The agent produces this list before anyone opens a payslip. The reviewer works down it. Each line closes with a note of who checked it. The payroll owner then approves the run, and the bank file is released by a named person, not by the agent.
Keep the draft and the final run side by side. If the numbers differ, the log shows which change was made, by whom and when.
Where KYN fits
KYN runs payroll for its own business on a CPF engine built to the 2026 rules, with payslips, bank and CPF files, and a journal for the accounting system. The same approach applies to a client build: rates and ceilings as dated data, a draft run, a flagged exceptions list and an approval step. Payroll runs in a cloud account in your name, every action is logged with the actor, and money and filings wait for a named person. See finance systems and security.
The first 14 days are a review of your stack and interviews with your team. A full build ships in under 90 days.
Frequently asked questions
Can an AI agent run payroll end to end?
It can prepare everything up to the approval. It should not approve, pay or file. A named person reviews the flags, signs off and releases the bank file.
Does the agent need to know CPF rules, or does the model?
The rules sit in a dated table that the code applies. The model is useful for reading messy inputs, such as a claim email, and for writing the reason for a flag. It should not do the arithmetic.
What happens when CPF rates change?
You add a row with the new effective date and run the golden test set. Pay months before that date still use the old row, so past runs reproduce.
Checked 30 October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.
