payroll-operations

Payroll operations

Payroll is the process with the least tolerance for error and the least visibility until it breaks.

Nobody notices it working; everybody notices a late or wrong payment, and trust recovers slowly.

**Payroll tax registration, withholding and filing obligations vary by jurisdiction and change

frequently. Get a qualified adviser or a provider who takes filing responsibility, and confirm

where liability actually sits.**

The calendar is the control

Work backwards from the pay date: funding date, approval, processing cutoff, time-entry deadline,

change deadline. Publish it, and treat the change deadline as real — the alternative is a

correction cycle running permanently alongside the pay cycle.

Bank holidays, month-end, and year-end all move cutoffs. A calendar that was right in January

quietly stops being right, and the first sign is a late funding.

Know what feeds pay, and make the HRIS the source

Every input is a place errors enter: new hires and terminations, pay changes, hours from time

systems, commissions and bonuses, expense reimbursements, benefit deductions, garnishments.

The failure that produces most wrong payments is two systems disagreeing about someone's status —

a leaver still active in payroll, a pay change entered in one place. Identity, employment status,

and pay data should originate in one system and flow outward. Where a feed is manual, it needs a

reconciliation, not a reminder.

Gross to net, and what sits between

Gross pay, pre-tax deductions, taxable wages, withholding, post-tax deductions, net. Understanding

the order matters because it determines what a change actually costs and why a raise produces a

smaller increase than expected.

Employer cost is not gross pay. Employer taxes, benefit contributions, and mandated insurances sit

on top, and a hiring plan built on salary alone understates cost materially.

Garnishments and support orders have legal priority and limits on how much can be taken. They

are one of the few payroll items where getting it wrong exposes the employer directly.

Every new jurisdiction is a registration, not just a line item

Hiring one person in a new state or country typically means registering as an employer there,

withholding under that jurisdiction's rules, filing its returns, and often carrying insurance

specific to it. Remote hires create this quietly, and the cost is usually discovered after the fact.

Track where employees actually work rather than where they were hired. Someone who moved is a

registration question the day they moved.

Corrections, off-cycles, and overpayments

Decide in advance what triggers an off-cycle payment rather than waiting for the next run, because

that decision made under pressure defaults to whatever is fastest.

Underpayments get corrected quickly, and usually should. Overpayment recovery is the harder one

— rules on recovering from future pay vary and are often restrictive, so the practical answer is

usually a written agreement rather than an adjustment made unilaterally.

Reconcile every cycle, and reconcile the year

Payroll register to general ledger, and the sum of the cycles to the annual filings. Reconciling

each cycle takes minutes; reconciling a year of unreconciled cycles at year-end takes weeks and

finds errors too late to correct cleanly.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions

here — what each one is authoritative for, and what you may do with it. Check them before

answering on anything they cover, and cite what you used. Most are free to read and not free

to reproduce; the use note on each is binding.

Never

• Pay from a spreadsheet that has not been reconciled to the system of record.
• Process a change that arrived after cutoff without deciding whether it is an off-cycle.
• Recover an overpayment by unilaterally adjusting the next payment.
• Add an employee in a new jurisdiction without checking what registering there requires.