# **SEPA direct debits** for sports centers

Hundreds of dues in a single operation. You see exactly what you are about to charge and to whom before anything goes to the bank.

- **URL:** https://sporttia.com/en/features/direct-debits-and-invoicing
- **Product:** Sporttia, sports facility management software
- **Module:** `receipt`
- **Data updated:** 2026-08-31

## On screen: What you are about to charge, before you charge it

- You give the concept and the month, and the list of debits that would go out appears, with each member and amount.
- The total shows before anything is sent: two hundred and eighteen debits and their sum.
- Only on generating does it go to the bank, and those charges are then treated as collected.

## What usually happens

- Membership dues collected one by one at the desk every month.
- Batch files prepared by hand and rejected by the bank over one mistyped IBAN.
- Returned debits nobody chases, because nobody knows which ones they were.
- Councils that collect through the banks and need payment slips with a barcode.
- Receipt numbering kept separately so that it stays sequential.

## A month of dues, one operation

### Two hundred debits at once

Every direct-debited due for the month goes out together in the file the bank asks for. The desk collects none of them.

### You see what you are charging before you send it

The full list with each member and their amount, and the total. If something is off, you see it before it reaches the bank.

### And the bank does not reject it

The system flags zero amounts, invalid IBANs and empty concepts, which is what a batch gets rejected for.

- **3** — rejection reasons flagged before you send: zero amount, invalid IBAN, empty concept
- **SEPA 19** — the file format every Spanish bank asks for
- **Q60** — barcoded payment slips, for municipal collection

## First you look, then you charge

The screen imposes that order, and it is not a detail: once generated, those charges are treated as collected.

|  | Before | After |
| --- | --- | --- |
| Before generating | You give the concept, the month and the charge date | The list of debits appears with each member, amount and the total |
| On generating | The batch does not exist yet | A file ready for the bank and the charges marked |

Being able to look at the list first is what avoids the expensive mistake: finding out from the statement that you charged dues to members who had already cancelled.

## When the bank returns a debit

### You know exactly which ones

You load the returns file and every returned debit is marked, with its member. None goes unchased any more.

### And they go back to outstanding

A returned charge reappears as debt, ready to chase or to include in next month's batch.

### With the turnstile as leverage

At centers with access control, a returned due blocks entry until it is settled. It is the most effective way to get paid.

## What a council needs

### Collection through the banks

Q60 payment slips with a barcode, and afterwards the bank's file to mark as paid whatever was settled over the counter.

### An audit trail for oversight

For every batch you keep the name, whether it was sent, whether it is collected and the total. You can reconstruct what was charged and when.

### Sequential receipt numbering

The system keeps it, using whatever pattern the center defines, and rolls it over at the start of a new financial year.

## What members sort out themselves

Desde la app gratuita, sin pasar por el mostrador.

- Set up a direct debit by giving their IBAN once.
- See which dues have been charged and what state they are in.

## What you should know

- Two things are needed for a due to join the batch: the member's IBAN and the due being set to collect by direct debit. With only one, it stays out.
- Generating the batch treats those charges as collected before the bank confirms. Returns are resolved afterwards, by loading their file.
- The format is SEPA rulebook 19. Apart from Q60 payment slips, there is no export to other formats.

## Frequently asked questions

### What batch format does Sporttia generate?

A SEPA file to rulebook 19, the one every Spanish bank asks for, with all outstanding direct-debited dues. Before generating it, it shows the list of what will go in and checks amounts, IBANs and concepts.

### What does a member need for their due to join the batch?

Two things: their IBAN on file and their due set to collect by direct debit. A due collected another way does not join, even if the member has an IBAN.

### Can I see what I am about to charge before sending it to the bank?

Yes, and that is the order the screen imposes. You give the concept, the period and the charge date, and the list of debits appears with each member, their amount and the total. The batch does not exist until you generate it.

### Can a batch that has already been generated be cancelled?

Yes, and the charges then go back to outstanding so you can generate it again. The exception is if specific debits had been removed from inside it: in that case you first have to recover that charge from the accounts.

### Does it work for a council that collects through the banks?

Yes. As well as the SEPA batch, it generates Q60 payment slips with a barcode, and afterwards you load the bank's file to mark as paid the ones settled over the counter.

## More information

- Full feature catalog: https://sporttia.com/en/features.md
- Getting started: https://sporttia.com/en/getting-started.md
- Landing page by center type: https://sporttia.com/en/sports-management-software/councils.md
- Landing page by center type: https://sporttia.com/en/sports-management-software/swimming-pools.md
- Landing page by center type: https://sporttia.com/en/sports-management-software/sports-academies.md