IN THIS ARTICLE▾
A single revenue platform lets an SA school run fee collection, event ticket sales, and fundraising through one system instead of three separate ones.
Ask most SA fee-paying schools how they collect revenue from parents, and the honest answer is: on several different systems, not one. Tuition and recurring fees run through a debit-order or billing platform. Event tickets, a gala dinner, a fun run, a fundraising quiz night, get sold through a separate ticketing tool, or a spreadsheet, or a WhatsApp-and-EFT arrangement. Fundraiser contributions get tracked yet another way. Each revenue line has its own system, its own reconciliation, and its own view of who's paid and who hasn't.
This piece looks at what a single revenue platform for a school actually means in practice, not as an abstract idea, but as a description of what changes when every parent-facing revenue line, not just recurring fees, runs through one system.
Where school revenue actually fragments today
Recurring fees, tuition, transport, activities, are usually the most mature part of a school's billing setup, because they're the largest and most predictable revenue line. Everything else tends to be handled more informally.
Event tickets for a school fundraiser, gala, or fun run are often sold through a generic consumer ticketing platform not built for schools, or tracked manually against a guest list. Fundraiser or capital-campaign contributions get logged in a spreadsheet, sometimes cross-referenced against a parent's fee account, sometimes not. Once-off event charges, a matric dance contribution, a sports-day levy, get collected however's easiest in the moment, which usually means outside the school's core billing system entirely.
None of this is unreasonable, given that these revenue lines are smaller and less frequent than recurring fees. But it means a parent's full financial relationship with the school, fees, events, fundraising, is scattered across multiple systems that don't talk to each other, and the school's own picture of total parent-facing revenue requires manually stitching those systems together.
Why this matters beyond convenience
Two consequences follow from the fragmentation, beyond it simply being inconvenient to manage.
The school doesn't have one view of a family's full financial relationship. A finance officer looking at a parent's fee account can't necessarily see, in the same view, whether that family bought gala tickets or contributed to the building fund, because that data lives somewhere else.
Event and fundraising revenue is harder to reconcile and report on. Where recurring fees have a mature recon process behind them, event ticket sales and fundraiser contributions often get reconciled manually, after the fact, against a guest list or a bank statement, exactly the kind of manual matching exercise that recurring fees have already moved away from.
What "single revenue platform" means as a direction
The idea is straightforward: extend the same billing, mandate, and recon infrastructure that already runs a school's recurring fees to also handle event ticket sales and other parent-facing revenue, so that every line, fees, tours, events, fundraising, sits inside one system with one reconciliation view, rather than fees on one platform and everything else scattered elsewhere.
Recurv is building in this direction. An event-ticketing capability is part of where the platform is headed, expanding beyond recurring fee collection into the other revenue lines schools currently manage separately. We're not committing to a specific date here, the point of this piece is the direction of travel and the problem it addresses, not a launch announcement.
What this would change for a school, directionally
If a school's fee billing, tour payment plans, and event ticket sales all sat on one platform, a few things follow structurally. The finance office would have one place to see a family's complete financial relationship with the school, rather than checking several systems. Event and fundraiser revenue would reconcile the same way recurring fees already do, rather than requiring separate manual matching. And a school running an event, a gala, a fun run, a matric function, wouldn't need to stand up a separate ticketing tool and then manually cross-reference the results against its core billing system afterward.
Why this is a school-specific problem, not a generic one
Generic event-ticketing platforms exist and work fine for one-off consumer events. What they don't do is connect back to a school's existing parent-fee relationship, they treat every ticket buyer as an anonymous consumer, not as a parent with an existing account, fee history, and mandate already on file. A platform built specifically for schools can connect event revenue to the same family record that already holds tuition, transport, and activity billing, which is the piece a generic ticketing tool structurally can't offer.
What this isn't
It isn't a promise of a specific delivery date. We're describing where the platform is headed and the problem this direction addresses, not committing to a quarter or month for a specific feature.
It isn't a claim that Recurv already does this today for every school. Recurring fee billing, multi-stream billing, and payment plans are live capabilities today. Event ticketing is part of the platform's direction, not a currently shipped feature for every school.
It isn't a suggestion that schools should hold off adopting Recurv for fee billing while waiting for event ticketing to arrive. The fee-billing and multi-stream capabilities described elsewhere on this blog are available now and solve real, current problems on their own; the single-revenue-platform vision is the direction the product is expanding toward on top of that foundation.
Related reading
See how Recurv handles recurring billing for schools & education.
View Schools & Education use case →