Union Payroll: Compliance, Dues, & Officer Pay Controls

Key Takeaways
- Union payroll runs on two pipelines: compensation the union pays out, and dues deductions employers collect and remit. Conflating them is where most compliance problems start.
- LMRDA reporting is public: every dollar paid to union officers is searchable by members, regulators, and the press.
- The NLRB’s Valley Hospital ruling changed dues checkoff: employers must maintain checkoff through contract negotiations even after a collective bargaining agreement expires.
- Officer compensation requires formal authorization: undocumented pay creates LM filing risk and personal liability for the officers who signed.
- Würk’s unified HCM platform handles multi-rate union payroll, CBA-driven pay rules, dues checkoff tracking, and certified payroll reporting from a single system.
Union payroll is not one process. It is two distinct financial operations that intersect at the member level but require separate tracking, different accounting treatment, and distinct compliance obligations. The payroll administrator processing a standard biweekly run and the treasurer managing officer compensation at a mid-size local are solving different problems, but both are doing union payroll.
This article covers both: what union payroll actually covers, where the compliance requirements come from, how dues checkoff flows and where it breaks down, and what records and controls make the whole system defensible. Managing union payroll well requires understanding which obligations belong to which pipeline and knowing the union payroll requirements that apply on each side.
What Is Union Payroll?
The Two Pipelines Leaders Must Separate
The first pipeline is compensation the union pays out. This includes wages and salaries for union staff, officer stipends, per diems, lost time payments, and reimbursements. These transactions flow from the union’s bank accounts, get recorded in the union’s general ledger, and generate W-2s or 1099s depending on worker classification. They appear in the union’s LM filings and are subject to member scrutiny.
The second pipeline is employer-side dues deductions. An employer collects dues from union members’ paychecks under a checkoff arrangement and remits them to the union. The union receives and receipts the funds, but the two organizations maintain separate accounting systems.
On the union side, payroll covers salaried officers, hourly administrative staff, elected officials receiving stipends, stewards compensated for grievance work, and temporary workers. On the employer side, union payroll processing covers any union worker whose dues are deducted under a checkoff agreement, which may span multiple job classifications and wage rates within a single payroll run. Conflating these pipelines creates classification and reporting errors that compound at filing time, complicating the intricacies of union labor.
Why Union Payroll Attracts Heightened Scrutiny
Standard employer payroll is an internal matter until something goes wrong. Union payroll is a public matter by design. The Labor-Management Reporting and Disclosure Act (LMRDA) requires unions to disclose officer and employee compensation on annual financial reports filed with the U.S. Department of Labor’s Office of Labor-Management Standards (OLMS). Those reports are publicly searchable.
Union membership has standing to challenge compensation they find unreasonable. Regulators audit LM filings and can initiate investigations. A payment that was administratively sloppy but financially correct can still generate a compliance narrative if the records don’t explain it clearly.
Compliance With Union Reporting Requirements
LMRDA, LM Forms, and What They Require of Payroll
The LMRDA requires every covered labor organization to file annual financial disclosure reports with OLMS to ensure accurate reporting. Which form is required depends on total receipts: unions with $250,000 or more in annual receipts file the LM-2, which requires itemized disclosure of all receipts and disbursements above reporting thresholds. Smaller unions file the LM-3 or LM-4. All forms are due within 90 days of fiscal year end.
The president and treasurer sign the LM-2 personally and are individually responsible for its accuracy under criminal penalty. That accountability traces directly back to payroll records: if officer compensation entries in the filing don’t reconcile to payroll records, the officers who signed are exposed, not just the system.
Payroll classifications must map cleanly to LM form categories. Direct disbursements to officers, indirect disbursements, allowances, reimbursements, and benefits are reported separately. A union that can’t produce that breakdown without manual reconstruction at filing time has both a systems problem and a governance problem.
Tax Compliance Issues That Still Trip Up Unions
Union status does not simplify payroll tax compliance. Unions with employees face the same withholding, deposit, and filing obligations as any other employer: federal income tax withholding, Social Security and Medicare taxes, FUTA, and applicable state and local equivalents.
Classification is where unions most commonly get into trouble. An organizer paid project-by-project, a field rep brought in during contract negotiations, or a technology consultant retained long-term may look like independent contractors but fail IRS classification tests based on behavioral control, financial control, and the nature of the relationship. Misclassification generates back taxes, penalties, and interest. It also produces errors in payroll reporting, showing up as a discrepancy between the union’s 1099s and what workers actually received. Multi-state unions add another layer: withholding rules vary significantly by jurisdiction, and it takes real effort to calculate obligations correctly in each state and reconcile deposits to them. Payroll software that handles multi-state compliance natively is the only practical way to keep that payroll process from becoming a quarterly scramble.
Written Policies That Reduce Exposure Before Software Enters
Technology enforces policies. It cannot substitute for them. The rules and regulations governing compensation, reimbursements, and stipends need to be written down before any system can be configured to enforce them. At minimum, union leaders need written policies that define compensation structures for each role type, approval chains for one-time payments, and the reimbursement framework.
The reimbursement policy distinction matters more than most unions realize. An IRS-compliant accountable plan requires that reimbursements be tied to a business purpose, substantiated with documentation, and returned if the employee receives more than the actual expense. Payments that don’t meet those requirements must be included in the employee’s W-2 as taxable wages. A union paying flat monthly expense allowances without substantiation is effectively paying additional taxable wages whether it intends to or not.
Paying Officers and Employees Correctly
Compensation Structures That Survive Scrutiny
Officer compensation is the highest-visibility line item in union payroll. LM-2 filers must itemize payments to each officer and employee earning more than $10,000 from the union, and the DOL’s OLMS guide for new union officers explicitly addresses fiduciary responsibility over compensation.
A compensation structure that survives scrutiny has three properties. It is formally authorized: the pay scale for each role is set by executive board or membership vote and recorded in meeting minutes before payments begin. This is the foundation of any effort to ensure compliance with both the union’s bylaws and LMRDA requirements. It aligns with the union’s bylaws and applicable policy resolutions. It distinguishes clearly between salary, stipends, allowances, and reimbursements, because each carries different tax treatment and different disclosure implications.
| Payment Type | Taxable? | W-2 Reportable? | LM-2 Category |
| Salary / hourly wages | Yes | Yes | Direct disbursement |
| Meeting stipends | Yes | Yes | Direct disbursement |
| Accountable plan reimbursements | No | No | Indirect disbursement |
| Non-accountable expense allowances | Yes | Yes | Direct disbursement |
| Per diem within IRS limits | No | No | Indirect disbursement |
| Per diem above IRS limits | Partial | Yes (excess) | Both categories |
Edge cases require specific documentation. Officers serving partial years need pro-rated records with start and end dates attached. Interim appointments need board authorization reflected in minutes before any payment. Retroactive pay adjustments need both the original authorization and the correction recorded separately.
Lost Time and Release Time Payments
Lost time is compensation paid to a union member for time away from their employer-side job to conduct union business, and it is one of the most documentation-intensive payment types in union payroll. The mechanics vary: some unions pay the member directly, some pay the employer who continues paying the member. Each structure has different payroll, tax, and LM reporting implications.
Time tracking discipline is what makes lost-time payments defensible. The core documentation requirement is a certified time record showing the member’s name, dates and hours covered, union business purpose, and the certifying officer. Without it, the payment becomes difficult to defend under audit. Double-pay situations, where a member collects both employer wages and union lost-time pay for the same period, are exactly what auditors look for.
Release time, where an employer releases a representative during working hours without pay loss, is the employer’s obligation to track; the union has no direct payroll liability, though tracking it still serves the union’s interests.
Benefits and Taxable Fringe Considerations
Union staff and officers may receive health insurance, retirement contributions, and other standard benefits. Tax treatment depends on the specifics. Where it gets complicated is in the fringes: union-provided vehicles, cell phone stipends, and travel benefits each carry specific IRS rules about taxability.
A union vehicle provided to an officer is a taxable fringe benefit unless it qualifies for a working condition exclusion or personal use is tracked and reported correctly. A flat monthly phone allowance with no business substantiation is taxable wages regardless of intent. In construction and trades, this often includes employer contributions to a health and welfare fund, pension, and training fund. Year-end fringe benefit reconciliation, where the union reviews every non-cash or allowance-based benefit against IRS taxability rules and adds required amounts to W-2s, is a standard payroll close step that many small unions skip until an auditor finds the gap.
How Dues Checkoff Works
The Mechanics of Dues Checkoff
Dues checkoff is a payroll deduction arrangement under which an employer deducts union dues from members’ wages each pay period and remits the collected funds to the union. It requires a signed authorization from each employee. Under Section 302 of the Labor Management Relations Act (LMRA), employees have the right to revoke dues checkoff authorizations, and the CBA and authorization form language govern revocation windows.
Remittance timing and format are typically specified in union agreements. Employer payroll teams that process union payroll under a checkoff arrangement should have those terms in hand and reflected in their remittance schedule. The union’s receiving process should include receipting controls that match remittances to the expected amount based on enrolled members, the applicable union rate, and pay periods. Any discrepancy should trigger a reconciliation against union rules for dues calculation before the next remittance cycle. Exceptions including new hires who haven’t yet authorized, members on leave, and terminated employees still appearing in a remittance batch all need a defined resolution workflow. Unresolved exceptions compound over time and become reconciliation problems at year-end.
Preventing Dues Deduction Disputes
The most common dues checkoff dispute is the member who claims they never authorized a deduction or that their revocation was ignored. Both scenarios require the same evidence: the original signed authorization or the received revocation request with a date stamp, along with documentation of what action was taken and when.
When a member raises a dispute, response timeline matters. A delayed response without documentation looks like either an admission or a records failure. The workflow should define who receives the dispute, what evidence is retrieved, what the response timeframe is, and who the member can escalate to if unsatisfied.
Dues rate changes create a separate risk. When a union increases rates, members who authorized a specific deduction amount may argue the new rate exceeds their authorization. Before implementing a rate change, the union should review its standard authorization form language and coordinate with employer payroll contacts to ensure the change is implemented accurately and on schedule.
Collective Bargaining Agreement Expiration and the Dues Checkoff Obligation
Contract expiration is a high-risk moment for dues checkoff operations. The NLRB’s ruling in Valley Hospital Medical Center II (2022) established that dues checkoff provisions are part of the employer’s status quo obligation after a CBA expires, meaning employers generally must continue checkoff through contract negotiations until a successor agreement is reached or a legitimate bargaining impasse occurs. This reversed decades of prior precedent.
The practical implication: don’t treat CBA expiration as a trigger to modify or suspend checkoff. Treat it as a trigger for legal review to ensure compliance with union requirements. Union regulations and the status quo obligation don’t dissolve when union contracts lapse. At each contract cycle, the local union’s payroll and HR teams should confirm that authorization forms are current, that remittance procedures are documented, and that any dues rate changes in the new contract are communicated to employer payroll contacts with adequate lead time.
Recordkeeping, Accounting, and LM Filing Accuracy
What to Retain and How to Organize It
The DOL’s OLMS recordkeeping guidance requires unions to maintain records that accurately reflect the financial transactions reported in LM filings for at least five years after the filing date. For payroll, that means retaining pay authorizations, rate change records, officer appointment documentation, timecards, lost time vouchers, expense substantiation, per diem logs, bank records, payroll registers, and general ledger entries, along with any change logs that document corrections.
The organizing principle is simple: maintain detailed records where every payment is traceable to a document and every document is tied to the payment. A payment in the payroll register should trace to an authorization; the authorization should trace to a board resolution; the resolution should be in meeting minutes. A system requiring a search through three filing cabinets and two email threads to reconstruct that chain is not audit-ready, even if the underlying transactions were correct. Payroll management discipline means the record is as clean as the payment.
Building an Audit-Ready Paper Trail
When OLMS opens an investigation, the first requests are predictable: a list of all compensated officers and employees, documentation supporting each officer’s compensation rate, and records for any disbursement above reporting thresholds. Having those materials organized and retrievable in days rather than weeks significantly changes how an investigation proceeds.
Each payment should be documented with four elements: the purpose, the authorizing official, the recipient, and the accounting category. When those four elements are consistently present, explaining the union’s practices to an audant is straightforward. When they’re inconsistently documented, the auditor fills in gaps with assumptions that favor scrutiny. LM-2 filers should also note that direct disbursements to officers, covering wages and taxable benefits, and indirect disbursements, covering union-paid expenses on their behalf, are reported separately. Miscellaneous catch-all buckets invite the questions a clean chart of accounts prevents.
Month-End, Quarter-End, and Year-End Close
A monthly reconciliation between the payroll register, the bank statement, and the general ledger catches errors while they’re still correctable. A union that reconciles only at year-end is guaranteeing a stressful close and may be filing an LM report that doesn’t reconcile to payroll records.
Year-end governance should include a formal compensation review: a documented confirmation that every officer payment was authorized, correctly classified, and reflected accurately in the filing. Fringe benefit review should be finalized before the last payroll run so taxable amounts are included in W-2s rather than added as adjustments after the fact.
| Cadence | Key Tasks |
| Weekly / Biweekly | Collect timecards and lost-time vouchers; run exception report; obtain two-person approval; release payroll |
| Monthly | Reconcile payroll register to bank and general ledger; review expense submissions against accountable plan standards |
| Quarterly | File and deposit payroll taxes; reconcile against prior quarters; produce officer compensation summary for leadership |
| Year-End | Validate SSNs and addresses; reconcile fringe benefits; prepare W-2s and 1099s; complete documented compensation review |
Internal Controls That Prevent Errors and Fraud
Segregation of Duties in Small Unions
Payroll fraud in unions follows a predictable pattern: a single person controls enough of the process to add a fictitious employee, approve a payment, and release funds without independent review. The GAO’s reporting on union financial integrity highlights that internal control weaknesses, not just intentional misconduct, account for a significant share of union financial problems. Most gaps are structural. They can be closed. Segregating those functions so the person who adds employees is not the person who approves payroll, and neither is the person who releases the bank transfer, breaks the fraud opportunity.
Small unions with limited staff often can’t achieve full segregation. The compensating control is two-person review at the points of highest risk: adding or changing an employee record, and releasing a payroll disbursement. Even when one person handles most of the processing, having a second officer sign off before funds are released adds a checkpoint that deters most internal fraud and catches most errors.
Approval Workflows and Red Flags
Not every payment requires the same level of pre-approval. Routine payroll at established rates should run under a standard approval workflow. One-time payments such as bonuses, special stipends, and retroactive adjustments should require documented pre-approval from a designated officer or executive board action before processing.
A periodic review of payroll data against a few simple indicators catches most problems before they compound:
- Duplicate payments: same employee, same amount, same period
- Payments to inactive or separated employees
- Unusual overtime or stipend spikes without corresponding event records
- Vendor overlap: a contractor who processes payroll should not also approve entries
- Officer compensation as a percentage of total receipts increasing without membership authorization
A treasurer who reviews the payroll register against these criteria quarterly and documents that review is following the best practices that auditors expect, and that documented review becomes part of the audit trail.
Union Payroll Technology and Outsourcing Decisions
What Union-Ready Payroll Software Needs
Payroll software built for standard employers handles most payroll tasks. Union payroll has requirements that standard platforms often don’t address well: multiple pay rates under a single CBA, fringe benefit contribution tracking tied to hours worked by classification, dues deduction tracking across authorization status changes, lost-time payment workflows, and reporting exports that align with LM form categories. Union payroll in construction adds prevailing wage calculations, certified payroll reporting, and pay scale differences across crafts and jurisdictions. The complexities of union payroll multiply with each additional local, CBA, or public works project in the mix. Specialized payroll software that handles these natively can automate payroll calculations that would otherwise require manual lookups, and streamline the audit trail that compliance requires. Standard payroll processing software systems simply aren’t built for this level of classification and rate complexity.
Role-based permissions and a full audit log of every system action are non-negotiable. When a compensation rate changes, the system should record who made the change, when, and from what previous value. That audit trail is the first thing an investigator asks for, and a system that can’t produce it creates a records problem that documentation practices can’t compensate for.
In-House vs. Outsourced Payroll: Risk Tradeoffs
In-house payroll gives the union direct control over timing, access, and error correction. The risk is that control depends on whoever currently holds the knowledge, and that person must stay informed as union regulations and tax rules change. When that person leaves, the union may have a continuity gap that takes months to address.
Outsourced payroll transfers processing responsibility to a vendor, with the union retaining approval authority. Any outsourced arrangement needs a documented RACI that specifies who owns accuracy for each step, who owns record retention, and what the escalation path is for errors. Vendors should be able to demonstrate how they automate compliance checks and handle the differences between union and non-union payroll rather than applying a standard template. Union and non-union workers sit on different tracks when it comes to rate tables, deduction rules, and reporting obligations. Vendor due diligence should include a review of the vendor’s SOC 2 report, data security practices, and whether their system can produce the exports the union needs for LM filings without manual reformatting.
How Würk Handles Union Payroll Complexity
Würk’s unified HCM platform is built for the compliance complexity that standard payroll systems treat as edge cases. Whether union payroll becomes more complex through multi-local structures or construction craft classifications, the platform handles multiple CBA rate tables, union wage calculations, fringe benefit contributions tied to hours worked, and dues checkoff tracking within a single system. Each union employee record carries the classification, rate, and benefit contribution data needed to run payroll correctly without manual lookups.
- Native time and labor management supports lost-time and release-time workflows with the documentation detail auditors expect: who certified the time, for what union business purpose, and against which payroll account
- Built-in union payroll compliance reporting supports W-2 generation, certified payroll workflows, and dues checkoff audit trails
- Role-based permissions and a complete audit log are standard, not add-ons
- For organizations managing multi-local structures, the platform handles inter-entity payroll and allocation tracking without requiring separate system instances
- Managed payroll services are available for unions that want expert processing support with full oversight retained in-house
- Reporting tools support joint trust funds, training programs, and multi-employer benefit administration alongside core payroll
Ready to see how Würk can simplify your union payroll?
Frequently Asked Questions
What is union payroll?
Union payroll covers two distinct operations: compensation the union pays to its officers and employees, including wages, stipends, and reimbursements, and dues deductions that employers collect from members’ paychecks and remit to the union. Each pipeline has separate accounting, tax, and compliance obligations, and conflating them is a common source of LM filing errors.
What does OLMS stand for?
OLMS stands for Office of Labor-Management Standards, the Department of Labor division that administers the LMRDA, reviews annual LM filings, and conducts compliance audits of union financial practices. LM filings are public record, meaning any member, journalist, or regulator can search officer compensation disclosures directly.
What is the difference between lost time and release time?
Lost time is compensation paid by the union to a member for hours spent on union business away from their employer’s job. Release time is when an employer allows a representative to conduct union business during working hours without pay loss, with the employer continuing to pay. Lost time generates a union payroll obligation and requires certified documentation; release time does not, though tracking it still serves the union’s interests.
If audited by OLMS tomorrow, could we produce a clean paper trail for every officer payment in the last three years?
Every officer payment should trace to an authorization, an accounting entry, and a bank record. If reconstructing that chain for any single payment takes more than a few minutes, the recordkeeping system needs work. Running a periodic internal audit simulation, pulling five random officer payments and tracing each through the full documentation chain, identifies gaps while there is still time to address them.
What controls prevent a single person from both processing and approving payroll disbursements?
The core control is segregation of duties: the person who processes payroll should not be the same person who approves it, and neither should be the person who releases the bank transfer. Where headcount is too limited for full segregation, a two-person sign-off requirement at the approval and release steps provides a compensating control. Role-based permissions in the payroll system enforce those controls at the technical level.
Blog Categories



Stay Connected
Subscribe to Würk's newsletter to receive the latest industry news, Würk product feature enhancements and promotions!
"*" indicates required fields
