IN THIS ARTICLE▾
An automated collection system can turn a golf club Treasurer's monthly committee report into a report that writes itself, rather than a week of manual reconciliation.
The Treasurer's monthly committee report is one of the more thankless jobs at a South African golf club. The committee meets, the Treasurer presents, and the conversation moves on to the next agenda item before most of the work behind the report has been seen. The work that's invisible is the recon week, the seven or so days between the debit-order run and the committee meeting where someone matches what came in to what should have come in, identifies the failures, decides retry strategy, and turns it into a one-page summary the committee can read in three minutes.
This piece is about what happens to that week, and to the report itself, when recon writes itself.
What goes into the committee report today
At most clubs, the Treasurer's monthly committee report carries some version of the following.
The financial summary: subs collected this month, outstanding subs (with member count and rand value), once-off fees collected, variances against budget. The defaulter view: members in arrears, length of arrears, action taken. The cycle outcome: how the debit-order run went, what failed and why. The narrative section: anything unusual the committee should know about, a member who's queried a charge, a recovery that needs a write-off decision, a fee structure question to escalate.
The financial summary and the defaulter view are the parts that get questioned most. *"How many members owe more than two months?"* *"What's the trend on failed collections?"* *"Are we down on subs versus this time last year?"* These are reasonable committee questions. The Treasurer's job is to answer them with a number, not a feeling.
The narrative section is where the Treasurer's judgment lives. The committee usually trusts that section because they trust the Treasurer. The financial section is where the trust gets earned, monthly, by the numbers being right.
Why the recon takes a week
The numbers being right is harder than it sounds. At a typical club, the data behind the financial summary is sourced from at least three places.
The bank's debit-order portal exports a CSV after each cycle, listing successful and failed collections. The club's accounting or member-management software has the expected receipts. The secretary's records of once-off fee collections, joining fees in transit, and any manual EFTs that came in directly. Competition entries collected at the pro shop sit in a fourth place, the daily takings sheet.
Putting these four sources together by hand is what the recon week consists of. Match the bank's failed-collection list to specific members. Identify the ones whose statement says paid but whose bank record says failed (or vice versa). Chase the gaps. Update the member records. Roll the numbers into the committee report's financial summary.
It's tractable work, but it's slow, and it's prone to small errors that get amplified at the committee table. The members-in-arrears number is only as good as the matching exercise behind it. The "what failed" view is only as good as the categorisation of the bank-returned reasons. And every month, someone is doing this from scratch.
The single-pane view
Here's what changes when every member fee runs on a single system with a single mandate behind it.
The recon source goes from four to one. The system's end-of-cycle view shows, per member: what was billed, what was collected, what failed, and the bank-returned reason for any failure. No matching exercise. No CSVs to import into spreadsheets. No reconciling the secretary's manual EFT log against the bank export.
That same view feeds the committee report's financial summary directly. Members in arrears, by length and value. Failed-collection breakdown by reason. Subs-trend month-over-month. Once-off fee collection status. The Treasurer's job shifts from *building the numbers* to *interpreting them*, which is the job the committee actually wants the Treasurer doing.
This isn't a transformation of what the Treasurer does. It's a transformation of where the Treasurer's hours go. The numbers still need to be presented, the narrative still needs to be written, the defaulter conversations still need to be had. But the underlying source of truth is one system instead of four, and that one source updates in real time after every cycle.
The committee's questions become answerable in real time
A subtle change worth calling out separately. Most committee meetings have a moment where a member asks a question the Treasurer can't quite answer in the room. *"How many of those failed collections were repeat offenders?"* *"What was the failure rate the same month last year?"* *"What's the average time-to-collect on a recovered failed debit?"*
When the data lives across four sources and the Treasurer reconciled it last week, those questions land as homework. *I'll come back to you next month.* When the data lives in one system that's queryable on the spot, those questions get answered in the meeting. The committee gets faster decisions; the Treasurer doesn't carry homework into the next month.
Treasurer-time-back, year-round
The "Treasurer time back" framing is sometimes shorthanded as "save the Treasurer ten hours a month". That number is a guess. The honest version is harder to quantify and easier to feel. The recon week becomes a recon afternoon. The committee report becomes a half-day exercise instead of a two-day one. The defaulter follow-up becomes targeted instead of mechanical, because the system has already done the categorisation.
The shape of this matters more than the magnitude. Treasurers, especially volunteer Treasurers at smaller member-owned clubs, burn out on the *mechanical* parts of the job, not the *judgment* parts. Returning the mechanical hours back to the human gets you a Treasurer who stays in role longer, which is its own win for committee continuity.
This holds year-round, not just at year-end. The pain of a slow recon is most visible when last year's outstanding subs collide with this year's first run. But the operational benefit accrues every month, evenly. A club running this way feels the difference in March and August as much as in January.
What it looks like at a club already running this way
An established SA golf club has been running every member fee on Recurv for some time. The Treasurer there reports that the committee report cycle compressed from a five-to-seven-day exercise into a one-day exercise. The financial summary section of the report draws from one source. The defaulter view is a filtered query, not a manual roll-up. The narrative section still gets the Treasurer's full attention, which is the way it should always have worked.
That experience won't be identical at every club. Volume, member mix, fee inventory, and committee culture all shape it. But the structural change, one source of truth replacing four, and the recon week compressing, is what most clubs see in the first cycle.
What this isn't
It isn't an automated Treasurer. The committee still needs a human in the role; the financial judgment, the narrative, the relationship with the auditor and the bank are still the Treasurer's. The system runs the numbers; the Treasurer runs the meaning.
It also isn't a replacement for the club's existing member-management software. If the club uses a member-management package for fixture management, member statements, and handicap admin, that stays. Recurv handles the collection cycle behind those systems, the money flow and the recon, and the two integrate where they need to.
Related reading
See how Recurv handles recurring billing for golf clubs.
View Golf Clubs use case →