For organizations
How to Track Who Has Paid Dues
What a dues record needs to contain, why spreadsheets drift out of sync with the bank, and how to run a reconciliation you can defend at a general meeting.
7 min readUpdated
Tracking dues sounds like bookkeeping, but in a membership organization it is really about standing: who is entitled to vote, to stand for office, to access benefits. Getting it wrong has governance consequences, not just financial ones.
This guide covers what to record, how records drift, and how to reconcile them.
What a dues record needs
For each member: an identifier that does not change, their name, contact details, membership category, and their join date. For each payment: the amount, the date, the method, the period it covers, a reference, and who recorded it.
The period covered is the field organizations most often omit, and it is the one that causes the most confusion. A payment of the annual amount does not tell you which year it was for. Without that field, a member who paid late for last year looks identical to one who paid early for this year.
Why spreadsheets drift
Spreadsheets are not the problem in themselves — plenty of small organizations run on them successfully. They drift because they are updated by hand from a separate source, and any manual copy introduces a delay and an error rate.
The usual failure pattern: payments arrive in the bank continuously, the sheet is updated in batches, someone edits a row without a note, two officers keep separate copies, and by the time anyone checks, nobody can say which version is authoritative. The fix is not a better spreadsheet but a shorter distance between the payment and the record.
Running a reconciliation
Reconciliation means proving your record matches the money. Take a defined period, list every payment in the bank or platform for that period, list every payment in your roster, and account for every difference in both directions.
Items in the bank but not the roster are usually unidentified payments — chase the reference. Items in the roster but not the bank are more serious: either a cash payment that never reached the account, or a record entered in error. Both need explanation, and the explanation belongs in a note attached to the record, not in someone's memory.
Do this monthly if you can. A month of unexplained differences is an afternoon's work; a year of them is why treasurers dread handover.
Reporting to members
Members are entitled to know the aggregate position: how many are in good standing, total collected, total outstanding. Publishing this regularly does more for collection rates than reminder messages, because it makes paying feel normal and visible.
Individual payment status is different. Treat it as confidential between the member and the organization — a public list of who has not paid is a governance and privacy problem, and it damages the goodwill that voluntary organizations run on.