Payroll Compliance Audit: How to Plan, Test, and Report

Posted on
21 Oct 2026
Sand Clock 14 minutes read

Your practice manager asks a simple question after payroll runs, and no one can answer it cleanly. Who approved that remote medical assistant's extra hours, why does the bank funding differ from the register, and could you prove the worker is a contractor if a regulator asked tomorrow? A payroll compliance audit is how you turn those uneasy guesses into documented answers. It isn't a year-end filing check. It's a reproducible test of the controls that produce payroll, from worker status and time records through tax deposits, reconciliations, and year-end reports.

Why a Payroll Compliance Audit Matters Now

A practice owner usually discovers the gap during an ordinary moment. A departing biller questions final pay, a new accountant can't tie Form 941 totals to W-2s, or a remote patient coordinator in Latin America has worked the same full-time schedule for a year under a contractor agreement. None of those situations proves a violation. Each one exposes whether your file can support the decisions you've already made.

That's the right way to frame a payroll compliance audit. You're not hunting for arithmetic perfection. You're testing whether classification, hours, pay calculations, withholding, deposits, and reporting agree with each other and with the records behind them. A useful audit produces conclusions another person could retest from source documents, calculation logic, approvals, and exception evidence.

What a Strong Audit Actually Answers

  • Worker status: Is each person an employee or contractor, and exempt or nonexempt, based on how the work happens?
  • Pay accuracy: Do hours, regular rates, overtime, deductions, and reimbursements recalculate correctly?
  • Tax compliance: Were liabilities reported accurately and deposited on schedule?
  • Evidence quality: Can you retrieve approval, access, and change records without reconstructing them from emails?

Remote staffing raises the stakes because work location, supervision, and payment routing often sit outside the routines built for onsite employees. A scheduler, insurance verification specialist, or prior-authorization assistant may use your systems, follow your scripts, and cover core patient workflows from another state or country. That arrangement can work well, but it needs more testing than a signature on an agreement.

This guide gives medical practices and other professional-services organizations a practical sequence for scoping risk, testing samples, reviewing classification, reporting findings, and maintaining controls between audits. It's general information, not individualized legal or tax advice. Confirm specific obligations with qualified counsel or a compliance professional, especially when workers span multiple jurisdictions.

Scoping the Audit and Building a Risk Map

Start by replacing a vague request to review payroll with a written scope. Define the review period, worker population, pay types, jurisdictions, and legal criteria before anyone pulls a sample. Include employees, contractors, terminated workers, temporary staff, and anyone paid through an intermediary. If you leave a population out, write down why, because an unexplained exclusion becomes a weakness in the final report.

The scale behind this discipline is laid out in the IRS tax gap estimates for tax year 2022, which put the projected annual gross federal tax gap at $696 billion, including approximately $127 billion for employment taxes. The IRS divides the total into $63 billion from nonfiling, $539 billion from underreporting, and $94 billion from underpayment or late remittance, a useful reminder that risk doesn't live only in gross-to-net math. Your scope should therefore cover identification, wage calculation, filing, deposit timing, and reconciliation as one lifecycle.

Older IRS research points in the same direction. In its analysis of employment-tax noncompliance for tax year 1987, the IRS estimated an 89% employment-tax net compliance rate and an approximately $25.1 billion employment-tax gap. About 78% was a reporting gap and 22% was a remittance gap, which is why a defensible scope tests both what you reported and whether withheld money reached the government.

A five-step infographic illustrating the audit scoping and risk mapping process for business management and planning.

Building the Risk Map

Map workers by status, location, pay complexity, and control environment rather than by department alone. A salaried practice manager, a per-diem receptionist, and a remote medical virtual assistant working fixed shifts create different audit questions. Cross-border arrangements deserve a separate line because home-country labor, tax, and social-insurance rules may not follow the U.S. conclusion, a distinction reflected in guidance on cross-border employment structures and jurisdiction mapping.

Risk Map for a Payroll Compliance Audit

