Payroll and benefits

Payroll Admin starts with a payroll calendar for the entity, country, currency and pay frequency. A payroll run names the period, pay date, type and current status. Each employee statement belongs to that run and has its own earnings, deductions, tax and employer lines. Reviewing the run together with statements lets the payroll team see which total belongs to which worker and which period.

For a weekly factory cycle, approved timesheets provide the hours context. Payroll Admin compares the current period with the employee population and benefits before preparing statements. A run marked pending approval needs a human decision on the numbers. Posting and recording payment follow as distinct record states, so a period can be reviewed after a correction or delayed payment.

• Schedule. A payroll calendar carries frequency, entity, currency, cutoff days and active state.
• Calculation record. A payroll run groups the period, and pay statements carry the employee result and line details.
• Coverage. A benefit plan defines available coverage; an enrollment records the employee’s tier, contribution and active dates.

Pay statement lines separate earning, pre-tax, post-tax, tax and employer categories. This makes an overtime earning distinguishable from a benefit deduction or withholding line. Tax jurisdictions and tax filings give Payroll Admin a place to track filing authority, due date, amount and status after the payroll period.

Confirm calendar frequency and cutoff rules for each entity. Decide who prepares the run, who approves it and what evidence they must inspect. Map the source of approved hours and benefit elections. If actual money movement happens in a bank or payment provider, agree on the confirmation needed before marking the run and statements paid. Tax filings likewise need a named owner and confirmation reference from the filing authority.

Review access carefully. Payroll Admin manages pay and tax records. HR Business Partner can view pay statements but maintains people records. Employee sees their own pay record under the configured role. The approving person should be identified for every period so the decision is traceable.

Choose a worker with approved overtime and an active benefit enrollment. Follow the employee to the weekly run, inspect their statement, then compare the line categories with the gross, deductions and net amount. Make the reviewer inspect the run’s period, calendar and pay date before approval. Finally, capture the payment confirmation in the team’s payment system and check that the paid state corresponds to that confirmation.

Repeat with a correction run. It should have its own run type and period context so a revised amount is not confused with an ordinary weekly cycle. Use the same employee and calendar to test whether the team can explain the difference.

• Payroll runs for approval — Period totals, calendar, dates and pay date ready for review.
• Active employee register — The current worker population used to check who belongs in the period.

Follow time to pay for the period review and leave request review for absence context.