Program revenue that reconciles by spreadsheet is a process problem, not a software problem. Picture the fourth business day of the month: the registrar exports one file from the registration system, the finance clerk exports another from the bank, and someone highlights rows until the two totals are a few hundred dollars apart. In this hypothetical, the gap turns out to be one refunded registration and a chargeback nobody mentioned.
This happens in departments that own perfectly good software. The registration system knows what was sold. The general ledger knows what was deposited. Neither one knows about the other. If you are evaluating recreation registration software, accounting integration is worth testing before you sign.
The registration system and the ledger count different things
Registration systems are built around people and programs. Accounting systems are built around funds and accounts. As a hypothetical, a single Saturday of camp signups can produce revenue that belongs to three program codes, a refundable deposit, a scholarship offset, and a non-resident surcharge your council directed to a separate pool. The bank sees one settlement. Your ledger needs several entries.
Manual reconciliation closes that gap with staff hours. It also puts a person in charge of deciding where money goes, with no rule written down anywhere. That is the kind of gap that also feeds revenue leakage.
Public money raises the bar
Private clubs reconcile for management. Public departments also reconcile for accountability, and records have to survive. As one example, the Texas State Library's local retention schedule lists 2 years for logs and applications documenting park and recreational facility reservations, 2 years for program files such as rosters and activity schedules, and 3 years from the end of the activity for liability waivers, longer if there was an accident. Retention rules vary by state, so check yours.
Card fees add another layer. Washington's MRSC guidance says surcharges may only be applied to credit cards, not debit cards, and are capped at 4% of the transaction. Whatever your state allows, those fees have to land somewhere in the ledger. "Netted out of the deposit" is not an answer an auditor will like. For who carries the card-security burden, see who owns PCI compliance.
A CSV export is not an integration, whatever the proposal says
Vendors call both of these integration. They are not the same thing.
- A CSV export is a file someone downloads, reformats, and uploads. It works until the person who knows the format takes a vacation.
- A real integration posts entries automatically on a schedule, maps each program to a GL account you control, and fails loudly when something does not match.
Put these in the requirements, not the demo:
- Program-level and fund-level GL account mapping that your finance staff configures, not the vendor.
- A daily settlement record that ties gross revenue, processing fees, refunds, and chargebacks to a single bank deposit.
- Refunds, credits, and voids as their own journal entries with the original transaction referenced.
- An audit trail showing who changed a fee, when, and what it was before.
- An open API, so the connection survives your next accounting system.
Ask for pricing the way the City of Rock Island did in its 2025 recreation management RFP, which requested annual subscription, implementation and training, and data migration as separate line items. Integration work often hides in the implementation and migration lines, so see how to read a quote past the subscription line, and how to write the RFP requirements.
No software can automate a posting rule nobody wrote down
Write down how a single camp registration should hit your ledger today, start to finish. If nobody can produce that in one page, no software will fix month-end, because the rule you would automate does not exist yet. Moving systems? Plan the historical balances too, using this data migration go-live plan.
Frequently asked questions
How do you reconcile recreation registration payments with the general ledger?
Require a daily settlement record that ties gross revenue, processing fees, refunds, and chargebacks to a single bank deposit, plus program-level GL account mapping that your finance staff controls. Then write down the posting rule for one registration so the software has something to automate.
Can a parks department add a credit card surcharge to registration fees?
It depends on your state and your card brands. Washington's MRSC guidance says surcharges may only be applied to credit cards, not debit cards, and are capped at 4% of the transaction. Check the rules where you operate before setting a fee.
Is a CSV export the same as an accounting integration?
No. A CSV export is a file someone downloads, reformats, and uploads by hand. A real integration posts entries automatically on a schedule, maps each program to a GL account you control, and flags entries that do not match.
How long do parks and recreation departments have to keep registration records?
It varies by state. Texas's local retention schedule lists 2 years for facility reservation logs and applications, 2 years for program files such as rosters, and 3 years from the end of the activity for liability waivers, longer if there was an accident. Check your own state's schedule.
What should we ask for in recreation software pricing?
Ask for subscription, implementation, and data migration itemized separately. The City of Rock Island's 2025 recreation management RFP asked vendors to price in a format like that, with those as separate lines.
Want the current cost of your manual close in hours and fees? Start with our free cost-recovery audit.
Find your leaks
See what your organization could recover.
A 20-minute audit, your numbers, no obligation.
Get my cost-recovery audit →Or get one practical playbook like this by email, every week.