POST
/
sepa-xml-files
/
generate
curl -X POST \
 /sepa-xml-files/generate \
 --header "Content-Type: application/json" \
 --header "Authorization: Bearer <token>" \
 --data '{
    "bankAccountId": "ad8f1b9e-2b0a-4b0a-8b0a-4b0a8b0a8b0a",
    "splitPayments": "1",
    "batchBooking": "1"
}'
{
  "message": "No payments to process."
}

Authorizations

​
Authorization
string
header
required

Value for the Authorization header parameter.

Body

The new SepaXmlStatement resource
​
bankAccountId
string | null

The bank account to generate the SEPA XML for. If not set, the default settings will be used, defined in the sepaXml settings.

Example:

"ad8f1b9e-2b0a-4b0a-8b0a-4b0a8b0a8b0a"

​
splitPayments
boolean | null

If set to true, each payment will be split into a single SEPA XML file. Some banks shows only one payment transaction for all sepa debits / credits per SEPA XML file, which could be not wanted. If not set, the default settings will be used, defined in the sepaXml settings.

Example:

true

​
batchBooking
boolean | null

If set to true, all sepa payments will be shown as one transaction on your bank account. Recommendation: Set this to false and use our bank transaction synchronization to get the best results.

Advantages of using the bank account synchronization:

  • more accurate payment status and payment date
  • correct accounting of the payment
  • declines are handled automatically
  • less manual work

If not set, the default settings will be used, defined in the sepaXml settings.

Example:

true

Response

200
application/json
No payments to process
​
message
string
Example:

"No payments to process."