Subscriptions and renewals

Rates sit against each grade with an effective date, so next year's card can be loaded, checked and argued about long before it applies to anybody. Concessionary, hardship, overseas and joint rates live alongside the standard rate for each grade rather than as exceptions somebody has to remember to apply. Where a body charges branch or chapter levies, those are added here too, so the figure a member is shown is the whole figure and not the opening of a conversation.

Anniversary or common renewal date, and both at once in the same organisation where different grades work differently. That combination is the one that catches general-purpose systems out, because it means renewal is not a date in the calendar but a rolling operation with peaks in it. Joining and transferring both land mid-cycle, so part-year and pro-rata rules apply on their own rather than being worked out by hand on the afternoon somebody asks.

Members are staged by renewal date. Fee and tax are calculated in the CRM, invoices raise, and employer-paid, group and organisational members are invoiced to whoever actually pays rather than to whoever holds the membership. Direct debit files go to the scheme with the advance notice it requires. Then the part everybody forgets: a member instructs payment, but the ledger only settles when the provider confirms it. A direct debit is not paid at the moment somebody clicks, and a report built on the click will flatter you for about a week.

Reminder sequences run on a schedule against renewal state, escalating as the date passes and stopping the moment payment is confirmed. That last part sounds trivial and it is the thing members actually notice. A sequence that carries on chasing somebody who paid a fortnight ago undoes more goodwill than the whole run creates, and it happens whenever reminders are driven by a list captured earlier rather than by the state at the moment of sending.

Returned collections come back into a worklist rather than quietly disappearing: an expired card, a closed account, a mandate somebody cancelled and forgot about. Each is re-presented or worked by hand, with an owner and a status against it. This is where a renewal run is genuinely won or lost. The successes need nobody. The failures are the actual work, they arrive in the same fortnight as everything else, and they are the reason a renewal report showing only what collected is worse than no report at all: it builds confidence while a queue builds behind it.

Grace periods are set by grade. When somebody does lapse, their entitlements, register listing and portal access all follow the CRM record automatically rather than waiting on somebody to remember which four places need updating. Reinstatement runs all year rather than only at renewal, and where your rules allow it a returning member keeps their continuity, so somebody who comes back in March is not treated as a brand new joiner with their years reset to nothing.

Instalments and payment plans are held against the subscription itself, with the schedule attached and collection scheduled from it. That keeps the plan and the membership in one place, so a member halfway through paying is an ordinary case rather than something somebody tracks separately in a spreadsheet. It also means the balance the member sees and the balance your finance team sees come out of the same calculation, which is what stops the two of them disagreeing while one is on the phone to the other.