Worker or Process Area Typical Failure Mode Primary Audit Test
Nonexempt remote staff Unrecorded hours or edited time Compare schedules, system activity, and approved time records
Contractors Employee relationship under a contractor label Test control, exclusivity, permanence, and economic dependence
Tax deposits Liability reported but paid late Reconcile liabilities to deposit confirmations and bank activity
Salaried employees Exemption based on salary alone Compare actual duties and salary basis to the applicable criteria
Final pay Missed adjustments or late payment Recalculate every terminated worker with a final-pay adjustment

Policy documents belong in the map too, not as decoration. If timekeeping, overtime approval, or remote-work rules differ from the handbook, that inconsistency is audit evidence. Practices with California workers can use a California employee handbook audit guide to check whether written policies still match the procedures managers follow.

Set cadence and triggers in a one-page charter. An annual audit suits many practices, but you should also scope a focused review after changing payroll providers, entering a new state, acquiring another practice, or adding a new worker category. Name the owner, reviewer, decision rights, deliverables, and deadline. Without decision rights, findings turn into discussion topics instead of corrections.

Sample Testing, Recalculation, and Reconciliation

Testing should be risk-based, not a convenient grab of clean payroll periods. Review every unusual or high-value payment, every terminated worker with final-pay adjustments, and every cross-border worker. Then add a random sample of ordinary transactions so you can say something about routine payroll, not only known exceptions. That design balances depth where exposure concentrates with coverage of the population that usually escapes attention.

For each sampled person and pay period, rebuild gross-to-net from source records. Start with authorized rate and status, then trace hours, paid leave, bonuses, differentials, deductions, reimbursements, garnishments where applicable, and employer taxes. Don't accept the payroll system's output as its own proof. The point is to learn whether inputs, configurations, and approvals produced the right result.

A laptop screen displaying a payroll table with a magnifying glass highlighting a suspicious termination payment amount.

Recalculating Overtime and Time Records

Overtime failures often look small in one check and expensive across a year. Recalculate the regular rate rather than multiplying the base hourly wage automatically, because nondiscretionary bonuses and shift differentials can change the amount used for overtime. Compare original time records with schedules, EHR or phone-system activity where appropriate, supervisor edits, and communications showing work outside recorded hours. Automatic meal deductions deserve special attention when there's no reliable exception process for interrupted breaks.

The exposure behind those tests is illustrated in payroll reporting on Wage and Hour Division enforcement, which notes the Division recovered more than $259 million in back wages for nearly 177,000 workers in fiscal year 2025, averaging approximately $1,465 per worker. You don't need a dramatic violation to create liability. A small recurring error across schedulers, receptionists, and billing staff can become the largest finding in the file.

Blockquote

A passing workpaper shows the source, formula, result, reviewer, and resolution of every variance. A screenshot of the payroll register proves only that payroll ran.

Reconciling Registers, Returns, and Bank Activity

Reconcile the payroll register to the general ledger, bank funding, quarterly employment-tax returns, annual wage statements, and contractor information returns. Investigate timing differences separately from errors. A void, manual check, amended filing, or corrected W-2 may explain a variance, but the explanation needs a document trail rather than a verbal assurance.

Deposit testing is especially valuable. Guidance summarized in IRS research material on federal tax compliance and audit controls supports treating deposits as a control point because employers generally deposit monthly or semiweekly, and a $100,000 or more accumulation during a deposit period triggers next-business-day remittance. Failure-to-deposit penalties can reach 15% of the unpaid amount, so compare each liability date to the deposit calendar, confirmation, and bank debit. A practice can calculate wages perfectly and still fail here.

Document exceptions as you find them. Record the worker, period, expected amount, paid amount, difference, cause, and supporting record. Preserve formulas instead of pasting values into a spreadsheet. If another reviewer can't rerun your logic, the finding isn't ready for the report.

Testing Worker Classification for Remote and Cross-Border Staff

