What data should my SEPA collections CSV file contain?
The file can include many columns, but only some are required for generating a valid SEPA direct debit file. Below is what we read from your CSV and which fields are mandatory. - Cliente
- name: client name (required)
- Client - ID: ID of the client.
- Customer - Email: Customer Email
- Customer - reference: Customer identifier in our system.
- Bank account - BIC: Destination bank identifier. It’s best to leave blank,
we fill it. - Bank account - IBAN: Bank account in IBAN format (mandatory IBAN or CCC) - Bank account - CCC: Bank account in old format, we do the conversion (mandatory IBAN or CCC) - Debit - description: concept of the receipt that v
was the customer in your online banking (required) - Debit - amount: amount of receipt. Indicate two decimals, ex: 52.91 (mandatory) - Debit - debit date: Date on which the receipt will be charged to the customer. If not set, one is set for the entire file defined in the co
nversión. En caso de indicarse, el formato debería ser DD/MM/YYYY (o su variante con -). Ej: 23-12-2018 . - Adeudo - referencia: Identificador del recibo en nuestro sistema. No es obligatorio, pero si lo tienes puede ser interesante ponerlo para identificar las devoluciones. -
Mandato - fecha de firma: Fecha en la que el cliente nos firmo el mandato o autorización para realizarle cargos en su cuenta. Obviamente no puede ser en el futuro y el formato debería ser DD/MM/YYYY (o su variante con -). Ej: 23-12-2018 (obligatorio). - Mandato - referencia:
Identifier of the authorization that the client gave us to make charges, something like “the contract identifier”. It must be unique in our company, not repeated between clients. (mandatory). It is important to understand the concept of mandate. The mandate is the self
rización que nos dió el cliente para realizarle cargos y hay varias cosas a tener en cuenta: - La pareja “referencia” y “fecha de firma” debe ser única. No se debe repetir la referencia con distintos clientes, ni se puede/debe usar la misma referencia con fechas distintas, puest
or that can cause unpaid due to error in the data. - The date cannot be in the future. - By complying with the above, we could have more than one mandate per client, but we should avoid it as far as possible because it can cause more collection problems.
ntar use for a client always the same signature-reference pair.
