Remittance Files

Regardless of whether you are using our File API through an SFTP connection or by uploading files through the Back Office, SlimPay supports a range of remittance file formats that allow merchants to deposit batch orders on our server.

This means you can process multiple payment orders (direct debits, credit transfers), update customer bank details, create, modify or cancel payment schedules, create Back Office user accounts or import existing mandates. . . using a single CSV file for each type of order.

Please note: The documentation below is for injecting remittance orders using our v1 format. To inject batch SEPA direct debit payments using the v2 format, please refer to our payments documentation for the appropriate file structure.

There are three types of lines contained in the remittance file: Header, Operation order and Footer. A remittance file requires one header and one footer, but there is no limit on the number of operation order lines. This means you can process dozens, hundreds or even thousands of orders in a single transaction!

Each file can only contain one type of order, meaning that direct debits, credit transfers or any other type of order must be sent in separate files. The merchant must ensure the remittance files provided comply with the different formats described on this page.

Header line

The first line of the remittance file is the header line. It mostly contains the merchant's information, allowing SlimPay to find the corresponding details stored on the server. The line consists of 14 fields, each separated by a semi-colon ;.


FieldContentDescriptionStatus (m = mandatory,
o = optional)		Max number
of characters
1 Type of line 0 (zero) for the first line of the file M 1
2 Merchant reference Unique value provided by SlimPay for each merchant. If the Merchant has divided their activity into several entities this field must contain the value: Merchant reference-Merchant entity (dash separated) M for mandate migration and bank account updates (file types 4 and 14) 35
3 Reference of the remittance file Value given by the merchant which SlimPay refers to in the acknowledgement file 0 35
4 Name of Merchant's company M for mandate migration and bank account updates (file types 4 and 14) 35
5 Empty
6 Empty
7 Empty
8 Remittance date ISO 8601 Date format (e.g. 2011-07-25) O 10
9 Number of orders Number of payment order lines in the file M
10 Merchant's BIC Bank Identification Code (or SWIFT code) O 11
11 Merchant's IBAN International Banking Account Number O 34
12 Country specific bank account details of Merchant Bank code O 5
13 Country specific bank account details of Merchant Branch code O 5
14 Country specific bank account details of Merchant Account number O 11

Below is an example of a header line, designating a single payment order.

0;;;;;;;;1;;;;;

Operation order line

Each operation order is represented by its own line in the remittance file. Made up of 33 fields (each separated by a semi-colon ;), each line consists of information about the user and the specific order/payment details.

You can find the structure of the various remittance file formats by clicking on the tabs below:


FieldContentDescriptionStatus (m = mandatory,
o = optional,
n/a = not applicable)		Max number
of characters
1 Type of order 1 Direct debit (if the user is a debtor) M 2
2 User reference This reference must be the same as the one the merchant transferred to SlimPay during the mandate signature process. The value is therefore equal to clientReference M if IBAN, BIC and Bank details are empty (fields 10, 11, 12, 13 and 14) 35
3 Transaction reference Transaction reference provided by the merchant and used by SlimPay in case of an R-Transaction. Must be alphanumeric, without special characters 0 35
4 Customer's company Company name if the user is a corporate user N/A 35
5 Customer's full name The last name and first name of the user N/A 32
6 Customer's email Email address of the user N/A 70
7 Customer's mobile phone International format, must include a + symbol (e.g. +33622446688) N/A 16
8 Date of direct debit or credit transfer Date on which the merchant intends to debit or credit the user's account. For debit, if the timeframe is too short, SlimPay will apply the earliest possible date.
ISO 8601 Date format (e.g. 2011-07-25)		 O 10
9 Amount in euros The amount of the direct debit or credit transfer, in euros (1457.25, for example) M 19
10 Customer's BIC Bank Identification Code (or SWIFT code) IBAN/BIC or RIB are M if user reference (field 2) is empty 34
11 Customer's IBAN International Banking Account Number IBAN/BIC or RIB are M if user reference (field 2) is empty 34
12 Customer's bank code Bank code IBAN/BIC or RIB are M if user reference (field 2) is empty 5
13 Customer's branch code Branch code IBAN/BIC or RIB are M if user reference (field 2) is empty 5
14 Customer's account number Account number IBAN/BIC or RIB are M if user reference (field 2) is empty 11
15 Label Label which will appear on the bank statement of the customer O 140
16 Customer's billing address Line 1 of the billing address N/A 70
17 Customer's billing address Line 2 of the billing address N/A 70
18 Customer's billing address Postal code N/A 5
19 Customer's billing address City N/A 35
20 Customer's billing address ISO 3166 country code (e.g. FR for France) N/A 2
21 Invoice reference Reference of the invoice O 35
22 Customer's title Title (0 = Mr, 1 = Miss, 2 = Mrs) N/A 1
23 Customer's first name First name of the user
Forbidden characters:
  • numerals 0-9
  • the at sign @
  • quotation marks "
  • forward slash /
  • backslash \
 N/A 32
24 Customer's last name Last name of the user
Forbidden characters:
  • numerals 0-9
  • the at sign @
  • quotation marks "
  • forward slash /
  • backslash \
 N/A 70
25 UMR Unique mandate reference O 35
26 Profile Name of the profile to be used for user creation N/A 70
27 Sequencing Deprecated N/A 4
28 SCI SCI of the creditor related to the mandate. Only for mandate imports (file type 14) N/A 35
29 Number of scheduled payments The number of direct debits to be scheduled. If no value is provided, the direct debit plan is unlimited N/A 3
30 Frequency The frequency of direct debits. Values include: daily, weekly, monthly, everyTwoMonths, everyThreeMonths, everyFourMonths, semiannual, yearly (case sensitive) N/A 16
31 Type of R-Transaction REJ for a reject, RET for a return N/A 3
32 Date of R-Transaction Receipt date of R-Transaction.
ISO 8601 Date format (e.g. 2011-08-02)		 N/A 10
33 Error code AM04 SEPA error code of the R-Transaction N/A 4

Below is an example of a payment order line, designating a direct debit of €570.99 from a testSubscriber.

1;testSubscriber;;;;;;;570.99;;;;;;;;;;;;;;;;;;;;;;;;

The remittance file must end with a footer line. The footer is structured with 9 fields, separated by a semi-colon ;.


FieldContentDescriptionStatus (m = mandatory,
o = optional)		Max number
of characters
1 Type of line 9 to designate the last line of the file M 1
2 Empty
3 Empty
4 Empty
5 Empty
6 Empty
7 Empty
8 Empty
9 Total amount The total amount of the payment orders in the file, in euros (23568.34, for example) M if the file contains payment orders (file type 1 or 2) 19

Below is an example of a footer line.

9;;;;;;;;4567.99

Putting the header, payment orders and footer lines together, below is an example of a complete direct debit order file.

0;;;;;;;;3;;;;;
1;testSubscriber1;;;;;;;4567.99;;;;;;;;;;;;;;;;;;;;;;;;
1;testSubscriber2;;;;;;;150.00;;;;;;;;;;;;;;;;;;;;;;;;
1;testSubscriber3;;;;;;;267.50;;;;;;;;;;;;;;;;;;;;;;;;
9;;;;;;;;4985.49

For details regarding file acknowledgement and error handling, please refer to our Overview section.