A signed contractor agreement doesn't settle worker status. Neither does issuing a Form 1099. The Department of Labor's explanation of employment relationships under the Fair Labor Standards Act states that receiving a 1099, being paid off the books, or agreeing in writing to contractor status doesn't determine classification. The controlling question is the economic reality of the relationship.

That distinction matters in medical practices because remote support often becomes embedded quickly. A medical virtual assistant may begin with a short scheduling project, then take fixed shifts, use your EHR and phone scripts, attend huddles, and handle intake or referral coordination every day. The work may be entirely appropriate for remote support, but the relationship no longer resembles an independent business serving multiple clients.

Applying the Six Economic Reality Factors

The Department of Labor's classification FAQs identify six factors for the current economic-reality analysis, with no single factor automatically deciding the outcome. Document each one from actual conditions. The revised rule described there was published January 10, 2024, and became effective March 11, 2024, so older one-factor shortcuts shouldn't drive your audit criteria.

  • Opportunity for profit or loss: Can the worker negotiate rates, choose assignments, hire help, or lose money based on managerial decisions?
  • Investments: Who supplies the computer, software, headset, workspace, and other tools, and how do those investments compare?
  • Permanence: Is the engagement project-based and finite, or continuous and indefinite?
  • Nature and degree of control: Who sets the schedule, sequence, scripts, productivity standards, and discipline process?
  • Integration: Is the work integral to scheduling, intake, billing, insurance verification, or another core practice function?
  • Skill and initiative: Does the worker use specialized skill to run an independent business, or mainly carry out your procedures?

Build a one-page classification evidence matrix for each remote contractor. Link every factor to a record, such as the agreement, invoices, schedule history, access logs, supervision structure, equipment terms, substitution rights, deliverables, and evidence of other clients. A more detailed comparison of independent contractor versus employee indicators can help structure the questions, but your evidence still has to describe this worker and this engagement.

Adding the Cross-Border Layer

For a worker in Latin America or another country, complete the U.S. analysis and then map the conclusion separately to local labor, tax, and social-insurance obligations. Test whether an intermediary employs the worker, merely processes payment, or has no meaningful role beyond invoicing. Also consider whether local registration or permanent-establishment concerns require specialist review. Different jurisdictions can reach different answers on the same facts.

Recent global payroll reporting from Lano describes governments moving toward defensible compliance and closer scrutiny of remote, multi-jurisdictional contractor arrangements. Treat classification as a recurring control, not an onboarding checkbox. Retest when a project becomes indefinite, hours expand, exclusivity increases, or supervisors gain more control over methods. The safest file explains both the original decision and why it still holds today.

Findings, Remediation, and a Defensible Report

Raw exceptions don't become useful findings until each one is written with precision. Use a four-part structure for every material issue. State the condition you observed, the criteria that should have governed it, the cause, and the effect. Tie each element to a record so a leader doesn't have to choose between competing recollections.

Quantify exposure in dollars, periods, and affected workers rather than labeling an issue moderate or concerning. Separate confirmed underpayments from estimated exposure and penalty risk. Show whether the amount came from a full-population recalculation or an extrapolation from a sample, and identify the assumptions. Counsel can advise on correction methods, amended returns, back pay, and communications. Your audit file should give counsel clean numbers instead of forcing a second investigation.

Sequencing Remediation

Rank findings by legal and financial severity, then assign an owner and due date. A deposit failure affecting trust-fund taxes needs faster action than a formatting defect in a personnel file. A misclassified group of full-time virtual assistants needs a different plan from one isolated overtime configuration error.

  • Correct the population: Recalculate all affected periods and workers, not only the sampled exceptions.
  • Fix the filing position: Prepare amended employment-tax returns or corrected wage statements where qualified advisers determine they're permitted and required.
  • Change the control: Update time approval, regular-rate configuration, deposit calendars, or classification review procedures.
  • Train the operators: Give practice managers and supervisors concrete rules for edits, off-the-clock work, meal breaks, and schedule changes.
  • Retest: Sample later payroll cycles to confirm the correction worked under normal operations.

