Invoicing, credit control and finance

Invoices with detail lines, credit notes and refunds, raised against membership, events, courses, products and anything else charged for, in one ledger rather than several. One ledger is the point: it is what lets somebody answer what a member owes in total rather than what they owe for their subscription, and it is why a member's outstanding balance can be broken down into membership, events and education instead of arriving as a single unexplained figure.

Card and direct debit providers configured per organisation: Stripe, GoCardless, Opayo with 3-D Secure, Paysafe and Authorize.Net among them. You keep your existing merchant relationship rather than moving it to suit the platform, which matters more than it sounds, because changing merchant account is a commercial negotiation and a compliance exercise rather than a configuration change, and no software decision should force one.

Provider confirmations arrive by webhook. Payment records write against the invoice, and the invoice balance is recalculated server-side on every payment change, net of refunds. The balance is never computed in the portal, which is what stops a member and a finance officer seeing two different numbers. It also means a refund in flight or a part payment shows the same way to both of them rather than resolving differently depending on which screen you are looking at.

Direct debit mandates, instalment schedules and payment plans, with collection scheduled from the plan and failures returned into a worklist. The mandate is held against the subscription rather than the member, so the platform notices when somebody comes off direct debit at renewal. That is one of the earliest lapse signals available and it is invisible to any system that files a payment method once against a person.

Aged debt by member and by organisation, reminder sequences, and the escalation path your finance team actually uses rather than a generic dunning process. Organisational debt is the case that catches systems out: the person who owes is not always the person who benefits, so employer-paid and corporate balances have to be chaseable against the organisation while the membership stays attached to the individual.

Reconciliation into your finance system, with VAT treatment applied at the point of invoicing rather than corrected afterwards. Integration with your accounting package rather than a re-key, so Xero, Sage or Business Central receives what happened instead of somebody transcribing it monthly. The ambition is not one source of truth for everything but one direction of truth per fact: the member balance lives here, the accounts live there.