Salaries going out on time feels like payroll working. The registrations, returns and records that sit around it are the part an inspection asks about, and they are usually the part nobody owns.
In most growing businesses payroll is judged on one thing: did everyone get paid, on the right day, the right amount. By that measure it usually works. The trouble is that the payment is the visible end of a cycle, and the rest of the cycle is where the exposure sits.
Every payroll run creates statutory obligations — deductions to compute and deposit, returns to file, registers to maintain, records to retain. Those obligations have their own calendar, which is not the same as the salary calendar, and they are frequently owned by nobody in particular.
Three records that must agree
Payroll sits at the junction of three systems that each hold a version of the same numbers:
- The payroll register — what was computed for each employee.
- The accounting ledger — what was booked as cost, as liability and as payment.
- The statutory returns — what was reported and deposited with each authority.
When these three reconcile, a query is answered by producing the reconciliation. When they do not, a query becomes a reconstruction, and payroll reconstructions are unusually painful because they touch individual people, arrears and prior periods.
A difference between payroll and the ledger is almost never an arithmetic error. It is a process that changed and did not reach both sides.
Where it typically breaks
- Inputs that arrive verbally
A roster change, an unpaid day, an advance, a reimbursement agreed in conversation. If it is not in a record, it is in someone's memory, and memory does not survive a query.
- Registrations obtained and then forgotten
Each one creates ongoing filing and record obligations from the date it is granted. Many businesses hold registrations whose recurring requirements nobody picked up.
- Full-and-final settlements handled outside the cycle
Exits are computed separately, often in a spreadsheet, and the statutory treatment differs from a normal month. They are a common source of both under-deduction and disputes.
- Contractors treated as employees, or the reverse
The classification drives the deduction, the return and the liability. Getting it wrong is not discovered until it is examined.
- Arrears and revisions applied without recomputing
A backdated increase changes deductions for prior months, and those corrections have their own reporting.
Confidentiality is a control, not a courtesy
Payroll data is the most sensitive information most businesses hold. It is also, in a small finance team, frequently the least controlled — visible to anyone with access to the accounting system, discussed in shared folders, emailed as attachments.
Restricting access to the people who need it, and separating the person who computes payroll from the person who releases the payment, is the same maker-checker discipline applied everywhere else. It happens to also be the control that prevents the most common payroll fraud.
What a well-run cycle looks like
- Inputs captured in a record, approved by someone who can verify them, before processing.
- A register of every registration held, with the obligations each creates on the compliance calendar.
- Payroll reconciled to the ledger and to the returns every cycle, with differences listed.
- Deductions reconciled to the credit available to employees, not assumed.
- Exits and arrears handled inside the cycle rather than beside it.
- Access restricted, and payment release separated from payment computation.
Where the boundary sits
We operate the payroll cycle, maintain the records and prepare the underlying data for statutory filings. Where a filing, certification or representation is reserved for a licensed professional, that is performed by an independently engaged professional and coordinated through us.