Eleven Things on a Payslip
Singapore prescribes what a payslip contains, item by item, and there are eleven of them. Two are dates of payment, two are the first and last days of a period, and one is a period that need not be the salary period at all — which makes this the most precisely checkable payroll requirement we have written about.
Where this lands
Of the eleven items a Singapore payslip must contain, our payroll holds seven as fields, derives two from a calendar month, and would need to start capturing two: the date the salary was actually paid, and the overtime period where it differs from the salary period. The itemisation requirement — every allowance and every deduction listed separately rather than totalled — is the one most systems fail and the one we are strongest on. The one that would need a schema change rather than a field is the salary period itself, because ours is a month and the Regulations expressly provide for periods shorter than that.
Most payroll requirements are about arithmetic: a rate, a threshold, a contribution. This one is about a document, and it is unusual in being checkable line by line without knowing anything about the reader's circumstances. The Third Schedule to Singapore's pay slip regulations lists eleven items. Either they are on the payslip or they are not.
Which makes it the ideal thing to hold a payroll system against, and we are going to hold ours against it in public rather than describe the requirement and stop.
The eleven items, and where each one lives here
| The item | What it asks for | In our payroll |
|---|---|---|
| 1. Employer's name | The name on the official register, or the name in which you employed them | One workspace name |
| 2. Trade name | If different from the first | The same one field |
| 3. Employee's name | As on the identity card, work pass or passport | A field on the employee |
| 4. Basic salary | For the period, by reference to the basic rate of pay | A field, with the prorated figure beside it |
| 5. Salary period | Its first and last days | Derived from a calendar month |
| 6. Allowances | With every one itemised where applicable | Separate lines, described and ordered |
| 7. Overtime period | Its first and last days, if it differs from the salary period | The salary month |
| 8. Overtime hours | Hours worked in that overtime period | A field on the payslip |
| 9. Overtime pay | The amount, and the date it was paid | The amount, as a line |
| 10. Deductions | With every one itemised where applicable | Separate lines, statutory and voluntary |
| 11. Net amount | The figure, and the date it was paid | The figure |
Read the right-hand column and the pattern is clear enough to be useful. Amounts are strong. Itemisation is strong. Dates are where it thins out — which is a shape worth recognising, because it is what happens when a payroll engine is built to compute correctly rather than to produce a particular document.
The itemisation requirement is the one to be pleased about
Items 6 and 10 are the ones we would put money on most systems failing, and they are the ones the Regulations are most emphatic about: allowances and other additional payments with itemisation of every allowance or payment, and deductions with itemisation of every deduction. Not an allowances total. Not a deductions total.
Ours are lines. Each carries what kind of thing it is — an earning, a statutory deduction, an employer contribution, a voluntary deduction — a category, a description and an amount, in a deliberate order. The payslip does also carry the two deduction totals, and it carries them as well as the lines rather than instead of them, which is the distinction that matters. A total computed from lines is a summary. A total with no lines behind it is a wall.
A payslip that shows one deductions figure has not saved anybody any space. It has moved a question from the page to a phone call.
The salary period is a month here, and the Regulations do not assume that
This is the one thing on the list that is a modelling decision rather than a missing field, and it is worth being precise about it. A payroll run in our product is a calendar month, per work country, with one run per month. So item 5 — the first and last days of the salary period — is derivable, because the first and last days of a month are not in doubt.
The Regulations, though, contemplate the other case explicitly. Regulation 8 says that if the salary period is one month you give a single pay slip for it, and if the salary period is less than one month you give either a consolidated pay slip covering all the periods not yet slipped, or a separate single slip for each. A semi-monthly or weekly salary period is not an edge case in this instrument; it is one of the two branches.
A month-shaped run cannot express that. Which is a good example of a general point about payroll software: the arithmetic is usually the part that has been thought about hardest, and the period is usually the part that was decided early, quietly, and once.
Two dates of payment, and a status that stands in for them
Items 9 and 11 each end with the same four words: and date of payment. The overtime pay, with the date it was paid. The net amount, with the date it was paid.
Our payroll run knows that it has been paid — paid is one of its four states, alongside draft, calculated and approved — and it holds the moment it was run, the moment it was approved and the moment it was posted to the ledger. It does not hold the moment the money went. So the nearest available answer is when the record's state last changed, which is a fact about the record and not about the payment, and the two diverge the moment somebody marks a run paid on Monday for a transfer that left on Friday.
And a delivery clock nobody has pointed at this
Regulation 7 gives the payslip to the employee on the salary payment date, or where that is not possible within three days, excluding any Saturday, Sunday or public holiday. That is a working-day window, and we already compute working-day windows — the same calendar that skips weekends and public holidays for support deadlines and leave arithmetic. What is missing is not the calendar. It is a salary payment date for it to count from, and something that notices when a payslip has not gone out. Our employees can already collect a payslip without a login, through a token and a PIN; nothing times that against anything.
The overtime period is a period in its own right
Items 7, 8 and 9 are the subtlest part of the Schedule and the easiest to read past. They do not say "show overtime hours and overtime pay". They treat overtime as having its own period, with its own first and last days, its own hours, its own pay and its own payment date — and item 7 applies only if different from each salary period, which is the tell: the drafters expected it to be different, often enough to legislate for.
Ours is a single number of overtime hours on a monthly payslip. Underneath it, the detail is better than that suggests: overtime is recorded per employee per day, with the hours, a reason and an approval decision, and it can be derived from attendance for a whole month at once. So the raw material for an overtime period exists at daily resolution and the payslip carries the sum. On what happens to the money, we have written separately about the multiplication that does not happen, which is a different gap on the same line of the payslip.
The record behind the document
One more layer, because the same instrument prescribes the employee record as well as the payslip, and its fourteen items include one that is easy to miss: hours worked each day, and the duration of any meal break or other break.
We hold the first half properly — a date, a clock-in, a clock-out, a flag for a shift that crosses midnight, and the hours worked. We hold no break of any kind. So a nine-hour span with an hour for lunch and an eight-hour span with none are the same record with a different number in them, and which one it was is not recoverable. The retention rule attached to these records is also its own small piece of drafting — two years from the entry, and a year past the end of employment — and it is a different shape from a fixed number of days.
The nineteen key employment terms, which must be given in writing to anyone serving a continuous period of fourteen days or more, are a similar story one level up. Our employment contract holds the first day, the fixed-term end date and the basic rate of pay as fields, and a free-text terms body where the other sixteen would go — including the two that this article has already shown to matter: the overtime payment period, and the rate of overtime pay.
What AWRA OpsHub does today
- Every allowance and every deduction as its own line, each carrying what kind of thing it is, a category, a description, an amount and an order — with the totals computed from the lines rather than replacing them.
- Basic salary and its prorated figure side by side, so a part-month is visible as an adjustment rather than as an unexplained number.
- Overtime recorded per employee per day, with the hours, a reason and an approval decision, derivable from attendance for a whole month in one pass.
- Attendance with a clock-in, a clock-out, the hours worked and a flag for a shift that crosses midnight, which is the part of a daily record most systems get wrong at the boundary.
- A payslip an employee can collect without a login, through a token and a PIN, so the document reaches people who have no account.
- A dated compensation record, so a change in pay carries the date it took effect rather than overwriting what came before.
- A working-day calendar that skips weekends and the organization's public holidays, already used for deadlines elsewhere in the product.
More we can add to your workspace
- The date the salary was actually paid, held on the run beside the paid state, so the two items that ask for a date of payment have one to print.
- A salary period shorter than a calendar month, with its own first and last days, so a weekly or semi-monthly cycle is a period rather than a workaround.
- An overtime period of its own, with a start, an end and a payment date, for the case the Schedule expects — where overtime is paid on a different cycle from salary.
- Break duration on a day's attendance, so hours worked and hours present are separable on the record that has to show both.
- A registered name and a trading name as two fields, since the Schedule asks for both and treats the second as meaningful only when it differs.
- The key employment terms as fields on a contract rather than prose in a terms body — the working hours, the rest days, the overtime cycle, the overtime rate, the probation and notice periods.
- A payslip delivery window measured in working days from the salary payment date, using the calendar that already exists, with something that notices a slip that has not gone.
Where we point you to a specialist
- We will not tell you which of your employees these Regulations cover. That runs through the Employment Act itself and the definitions in it, which we read no part of for this article — we read the pay slip regulations and stopped there on purpose. Coverage is a question for your employment adviser, and the answer changes what several of these items require.
- We will not print a payslip item we inferred. Several of the eleven carry the words "if applicable", and whether an overtime period differs from a salary period, or whether an allowance exists at all, is a fact about somebody's employment rather than a default a system should choose. Where we have the field we will print it; where we do not, we would rather the document be visibly short than quietly invented.
The first item is a column and a form field, and it closes two of the eleven at once. The fourth and fifth are a column each. The third and the sixth are the interesting ones to scope together, because an overtime cycle and an overtime rate both want to live on a contract rather than be re-entered per run — and a contract with the nineteen terms as fields is the same piece of work that makes the written statement producible instead of typed. The second is the largest and would want a proper conversation first: a salary period that is not a month reaches the run, the payslip, the attendance rollup and the accounting posting.
What we can build for Singapore on top of the standard product
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point for Singapore, not a limit on what AWRA OpsHub can do there. Kenya's eTIMS integration and its maintained payroll engine are in the product because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If an InvoiceNow access point, a CPF engine, a bank or mobile money feed, a statutory return format, a rule specific to how your operation runs, or a link to a system you already have is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
InvoiceNow, Peppol and GST reporting
Sending and receiving structured invoices through a Peppol access point on the InvoiceNow network, invoice data transmitted to IRAS on the schedule your registration date puts you in, and GST returns assembled from the underlying documents rather than from a summary. Worth stating plainly: Peppol is a receiving network as much as a sending one, and the inbound half is the one most implementations leave until last.
PayNow, GIRO and multi-currency banking
PayNow collection matched to the invoice, GIRO files, and multi-currency bank feeds wired into the Payments Register — which is most of the point in a market where the bank account and the operation are usually in different countries.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
Payroll and statutory returns
CPF contributions by age band and residency status, the Skills Development Levy, IR8A submission and IR21 tax clearance for departing foreign employees, computed on live records rather than assembled at year end.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedFour questions, and the first one takes ten seconds
Show me a payslip with five different deductions on it.
What you will probably hear
Either five lines, or one figure and an explanation.
How to read it
This is the fastest real test of a payroll system and it needs no configuration. Itemisation of every deduction is a requirement here, and a single total is not a presentation choice — it is the absence of the underlying records.
What is your salary period, structurally?
What you will probably hear
A month, described as a setting.
How to read it
Ask whether a weekly or semi-monthly cycle is a supported period or a workaround involving two runs. Ours is a month, and we say so. A vendor who has not been asked this before will tell you it is configurable and mean the pay date.
Where is the date the money actually left?
What you will probably hear
A status, or the date the run was approved.
How to read it
Approved, posted and paid are three different events and most systems hold the first two. A payslip item that asks for the date of payment cannot be filled from a state, and the gap only shows up when a run is marked paid on a different day from the transfer.
Does a day's attendance record a break?
What you will probably hear
A description of hours worked.
How to read it
Hours present and hours worked are the same field in most systems, and the record required here asks for the break separately. It is a small column and it is not recoverable retrospectively, which is the only reason it is worth asking about before you buy rather than after.
See the payroll module
Itemised earnings and deductions as lines, prorated basic pay, overtime recorded per day and approved, dated compensation records, and payslips employees collect without a login.
Explore payrollFrequently asked questions
Does your payroll produce a compliant Singapore payslip?
Not as it stands, and the honest answer is item by item rather than yes or no. Seven of the eleven prescribed items are fields today, two more are derivable because our salary period is a calendar month, and two would need capturing: the date the salary was actually paid, and the overtime period where it differs from the salary period. We also have no CPF engine and this article makes no claim about one — the argument here is about the document's contents, which is a separate question from the contribution arithmetic.
Why does the salary period matter more than the missing fields?
Because a field is a column and a period is a model. A payroll run here is a calendar month, one per work country, and the Regulations expressly provide for a salary period of less than one month — with a choice between a consolidated payslip covering the un-slipped periods and a separate slip for each. A month-shaped run cannot represent a weekly or semi-monthly cycle, and changing that reaches the run, the payslip, the attendance rollup and the accounting posting. It is the one item on the list we would want to scope properly rather than estimate.
Are allowances and deductions itemised on your payslip?
Yes, and it is the strongest thing on the page. Each is its own line carrying what kind of thing it is — an earning, a statutory deduction, an employer contribution, a voluntary deduction — with a category, a description, an amount and a deliberate order. The payslip also carries the deduction totals, and it carries them as well as the lines rather than instead of them. The Schedule is emphatic about this: every allowance and every deduction, itemised.
Can you tell us when a payslip has to go out?
The Regulations say on the salary payment date, or where that is not possible within three days excluding any Saturday, Sunday or public holiday. We already compute working-day windows on that exact basis for deadlines elsewhere in the product, so the calendar is not the missing piece — a salary payment date to count from is, and so is something that notices a payslip which has not been sent. Both are in the buildable list rather than the built one.
Does your attendance record meet the employee-record requirement?
Half of it. The record must show hours worked each day and the duration of any meal break or other break. We hold the date, the clock-in, the clock-out, a flag for a shift crossing midnight and the hours worked — and no break of any kind, so a nine-hour span with an hour for lunch and an eight-hour span with none are indistinguishable afterwards. It is a small column, it cannot be reconstructed retrospectively, and that is why it is worth naming rather than leaving to be discovered.
