Payroll · the pre-run review
A payroll that fails is annoying. A payroll that succeeds and is wrong is expensive.
The review that runs before you approve. Sixteen automated flags, three account-wide hygiene checks, variance against the last run, and an audit feed.
Across nine categories and three severities
Duplicates and someone terminated still being paid
With a line-level audit trail

Trusted by the Caribbean’s best-known employers
Airlines, telecoms, utilities, hotels, credit unions and the National Insurance Board itself.

All sixteen, named
Anybody can claim intelligence. Here’s the list, so you can check it. Nine categories and three severities.
| Category | Flag | Severity |
|---|---|---|
| Timesheets | Pending timesheet | Error |
| Timesheets | Missing timesheet | Error |
| Timesheets | Regular hours exceeded | Warning |
| Bank accounts | Missing bank account | Error |
| Bank accounts | Invalid bank account distribution | Error |
| Invalid pay | Invalid gross pay | Error |
| Invalid pay | Invalid net pay | Error |
| Taxes | Tax category changed in period | Warning |
| Configuration | Uninsured time off replaced pay | Warning |
| Hired and left | Hired in period | Info |
| Hired and left | Terminated in period | Info |
| Employment status | Suspended | Info |
| Employment status | On probation | Info |
| Employment status | On contract | Info |
| Payslips | Payslip dispatch failed | Warning |
| Runtime | Runtime exception | Error |
Seven errors, four warnings and five information flags. Every one of the sixteen carries a severity.
The severities do real work. An error is a payslip that will be wrong: no bank account, invalid net pay, a missing timesheet. A warning is a figure that may be right but looks unusual: hours over the regular threshold, a tax category that changed mid-period. Information flags are context: someone hired in the period, someone on probation, someone on contract. Give an approver sixteen equal alerts and they’ll weigh none of them.
Three checks that look across the whole account
A different kind of check from the sixteen. And each one is a conversation nobody wants to have after the fact.
Duplicate bank accounts
Two employees paid into the same account. Sometimes it’s a couple. Sometimes it isn’t. Either way, somebody should know before the payment file is generated.
Duplicate NIB numbers
Usually a data-entry error. Occasionally something else. Always a problem at the contribution return, where it turns up as a rejected schedule long after the run.
Terminated and still being paid
The recovery conversation is the worst one in payroll. Catch it in the review and it’s a correction. Miss it and you’re asking somebody who no longer works for you to give money back.
You can’t find any of the three by looking at one employee, which is why they sit apart from the sixteen. A careful payroll manager runs them by eye once a quarter. Nobody runs them every period.
Variance, mapping gaps and the approval itself
Variance against the previous run
A number that moved gets noticed before it’s approved. Most payroll errors are ordinary. An allowance entered twice. A rate changed on the wrong record. A timesheet counted in two periods. Every one of them shows up as a movement.
Accounting mapping gaps
A pay element with nowhere to post is caught before the export. Long before month-end, when finance asks why the journal doesn’t balance.
An audit feed across the run
What changed, when, and by whom, alongside the checks.
Approval on the run itself
Staged approval with recall and cancel and a line-level audit trail. Approved it, then spotted something? Recall it. And every line carries its own history, so the conversation afterwards is about facts.
Put together, the review answers three questions, in the order whoever runs payroll actually asks them. Is anybody’s pay going to be wrong? Has anything moved that I can’t explain? Will this post cleanly? Everything above answers one of those three.
Then each territory produces its own filings from the run you approved. The C10 in The Bahamas, the S01 in Jamaica, and so on through all six. So a return can’t disagree with what was paid.
Why this is worth more attention than it usually gets
Pre-run checking is the least glamorous thing a payroll system does. It’s also the thing that decides how your month goes.
A failed run announces itself. Somebody sees an error, the run doesn’t complete, and the problem gets fixed before anybody is paid. Those are cheap.
The expensive failures complete successfully. An employee paid on last month’s rate, a bank account entered with a transposed digit, a timesheet counted twice, a contribution computed on the wrong category. The run finishes, the file goes to the bank, the payslips go out. And the error is found by the employee, or by a contribution schedule rejected six weeks later, or by an auditor.
By then you’re past correcting. You’re having a conversation with a person about money, running an off-cycle, amending a return, and in the worst case asking for something back. The amount is almost never what it costs you. The handling is.
What that means for how the checks are designed
Every one of the sixteen points at a specific employee, because “this run looks unusual” is no use to you on a deadline. Every one carries a severity, because sixteen equal alerts get weighed as none. And the three account-wide checks stand on their own, because the costliest errors can’t be seen from any single record. A duplicate account. A duplicate contribution number. Somebody terminated and still being paid.
That’s also why the review sits before approval. We could produce all of this as a report on a completed run. It would be worth a lot less. The same information, arriving after the payment file, is a list of things to apologise for.
Who decides
It does not stop you approving a run
It tells you what it found, with a severity, and a person decides. There’s no gate, and that’s on purpose. A payroll deadline doesn’t move because a warning fired. And a system that blocks you on the Friday of a pay week teaches people to work around it.
The flags that matter most are errors, and an error usually means somebody has to do something before the run is right. Add a bank account. Submit a timesheet. But whether to hold the run, or pay and correct, is a call for the person who’ll answer for it.
What the review guarantees is an informed decision. That’s why approvers keep reading it.
Articles
Further reading
A payroll that succeeds and is wrong is the expensive one
Failure announces itself. Correctness has to be checked.
Read the article ArticleVariance between two pay runs
Which differences are ordinary, and which deserve a look before approval.
Read the article ArticleCatching a statutory change before it reaches a payslip
Rates move on dates, and the date is usually the part that is missed.
Read the articleQuestions payroll managers ask about the review
What are the sixteen flags?
Will it stop a run that has errors?
What are the three account-wide checks?
Can we see what changed since the last run?
What happens after approval?
See it on your own data
Bring a run that gave you trouble. We’ll put it through the review, including the flags you’d rather it didn’t raise.
- The sixteen flags against real-shaped data
- The three account-wide hygiene checks
- Variance against a previous period
- Staged approval with recall and the line-level trail
- SOC 2 Type II attested
- AES-256 at rest
- 99.9% uptime
- Built in The Bahamas
Where to go next
The review guards the run. These are the pages either side of it.
Payroll Intelligence is part of the Payroll module. Statutory rates, ceilings and filing calendars are maintained per territory and published with their sources on each territory page, The Bahamas, Jamaica, Barbados, Trinidad and Tobago, Turks and Caicos and Saint Lucia. Security: AES-256 at rest via AWS KMS, TLS 1.2 and above in transit, SOC 2 Type II attested against the Security criteria with the report available under NDA. See also Core HR, Workforce and Talent · contact.
