A payroll result is only as sound as the decisions behind it. You must identify who is being paid, which hours and benefits count as wages, which taxes and deductions apply, and when the payment must be available. Those decisions also flow into deposits, reports, records, and accounting entries. This guide builds from worker status and wage rules through paycheck calculations, then follows the results into payroll systems, audits, and the general ledger. Each concept has a specific decision or calculation to practice. Pay particular attention to the difference between gross earnings, taxable wages, disposable earnings, net pay, and employer cost: they often start with the same paycheck but answer different questions.
Core Payroll Concepts
1. Employee or independent contractor
For federal employment tax, worker status depends on the working relationship, not the label on an agreement. The common-law inquiry looks at behavioral control, such as instructions and training; financial control, such as investment, expenses, and opportunity for profit or loss; and the parties' relationship, including benefits and the expected duration of the work. No single fact decides every case. Start by documenting what the business actually controls, then weigh the facts together. A worker may have specialized skills yet still be an employee when the business directs how the work is performed. Classification affects withholding, employer taxes, and wage reporting. If the federal tax result remains genuinely disputed, the worker or business can request an IRS determination on Form SS-8. The current FPC outline identifies both the common-law test and that form as study topics.
Worked example: A designer signs a contractor agreement but uses the company's computer, follows its assigned daily schedule, and receives detailed instructions from a manager. Those facts show substantial control over how the work is done and point toward employee status. Payroll should assess the full relationship before choosing wage treatment. If material facts remain disputed, either party can submit Form SS-8 for a federal tax determination.
Watch the distinction: A signed contractor agreement records the parties' stated intent; it does not override the actual working relationship. Payment by invoice also fails to settle status by itself.
2. Staffing arrangements and status tests
A staffing arrangement has at least two questions: who performs payroll duties, and which businesses bear legal responsibility for the work. The agency may recruit, hire, pay, and issue wage statements while the client controls daily assignments and supervises the worker. Agency payment does not turn the individual into an independent contractor. For federal tax purposes, examine the arrangement and the relevant control facts to identify the responsible employer and reporting duties. For wage and hour purposes, examine the real working relationship separately; an agency and client may both have obligations where they jointly employ the worker. Determine who records hours, who receives corrections, and who ensures overtime is paid. A service contract can allocate tasks between businesses, but it cannot remove a worker's statutory wage rights.
Worked example: A staffing agency pays Maya, and a warehouse client sets her shifts and directs her work. Maya is not a contractor merely because the client does not issue her paycheck. The agency should obtain accurate hours and process pay. The client must assess its own responsibilities for hours and working conditions. Both parties examine whether the actual arrangement creates shared FLSA obligations.
Watch the distinction: Do not use the identity of the check issuer as a complete classification test. Payroll administration, federal tax employer status, and FLSA responsibility require related but distinct inquiries.
3. Exempt and nonexempt work
An overtime exemption depends on the applicable legal criteria, including actual duties and any required method or level of pay. A salary, a managerial title, or a professional sounding job description alone cannot establish one. Begin with the work the employee normally performs: decision authority, discretion, supervision, and the type of tasks matter more than the title. Next check the pay requirements for the particular exemption and the governing federal and state rules. If an employee is nonexempt, record every hour worked and compute overtime from the regular rate for hours above 40 in the fixed workweek, unless a specific rule applies. Salary paid to a nonexempt worker still needs a lawful overtime calculation. For study problems, identify whether straight-time pay already covers the overtime hours before adding a full or half-time premium.
Worked example: A clerk earns a stated $20 hourly equivalent, performs routine data entry, and works 50 hours in one fixed workweek. The job facts give no basis here to assume an exemption. Straight-time pay is 50 × $20 = $1,000. Because that amount already covers all 50 hours, add 10 × $10 half-time premium = $100. Gross pay is $1,100.
Watch the distinction: Calling the clerk salaried does not remove overtime. The decisive issue is whether a specific exemption's duties and pay criteria are met under applicable law.
4. The fixed workweek
The FLSA workweek is a fixed, recurring span of 168 hours: seven consecutive 24-hour periods. It may start on any day and need not match the calendar week or payroll period. For each nonexempt employee, place actual hours into the employer's established workweeks, then identify hours above 40 within each one. Do not average a long week with a short week, even when a biweekly paycheck covers both. Overtime generally uses the week's regular rate, which can include more than the base hourly rate. A special statutory arrangement may have its own rules, so first determine which framework applies. The certified payroll professional guide is useful for further study of complex pay arrangements after you can reliably separate workweeks and compute the regular rate.
Worked example: Assume a nonexempt employee earns $20 per hour, with no other regular-rate earnings. They work 45 hours in week one and 35 in week two. Week one pays 45 × $20 + 5 × $10 additional premium = $950. Week two pays 35 × $20 = $700. Total biweekly gross is $1,650, including five overtime hours despite 80 total hours.
Watch the distinction: Eighty hours over two weeks does not mean there is no overtime. The 35-hour week cannot cancel five hours above 40 in the earlier fixed workweek.
5. Hours actually worked
Calculate wages from compensable time, not just the posted schedule. Time spent working is generally counted even if a supervisor did not authorize it in advance but knew or had reason to know it occurred. Waiting time can be work when the employee must remain available for the employer's immediate needs; a genuinely relieved period can differ. A meal period is unpaid only when the employee is relieved of duties. If calls or tasks interrupt it, determine the time actually worked rather than automatically deducting the scheduled break. Record those hours before testing the workweek for overtime. Managers may enforce scheduling rules separately, but they must not erase permitted work from time records. The Department of Labor's overtime fact sheet confirms that an advance-approval rule does not defeat pay for compensable overtime worked.
Worked example: Luis completes eight scheduled working hours and spends an additional 30-minute meal period answering customer calls throughout. The meal was not duty free, so record 8 hours + 0.5 hour = 8.5 hours worked. At an assumed $20 hourly rate, that is $170 before taxes. If his workweek exceeds 40 hours, test these minutes for overtime too.
Watch the distinction: An unpaid-break code is not proof that no work occurred. Likewise, unauthorized work still enters the wage calculation when the employer permits it.
6. Rounding time records
A time-rounding practice converts recorded punches to a stated increment, such as the nearest five minutes. Apply the same rule to early and late punches, and calculate work time from the rounded entries only when the practice is permissible and neutral in effect. The key audit is not whether a particular day gains or loses minutes; it is whether rounding over time systematically favors the employer by undercounting hours worked. Preserve original punches so payroll can compare them with rounded results and investigate patterns by shift or employee group. Do not let rounding hide work that managers know occurred outside the punch record. When a worker crosses the overtime boundary, even a few minutes can change the premium due, so reconcile actual records and weekly totals before finalizing pay.
Worked example: Assume a consistently applied nearest-five-minute rule and no unpaid break. An employee punches in at 8:02 a.m. and out at 4:58 p.m. The punches round to 8:00 a.m. and 5:00 p.m., giving nine recorded hours. Actual elapsed time is eight hours 56 minutes; compare gains and losses across many shifts to test neutrality.
Watch the distinction: One employee-friendly rounded day does not prove the practice is neutral. A pattern of lost minutes across pay periods calls for review even when the rule looks symmetric.
Reference: [2]
7. Tip credit and wage shortfalls
A tip credit allows an eligible employer to count qualifying tips toward part of an applicable minimum wage obligation, subject to the governing conditions. First identify the worker's covered hours and applicable minimum wage. Multiply those hours by the required hourly amount. Then compare that result with employer-paid cash wages plus tips that may lawfully be counted for the same period. If the sum falls short, the employer supplies the difference. Keep employer cash and customer tips separate in payroll records because their sources, wage tests, and tax handling differ. Eligibility can also depend on notice and the worker's duties, and a more protective state rule may reduce or eliminate the credit. A high-tip day cannot substitute for an accurate period-level calculation under the applicable rule.
Worked example: Assume an applicable minimum of $10 per hour, 40 covered hours, $160 in employer cash wages, and $200 in eligible tips. Required compensation is 40 × $10 = $400. Cash plus eligible tips is $160 + $200 = $360. The employer adds $40, bringing the total to $400, subject to any more protective state requirement.
Watch the distinction: Tips are not employer-paid cash wages. Counting every reported tip without checking eligibility and the applicable wage rule can conceal an employer-funded shortfall.
8. Youth work restrictions
Youth employment rules require separate checks for the worker's age, proposed duties, and work schedule. Some tasks are restricted because of the equipment or hazard involved, regardless of the amount offered for the shift. For younger workers, applicable limits may also depend on school days, hours of day, and the total hours worked. Verify the worker's age and the actual task, including occasional duties or equipment use, before assigning the shift. Then test its proposed hours under federal and any more protective state rules. Permission from a parent or supervisor does not waive a legal restriction. Keep accurate records of assigned and worked time; if prohibited work nevertheless occurred, the employer still needs to address wages owed while correcting the assignment and preventing recurrence.
Worked example: A supervisor offers a minor an extra shift using equipment classified as hazardous for that worker's age. The offered premium pay does not make the assignment permissible, and parental consent does not cure it. Remove the hazardous task. Next evaluate whether the proposed shift hours are otherwise allowed for that age and school schedule before assigning permitted work.
Watch the distinction: Do not treat youth rules as merely an hourly cap. A minor can be within permitted hours yet still be barred from a particular hazardous task.
Reference: [2]
9. Who owes each employment tax
Separate taxes withheld from employee wages from taxes the employer pays in addition to wages. Federal income tax withholding comes from the employee's taxable wages using Form W-4 information and the applicable withholding method. Social Security and Medicare generally have employee and employer portions under FICA. For 2026, the Social Security rate is 6.2% for each side up to the annual wage base, while Medicare is 1.45% for each side without that wage base. Employer FUTA, when applicable, is not an employee deduction. Build each liability from its proper taxable wage base before calculating the paycheck; benefit deductions can affect those bases differently. The IRS 2026 Employer's Tax Guide supplies the stated FICA rates and wage base, while each employee's withholding information determines income tax withholding.
Worked example: Assume $1,000 of current wages are fully subject to 2026 Social Security and Medicare, with the employee still below the Social Security wage base. Employee withholding is $1,000 × 6.2% = $62 and $1,000 × 1.45% = $14.50, totaling $76.50. The employer owes another $76.50 in matching FICA. Federal income tax and any FUTA require separate calculations.
Watch the distinction: Do not subtract the employer's matching FICA or FUTA from employee net pay. Those amounts increase employer cost; they are not employee withholding.
10. Federal withholding methods
Federal income tax withholding depends on the taxable wages for the payroll period, the employee's Form W-4 entries, pay frequency, and the chosen permitted method. Wage-bracket and percentage methods organize the calculation differently, but neither authorizes using an arbitrary flat percentage for ordinary wages. An annualized method translates period wages and Form W-4 adjustments into annual terms, computes annual withholding under its table or formula, and divides back by the number of pay periods. Apply any additional per-paycheck withholding requested on Form W-4 at the correct stage. Keep rounding consistent with the supplied method. If a practice problem supplies a table value, use that value rather than guessing tax brackets. Check whether the value is annual or per period before dividing, and whether a change in pay frequency requires a fresh calculation.
Worked example: Assume a simplified annualized table produces $4,200 of annual federal income tax withholding for a worker paid in 26 equal periods, with no extra Form W-4 withholding. Per-period withholding is $4,200 ÷ 26 = $161.53846, rounded to $161.54. Withholding $161.54 in all 26 periods would total $4,200.04 because each paycheck is rounded.
Watch the distinction: Do not divide an annual result by 12 merely because wages are quoted monthly when the employee is paid biweekly. Pay frequency controls the period conversion.
11. Work across state lines
Cross-state payroll begins with facts, not a single address field. Record where the employee physically performs services, where they reside, and which business entity employs them. For income tax withholding, determine whether the work state taxes the wages, whether the residence state also requires withholding, and whether reciprocity or a credit mechanism changes the result. Employer nexus can create registration and withholding obligations even when the business has no traditional office in a state. Unemployment insurance uses its own jurisdiction rules, often examining localization of services before other factors. State wage-payment and leave rules may also follow different connections. Keep these questions separate in the payroll setup; a correct income tax state code does not automatically establish the correct unemployment account or wage-law treatment.
Worked example: A worker lives in State A and performs all current services at a site in State B. Payroll first records State B as the physical work location. It then checks both states' withholding rules and any reciprocity arrangement, plus the employer's registrations. For unemployment insurance, it applies the relevant localization sequence rather than assigning State A solely because that is the home address.
Watch the distinction: Residence alone does not settle every state payroll obligation. Work location, nexus, reciprocity, and unemployment localization can point to different questions and potentially different jurisdictions.
Reference: [2]
12. Retirement deferrals and tax wages
A traditional qualified retirement deferral changes some wage bases but does not eliminate the employee's compensation. For a typical traditional 401(k) elective deferral, subtract the contribution when determining wages subject to federal income tax withholding, while generally retaining it in Social Security and Medicare wages. The amount also reduces cash available for the paycheck because it is directed to the plan. Establish the gross wage first, confirm the deduction is a valid traditional deferral, then calculate each tax base separately. Roth contributions have different income tax treatment, so the plan election matters. Annual contribution limits and any catch-up rules are separate compliance checks; do not infer them from a single paycheck. A clean register shows gross earnings, the deferral, each taxable wage base, taxes, and resulting net pay.
Worked example: An employee earns $1,000 and elects a $100 traditional 401(k) deferral. Assume no other taxable items or pretax deductions. Federal income tax withholding wages are $1,000 − $100 = $900. Social Security and Medicare wages remain $1,000. The employee receives no cash for the deferred $100, so it must also be accounted for when net pay is calculated.
Watch the distinction: Do not remove a traditional 401(k) deferral from every tax base. Its federal income tax treatment and FICA treatment differ.
13. Imputed benefit income
Some employer-provided benefits create taxable compensation even though no money is handed to the employee. Payroll records this as imputed income. First identify the benefit and the valuation rule that applies; for excess group-term life insurance, the taxable cost is determined from the applicable table. Then subtract any qualifying employee contribution made with after-tax money to find the taxable value. Add that value to the tax bases to which the benefit is subject, and calculate associated withholding. Do not add the imputed amount to cash disbursed. The timing of recognition also matters: a monthly benefit value must be placed in the appropriate payroll periods and year-to-date totals. Treating imputed income as a separate earning code helps reconcile taxable wages, tax withholding, and the unchanged cash paid to the worker.
Worked example: Assume the applicable monthly table values an employee's excess group-term life coverage at $12, and the employee pays $4 toward that coverage after tax. Imputed income is $12 − $4 = $8. Add $8 to the applicable taxable wage bases for the month. The employee does not receive an extra $8 in cash; any additional withholding reduces cash otherwise payable.
Watch the distinction: Do not equate taxable wages with cash wages. A benefit can increase reported wages and taxes while adding nothing to the employee's deposit.
14. Health coverage reporting
Health coverage affects payroll deductions and employer reporting through different processes. A qualifying employee premium paid through a Section 125 cafeteria plan generally reduces applicable federal income tax and FICA wage bases, subject to the plan and coverage details. That deduction does not itself establish what coverage was offered, to whom, or for which months. An applicable large employer must gather offer and coverage information for its applicable ACA reporting, including employee statements on Form 1095-C and the Form 1094-C transmittal. Payroll, benefits, and HR records should agree on employee identity, coverage periods, and contribution amounts, but each record answers a different question. Check the benefit election's effective date before reducing wages, and preserve separate data showing the employer's offer even when an employee declines coverage.
Worked example: An applicable large employer offers health coverage, and an employee elects a qualifying $90 cafeteria-plan premium for one paycheck. Payroll applies the $90 deduction to the relevant wage bases under the plan. Benefits records separately show what was offered and for which months. The employer uses those offer records for applicable Form 1095-C reporting and Form 1094-C transmittal.
Watch the distinction: A premium deduction is not a substitute for ACA offer data. An employee can decline an offer, leaving no deduction while the employer still needs accurate offer records.
Reference: [2]
15. Forms across the payroll year
Choose payroll forms by the purpose of each document and the worker's status. Form I-9 documents employment eligibility verification for an employee; Form W-4 supplies federal income tax withholding information. During the year, the employer reports applicable employment taxes on the appropriate Form 941 series return. After the year, Form W-2 reports employee wages and withholding, with Form W-3 serving as a transmittal where applicable. A genuine independent contractor commonly provides Form W-9 so the payer has identifying information for potential Form 1099 reporting. Form W-9 does not prove contractor status. Other annual forms, including Form 940 for FUTA, have different purposes. Reconcile payroll registers and tax liabilities to periodic returns and annual statements, taking documented adjustments into account, instead of assuming one form's totals must match every other box.
Worked example: A business hires one employee and engages a genuinely independent designer. It collects the employee's Form I-9 and Form W-4 information, includes the employee's wages on applicable Form 941 series returns, and prepares Form W-2. It requests Form W-9 from the designer and evaluates applicable Form 1099 reporting for those service payments rather than issuing a W-2 for them.
Watch the distinction: Form W-9 is an information collection form, not a classification ruling. Giving one to a worker cannot convert an employment relationship into independent contracting.
16. Confidential payroll data
Payroll systems hold bank details, identifiers, compensation, tax data, and sometimes sensitive benefit information. Grant access according to job duties: a manager who approves time need not see deposit accounts, and a payroll processor need not have unrestricted benefits access. Separate permission to request, approve, enter, and release sensitive changes where practical. Keep logs showing the account used, time, prior value, new value, and approval. When an unexpected change appears, contain its effect before the payment file is released, verify the request through an established independent channel, and preserve evidence for investigation. Assess the fields exposed and the governing obligations before deciding on notification. Health information may bring additional privacy requirements, so restrict access according to the employer's actual role and applicable law rather than treating all personnel files alike.
Worked example: A deposit-account change appears after an unfamiliar login, one day before payroll release. Payroll suspends the change, contacts the employee through a previously established channel, and retains login and change logs. It limits access while the incident is reviewed. If benefit or health information was also accessed, the investigation identifies those fields for the appropriate privacy assessment.
Watch the distinction: A successful login does not prove that a bank change was authorized. Verification should use an independent channel, especially when the request itself may be fraudulent.
Reference: [2]
17. When wages become available
A payroll run is complete for wage-payment purposes only when employees can receive their wages under the applicable pay method and deadline. Entering payroll data or transmitting an ACH file is an earlier operational step. In ACH direct deposit, the employer works through an originating depository financial institution, or ODFI; the receiving depository financial institution, or RDFI, credits the employee's account according to the applicable processing schedule. Federal bank holidays can interrupt ordinary settlement timing, so payroll should work backward from the required availability date and meet the bank's submission cutoff. State rules can govern pay frequency, consent, and permitted methods such as check, direct deposit, or pay card. Constructive receipt concerns when wages are made available without substantial restriction, which may differ from when payroll keyed the transaction.
Worked example: A scheduled Friday payday falls on a federal bank holiday. Payroll checks the applicable wage-payment requirement and coordinates an earlier ACH submission with its ODFI so the RDFI can make funds available on the required date. The file creation date alone is insufficient evidence of payment. Payroll verifies the settlement schedule and the employee-facing availability date before release.
Watch the distinction: Do not assume a Friday ACH submission produces Friday access to funds on a bank holiday. Processing, settlement, and wage availability are separate events.
Reference: [2]
Compliance/Research and Resources
18. Disposable earnings for attachments
Disposable earnings are the starting base for many wage-attachment limits. Begin with gross earnings for the relevant pay period and subtract amounts required by law to be withheld, such as applicable taxes. Ordinary voluntary deductions, including many employee-elected benefit deductions, generally do not reduce this base. Next identify the attachment type and its governing limit; the same disposable-earnings figure may be used in different ways for different orders. Calculate the amount available under the relevant cap, compare it with the order's demand, and withhold the lesser amount when that rule applies. Competing orders may require priority analysis before any final deduction. Keep the wage base, legal withholdings, voluntary deductions, cap, and amount withheld visible in the workpaper so the calculation can be checked.
Worked example: Gross pay is $1,000, legally required withholdings total $250, and an elected benefit deduction is $50. Disposable earnings are $1,000 − $250 = $750; the $50 election does not lower that figure. Assume this problem supplies an applicable creditor-garnishment ceiling of 20% of disposable earnings. The ceiling is $750 × 20% = $150, before comparing it with the order's requested amount.
Watch the distinction: Subtracting the voluntary $50 would produce a false $700 base and a false $140 ceiling. Keep legally required withholding distinct from employee-elected deductions.
Reference: [2]
19. Reading an attachment order
An attachment notice tells payroll what obligation exists, which earnings are reached, how much to withhold, when to start, and where to remit. Read those instructions before calculating. Child support, creditor garnishment, federal tax levy, and a National Medical Support Notice do not share one universal formula or priority. A voluntary wage assignment arises from a different source and may be limited by applicable law. For a levy, determine the amount available under its instructions and subtract the specified exempt amount; do not substitute an ordinary creditor-garnishment percentage. For a medical support notice, assess enrollment, coverage, and contribution instructions rather than treating it as a simple cash levy. When more than one order applies, resolve priority and limits using the governing documents and applicable law, then document the sequence used.
Worked example: Assume a federal levy notice says $1,100 is available for the levy and directs payroll to leave $400 exempt. The levy calculation is $1,100 − $400 = $700, subject to the notice's other instructions. A separate medical support notice requires review of benefit enrollment and any employee contribution. It does not automatically create another $700 cash deduction from this paycheck.
Watch the distinction: Do not run every legal notice through the creditor-garnishment worksheet. A levy exemption, support order, and medical support notice each require their own instructions.
Reference: [2]
20. Employment tax deposits
For an ordinary federal employment tax deposit, combine federal income tax withheld from employees with both employee and employer Social Security and Medicare liabilities. The employer share is added because it is owed even though it never reduced employee net pay. FUTA is an employer tax handled under a separate calculation and deposit process. Once the liability is correct, determine the due date from the employer's assigned deposit schedule and any applicable special rule; a quarterly return's filing date is not automatically the deposit date. Reconcile the deposit workpaper to payroll registers and tax liability records so omissions or duplicate amounts are visible. The FPC practice questions can reinforce the distinction between calculating a liability and choosing its deadline, provided each question's stated assumptions control.
Worked example: One payroll has $1,000 of federal income tax withheld, $765 of employee FICA withheld, and $765 of employer FICA. The combined employment tax deposit liability is $1,000 + $765 + $765 = $2,530. Determine when that $2,530 is due from the employer's applicable deposit schedule. Calculate any FUTA liability separately; the Form 941 filing date does not establish this deposit's deadline.
Watch the distinction: A balanced quarterly return does not prove deposits were timely. Filing and depositing are separate duties, with separate schedules and potentially separate penalties.
21. Reporting and identity checks
Start a reporting reconciliation by matching like amounts: the same employee, calendar year, wage definition, and tax category. Add the quarterly Form 941 wage and withholding figures, then compare them with the corresponding annual Forms W-2 and W-3 totals. A difference may reflect a correction, a third-party payment, or a mapping error, so trace it to payroll records before changing a return. Identity checks answer different questions. The Social Security Number Verification Service helps match an employee’s name and Social Security number for wage reporting. Form I-9 documents employment eligibility, while new-hire reporting sends required hire information to the designated state system. Completing one does not complete either of the others. The current FPC content outline includes these distinct reporting and verification tasks.
Worked example: Suppose four quarterly reports each show $10,000 in the same employee wage category. Their annual total should be $10,000 × 4 = $40,000. If the corresponding W-2 total is $39,800, investigate the $200 difference using the quarterly returns and pay register. An SSNVS match would help check the employee’s reporting identity, but it would not explain the wage difference or satisfy Form I-9 and new-hire reporting.
Watch the distinction: A name and Social Security number match does not establish work authorization. It also cannot prove that quarterly tax returns reconcile with annual wage statements.
22. Keeping payroll evidence
A payroll record should let another person reconstruct what was earned, what was paid, and why any later change occurred. For a wage dispute, retain source time entries, edit history, approvals, rate records, calculations, pay registers, and proof of payment. Tax records support wages and deposits reported to the IRS; wage-hour records support hours and pay; leave records support covered leave decisions; and Form I-9 records support employment eligibility verification. These record groups have different governing retention rules, so identify the record’s purpose before assigning a destruction date. Preserve relevant records when a dispute or investigation is open, even if a routine schedule would otherwise remove them. A correction should carry a reason, approval, and link to the original transaction so that the audit trail remains understandable.
Worked example: A worker says last month’s check omitted two overtime hours. Original punches show 42 hours, but an edit reduced the approved total to 40. At a hypothetical $20 regular rate, the missing two hours at time and one-half are worth 2 × $30 = $60 gross. Preserve the punches, edit, approval, original register, and $60 correction record. The corrected register alone would conceal how the shortage arose.
Watch the distinction: Keeping only the final pay register loses the evidence needed to verify hours and explain edits. Retention also depends on the record’s governing rule.
23. Unclaimed pay and compliance notices
An uncashed paycheck remains an outstanding obligation while payroll determines whether the employee can be paid. Reconcile the check against the bank, check for a replacement or stop-payment event, and retain a history of contact attempts. If it remains unclaimed, determine the state whose unclaimed-property rules govern, then follow that state’s dormancy, notice, and remittance process. The employer cannot simply recognize the unpaid wages as income. Treat an agency notice as a separate investigation: identify its tax period, form, amount, response deadline, and whether it alleges a late deposit, late filing, or another issue. A deposit notice concerns when funds were paid; a filing notice concerns when a return was submitted. Payment and filing records resolve those questions, and the same agency letter may require more than one reconciliation.
Worked example: A former employee’s $500 check has not cleared. The register shows $500 issued, while bank activity shows $0 paid, leaving a $500 outstanding item. Payroll verifies the address and checks the governing state’s unclaimed-property process. A separate agency notice cites a late tax deposit; payroll compares its deposit confirmation and liability dates, rather than treating the uncashed check as the explanation.
Watch the distinction: An uncashed check is not a $500 gain for the employer. A timely filed return also does not, by itself, prove a tax deposit was timely.
24. Cross-border worker taxation
Cross-border payroll begins with facts about the person and the work, not a label such as “expat.” Determine where services are performed, the worker’s U.S. tax residency classification, who pays the compensation, and whether a treaty or specific payroll arrangement changes treatment. A U.S. employee assigned abroad may still have U.S. payroll reporting questions even when local taxes also apply. A worker arriving in the United States may be a resident alien or nonresident alien for tax purposes; visa status alone does not settle that distinction. Source and residence can affect income tax withholding, while Social Security coverage may require a separate analysis. Build a timeline because status or work location can change during a year. Record the conclusion and its effective dates before configuring withholding and reporting.
Worked example: Alex, a U.S. employee, works abroad from July through December. Bea arrives on a temporary visa and works in the United States from October. Payroll records each person’s work dates, tax residence facts, payer, and compensation source. It then evaluates applicable treaty and payroll rules separately. Alex’s foreign assignment does not automatically end U.S. reporting, and Bea’s visa does not by itself establish nonresident tax status.
Watch the distinction: Calling someone an expatriate or visa holder is a description, not a withholding decision. Tax residence, work location, and applicable agreements must be assessed separately.
Reference: [2]
Calculation of the Paycheck
25. Gross pay from production work
Piece rates and commissions are ways to earn wages; neither removes minimum wage or overtime checks. First calculate every component earned in the workweek under the plan’s terms. Add piece earnings and earned commission to find gross straight-time earnings, then divide includable compensation by hours actually worked to assess the regular rate. Compare pay with the applicable wage floor for those hours. If a covered, nonexempt employee worked overtime, determine the premium due using the regular rate, rather than assuming the piece price already covers it. Commission timing can require an allocation when the amount becomes known after the workweek. Compensation design matters, but payroll must translate the design into hours, earnings, and wage compliance. The certified compensation professional guide explores broader pay design.
Worked example: A worker completes 100 pieces at $8 each and earns a $200 commission during a 40-hour week. Piece earnings are 100 × $8 = $800; gross earnings are $800 + $200 = $1,000. Dividing $1,000 by 40 hours gives $25 per hour for this week. Compare that amount with the applicable wage requirement. There are no hours over 40 in this example, so no federal weekly overtime premium arises.
Watch the distinction: A high piece price does not prove wage compliance without counting hours. If overtime occurs, the regular rate generally includes earned commissions as well as piece earnings.
26. Bonus in the overtime rate
A nondiscretionary production bonus rewards work under a stated condition and generally belongs in the regular rate for the period it covers. Identify the covered workweeks, allocate the bonus to them, and add the allocated amount to other includable straight-time earnings. Divide by hours worked to obtain the regular hourly rate. When straight-time compensation already covers every hour, including overtime hours, add one-half of that regular rate for each overtime hour to complete the required time-and-one-half payment. If the bonus covers several weeks and was paid later, calculate any additional overtime premium for each affected week rather than assigning the entire bonus to its payment week. Keep the bonus itself in gross pay; the extra premium is a separate amount. Check whether a payment is genuinely excludable before leaving it out.
Worked example: A nonexempt employee works 45 hours at $20 per hour and earns a $90 production bonus for that week. Hourly straight-time pay is 45 × $20 = $900. Includable earnings are $900 + $90 = $990, giving a $22 regular rate over 45 hours. Five overtime hours need an added half-rate premium of 5 × $11 = $55. Gross pay is $900 + $90 + $55 = $1,045.
Watch the distinction: Adding the bonus after calculating overtime understates the regular rate. Paying the hourly rate for all 45 hours covers straight time, but leaves the overtime premium due.
27. Cash wages and reported tips
For a tipped employee, keep three amounts distinct: employer-paid cash wages, eligible customer tips, and any employer make-up payment. Multiply hours worked by the applicable minimum hourly requirement, then compare that requirement with cash wages plus tips that may lawfully count toward it. If the combined amount falls short, the employer makes up the difference. Confirm that the employer’s cash wage itself satisfies the governing cash-wage rule and that any tip credit conditions are met; a more protective state rule may change the result. Tips reported for payroll tax purposes do not become employer-paid cash wages merely because payroll records them. If cash wages are too small to collect all tax due on reported tips, handle the uncollected amount under the applicable reporting process rather than silently treating the tips as cash in the paycheck.
Worked example: Assume an applicable $9 hourly minimum, 30 hours worked, $4 hourly employer cash wages, and $150 in eligible tips. Required compensation is 30 × $9 = $270. The employer pays 30 × $4 = $120 cash; with tips, compensation is $120 + $150 = $270. The shortfall is $0 under these assumptions. The $150 in customer tips still enters the relevant payroll tax analysis.
Watch the distinction: Reported tips are not an extra $150 paid by the employer. Meeting the combined wage amount also does not excuse failure to satisfy separate tip-credit conditions.
28. Separately paid supplemental wages
A separately paid bonus is supplemental wages, but separate payment alone does not guarantee a particular federal income tax withholding method. Determine whether the conditions for the optional flat method are met, including the relationship to regular wages and required prior withholding; otherwise use the applicable aggregate method. The 2026 IRS Employer’s Tax Guide describes the supplemental-wage rules. Federal income tax withholding is only one part of the calculation. Test the bonus for Social Security and Medicare tax, consider any remaining Social Security wage base, and apply other authorized deductions if the facts require them. Calculate each tax on its own base, round as required, and subtract the amounts actually withheld from the cash bonus. Keep employer tax expense outside the employee’s net-pay subtraction.
Worked example: Assume a separately paid $1,000 bonus qualifies for the 2026 optional 22% federal income tax method. It is fully subject to Social Security and Medicare, with no other deductions. Federal income tax withholding is $1,000 × 22% = $220; Social Security is $62; Medicare is $14.50. Total employee withholding is $296.50, so cash bonus pay is $1,000 − $296.50 = $703.50.
Watch the distinction: The 22% method is conditional; it is not the automatic tax rate for every bonus. Employer FICA matching is an employer cost, not another employee deduction.
29. Back pay and wage recovery
Back pay compensates wages owed for earlier work, while overpayment recovery collects money previously paid in excess. Record these as separate transactions so gross wages, withholding, employee cash, and year-to-date balances remain traceable. Determine the back-pay period and any associated rate or overtime correction, then include the resulting earnings in the appropriate payroll treatment. For recovery, establish the amount originally overpaid, the authorization or governing rule, and whether limits on deductions or final pay affect collection. A recovery may require tax adjustments that depend on when the original wages were paid; do not assume every recovery simply reduces current taxable wages. Final-pay timing is a separate question governed by the applicable jurisdiction. The payroll register should show both the wage correction and the recovery, allowing the employee to understand each.
Worked example: An employee earns $1,200 regular pay plus $200 back pay, for $1,400 current gross. Assume the correctly calculated current taxes are $250 and a lawful, authorized $100 recovery is taken from after-tax pay. Cash pay is $1,400 − $250 − $100 = $1,050. The register still reports the $200 back-pay earning; the $100 recovery is separately identified. Check any applicable final-pay deadline independently.
Watch the distinction: Netting a recovery against back pay can hide wages earned and distort tax records. An employer’s claim of an overpayment does not alone establish a permitted deduction.
Reference: [2]
30. Valuing noncash fringes
Some benefits add taxable compensation without adding cash to a paycheck. First identify the benefit and the valuation method that applies. For personal use of a company car, separate business from personal use and determine the taxable value under the selected permissible method. For excess group-term life insurance, use the applicable coverage and cost calculation, then account for any employee after-tax contribution. Add the resulting imputed amount to each taxable wage base that applies to that benefit; wage bases need not always match. Calculate withholding and employer taxes on the adjusted bases, while leaving cash earnings unchanged. Because no cash accompanies the imputed income, the employer must plan how employee withholding will be collected. Preserve the valuation inputs and employee contribution record so the year-end wage statement can be reconciled.
Worked example: Assume the permitted car valuation produces $50 of taxable personal use. Excess group-term life coverage has a $12 applicable table cost, and the employee paid $4 after tax toward that cost. Life-insurance imputed income is $12 − $4 = $8; total imputed income is $50 + $8 = $58. Add $58 to the applicable tax wage bases. Cash earnings do not increase by $58.
Watch the distinction: Imputed income is taxable value, not money handed to the employee. Subtract an after-tax contribution only where the relevant benefit valuation rules allow it.
31. Two kinds of pretax deduction
“Pretax” is incomplete unless you name the tax. A traditional 401(k) elective deferral generally reduces wages used for federal income tax withholding, but remains in Social Security and Medicare wages. A qualifying Section 125 health contribution generally reduces both federal income tax and FICA wage bases. Start with gross compensation, classify each deduction by plan and tax treatment, and build separate wage bases rather than subtracting every deduction from one universal figure. Then apply the relevant tax method to each base. The deductions also reduce cash available for net pay, even when they do not reduce a particular tax base. Check annual contribution limits and any plan-specific eligibility separately; they do not change the basic distinction between income tax and FICA treatment. Keep the bases visible on a worksheet so later reconciliation is possible.
Worked example: Gross pay is $2,000. The employee defers $150 to a traditional 401(k) and contributes $100 to a qualifying Section 125 health plan. Federal income tax withholding wages are $2,000 − $150 − $100 = $1,750. Social Security and Medicare wages are generally $2,000 − $100 = $1,900 because the $150 deferral remains subject to FICA. Both deductions reduce cash pay by $250.
Watch the distinction: Subtracting the 401(k) deferral from FICA wages understates Social Security and Medicare tax. A deduction’s label as pretax does not specify which taxes it affects.
32. Social Security wage-base crossover
Social Security tax applies only to an employee’s covered wages up to the annual Social Security wage base. For each payment, subtract prior-year-to-date Social Security wages from the 2026 base, then tax the smaller of the remaining base and current Social Security wages. If the remaining amount is zero, withhold no further Social Security tax from that employer’s payments for the year. Medicare tax uses its own wage base and has no comparable upper wage limit. Compute it on current Medicare wages even when Social Security withholding has stopped; additional Medicare withholding is a separate question when applicable facts require it. Use the employee’s year-to-date taxable wages, not gross cash or another employee’s history. The employer normally matches the ordinary Social Security and Medicare amounts calculated on its covered wages.
Worked example: An employee has $184,400 in prior 2026 Social Security wages and receives $1,000 more, all subject to ordinary FICA. The $184,500 base leaves $100 taxable for Social Security: $100 × 6.2% = $6.20. Medicare applies to the full $1,000: $1,000 × 1.45% = $14.50. Ordinary employee FICA on this payment is $6.20 + $14.50 = $20.70.
Watch the distinction: Crossing the Social Security base does not exempt the entire paycheck from Social Security tax. It also does not stop Medicare tax on the payment.
33. Withholding from a supplied table
A supplied withholding table is usable only with the wage amount and pay period it was built for. Establish federal income tax withholding wages after deductions that affect that base, then identify the employee’s pay frequency and Form W-4 entries. Follow the specified table or method to find the base withholding amount. If the Form W-4 requests an additional fixed amount per paycheck, add it after the table calculation; it does not change taxable wages. Keep Social Security and Medicare calculations separate because they use different bases and rates. In a timed problem, write down the selected table row and the extra amount before adding them. FPC practice questions can help you rehearse that sequence with supplied table data.
Worked example: Assume the correct table for this employee’s pay frequency and Form W-4 entries gives $175 withholding on $2,000 of applicable period wages. The Form W-4 also requests $20 additional withholding each paycheck. Federal income tax withholding is $175 + $20 = $195. The $2,000 wage base remains $2,000; the extra $20 changes tax withheld, not compensation or the table lookup.
Watch the distinction: Do not subtract extra Form W-4 withholding from wages before using the table. Using an annual or monthly table for a different pay frequency also changes the result.
34. Third-party sick pay coordination
Third-party sick pay creates a coordination problem because a payer other than the employer may issue taxable compensation and withhold tax. Identify who paid the employee, which amounts are taxable, who withheld each tax, and which party has reporting responsibility under the arrangement. Import the information into payroll records for reconciliation without issuing the same cash payment again. Wages and withholding should each appear once in the combined annual reporting picture. Distinguish third-party sick pay from workers’ compensation or another disability payment whose tax treatment may differ. Dates and payer notices matter because they determine which payroll period and year-end statement must include the amount. Reconcile the payer’s statement to the employer’s records before filing, and document who will correct any mismatch.
Worked example: An insurer paid $500 taxable sick pay and reports $38.25 employee FICA already withheld. Payroll records the $500 once for coordinated reporting and credits the reported $38.25 once; $500 × 7.65% = $38.25, consistent with ordinary FICA on these assumptions. The employer does not create another $500 payment. It verifies the arrangement’s reporting and employer-tax responsibilities before closing the period.
Watch the distinction: Recording the insurer’s payment as a new employer paycheck duplicates cash and wages. Ignoring tax already withheld can also double-count employee FICA.
35. Capped involuntary deduction
An involuntary deduction begins with the governing order, not with the amount requested on its face. Identify the type of attachment, the employee and pay period covered, the earnings base specified by its rules, and any priority over competing orders. For many wage attachments, disposable earnings are gross earnings less legally required deductions; ordinary voluntary deductions do not reduce that base. Next calculate the applicable ceiling and compare it with the amount demanded. Withhold the lesser permitted amount, subject to any priority and minimum-protection rules that apply. Record what remains unsatisfied and follow the order’s instructions for remittance and future checks. Child support, creditor garnishment, tax levy, and medical support documents can operate differently, so a limit supplied for one kind of order cannot be carried over to another.
Worked example: Assume disposable earnings are correctly calculated as $800. A creditor order requests $250 from this paycheck, and the problem supplies an applicable $180 ceiling. Compare the request and ceiling: the permitted withholding is the lesser amount, $180. The current unpaid portion of the request is $250 − $180 = $70. Subtract $180 from otherwise available net pay and track the order for subsequent periods.
Watch the distinction: Withholding the full $250 because an order requests it ignores the supplied ceiling. Reducing disposable earnings by voluntary benefits can produce an equally wrong limit.
Reference: [2]
36. From gross to net pay
Net pay is the cash remaining after all employee-side taxes and authorized deductions have been applied once. Begin with gross earnings, including cash compensation and any taxable noncash value needed for tax calculations. Build the tax bases after pretax deductions, calculate withholding, and then return to cash gross for the net-pay bridge. Subtract employee taxes, the cash amount of pretax benefits and deferrals, after-tax voluntary deductions, and permitted involuntary deductions. Do not subtract imputed income as though it were cash paid, and do not subtract an employer-side tax from the employee’s check. A clear worksheet labels each line as an earning, tax-base adjustment, employee deduction, or employer cost. Finally, compare total deductions plus net pay with cash gross and explain any noncash items separately.
Worked example: Assume $2,000 cash gross pay and correctly calculated employee tax withholding of $353. Cash deductions are $100 qualifying health, $150 retirement, and $25 dues. The deductions total $353 + $100 + $150 + $25 = $628. Net cash pay is $2,000 − $628 = $1,372. The check balances because $628 in deductions plus $1,372 net equals $2,000 gross.
Watch the distinction: A pretax deduction reduces a tax base and still reduces cash pay, but it is subtracted only once in the net-pay bridge. Employer taxes never reduce employee net pay.
37. Employer unemployment cost
FUTA is generally an employer tax, so calculate it as payroll cost rather than an employee withholding. For each employee, determine current-year wages subject to FUTA and how much of the federal wage base remains. Tax only the current wages within that base. Apply the federal FUTA rate, then determine the state unemployment credit actually available; the full credit depends on the relevant conditions, including timely state contributions and any credit reduction. The state unemployment wage base and rate are separate from FUTA’s federal base. Record FUTA liability by the relevant period and follow its deposit rules independently of federal income tax and FICA deposits. When a problem explicitly supplies a full-credit assumption, use it; otherwise do not assume every employer’s effective FUTA rate is the same.
Worked example: An employee has $6,500 of prior FUTA wages and earns $1,000 now. The $7,000 federal base leaves $500 taxable this period. Gross FUTA is $500 × 6% = $30. Assuming the full 5.4% state credit applies to these wages, the credit is $500 × 5.4% = $27. Net employer FUTA cost is $30 − $27 = $3; employee net pay is unaffected.
Watch the distinction: Applying FUTA to the full $1,000 ignores the remaining wage base. Treating the $3 as employee withholding confuses employer cost with paycheck deductions.
38. Grossing up employer-paid tax
A net-pay promise means the employer must fund both the cash award and the employee tax it agrees to bear. If an explicitly supplied, applicable combined withholding rate is constant, express cash net as gross multiplied by one minus that rate. Divide the promised net by the after-tax fraction to solve for gross, then check by calculating withholding and subtracting it. Real payroll may use multiple wage bases, progressive withholding, supplemental-wage rules, rounding, and year-to-date limits. In those cases, calculate each tax separately and, if necessary, iterate until the promised net is reached. Employer-side payroll taxes add cost beyond the grossed-up wage; they are not part of employee withholding. Record the taxable gross award and its taxes, not merely the cash the employee receives.
Worked example: Assume a hypothetical award uses a constant 30% combined employee withholding rate and promises $700 cash, with no other deductions. The employee keeps 70% of gross, so gross is $700 ÷ 0.70 = $1,000. Withholding is $1,000 × 30% = $300, and $1,000 − $300 = $700 cash. Calculate any employer-side tax separately from this $1,000 gross.
Watch the distinction: Adding 30% of $700 gives $910, whose 30% withholding leaves only $637. Gross-up divides by the after-tax fraction because tax applies to gross.
Reference: [2]
Payroll Process and Supporting Systems and Administration
39. Effective-dated master data
A pay rate or status change has at least two important dates: when it was approved or entered and when it becomes effective for work performed. Store the authorized effective date in the employee master record, preserve the prior value, and apply each value to earnings in its own period. A late-entered raise may require retroactive pay for work already performed after its effective date. Conversely, applying the new rate to work before that date creates an overpayment. The approval trail should identify who requested, approved, and entered the change, plus the reason and effective date. Before releasing payroll, compare the master file with approved personnel actions and review exceptions around the change date. This same approach applies to transfers, tax status changes, and deductions, though their effective-date rules may differ.
Worked example: An employee works 40 hours in the week before an approved raise and 40 hours in the week after it. The rate rises from $20 to $22 per hour at the start of the second week. Pay is 40 × $20 = $800, then 40 × $22 = $880, totaling $1,680. Using $22 for all 80 hours would pay $1,760, an $80 overpayment.
Watch the distinction: The date someone enters a raise is not automatically its earning date. Applying one current rate to all past hours can overpay or underpay wages.
Reference: [2]
40. Time-system interfaces
A time-system interface transfers source hours into payroll, but a successful file transfer does not prove the hours are complete. Reconcile record counts and total hours, then inspect exceptions such as rejected rows, changed employee IDs, duplicate imports, and overtime hours dropped during mapping. Compare approved source time with imported payroll data before calculating wages. If the totals differ, find the employee-level transaction and correct the import or source as appropriate. Preserve the original file, error log, approval, and correction so the result can be audited. After correction, recompute gross pay using the applicable workweek and rate rules; a two-hour omission may cost more than two straight-time hours if those hours are overtime. Confirm the corrected amount appears once in year-to-date balances.
Worked example: Approved time shows 42 hours in one workweek at $20 per hour, but payroll imported 40. Assuming the worker is nonexempt, the last two hours qualify for time-and-one-half, and there are no other regular-rate adjustments. Correct gross pay is 40 × $20 + 2 × $30 = $860. The imported 40 hours would pay $800, so the interface error creates a $60 gross shortage.
Watch the distinction: A balanced file count can still conceal incorrect hours. Paying the omitted two hours at $20 each would miss the assumed overtime premium and undercorrect the check.
41. Batch count and amount controls
A batch control compares what the source system sent with what payroll accepted. Record count detects a missing or extra row; a monetary control total detects a changed amount. Use both because equal totals can conceal offsetting errors, and equal counts can conceal altered payments. Establish the expected count and total from approved input before the interface runs. After import, compare accepted, rejected, and pending records with that source. A difference is a clue, not a diagnosis: inspect rejection reports and match transactions by employee, earning code, and amount. Also confirm that a one-time payment was not loaded into the wrong pay period. The FPC content outline includes batch processing and totals within payroll systems.
Worked example: Approved input contains 100 one-time payments totaling $50,000. Payroll accepts 99 payments totaling $49,600. The count is short by one and the amount by $400. A single missing $400 payment fits both differences, but it is still a hypothesis. Match source and accepted transaction IDs, locate the rejected or omitted row, correct it, and rerun the controls before release.
Watch the distinction: Treating the $400 difference as proof of exactly one missing $400 payment skips transaction matching. One missing row and another altered amount could produce the same totals.
Reference: [2]
42. Corrections without duplicate pay
An off-cycle correction should change the employee's records by the amount still owed, called the delta. First reconstruct correct gross pay from approved hours, rates, and earning codes. Subtract gross pay already processed for that work. Enter the difference with its own transaction identifier and calculate withholding under the applicable treatment for the correction. Then reconcile year-to-date gross and each affected taxable-wage accumulator to the prior balance plus the correction. A negative delta calls for a separately authorized recovery process; it is not a reason to silently reduce unrelated earned wages. Check the net payment file as well as the gross register, since a correct gross adjustment can still be sent twice. The audit trail should connect the original payment, reason for correction, approval, and resulting payment.
Worked example: An employee received $1,000 gross for a period but should have received $1,120. The unpaid gross delta is $1,120 − $1,000 = $120. Process $120 gross off-cycle, calculate its applicable withholding, and increase year-to-date gross by $120. If prior year-to-date gross was $8,000 including the original payment, the corrected balance is $8,120, not $9,120.
Watch the distinction: Reprocessing the correct $1,120 as a new payment duplicates the $1,000 already paid. A correction must account for the original transaction and update accumulators only by the difference.
Reference: [2]
43. Self-service access
Self-service access should follow the task a user needs to perform. An employee may view pay statements or request a deposit change; a manager may approve time for assigned workers. Those rights do not imply access to tax identifiers, bank details, or other employees' benefit information. Configure permissions by role and, where possible, by the population the role supervises. Sensitive changes need an attributable request, appropriate verification, a recorded approval or system control, and an audit log showing old and new values. A deposit-account change deserves particular attention because it can divert net pay even when gross payroll is correct. Review access after transfers and terminations, and compare change reports with authorized requests before producing the payment file. This links system security to the actual payroll release process.
Worked example: A manager supervises ten employees and must approve their hours. Grant time-approval access for those ten records, without bank-account viewing or editing rights. An employee then requests a new deposit account. Record the request, verify it through the established channel, retain the change log, and confirm the approved account in the payment file before release.
Watch the distinction: A manager's responsibility for a team's hours does not justify broad payroll access. Giving that manager bank-editing rights creates a payment-diversion path unrelated to time approval.
Reference: [2]
44. Production reports and funding
The payroll register shows calculated gross pay, deductions, and net pay by employee. A payment schedule groups the net amounts by payment method and date; a funding file tells the bank or payment provider what to disburse. Reconcile these stages before release. Start with payment counts and net totals, then match employee or payment identifiers and amounts. Account separately for checks, direct deposits, voids, reversals, and any held payments so the comparison uses the same population. A difference can arise from an omitted row, a changed amount, or a file generated before the final payroll calculation. Funding too little delays pay; funding too much may send an unauthorized payment. Preserve the approved register and the final transmitted file so later bank activity can be traced to a specific run.
Worked example: The approved register contains $160,000 in net pay, while the proposed funding file contains $159,500. The file is $500 short. Compare payment IDs and net amounts; suppose one approved $500 deposit is absent. Add that payment through the controlled file process, regenerate the file, and verify its total is $160,000 before release.
Watch the distinction: A file can have the correct payment count and still contain a wrong amount. Reconcile amounts and identifiers as well as counts before treating funding as complete.
Reference: [2]
45. Payroll during an outage
A continuity procedure identifies how payroll can receive authorized inputs, calculate pay, and meet payment timing when a normal system is unavailable. It should name a decision owner, alternate records and communication channels, approval evidence, a secure place for temporary files, and a method to produce and review payments. Manual entries need unique references so they can be recognized when the failed interface returns. The recovery stage is as important as the emergency run: compare paper or alternate-system entries with restored source data, mark items already paid, and process only remaining differences. Keep a record of assumptions made during the outage and resolve uncertain hours or rates from evidence. A temporary method should preserve confidentiality and a usable audit trail even if it has fewer automated checks.
Worked example: The time system fails after a supervisor signs a paper record for ten hours. Payroll enters ten approved hours through its contingency process and records the paper reference. When the interface returns, its ten-hour record is matched to the paid entry and excluded from new earnings. Year-to-date paid hours increase by ten, not twenty.
Watch the distinction: Importing restored time without matching it to emergency entries can pay the same work twice. Recovery requires a source-to-payment reconciliation, not simply restarting the normal interface.
Reference: [2]
46. Testing continuity plans
A continuity plan becomes useful when a realistic test shows that its people, systems, and dependencies can deliver payroll on time. Set a measurable internal objective, such as how long access may be unavailable, and define what successful recovery must produce. Simulate a specific failure, assign the usual roles, and record when each step starts and finishes. Include input approval, calculation, payment-file creation, and reconciliation; restoring a login alone does not show that employees can be paid. Compare actual results with the objective, identify the delayed step, revise the procedure or resources, and retest that failure. A short FPC practice question set can help you rehearse the decision sequence, but operational readiness comes from testing the complete process.
Worked example: A simulated outage has an internal four-hour recovery objective. Payroll access returns after six hours, so the test misses the objective by two hours, or 50% of the allowed time. Logs show that an unavailable backup approver caused the delay. Assign a second qualified approver, update contact instructions, and retest the approval and payment steps.
Watch the distinction: Calling the test successful because the system eventually reopened ignores the stated objective and whether payroll could actually be completed. Measure the full recovery path.
Reference: [2]
Payroll Administration and Management
47. Documented approval workflows
A payroll-changing action should have a visible path from request to approved payment. Identify who initiates a raise or transfer, who has authority to approve it, who enters the master-file change, and who independently checks the result. Record the authorized effective date separately from the date payroll receives the request; wages may have been earned at the new rate before data entry. The reviewer should compare the approved document with the system's rate, earning code, effective date, and first calculated paycheck. Separating request, approval, and entry reduces both accidental errors and unauthorized changes. If an approval is missing, preserve the request and route it to the designated decision maker while assessing when legally owed wages must be paid. A workflow is useful only if exceptions leave evidence.
Worked example: A supervisor requests a $200 increase per pay period without the approval required by company policy. Payroll holds the master-file change and obtains approval. If the approved effective date covers two completed periods, the employee has $200 × 2 = $400 in additional gross wages due. Enter the new rate and process the $400 difference with applicable withholding.
Watch the distinction: Using the date a raise was entered as its effective date can omit earned pay. Use the authorized effective date and calculate any affected prior periods.
Reference: [2]
48. Interdepartmental cutoffs
An interdepartmental agreement makes a payroll handoff predictable. It should identify which team supplies each input, the required fields and approvals, the cutoff, how receipt is confirmed, and who handles exceptions. A cutoff gives payroll time to validate and calculate a run; it does not decide whether an employee earned wages. When information arrives late, distinguish an administrative delay from the underlying effective date and any applicable pay deadline. Determine whether the change can be included safely in the current run, needs an approved off-cycle payment, or requires another documented correction. Track late submissions by source and cause so the agreement can be improved. Payroll, HR, and timekeeping should work from the same pay calendar and escalation contacts, especially around holidays or system outages.
Worked example: An agreement calls for approved changes by noon Tuesday, but HR submits a Wednesday change worth $75 for work already completed. Payroll confirms its effective date and applicable pay timing. If the main run is closed, use the documented exception route to pay the $75 gross difference with applicable withholding, then reconcile the employee's year-to-date wages.
Watch the distinction: A missed internal cutoff does not erase compensation for completed work. It triggers an exception decision about how to pay and record the amount.
Reference: [2]
49. Resolving a pay inquiry
A useful response to a pay inquiry begins with the employee's stated expectation and the specific pay period. Compare the pay statement with approved time, rates, earning codes, deductions, and prior corrections. Identify whether the difference is gross pay, withholding, another deduction, or payment delivery; each has a different remedy. Explain the finding in familiar terms and show the calculation without exposing another worker's data. If wages are short, document the evidence, obtain the needed correction approval, and state when the additional payment will be available. If the calculation is correct, explain the relevant input and give the employee a way to challenge an incorrect source record. Record the case and its resolution so repeated problems can be traced to a process rather than handled as isolated complaints.
Worked example: An employee expected $1,250 gross, but the register shows $1,200. Approved time includes a $50 shift payment missing from the import, so the gross shortage is $1,250 − $1,200 = $50. Confirm the earning code, authorize a $50 gross correction with applicable withholding, and tell the employee its payment date. Keep coworkers' records out of the explanation.
Watch the distinction: Telling the employee only that net pay differs leaves the cause unresolved. First locate the discrepancy in gross earnings, taxes, deductions, or delivery.
Reference: [2]
50. Measuring payroll errors
An error measure needs a defined numerator, denominator, and period. For example, count payments requiring correction and divide by all payments issued in that cycle. Use the same definition over time: including late employee requests in one month but excluding them in another makes the trend misleading. Compare the result with a stated internal target, then group errors by cause, such as late time submissions, incorrect master data, or failed interfaces. The rate tells you how often a problem occurs, while the cause tells you where to intervene. Check the severity as well as the count, since one missed paycheck matters differently from a minor adjustment. After changing a handoff or control, measure later cycles using the same method to see whether the change worked.
Worked example: Eight of 1,000 payments need correction, giving 8 ÷ 1,000 = 0.008, or 0.8%. A hypothetical internal target is 0.5%, so the rate is 0.3 percentage points above target. Six of the eight errors came from late time submissions, or 75% of corrections. Improve that handoff and measure the next cycle consistently.
Watch the distinction: Subtracting 0.5% from 0.8% gives 0.3 percentage points, not 0.3% of payments. Keep rates, percentage-point gaps, and error counts distinct.
Reference: [2]
Audits
51. Segregation and phantom workers
A phantom worker is a person or record receiving payroll payments without a valid employment basis. The control problem is especially serious if one user can create an employee, enter time, approve it, and release funds. Divide these capabilities among roles, or require an independent review where staffing is limited. Compare the active payroll roster with approved HR records, and inspect new hires, reactivations, address changes, and deposit-account changes near payment dates. A flagged record is evidence to investigate, not proof of fraud: a legitimate employee may be missing from a roster because of a data delay. Hold a questionable payment through the appropriate process, verify employment and approved work from an independent source, and document the outcome. Review user access after the case so the same path cannot recur.
Worked example: A payroll user can create workers, approve time, and release deposits. A $1,000 payment appears for a person absent from the approved active roster. Hold that payment, compare the employee ID with HR's authorization and work evidence, and verify any bank change. If no valid employment record exists, investigate the setup and remove the incompatible access combination.
Watch the distinction: A payment absent from the roster deserves investigation, but the mismatch alone does not establish fraud. Confirm source records before deciding whether it is a phantom worker.
Reference: [2]
52. Year-to-date accumulator checks
A year-to-date accumulator should equal its prior verified balance plus current activity and any documented adjustments. Reconcile each relevant measure separately: gross wages, federal income tax wages, Social Security wages, Medicare wages, withholding, and deductions can differ for valid reasons. Use the same pay-date basis and employee population on both sides. If the balance fails, trace earning-code mapping, voids, reversals, off-cycle checks, and imports rather than changing the accumulator to force agreement. A wrong accumulator can distort later wage-base calculations and annual reporting even when the current net paycheck looks correct. Preserve a roll-forward showing opening balance, additions, subtractions, and closing balance. That structure makes a small variance easier to locate and gives an auditor a reproducible explanation.
Worked example: Prior year-to-date gross wages are $9,900. The current approved payroll adds $1,000 and no adjustments, so expected year-to-date gross is $9,900 + $1,000 = $10,900. The system shows $10,800, a $100 shortage. Trace current earning rows and any void or mapping entry for $100 before relying on the balance for later calculations.
Watch the distinction: Changing the displayed accumulator to $10,900 without finding the missing $100 conceals the source error. Reconcile the underlying transactions first.
Reference: [2]
53. Vendor remittance reconciliation
A vendor reconciliation connects payroll deductions and employer contributions with what the plan or benefit provider actually received. Compare the same pay dates, plan, employee identifiers, and contribution types on both sides. A total difference may come from a missing participant row, an incorrect amount, a late file, or a contribution posted to a different period. Start with control totals, then compare individual rows and confirm that cash remitted equals the final accepted file. Keep employee deductions distinct from employer contributions because they may have different accounting entries. For retirement contributions, the administrator QKA guide offers related plan-administration context; payroll's immediate task is to make the deduction and remittance records agree. Document corrections so the employee's pay record and vendor account reflect the same transaction.
Worked example: Payroll records $25,000 of employee retirement deductions for a run, but the vendor accepts $24,750. The shortfall is $250. Employee-level matching finds one $250 deduction absent from the vendor file. Add the supported row through the vendor's correction process, verify acceptance, and reconcile the final $25,000 file and remittance to payroll.
Watch the distinction: Sending the $250 difference without identifying its employee could leave the wrong account funded. Reconcile participant rows as well as the aggregate total.
Reference: [2]
54. Internal payment reconciliation
Internal reconciliation follows payroll output into the systems that fund or record payments, such as treasury and accounts payable. Compare approved payment counts and amounts with the funding schedule using the same payment date, run ID, and payment population. Then match individual payment identifiers to identify omissions, duplicates, changed amounts, and legitimate timing items. A check issued but not yet cleared may explain a bank difference, while a payment missing from the funding file requires action before release. Keep voids and reversals visible rather than netting them silently into a total. The reconciliation should state each variance and its disposition so another person can reproduce it. Equal counts are a useful first check, but amounts and recipients determine whether the approved payroll was funded accurately.
Worked example: Payroll approves 80 payments totaling $100,000. Treasury's funding report also lists 80 payments but totals $99,500, leaving a $500 variance. Row matching shows one approved payment reduced by $500 and no change in count. Correct the funding record, regenerate the report, and verify 80 payments totaling $100,000 before release.
Watch the distinction: Matching the count of 80 payments does not establish that treasury funded the right amounts. A changed payment can preserve the count while creating a shortfall.
Reference: [2]
55. Audit trail after a data incident
After a suspected payroll-data incident, preserve enough evidence to determine what happened while limiting further access. Record when the event was discovered, retain relevant logs and files securely, and restrict the account or transfer path involved. Identify the data fields, affected people, recipients, and whether the export was actually accessed or sent beyond authorized control. Those facts inform the employer's legal and policy assessment; the number of records alone does not determine notification duties. Keep an incident timeline, copies of investigative decisions, and a record of corrective access changes. Avoid altering original logs while reviewing them. Payroll's role is to supply accurate employee and transaction facts, protect ongoing payments, and coordinate with the designated security and legal teams on any required response.
Worked example: An unauthorized export contains 50 employee records. Payroll restricts the account, preserves the export and access logs, and determines that the file includes names and deposit details for those 50 people. The team documents who received it and when, then sends those facts for the applicable notification assessment. The count of 50 is evidence, not a notification threshold.
Watch the distinction: Deleting the export immediately may destroy evidence needed to identify affected people and recipients. Secure it, preserve logs, and follow the incident process.
Reference: [2]
Accounting
56. Classifying payroll accounts
Payroll accounting separates the cost of work from amounts the employer owes after calculating pay. Gross wages are generally a wage expense when earned. Employee tax withholding reduces cash paid to the employee, but it creates a liability to the taxing authority; it does not reduce gross wage expense. Net pay awaiting disbursement is also a liability. In a journal entry, debits increase expenses and credits increase liabilities. When the employer pays employees or remits taxes, the relevant liability is debited and cash is credited. Keep employer payroll taxes in a separate expense and payable account because they are an additional employer cost, not part of employee withholding. Classifying each amount before posting makes the entry easier to balance and prevents a later payment from being mistaken for another expense.
Worked example: Assume gross wages of $1,000, consisting of $700 net owed to an employee and $300 withheld taxes owed to authorities. Debit wage expense $1,000. Credit net-pay liability $700 and tax liabilities $300. Credits total $700 + $300 = $1,000, matching the debit. The $300 is still part of gross wages, although the employee receives only $700 cash.
Watch the distinction: Posting only $700 as wage expense understates labor cost. The $300 withheld from gross wages is recorded as a liability until remitted.
Reference: [2]
57. Recording a complete payroll
A complete payroll entry begins with gross wage expense, then records each employee withholding as a payable and the remainder as net pay owed. Employer payroll taxes add a separate expense and a separate payable. For FICA, the payable includes both the employee amount withheld and the employer match, although only the employer match creates additional tax expense in this entry. Calculate net pay from gross wages less employee withholding before posting. Then check that total debits equal total credits and that the payable balances match the payroll tax register. For a 2026 example using ordinary FICA, assume all wages remain below the Social Security wage base and no other tax adjustment applies. The IRS employer tax guide supplies the federal tax context; the journal-entry structure follows accounting principles.
Worked example: Assume $10,000 gross wages, $1,000 federal income tax withheld, $765 employee FICA, and $765 employer FICA, with no other deductions or taxes. Net pay is $10,000 − $1,000 − $765 = $8,235. Debit wage expense $10,000 and payroll tax expense $765. Credit net pay $8,235, income tax payable $1,000, and FICA payable $1,530. Each side totals $10,765.
Watch the distinction: Crediting only $765 to FICA payable omits either the employee withholding or employer match. The liability holds both until deposit.
58. Clearing tax liabilities
When payroll is recorded, withheld taxes and employer taxes become liabilities. Depositing them transfers cash to the taxing authority and clears those liabilities; it does not create the same expense again. Read the ledger before preparing the deposit entry, and match each payable to the tax period and liability shown on the payroll records. Debit the liability accounts to reduce what is owed and credit cash for the amount sent. If a payment differs from the liability, investigate prior deposits, adjustments, interest, penalties, or an incorrect posting instead of forcing the difference into wage expense. Deposit timing and return filing are separate processes. A balanced deposit entry proves its arithmetic, while a reconciliation to the tax ledger shows whether the right obligations were settled.
Worked example: The ledger shows $1,000 federal income tax payable and $1,530 FICA payable from an earlier payroll. The employer deposits $2,530. Debit income tax payable $1,000 and FICA payable $1,530; credit cash $2,530. Debits equal credits, and both listed liabilities become zero, assuming there were no other balances or adjustments.
Watch the distinction: Debiting payroll tax expense for the $2,530 deposit records a second expense and leaves the original payables open. Clear the accrued liabilities instead.
59. Accruals across accounting periods
Accrual accounting places wage expense in the period when employees perform the work, even if payday occurs later. At period end, calculate unpaid earned wages from approved days or hours and record a debit to wage expense with a credit to wages payable. A reversal at the start of the next period removes that temporary liability and offsets the expense before the ordinary payroll entry is posted. Without the reversal or another explicit clearing method, the same earned wages can appear as expense in both periods. Reconcile the accrual estimate with actual payroll and record any difference in the period when it becomes known under the employer's accounting method. Keep the work dates and payment dates distinct: the former drive the accrual, while the latter drive payroll disbursement and related reporting.
Worked example: Five days of work at $200 per day remain unpaid at month-end. Accrue $1,000 by debiting wage expense and crediting wages payable. Next month, reverse that $1,000, then record regular payroll that includes $1,200 of wages. The next month's net wage expense from these entries is $1,200 − $1,000 = $200; the earlier month retains $1,000.
Watch the distinction: Recording the $1,000 accrual and then the full $1,200 payroll expense without a reversal or clearing entry counts the first $1,000 twice.
Reference: [2]
60. Explaining a clearing balance
A clearing balance is explained by tracing issued payroll payments through the ledger and bank records. Begin with the approved payment register, identify what was posted to cash or clearing, and compare it with transactions the bank has processed through the reconciliation date. An issued check that has not cleared is a timing item if its amount and identifier match an approved payment. A payment posted twice, omitted from the bank file, or entered for the wrong amount is a posting or transmission problem that needs correction. Keep a list of outstanding items and review it in later periods so stale checks receive the required follow-up. A void or stop payment changes the record only when properly processed; today's bank difference does not itself create a new payroll expense.
Worked example: The ledger records $10,200 of issued payroll payments, while the bank has cleared $10,000 by reconciliation date. The $200 difference equals one identified, approved check still outstanding. List that check as a reconciling item; the issued total less the outstanding amount equals cleared payments: $10,200 − $200 = $10,000. Follow it until it clears or is properly voided.
Watch the distinction: Writing off the $200 as an expense merely to match the bank obscures an outstanding payment. Identify the check and retain it on the reconciliation.
Reference: [2]
Official references and further reading
- Fundamental Payroll Certification (FPC) | PayrollOrg
- Current FPC September 2026 knowledge skills abilities
- PayrollOrg issuer-authored 2026?2027 FPC handbook, cohosted by a local payroll chapter
- payroll-irs-2026-p15
- Fact Sheet #23: Overtime Pay Requirements of the FLSA | U.S. Department of Labor