What is dues management?

Everything that happens around dues beyond taking the payment: maintaining the member roster, tracking who owes what, reconciling payments against records, handling arrears, reporting to members, and transferring all of it to the next officer.

Do we need dues management software?

Not necessarily. A small organization with a simple annual subscription can run well on a bank account and a spreadsheet. It becomes worthwhile when reconciliation takes real time each month, when nobody can state the outstanding total on demand, or when handovers keep losing information.

What should a dues record contain?

For each member: a stable identifier, name, contact details, category and join date. For each payment: amount, date, method, the period it covers, a reference, and who recorded it. The period covered is the field most often omitted and the one that causes the most confusion.

How often should we reconcile?

Monthly if you can. A month of unexplained differences is an afternoon's work; a year of them is why treasurers dread handover. Reconcile weekly during the first cycle after any change to how you collect.

Should we publish who has not paid?

No. Publish aggregate figures — how many are in good standing, total collected, total outstanding — but treat individual payment status as confidential between the member and the organization. Public arrears lists are a privacy problem and damage the goodwill voluntary organizations depend on.

For organizations

Dues management

Collecting a payment is one event. Managing dues is everything around it — the roster, the reconciliation, the arrears, the reporting and the handover to whoever holds the role next. This page covers what that involves and how to keep it from degrading over time.

The test of a dues management process

There is a simple test. Can you state, right now, without preparing anything: how many members you have, how many are in good standing, what has been collected this period, and what is outstanding?

If answering requires an afternoon of work, your records are not giving you a current picture — they are giving you the raw material from which a picture can be reconstructed. That distinction is the whole of dues management.

It matters for more than tidiness. In most membership organizations, standing determines voting rights and eligibility for office, so an inaccurate register is a governance exposure and not merely an accounting one.

The member record

Everything rests on the roster. A dues process built on an unreliable member list produces unreliable everything else. Each member record should carry:

A stable identifier that does not change when a name, email or address does.
Name, contact details, and a date those details were last confirmed.
Membership category, and the history of category changes with effective dates.
Join date, and where applicable the date membership lapsed or ended.
Current standing — paid to which period, and what is outstanding.
Notes on anything non-standard: a waiver, a hardship arrangement, a payment plan, a disputed charge.

That last item is the one most often kept in someone’s head. An informal arrangement understood by two people disappears at the next handover, and the member is then chased for something they were told they did not owe.

Reconciliation

Reconciliation means proving your records match the money. Take a period, list every payment the bank or platform shows, list every payment your roster shows, and account for every difference in both directions.

Money in the bank but not in the roster is usually an unidentified payment — chase the reference and attribute it. Records in the roster but not in the bank are more serious: either a cash payment that never reached the account, or an entry made in error. Both need an explanation, and the explanation belongs in a note on the record rather than in a conversation someone will forget.

Do this monthly. The work scales badly with time — the same volume of differences is trivially resolved while the context is fresh and nearly impossible a year later when the people involved have moved on.

Arrears

Every organization carries some. The question is whether they are understood or merely accumulating. Sort them by cause before acting — members who never received a request need a request, members with dead contact details need reaching another way, and members in hardship need the hardship process rather than escalation.

Then, where escalation is warranted:

Follow the constitution or bylaws exactly, including any grace period and notice requirement.
Document each step taken and when, so the process is defensible if challenged.
Keep reminders specific: the exact amount, the period covered, how to pay, by when.
Keep the tone administrative. These are colleagues who will be asked again next year.
Record hardship arrangements and payment plans like any other commitment, with agreed amounts and dates.
Write off what is genuinely unrecoverable, with approval and a stated reason, rather than carrying fiction forward.

Reporting

Members are entitled to know the aggregate position, and telling them regularly does more for collection than reminder campaigns. Report the number in good standing, the total collected, the total outstanding, and — most persuasively — what the money funded.

Individual status is different. It should be visible to the member themselves and to the officers who need it, and to nobody else. A public list of who has not paid is both a privacy problem and a reliable way to lose members permanently.

Handover

In volunteer-run organizations this is where processes actually fail. Officers serve fixed terms; the knowledge leaves with them; the successor rebuilds from fragments. Everything above is worthless if it does not survive the transition.

What must belong to the organization, not a person

The bank account, with more than one signatory. The payment channel. The member records and the system holding them. Access credentials, transferable without depending on a former officer’s cooperation. If any of these are attached to an individual, the organization is one resignation away from losing them.

What dues management software should do

If you are evaluating whether to move off spreadsheets, these are the capabilities that actually matter — as opposed to features that sound impressive and go unused:

Hold the member roster and the payment history in one place, so they cannot disagree.
Accept the payment methods your members actually use in your country.
Attach each payment to a member automatically, without manual matching.
Issue receipts automatically and let members retrieve past ones themselves.
Show current standing and outstanding balances without a report having to be run.
Support membership categories and reduced rates as first-class concepts, not workarounds.
Give several officers appropriately scoped access, with a record of who changed what.
Export your own data in a usable format — a system you cannot leave is one you should not enter.

For what the available tools cost and which organizations they actually suit, see dues collection software. For the sequence of actually setting one up, see how to create an online dues payment system.

Frequently asked questions

What is dues management?: Everything that happens around dues beyond taking the payment: maintaining the member roster, tracking who owes what, reconciling payments against records, handling arrears, reporting to members, and transferring all of it to the next officer.
Do we need dues management software?: Not necessarily. A small organization with a simple annual subscription can run well on a bank account and a spreadsheet. It becomes worthwhile when reconciliation takes real time each month, when nobody can state the outstanding total on demand, or when handovers keep losing information.
What should a dues record contain?: For each member: a stable identifier, name, contact details, category and join date. For each payment: amount, date, method, the period it covers, a reference, and who recorded it. The period covered is the field most often omitted and the one that causes the most confusion.
How often should we reconcile?: Monthly if you can. A month of unexplained differences is an afternoon's work; a year of them is why treasurers dread handover. Reconcile weekly during the first cycle after any change to how you collect.
Should we publish who has not paid?: No. Publish aggregate figures — how many are in good standing, total collected, total outstanding — but treat individual payment status as confidential between the member and the organization. Public arrears lists are a privacy problem and damage the goodwill voluntary organizations depend on.