The Step That Cannot Easily Be Undone
Approval is treated as a click and behaves like a commitment. Knowing what your package does at that moment is worth finding out before you need it.
Nobody elseif the person who does this is away
Approval is treated by most people as a click and behaves in most packages as a commitment. It locks the period, enables the filing, produces the payment file and in some products cannot be reversed without help.
The practical lesson in “The Step That Cannot Easily Be Undone” is that payroll depends on a sequence somebody can explain. When a small team reviews what to review for productivity trends for productivity trends, the useful role is to organise time and project evidence before approval, with proportional settings and a clear correction route for employees.
Finding out what yours actually does is a ten-minute job, best done in a month when nothing depends on the answer.
For an outside reference relevant to “The Step That Cannot Easily Be Undone”, consult Remote employment resources. Compare general guidance with the employer’s jurisdiction, contracts and current payroll process.
Why it feels small
Because the work was the keying and the checking, and this is the button at the end. The psychological weight is in the wrong place: the keying is recoverable and this generally is not.
Four or five consequences from one action:
- The period closes.
- Figures become year-to-date.
- The submission becomes available, or is sent.
- Payslips generate.
- The payment file is produced.
What it typically triggers
The period closes. Figures become year-to-date. The submission becomes available or is sent. Payslips generate. The payment file is produced.
Four or five consequences from one action, most of which are visible to other people.
What reversal looks like
In some packages a rollback that undoes the period cleanly. In others a correction in the following period. In others a telephone call to support, and a wait.
The difference between these matters enormously on the day you need it, and not at all before.
Finding out safely
Ask the provider, or test it in a trial environment if one exists. Not by trying it on a live period in the week of a run.
The commonest regret
Approving before checking, because the checking was going to happen afterwards and then did not. The sequence exists to prevent exactly this, and the sequence is what gets compressed.
Approving on somebody else's behalf
A substitute who has followed a written sequence and reached this point should have somebody to ask before pressing it.
This is the one step where "I'll just carry on and hope" is most expensive, and where a five-minute call is cheapest.
The filing that goes with it
In many arrangements approval and submission are coupled, which means an approval made early sends a filing early, and an approval made late sends one late.
Decoupling them is sometimes possible and worth knowing about.
What you are confirming
Not that the figures are right in some abstract sense, but that you have looked at the specific things listed in the previous note and that they are what you intended.
Approval without that is a signature on something unread.
The record it creates
Who approved, when, and what the figures were at that moment. In a single-person payroll this is the only audit trail that exists, which is a reason to let the system record it properly rather than working around it with shared logins.
Shared logins and why they spoil this
If two people use one login, nothing about the approval identifies who did it. The business then has a record that is technically present and practically worthless.
Separate users cost a small amount in most packages and are the cheapest governance a small business can buy.
After approving
Fund, file, and confirm payslips went out. The run is not finished at approval; it is finished when the money has moved and the obligations are discharged.
The pause worth taking
Ten seconds between deciding and clicking, in which the only question is whether anything about this run is unexplained.
Finding out what yours does, safely
Ask the provider directly: what happens when I approve, and what are my options if I need to undo it.
Two questions, one email, an answer that is worth writing into the sequence. The alternative is discovering the answer on the day something is wrong, which is also the day you have least time to absorb it.
The approval nobody recorded
In a one-person payroll the system's own record is the only evidence that anybody reviewed anything. Shared logins destroy it, and so does a deputy using the main person's credentials.
It feels like an irrelevance in a business of fourteen people until the first time somebody asks who authorised a payment, which happens exactly when things have already gone wrong.
What follows it immediately
Fund, file, confirm payslips went. Three steps, all outside the approval screen, all easy to believe are finished because the difficult part is over.
The run is complete when the money has moved and the obligations are discharged, not when the button has been pressed.
The gap worth building in
Key it on one day, approve it the next. The run has to be ready earlier, which is the point: a gap of a night means the approval is made by somebody who has not just spent an hour typing.
Most of what the checks are looking for is visible to fresh attention and invisible to attention that has been staring at the same screens.
The honest reason to care
Because every correction described in the later part of this collection begins with a run that was approved without that ten seconds.