Cairos
Invoicing
Invoicing softwareQuotesRecurring invoicesExpenses and suppliersReceipts and cash flow
Accounting and tax
AccountingAEAT tax formsRecord booksFixed assetsIGIC and the Canary Islands
Operations
Inventory and warehousesCRMTime trackingProjectsGrants and funding
Compliance
VeriFactuTicketBAIElectronic invoicingAll the regulationsSecurity and data
By type of business
Self-employedSmall businessesAccountants and tax advisersForeigners in SpainStartupsRetail and shops
By sector
Hospitality and restaurantsConstruction and renovationProfessional servicesE-commerceAll sectors
By legal structure
AssociationsFoundationsCooperativesSports clubsAll legal structures
Switching software
ComparisonsAn alternative to HoldedMigrating your data
Free tools
Invoice templateVAT calculatorIRPF calculatorAll the tools
Learn
GuidesGlossaryTax calendarBlog
Developers
API and documentationGet started in five minutesResource referenceWebhooks
Help
Help centreContact
Pricing
Start for free Log in
Glossary · Payments and banking

Batch: 320 debits in a single file

The bank does not want a list in an email: it wants an XML in an exact format. And if one line is wrong, it does not reject that line: it rejects the whole file.

With the rule citedWith a worked exampleNo fluff
In one sentence

The set of debits or payment orders sent to the bank in one go, in a file in a standard format.

Payments and banking · Cairos glossary

The format is the ISO 20022 standard. For direct debits, the message is pain.008 (CustomerDirectDebitInitiation); for transfers, pain.001. The Spanish implementation guide is published jointly by the AEB, the CECA and the UNACC, and it is updated with each revision of the standard: the message version your bank accepts today is not the same one it accepted ten years ago, so it is worth checking before you generate anything.

What it contains

  • Header: the creditor, their SEPA identifier, the number of transactions, the total amount and the requested collection date.
  • One line per debit: the mandate reference and the date it was signed, the debtor's name and IBAN, the amount and the description.

The sequence

Each debit carries an indicator: FRST (first), RCUR (recurring), OOFF (one-off) and FNAL (final). Since the 2016 revision it is no longer compulsory to flag the first one: everything can be presented as RCUR, which simplifies things considerably.

An example

320 debits of €39 fit in a file of about 200 KB. The bank confirms receipt, charges on the requested date, and the returns arrive afterwards, separately and with their reason codes.

The mistake that comes up most

Building the file by hand in a spreadsheet. Amounts go with a decimal point and no thousands separator, dates in ISO format and names without characters the standard does not accept. One badly formed field and the bank returns the whole file, usually the day before the collection date.

Where this carries on in Cairos: Generating batches from the invoices.

This, handled without thinking about it

Cairos keeps the invoices, the record books and Hacienda's forms from the same data, so the theory on this page turns into boxes that are already filled in.

No card and no minimum term.

Support