Batch overview

For each batch, the following information is displayed:

• Profile ID and profile name
• The gateway used for collection
• Total amount to be collected
• Number of transactions in the batch

By clicking on a batch, you can open the batch details, where you can:

• View and manage individual transactions
• Identify and resolve uncollectable transactions
• Send the batch to the bank

For more information, see the related article on batch details.

Available actions

From this screen, you can perform the following actions:

1. Delete a batch of transactions for a specific profile
2. Import a batch of transactions using a specific direct debit file or CSV file or another type of file.
3. Export a batch of transactions that are still pending of a specific profile
4. Refresh the transaction overview
5. Filter on future transactions
6. Schedule a profile of future batches
7. Search within future transactions

Clicking on a specific batch opens the detailed view of that batch.

Next to each batch, the 'Notify debtor' icon may appear which indicates that a collection notification email will be sent to all customers when the batch is sent to the bank.

Collection date rules

The earliest valid collection date depends on the payment method:

SEPA Direct Debit (SDD)

The EPC SEPA Core rulebook requires the batch to reach the debtor's bank at least 1 inter-PSP business day before the requested collection date (D-1). In practice:

• If the batch is submitted before the bank's cut-off time on a business day, tomorrow is the earliest valid collection date.
• If submitted after the cut-off, the day after tomorrow must be used.

Twikey uses 10:00 as its internal default cut-off, which is intentionally conservative to accommodate banks with stricter deadlines. When no collection date is provided, Twikey automatically assigns the earliest safe date.

BACS Direct Debit (UK)

BACS requires a minimum of 3 working days between submission and the collection date, excluding UK bank holidays.

Mismatch between transactions on screen and actual number of transactions

When a merchant manually approves a batch, the number of approved transactions may differ from the number that would actually be included at send time. This mismatch can occur because:

• The API is still receiving new transactions that qualify for inclusion in that batch.
• Bank feedback has caused some transactions to be excluded (e.g. mandate issues) or re-offered (e.g. retry after a technical failure).

This is not an issue for API-triggered or automatic sending.

When a mismatch is detected, the interface blocks the send and the merchant receives an error notification by email (because this typically involves large amounts). The email contains a link to the relevant support article. Twikey Support can force-send the batch even when a count mismatch exists — this is an exceptional, manual action reserved for support staff.