TL;DR
Most leaders treat payroll compliance as an HR function to be delegated and forgotten. That works until it doesn't. IRS penalties, employee misclassification exposure, and state compliance failures rarely originate from a failure in HR's day-to-day execution. They originate from a governance failure that starts at the leadership level: insufficient oversight, underfunded infrastructure, and a structural design that puts compliance responsibilities on people who weren't set up to carry them. The Novum Growth Framework's DTS model (Discover, Transform, Steward) starts with a diagnostic that surfaces where these gaps actually live.
The Call You Don't Want to Get
There's a particular kind of bad morning that hits leaders who haven't been paying attention to their payroll function.
It usually starts with an email from the IRS. Or a letter from the state tax authority. Or a call from an employee asking why their W-2 doesn't match what they thought they made. Or a quiet conversation with your HR director where she tells you she's been doing her best with the system you gave her, but she's not sure it's been set up correctly for the last 18 months.
By the time the problem is visible, it's expensive. Back taxes, penalties, interest. Potential personal liability for the officers who signed the payroll filings. Employee trust, once broken by a payroll error, takes a long time to rebuild. And the fix usually costs three to five times more than it would have cost to prevent.
None of this is the HR director's fault in the way it's usually framed. Yes, payroll is in her job description. Yes, she should have flagged it sooner. But the real questions are: Was she set up to succeed? Did she have the tools, training, and oversight structure to catch what went wrong? Was there a governance layer above her that was monitoring compliance posture, not just signing off on the paycheck run?
In most cases, the answer to all three questions is no. And that's a leadership problem.
Why This Is a Governance Failure
Payroll is one of the most regulated functions in any organization. Federal withholding requirements, state income tax obligations, FICA, FUTA, state unemployment insurance, worker's compensation, benefits reporting, employee versus contractor classification, housing allowance documentation for clergy, exempt versus non-exempt status under the FLSA. The compliance surface is large, the rules change frequently, and the penalties for getting it wrong are real.
Most organizations at the $5M to $30M range handle this function with one or two people who are also doing other things. The person running payroll is often also managing onboarding, coordinating benefits open enrollment, answering employee questions, and keeping up with a dozen other HR responsibilities. Compliance isn't neglected because they don't care. It's fragile because the structure was never designed to hold it.
The DTS model in the Novum Growth Framework starts with Discover: an honest diagnostic of the current state before any transformation work begins. In the HR and payroll space, the Discover phase asks questions that most organizations have never formally asked.
Who actually owns payroll compliance? Not processing payroll, that's a different question. Who owns the compliance posture: ensuring classifications are correct, verifying that the payroll system is set up accurately, monitoring for regulatory changes, and managing the relationship with any third-party payroll provider?
In most organizations, the honest answer is that nobody clearly owns it. Processing happens. Compliance is assumed to be happening because nothing has gone wrong yet.
"Nothing has gone wrong yet" is not the same as "we are compliant." And the gap between those two statements is where most payroll problems live.
Gartner research on HR function effectiveness consistently finds that compliance failures in smaller organizations are primarily governance failures rather than execution failures. The execution layer is doing its best with what it has. The governance layer hasn't defined what "correct" looks like, invested in the infrastructure needed to achieve it, or built the oversight structure to know whether it's happening.
What Payroll Compliance Actually Requires
Payroll compliance is not a software problem. Most organizations think it is. They buy a payroll platform, configure it as best they can, and trust that the technology is doing what it needs to do.
Payroll software processes payroll accurately based on the inputs it receives. It does not verify that those inputs are correct. It does not catch misclassifications. It does not know that your state changed its unemployment insurance rate in Q3. It does not flag that your overtime calculations aren't accounting for all compensable time. It processes what it's given and produces what you told it to produce.
Payroll compliance requires four things no software platform can provide on its own.
Accurate job classification. Every person in the organization needs to be correctly classified as either an employee or an independent contractor, and within that, as either exempt or non-exempt under FLSA standards. Misclassification is one of the most common and expensive payroll compliance failures. The exposure isn't just the back wages. It includes penalties, interest, potential litigation, and in some states, civil damages.
Accurate pay practice design. Overtime calculations, tip credits, commissioned employee rules, piece-rate calculations, and state-specific minimum wage requirements all need to be designed into how the organization pays people, not just into how it processes payroll. A payroll system that correctly calculates overtime based on incorrect pay practice assumptions will still produce a compliance failure.
Up-to-date regulatory awareness. Federal and state employment laws change every year. Minimum wage rates change. Benefits reporting requirements evolve. Salary thresholds for exempt status are updated. Someone in the organization needs to be monitoring these changes and ensuring the payroll function reflects them. This requires either internal expertise or an external partner who brings it.
An oversight structure above the processing layer. Someone in a governance or leadership position needs to be reviewing compliance posture, not just reviewing whether the payroll ran on time. This is typically a quarterly review of classification, pay practices, and regulatory alignment, and an annual audit of the payroll setup.
The Special Case of Faith-Based Organizations
For churches and faith-based nonprofits, the payroll compliance picture has additional complexity that secular organizations don't face.
Housing allowance documentation for ordained clergy is one of the most significant and most frequently mishandled elements of church payroll. A properly documented housing allowance designation, approved by the board in advance and reflected correctly in both payroll and tax reporting, is a significant tax benefit for clergy. Done incorrectly, it creates retroactive tax liability and potential IRS scrutiny of the entire compensation structure.
Contractor versus employee classification in ministry settings is also frequently mishandled. Musicians, childcare workers, event staff, and ministry volunteers who are paid on a regular basis often meet the IRS's test for employee status even when they are being treated and paid as contractors. The exposure from retroactive reclassification includes back payroll taxes, penalties, and state-level complications.
ECFA governance standards for compensation require that all compensation be reasonable, documented, and approved by the board or a board-delegated committee. This standard applies not just to the executive director or senior pastor but to the compensation structure across the organization. Organizations that lack a formal compensation governance process are carrying exposure they often don't know is there.
What Leadership Oversight of Payroll Actually Looks Like
Saying "payroll compliance is a leadership problem" requires answering what leadership should actually do about it.
It doesn't mean the CEO should process payroll or attend to every compliance detail. It means the CEO, COO, or CFO should be accountable for the governance structure that ensures compliance happens reliably.
In practice, this looks like four things.
A clear ownership structure. One person in the organization is accountable for payroll compliance posture. Not payroll processing, compliance posture. This is distinct from the person who runs the payroll. It may be the HR director, the Controller, or the CFO. It may be an external partner. But it is clearly assigned, not assumed.
A regular compliance review cadence. At least quarterly, the person accountable for compliance posture reports to the CEO, COO, or CFO on the state of compliance: any changes in the regulatory environment that affect the organization, any flags from the payroll platform or third-party provider, any classification or pay practice questions that need resolution. This is not a 20-minute check-in. It is a substantive governance conversation.
An annual payroll audit. Once a year, the payroll setup, classification decisions, pay practices, and benefits reporting are reviewed systematically either internally or by an outside adviser. The goal is not to find problems, though it often does. The goal is to verify that the system reflects the organization as it currently exists, not as it existed two years ago when the setup was last touched.
Adequate investment in the function. Payroll compliance cannot be treated as a cost-minimization problem. The person or team responsible for it needs the tools, training, and capacity to do it correctly. Cutting payroll function costs below the level needed for reliable compliance is not a savings. It is a risk transfer to the organization's leadership and ultimately to its mission.
The Counter-Move
The most common response to a payroll compliance scare is to get better software. The organization upgrades its payroll platform, imports all the old data, and trusts that the new technology will solve the problem.
Technology is necessary but not sufficient. The new platform will process payroll correctly based on the inputs it receives, just like the old one did. If the inputs are wrong, which is usually why the compliance problem existed, the new platform will process the wrong inputs more efficiently.
What Novum counsels instead is to start with the diagnostic. Before investing in new technology, identify what the compliance gaps actually are and where they originate. Are they classification gaps? Pay practice design problems? Regulatory alignment failures? Oversight structure weaknesses? The answer determines what needs to change and in what order.
Fix the design before you upgrade the processing. Otherwise you're scaling a compliance problem.
The Invitation
If your organization hasn't had a formal payroll compliance review in the last 18 months, you are likely carrying exposure you don't know about. That's not an accusation. It's the base rate reality for most organizations in the $5M to $30M range who have grown faster than their compliance infrastructure.
Novum's HR and Payroll vertical works with churches, nonprofits, and faith-driven businesses to diagnose and close compliance gaps, design the oversight structure that prevents future exposure, and build the payroll function to the standard the organization's scale requires. We bring the compliance expertise. You bring the organizational knowledge. Together, we build something that holds.
If this article described your organization, the next step is a conversation.