1.2 Payroll Cycle, Stakeholders, and Source Documents
Key Takeaways
- A payroll cycle turns authorized worker, time, compensation, tax, deduction, and banking data into accurate net pay, reports, deposits, and accounting records.
- Source documents control the cycle because they prove who approved the worker, what pay was earned, what deductions apply, and how payment should be delivered.
- IRS Publication 15 ties new-hire payroll setup to Form W-4, employment eligibility verification, name and SSN records, new-hire reporting, and Form W-2 wage reporting.
- Strong payroll operations separate input, approval, calculation, funding, distribution, reporting, reconciliation, and retention responsibilities.
- The FPC often tests the earliest broken step in a process, not only the final paycheck error.
Payroll as a controlled cycle
Payroll is not one calculation at the end of a pay period. It is a controlled cycle that starts when a worker is hired, classified, assigned a pay rate, and connected to tax, benefit, timekeeping, and banking records. The cycle ends only after wages are paid, taxes and deductions are remitted, reports are filed, accounting entries are posted, exceptions are resolved, and records are retained.
For the FPC, think of each paycheck as the output of several upstream decisions. A wrong net pay may be caused by a bad hourly rate, an unapproved bonus, missing overtime hours, a stale Form W-4, a benefit deduction entered as post-tax instead of pre-tax, a garnishment priority error, or a bank account change made without proper verification. Exam questions often describe the symptom and ask for the control point.
Stakeholders and responsibilities
Payroll depends on many groups, but each should own a different part of the evidence trail.
| Stakeholder | Typical payroll role | Common source evidence |
|---|---|---|
| Employee | Provides tax, banking, benefit, and personal data | Form W-4, direct deposit authorization, benefit elections, address updates |
| Manager | Confirms work performed and approves pay inputs | Time approval, overtime approval, bonus authorization, PTO approval |
| Human resources | Maintains employment status and job data | Offer letter, job change, termination notice, leave status |
| Payroll | Calculates, validates, pays, reports, and retains | Payroll register, exception reports, reconciliation files |
| Finance or treasury | Funds payroll and posts accounting | Funding approval, bank file, general ledger mapping |
| Benefits and vendors | Provide deduction and remittance details | Carrier invoices, plan elections, retirement files |
| Tax agencies and courts | Issue legal obligations | tax notices, garnishment orders, child support orders, levy releases |
Segregation matters because payroll data is sensitive and payroll money moves quickly. A small employer may not have enough staff for perfect separation, but the control concept remains: the person who creates a master-file change should not be the only person approving the payroll that uses it, releasing the payment file, and reconciling the bank withdrawal.
Source documents you should recognize
A source document is the original support for a payroll action. It does not need to be paper; an approved workflow record, electronic signature, system timestamp, or vendor file can serve as source evidence if it is complete, readable, secure, and retrievable.
Core employee setup documents include the approved job record, pay rate, employment status, work location, Form W-4, state withholding documents when applicable, direct deposit authorization, and benefit elections. IRS Publication 15 instructs employers to ask new employees for Form W-4, record employee name and Social Security number information, verify work eligibility, report new hires to state registries, and report employee wages on Form W-2 rather than Form 1099.
Recurring payroll documents include timesheets, time-clock exports, work schedules, exception approvals, PTO records, commission files, bonus approvals, retroactive pay calculations, deduction files, garnishment orders, manual check logs, void and reversal records, and payroll calendars. Year-end documents include W-2 support, quarterly Form 941 reconciliations, tax deposit confirmations, fringe benefit valuations, and general ledger tie-outs.
Cycle map
- Set up the worker. Confirm status, identity, tax records, pay rate, location, department, benefits, and payment method.
- Collect pay inputs. Import hours, salary changes, overtime, leave, incentives, adjustments, and special payments.
- Validate exceptions. Review missing punches, negative net pay, unusual hours, large bonuses, duplicate checks, and terminated employees with pay.
- Calculate gross-to-net. Apply earnings, taxable wage rules, withholding, employment taxes, deductions, garnishments, and net pay.
- Approve and fund. Review the payroll register, obtain signoff, create bank files, fund taxes and deductions, and release payments.
- Report and reconcile. Match registers to deposits, W-2 accumulators, Form 941 totals, bank withdrawals, vendor remittances, and GL postings.
- Retain records. Preserve the documents needed to prove the payroll was accurate and authorized.
Payroll example
A manager emails payroll, "Add a $1,200 retention bonus to Jordan's check today." Payroll should not simply key the amount. The correct cycle response is to verify that the bonus is authorized under company policy, identify whether it is supplemental wages for withholding, confirm whether it affects any overtime regular-rate calculation, and make sure the approval is retained with the payroll run. The issue is not whether payroll can type the amount; it is whether the amount is valid, taxable, and supported.
Compliance trap
Do not confuse a payroll register with source evidence. A register proves what the system calculated. It does not prove that the hours were worked, the rate was approved, the deduction was authorized, the bank change was legitimate, or the tax setup was based on a valid withholding certificate. On audit questions, look one step upstream from the register.
How this appears on FPC items
FPC cycle questions usually reward process thinking. If a newly hired employee receives no check, the likely answer may be a missing master-file setup or unapproved time record. If an employee is paid after termination, the issue may be the termination interface or final-pay approval. If a tax notice arrives for a missing deposit, the problem may be calendar control, EFTPS confirmation review, or reconciliation, not only the person who filed the quarterly return.
A clean payroll cycle is built on four habits: require source evidence, review exceptions before release, reconcile after release, and retain support in a way that protects confidential data. Those habits connect core concepts to the later FPC domains on systems, audits, accounting, and administration.
A payroll register shows that an employee received a $1,200 bonus, but no approval record can be found. What is the strongest audit concern?
Which sequence best describes a controlled payroll cycle?
A payroll specialist discovers that one user can create new employees, change direct deposit accounts, approve payroll, and reconcile the payroll bank account. What control issue is most direct?