Union Membership and Dues Software: When 300 Employer Remittances Do Not Match Your Roll

The reconciliation that eats the first two weeks of every month

Employers remit dues on their own schedule in their own format. One sends a clean CSV. One sends a PDF that used to be a spreadsheet. One sends a bank transfer with a total and no detail at all, and you have to ask. Names arrive as Mike where your roll says Michael, as married names where your roll has maiden names, as payroll identifiers that do not exist in your system. Somebody left in March and is still on the remittance in May. Somebody was hired in April and is not on it at all.

So the membership team spends two weeks matching, and the output is three questions that matter more than the matching itself. Who is actually in good standing, because good standing determines who can vote, run for office and receive benefits. Who is in arrears and by how much, because arrears drive suspension procedures written into your constitution. And what does the local owe the international in per capita, because that is calculated off a headcount that is only as good as the reconciliation.

The corrosive part is not the effort. It is that the answer arrives too late to act on. By the time you know a member fell off an employer's remittance, they have been unrepresented on the record for two months, and the first they hear about it is a letter saying they are in arrears for something that was the employer's error.

What UnionWare and UnionTrack do, and where they stop

UnionWare has been built specifically for unions for a long time and understands membership, dues and grievances as one domain rather than as a CRM (Customer Relationship Management) with custom fields. UnionTrack ENGAGE is stronger on member communication and organising, which is where a lot of union investment is going. Both are credible and both beat what most locals are running today.

They run short in a predictable place, which is the collective bargaining agreement. Dues in this sector are not a subscription. They might be a percentage of gross wages capped at a monthly maximum, or two hours pay per month at the member's classified rate, or a flat amount by classification with a different amount for apprentices, part timers and retirees, plus a working dues assessment on hours worked that only applies to members under one of your four agreements. Every one of those is a formula with inputs that arrive on the employer remittance. Packaged products expose the common shapes and handle the rest as manual adjustments, which is exactly where the errors live.

The second gap is grievance handling. A grievance is not a support ticket. It has contractual step deadlines that vary by agreement, and a missed deadline can extinguish a meritorious grievance permanently. That means the system has to compute the next deadline from the agreement, the step, the date of the triggering event and the working day calendar, and escalate before it expires rather than reporting after. Generic case tools give you a due date field and no understanding of why the date matters.

Problem one: matching remittances to the roll

The technical work here is unglamorous and pays for the project. Build an import layer that accepts each employer's actual format, keeps the raw file untouched as evidence, and maps to a normalised remittance line. Match on employer identifier first where one exists, then a scored match on name, date of birth and worksite, then a manual queue for the rest with the match decision remembered so the same person does not need matching again next month.

Two features change the experience more than anything else. Exception detection: a member who appeared on last month's remittance and is missing from this one is flagged immediately, and the local can call the employer while the answer is still cheap. Variance detection: a member whose dues dropped materially without a classification change usually means the employer changed their status or their hours, which is worth a conversation. Both of these are trivial to compute once the data is structured and impossible from a stack of PDFs.

Machine assistance has one honest job here, which is reading the remittance documents that arrive as PDFs and scans and turning them into structured lines for the same matching pipeline. Use it for extraction, not for deciding who is a member.

Problem two: dues formulas that are contract law

Model the agreement as a first class object with an effective period, and attach dues rules to it rather than to the member. A member's dues then derive from their classification, their employer, the applicable agreement and the reported earnings or hours for the period. When the agreement is renegotiated, you add a version with an effective date and every calculation after that date follows it, while historical periods stay computed the way they actually were.

This matters beyond accuracy. When a member disputes an arrears figure, you need to show the calculation: this agreement, this rule version, this classification, these reported hours, this amount. A number without a derivation is an argument. A number with a derivation is usually the end of the conversation.

The same object supports the things built on top of dues: per capita to the international, which is typically a per member per month amount that has to reconcile with what you reported, and any dues rebate or reduced rate categories your constitution allows for retirees, unemployed members and those on leave.

Problem three: seniority and good standing are consequential records

Seniority lists drive layoff order, recall rights, shift and vacation selection, and in many trades the referral or out of work list that determines who gets dispatched to a job. Members compare their position on that list and they will find every error in it. The list has to be reproducible as of a date, because a layoff that happened in February is judged against February's list, not today's.

Good standing is the same problem in a different suit. It determines eligibility to vote and to hold office, and under federal law governing union elections the conduct of internal elections is itself regulated, so an incorrect eligibility determination is not a clerical matter. Build good standing as a derived state with a full audit trail: this member was in good standing on this date because dues were paid through this period under this rule, and here is the remittance line that proves it.

Problem four: grievances with clocks running

Each grievance carries the member, the employer, the worksite, the contract articles alleged to have been violated, the steward, the step, and dates. The system computes the next deadline from the agreement's own timelines and the applicable calendar, warns before it lands, and refuses to let a step quietly lapse. Arbitration adds cost tracking, arbitrator selection history and outcomes, which over time becomes the most useful dataset the union owns, because it tells you which articles generate disputes at which employers and how you have fared. Very few locals can answer that question today.

Cost, timeline and what drives the number

In Digital Heroes delivery experience a first release covering the roll, remittance import and matching, contract driven dues calculation, arrears and good standing runs $75,000 to $150,000 in 12 to 18 weeks. Adding grievance and arbitration management, seniority and referral lists, per capita reporting, member self service and benefit or strike fund administration takes it to $180,000 to $400,000 over 8 to 14 months.

Price drivers: the number of distinct collective agreements and how different their dues formulas genuinely are. The number of employers and the variety of remittance formats, since each new shape is real work. Referral and dispatch lists for building trades, which are effectively a second system with their own rules and a very attentive audience. Statutory financial reporting to the Department of Labor, since a system that produces the figures for the annual LM report saves weeks but has to be built to the form. Member self service, which is straightforward technically and needs careful thought about what a member may see and change. And data migration from whatever you run now, which in this sector is often a database old enough to vote.

What keeps it down: starting with your largest employers by member count, keeping grievances in phase two, and treating self service as a read only view before allowing updates.

When to buy instead

Buy if you have one or two employers, a single dues formula and under a couple of thousand members. UnionWare will handle that and the total cost sits far below a build. Buy if the union has no capacity to own a product, since a system this closely tied to constitutional rules needs an internal owner who knows the constitution.

Build when several are true. You take remittances from dozens of employers in incompatible formats. Your dues formulas differ by agreement in ways that require monthly manual adjustment. You run referral or dispatch lists where the rules are specific to your trade. Grievance deadlines have been missed. Or the international requires reporting your current system cannot produce without a week of assembly. The honest trigger is that the union's rules, meaning the constitution and the agreements, are the software's requirements, and if those rules are unusual then generic software will keep making you the workaround.

How to choose a developer

Ask them to explain how they would model dues for a member covered by an agreement that charges two hours pay per month at the classified rate, with a different rate for apprentices and a working dues assessment on overtime hours. If the answer is a rate field on the member record, they have not understood that the contract is the object.

Ask how they would reproduce the seniority list as it stood on a date fourteen months ago. The answer should involve an event log rather than a nightly snapshot table someone might have missed.

Ask what they have done with messy inbound files and whether they keep the original as evidence. In a dispute with an employer over what was remitted, the untouched original file is the record that matters.

Ask about member data protection, because you hold employment, earnings and sometimes health related information about people whose employers would find it useful. Then settle ownership before kickoff. The repository, the cloud accounts and the right to hire another firm should be yours in writing. At Digital Heroes the client owns the code from the first commit, and a union in particular should not hold its membership record inside a vendor's account.