Retention belongs in the report because remediation may require older evidence. IRS Publication 15 requires employers to keep employment-tax records for at least four years and make them available for IRS review. Treat that period as a federal baseline. State wage laws, contracts, litigation holds, or other tax rules may require you to keep records longer.

Blockquote

Report discipline: If a finding can't name the criterion, affected population, dollar effect, owner, and retest date, it isn't finished.

End with a concise report that a busy owner can use. Include an executive summary, scope and exclusions, methodology, findings, quantified exposure, remediation plan, responsible owners, and retest schedule. Attach the population list, sampling rationale, reconciliations, and classification matrices. Keep privileged legal analysis separate where counsel directs, but don't use confidentiality as a reason to leave operational facts undocumented.

Records, Access Controls, and Ongoing Governance

A numerically correct paycheck can still rest on weak governance. You need to prove who entered the rate, approved the hours, changed bank details, released funding, and accessed sensitive identity data. Those questions matter during a tax review, wage dispute, privacy incident, or client security assessment. They also matter when a payroll employee leaves and institutional memory leaves with them.

Define a complete payroll file before the next cycle. It should contain the register, source time records, approval logs, onboarding and status documents, rate changes, benefit and fringe records, deposit confirmations, quarterly and annual returns, bank reconciliations, and correction evidence. For year-end work, some practices may use tools that automate W-2 data capture to reduce manual transcription, but the audit still needs source-to-return reconciliation and reviewer sign-off.

An infographic titled Payroll Records and Ongoing Governance displaying five essential compliance components for payroll management systems.

Testing Access and Change Controls

Review role-based permissions, unique credentials, multifactor authentication, and segregation between time approval and pay release. Inspect change logs for bank accounts, tax elections, rates, deductions, and worker status. Terminated workers and former administrators should lose access promptly. Strong audit trail management practices make those events reviewable without exposing the entire payroll file to everyone involved.

Remote access adds a healthcare-specific layer when staff can reach electronic protected health information. HHS guidance on remote use under the HIPAA Security Rule addresses policies for authorizing and supervising workforce access to electronic patient information. Test whether each virtual receptionist, patient coordinator, or billing assistant can reach only the systems needed for assigned duties, whether shared accounts are prohibited, and whether offboarding is documented. Don't call a worker or workflow HIPAA certified, because HHS doesn't recognize an official HIPAA certification.

Broader payroll governance is also tightening around evidence quality. The 2026 Global Payroll Playbook from IRIS highlights data-handling mandates, encryption, access controls, local-storage requirements, and expectations for access to earnings and deduction information. Use that direction practically. Maintain a quarterly dashboard for unreconciled variances, late deposits, classification retests, stale system access, missing approvals, and unresolved findings. Put recurring tests on a calendar tied to payroll, quarter-end, and year-end. The next audit should begin with a current control file, not an archaeological dig.

The Takeaway

A payroll compliance audit holds up when three things are true. The scope and risk map explain what you tested and why. Recalculations and reconciliations prove the numbers from source records. Classification conclusions reflect actual working conditions rather than contract labels, especially for remote and cross-border staff.

Act this week by fixing the review period, listing every worker and jurisdiction, and inventorying the records you can retrieve today. This quarter, run the first risk-based sample, complete classification matrices for remote contractors, quantify findings, and schedule remediation retests. Keep watching deposit timing, time edits, access changes, and relationships that gradually become more permanent or controlled. Confirm jurisdiction-specific duties with qualified counsel before making corrections.


If documentation gaps are slowing your review, Medical Virtual Assistants can supply pre-vetted bilingual LATAM healthcare talent aligned with U.S. hours, with interview-before-hire and documented worker information for roles such as scheduling, insurance verification, patient coordination, and billing support. Reach out for a shortlist and use your audit time to test controls, not rebuild missing worker files.