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.

Employee flags
16

Across nine categories and three severities

Account-wide checks
Three

Duplicates and someone terminated still being paid

On the run itself
Recall and cancel

With a line-level audit trail

app.triblockhr.com/payroll/intelligence/flags
The Payroll Issues panel open beside a draft TriblockHR pay run: flags grouped by category with their counts, each raised against a named employee, among them an invalid gross pay, a bank distribution that does not add up to 100 per cent and a timesheet still awaiting approval.

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.

Automated pre-run employee flags
CategoryFlagSeverity
TimesheetsPending timesheetError
TimesheetsMissing timesheetError
TimesheetsRegular hours exceededWarning
Bank accountsMissing bank accountError
Bank accountsInvalid bank account distributionError
Invalid payInvalid gross payError
Invalid payInvalid net payError
TaxesTax category changed in periodWarning
ConfigurationUninsured time off replaced payWarning
Hired and leftHired in periodInfo
Hired and leftTerminated in periodInfo
Employment statusSuspendedInfo
Employment statusOn probationInfo
Employment statusOn contractInfo
PayslipsPayslip dispatch failedWarning
RuntimeRuntime exceptionError

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.

Questions payroll managers ask about the review

What are the sixteen flags?
They’re all named on this page, grouped by their nine categories: timesheets, bank accounts, invalid pay, taxes, configuration, hired and left, employment status, payslips and runtime. Seven are errors, four are warnings and five are information.
Will it stop a run that has errors?
No. It reports what it found, with a severity, and a person decides. A payroll deadline doesn’t move because a warning fired, and a system that blocks on the Friday of a pay week teaches people to work around it. The review guarantees the decision is informed.
What are the three account-wide checks?
Duplicate bank accounts, duplicate NIB numbers, and someone terminated who is still being paid. They look across people, which makes them a different kind of check from the sixteen. None of them can be found by looking at a single record. And each one is a conversation nobody wants to have afterwards.
Can we see what changed since the last run?
Yes. Variance against the previous run shows movements before approval. 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 against the last period.
What happens after approval?
Staged approval carries recall and cancel with a line-level audit trail. Spot something after approving and you can recall it, and every line keeps its own history. Then each territory produces its own filings from the run you approved. That’s what stops a return disagreeing with what was actually paid.

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

Tell us about your payroll

A few details first, so the demo runs on your territories and your size.

Where do you run payroll?

Already running payroll on TriblockHR

  • Bahamasair
  • Bahamas Telecommunications Company
  • National Insurance Board
  • Gilgan Company