Batch information

At the top of the batch details page, you’ll find the following information:

• Gateway : The IBAN where the collected funds will be deposited.
• Requested collection date : The date on which the transactions are intended to be collected.
  Transactions become ready to send approximately 3 days before this date to account for bank processing times.
• IBAN : The account number on which the direct debits will be deposited.
• Notify debtor : Indicates whether a collection notification email will be sent to customers when the batch is sent to the bank.
  This setting cannot be changed here and is configured under Settings > Profiles > Emails.
• Transactions : The total number of collectable transactions in the batch (uncollectable transactions excluded).
• Amount: The total collectable amount of the batch (uncollectable transactions excluded).

Preparing a batch of transactions for collection

Under the Transactions tab, you’ll find all transactions that are ready to be sent to the bank.

From here, you can:

• Exclude specific transactions from this batch by deselecting the checkbox
• Remove a transaction entirely using the recycle bin icon
• Search after a specific transaction in the batch

Sending a batch of transactions for collection

Once you have checked the content of your batch you can send it to the bank or PSP for collection.

1. Click the Prepare button in the top right corner of the screen
2. A new screen opens allowing you to:

• Confirm and send the batch directly to the bank or PSP via the configured bank integration
• Download the pain.008 file for manual upload in your own banking environment
  (the download option is only available when no bank integration is configured)

3. When confirmed, the batch is then sent to the bank or your payment service provider.
4. Sent transactions can be found under the “Batches” menu.

Uncollectable transactions

This section lists transactions that were planned for collection but cannot be collected due to the current state of the mandate.

Common reasons include:

• Suspended mandates
• Missing or invalid mandate information
• Amendment in progress — when a mandate is amended, only the first transaction (which carries the amendment) is included in the current batch. Any subsequent transactions for the same mandate are held back and will be picked up in the next batch, to avoid a race condition at the debtor bank.

Available actions

You can select one or more uncollectable transactions and choose one of the following actions:

• Treat as technical failure
  Moves the transactions to a batch as if they were sent to the bank.
  All transactions are marked as unsettled with error code MD01 (invalid mandate).

• Archive
  Places the elected transactions in a batch that is immediately archived.

• Send to bank
  Sends the selected transactions to the bank for collection regardless of mandate status.

Other available actions

On this screen, you can also:

1. Change the specific collection date of the batch
2. Select one or multiple transactions to export as a CSV file
3. View uncollectable transactions
4. Choose the columns you want to view