The gap between tasks is often the problem
The treasurer understands the process, the board receives isolated questions and every returned payment starts another search. If only one person knows what has been checked, absence or a board change becomes a risk. A shared working record helps the team keep track.
Prepare and review the fee run
Memberships and contributions provide the basis for invoices and fee runs. Amounts, mandate details and unresolved record issues must be reviewed before export. Start with a small sample against your fee rules. Complex family and age-based rules need prior agreement; automatic support for every rule is not promised.
A SEPA file still needs bank acceptance
The product generates SEPA files and validates them against the configured XSD schema. Advance notifications are part of the workflow. XML validation does not replace acceptance by your bank. Agree the format and submission route before the first real collection. Club fees use your banking route; Stripe handles the software subscription.
Continue after collection
CAMT.053 bank statements can be matched. Open questions receive an owner, deputy and next step in the club office, giving the treasurer and board a shared status. This is not a promise of a complete automated debt-chasing process.
A realistic first milestone
Start with a reviewed sample fee run, an agreed bank format and ownership of unresolved cases. Only actual acceptance proves your bank submission route. Agree data processing and any migration scope before using real member information.
Frequently asked questions
Are members’ fees collected through Stripe?
No. Stripe handles your software subscription. The product creates SEPA files for your own bank submission route. Check mandates, format and submission before a real run.
Will every bank accept the generated file?
We do not promise universal acceptance. The file is validated against the configured schema; your specific bank portal and its requirements need a separate check.
Are fee-management functions included in every plan?
Yes. Plans differ by ongoing membership count, not by core features. Special fee rules and custom development require prior agreement.