SEPA Remittances
Direct debit collection orders and credit transfer payment orders, generated from outstanding due dates and ready to upload to your bank.
You select which due dates go into the batch (by date, by customer, by payment method) and the system produces the file in the standard format your bank expects. What used to be keying transfers one by one, or hand-fixing a file the bank rejects over a single digit, becomes a two-click process.
Every batch is recorded with its instruments, so you know what was sent, when and with what outcome. Returned debits come back into the ledger with their reason, without losing track of which invoice it was or how many times collection has been attempted.
From due date to file
Select, generate and upload: that is the whole process
The due dates going into the batch are picked with the usual filters (by date, by customer, by payment method, by amount) and the system produces the standard file your bank expects.
What disappears is the part that eats time and causes errors: keying transfers one by one into online banking, copying IBANs by hand or fighting a file the bank rejects wholesale over one miscalculated check digit. Bank details come from the customer or supplier record, already validated.
Each batch is recorded with the instruments it contains, so afterwards you know what was sent, when and with what outcome.
Collections and payments
Direct debits to collect, transfers to pay
Two different flows, both handled equally well from the same place.
Collection orders
Direct debits charge the customer's account for the due dates that correspond to them. Each one travels with its mandate reference and the information the customer needs to identify the charge on their statement, which prevents half the returns caused by simple confusion.
Payment orders
Credit transfers settle suppliers and creditors in a single operation, grouping several due dates for the same payee where appropriate. The batch is prepared in advance and sent on the right day.
In both cases instruments change status when remitted, so the ledger reflects what is in progress and does not include it again in the next batch.
Returns
A returned debit cannot fall off the map
When a direct debit comes back, the instrument returns to the ledger with its return reason and its charges, keeping the link to the invoice that originated it. Without that, a returned debit becomes a loose entry at the bank that somebody has to investigate.
With the instrument live again, the chasing process continues where it left off: you can see how many collection attempts it has had, what was agreed with the customer and whether to remit it again or handle it another way.
And because bank transactions arrive on their own through reconciliation, the return is spotted when it happens rather than while balancing the following month.
Clearing things up
Frequently asked questions
Answers to what we get asked most.
What format does it generate for the bank?
The standard SEPA file your bank expects, both for direct debit collection orders and for credit transfer payment orders. Bank details come from the customer or supplier record, already validated, so there are no hand-typed IBANs.
How do I choose what goes into each batch?
With the usual filters over outstanding due dates: by date, by customer, by payment method or by amount. On remittance, instruments change status, so the ledger reflects what is in progress and does not include it again in the next batch.
Can I pay several suppliers at once?
Yes, the credit transfer batch settles suppliers and creditors in a single operation, grouping several due dates for the same payee where appropriate. It is prepared in advance and sent on the right day.
What if the customer returns the debit?
The instrument returns to the ledger with its return reason and its charges, without losing track of which invoice it was or how many collection attempts there have been. Because bank transactions arrive on their own through reconciliation, it is spotted when it happens rather than while balancing the following month.
Accounting and finance
Invoices post themselves, AEAT tax forms are built from real data and the bank reconciles almost on its own. With Verifactu, TicketBAI and SII solved.
Verifactu
Compliance with the Spanish tax authority's Verifactu regulation: every invoice generates a signed invoicing record chained to the previous one, with its QR code and, if you choose that mode, immediate submission to the tax authority.
View moduleTicketBAI
TicketBAI compliance for invoicing to the Basque regional tax authorities: electronic signature on every invoice, chained records, QR code and submission to the relevant administration.
View moduleSII (AEAT)
Immediate Supply of Information on VAT: the record books of issued and received invoices are reported to the Spanish tax authority within the legal deadline, with no manual work.
View moduleBank Reconciliation
Connect to your banks, download transactions without anyone exporting a file, and reconcile them automatically against receipts, payments and accounting entries.
View moduleReceivables and Payables
Every instrument and due date in one place: what is left to collect, what to pay, when each falls due and what state it is in.
View module