The direct debit was rejected or the batch is not generated

Symptom

You want to collect an invoice by direct debit and the batch cannot be created, validated or marked as sent, or the bank has already replied that it rejected the collection and resending is refused.

The normal paths are in How to create and send a direct debit batch and in How to handle direct debit returns. To pay suppliers, see I cannot issue the payment note to suppliers.

The examples were made on 04/11/2026 with the Accountant profile, in Empresa Demonstração, Lda, with invoice FT D26/33 of Clínica Dentária Sorriso, SA, for €147.60, and with test files from the bank.

Message

No active mandate. In Actions › Create SDD batch, when you click Create SDD batch:

“None of the invoices can be collected by direct debit: - FT D26/33: Clínica Dentária Sorriso, SA has no active SDD mandate.”

B2B mandate without the bank's confirmation. In Activate, with the Scheme set to B2B (companies):

“A B2B mandate needs the confirmation of the debtor bank before the first collection: tick “Validated by the debtor bank” when you have it.”

Missing or wrong creditor identifier. In Validate and generate the file:

“The SEPA file cannot be generated: - the SEPA creditor identifier of the company is missing or not valid (ask the administrator to fix it in Settings › Accounting › SEPA direct debit)”

Collection date too close, or invoice already in another batch. In Validate and generate the file, on a batch with the collection set for today and the invoice already in another batch:

“The batch cannot be validated: - RUM/00001: an invoice is already in the batch SDD/00002. - RUM/00001: the collection date 04/11/2026 is too close. CORE needs at least 1 business day(s) after today: choose 05/11/2026 or a later date.”

Mandate in another batch not yet sent. In Validate and generate the file, with the other batch already validated:

“The batch cannot be validated: - RUM/00001: an invoice is already in the batch SDD/00002. - RUM/00001: the mandate is already in the validated batch SDD/00002 that was not sent. Send it (or cancel it) before validating this one, so that the sequence type (first or recurrent) is right.”

There is no longer time to notify the customer. In Pre-notify the customers, with the collection on 05/11/2026 and a 14-day period:

“The pre-notifications cannot be made: - RUM/00001: the customer must be told 14 day(s) before the collection date 05/11/2026, that is until 22/10/2026, and it is too late. Record in the mandate a shorter period agreed with the customer, or move the collection date.”

In Mark as sent, after Confirm, on the same batch:

“The batch cannot be marked as sent: some customers would be debited without the pre-notification. - RUM/00001: the customer had to be told 14 day(s) before the collection date 05/11/2026, that is until 22/10/2026, and it is too late. Move the collection date (cancel this batch and make another), or record in the mandate a shorter period agreed with the customer.”

The bank rejected it and the code requires a correction (for example, AM04). In Resend the errors, after Confirm, with Resend set to Needs correction:

“No collection can be sent again. Check the reasons below and solve them with the customer first: - RUM/00001: the bank code AM04 needs the cause to be corrected first. Fix it and use “Cause solved” on the collection, then resend.”

The bank rejected it and the code is blocked (for example, MD07). In Resend the errors, after Confirm, with Resend set to Blocked:

“No collection can be sent again. Check the reasons below and solve them with the customer first: - RUM/00001: the bank code MD07 is blocked (or unknown): the customer refused it, or the mandate or account is not valid. Solve it with the customer first.”

Verified causes

• The customer has no active mandate, or the B2B mandate does not yet have the confirmation of the customer's bank.
• The company does not have a valid creditor identifier. The identifier is assigned by the bank and is kept in the company settings.
• The collection date does not give the bank enough time. The batch in Draft saved today's date without warning: the refusal only appears on validation.
• The invoice or the mandate is already in another batch. Currently, the creation window lets you create a second batch with the same invoice: the refusal also only appears on validation.
• The period for notifying the customer has passed and no pre-notification was made. The period comes from the mandate or, if the mandate has nothing, from the company settings (14 days in the example). The pre-notification and the sending to the bank are refused.
• The bank rejected the collection, and the Resend of each collection says what you can do. Import the bank's response as explained in How to handle direct debit returns. The invoice remains unpaid: in the example, FT D26/33 kept its €147.60 open.

What to check

1. In Accounting › Record › Collections from customers › Direct debit mandates, whether the customer's mandate is Active, with the right Scheme.
2. The batch's Collection date and the date by which the customer should have been notified, which the message gives.
3. Whether the invoice is already in another batch, in Direct debit batches.
4. On the batch, the Bank answer, the Reason code and the Resend of each collection.

How to fix it

What you do yourself:

1. No mandate: create and activate the mandate with the date on which the customer signed it. The Debtor account list only shows the accounts the customer already has: if it is empty, first add the IBAN on the customer's form.
2. B2B without confirmation: ask the customer to confirm the mandate with their bank. Once you have the confirmation, tick Validated by the debtor bank, save and click Activate.
3. Date too close: on a batch in Draft, change the Collection date to the one the message gives, or a later one.
4. Invoice or mandate in another batch: keep one of the batches and click Cancel on the other, or send the validated batch first, as the message asks.
5. No longer time to notify the customer: click Cancel and create a batch with a Collection date that allows the period to be met. Only record a shorter period in Agreed pre-notification days, on the mandate, if you have agreed it with the customer. The new period must also fit: in the example, on 04/11/2026, with the collection on 05/11/2026, 2 days were refused and 1 day was accepted. Then click Pre-notify the customers and Mark as sent.
6. Code that requires a correction: talk to the customer and resolve the cause. On the collection line, click Cause solved: Resend changes to Eligible to resend. Click Resend the errors and Confirm. A new batch opens in Draft, with only the rejected or returned collections. As the window warns, nothing is sent to the bank from here: validate that batch and take the file to the bank.
7. Blocked code: this collection has no Cause solved button. Talk to the customer and collect the invoice another way, or make a new mandate if the account has changed. The mandate in the example remained Active: it does not change by itself with this response.

What you ask someone else to do:

8. Creditor identifier: ask the Administrator profile to fill it in, as explained in step 1 of How to create and send a direct debit batch, and click Validate and generate the file again.

Make the pre-notification before taking the file to the bank

Currently, the Mark as sent refusal only applies once the notice period has passed. Before that, fiscaldoo does not require the pre-notification to have been made: in the example, a batch with the collection on 30/12/2026 became Sent without any. Check it on the batch itself before marking it and taking the file to the bank: the Pre-notifications button only appears when there is at least one. Without that button, click Pre-notify the customers.

Expected result

• The mandate becomes Active.
• The batch moves from Draft to Validated, with Download file, and to Sent after Mark as sent.
• After the correction, the new batch carries only the rejected or returned collections. The invoice remains open until the bank collects it.

When to contact support

• The message persists after following what it says.
• Your message is not in this article. A wrong IBAN, an expired mandate and an invalid mandate reference have their own messages, which this article does not cover.

Information to send

Follow How to ask support for help and what information to send, with:

• the batch number, for example SDD/00034, and the mandate reference;
• the Collection date and the date on which you tried;
• the full text of the message and, if the bank rejected it, the Reason code.