Handle SEPA Direct Debit chargebacks

Plans supporting this feature: Growth Scale

Overview

A SEPA Direct Debit chargeback happens when a bank reverses a collected payment. Customers can trigger this by disputing a debit or by exercising their unconditional right of refund under SEPA rules; typically within 8 weeks of the original transaction, or up to 13 months for unauthorised payments.

Frisbii Billing automatically detects incoming SEPA chargebacks and manages the full lifecycle for you. No manual workaround needed. It updates the affected invoice, deactivates the payment method, and re-enters the invoice into your dunning flow.

🚫 Limitations
SEPA chargebacks are final and irreversible. Unlike credit card disputes, there is no dispute resolution process — Frisbii treats the chargeback as resolved the moment it arrives.
This feature covers SEPA Direct Debit only (via PPRO or EBICS). Credit card chargebacks and other payment methods fall outside scope.
Chargeback processing requires accounting invoices to be enabled. Without it, Frisbii creates a Dispute record only — it does not change the invoice state or trigger dunning.

💡 Good to know

Frisbii picks up chargebacks automatically via bank reports or webhooks, depending on whether you use PPRO or EBICS. You don't need to do anything to trigger the process.
Frisbii never modifies the original invoice — it keeps the amount, VAT, and document intact and records a separate reversal transaction instead.
If you use e-invoicing, Frisbii automatically issues a credit note to stay compliant with VAT rules. The original e-invoice stays immutable.
You can choose to pass the bank's chargeback return fee on to your customer. When you enable this, Frisbii adds the fee to the customer's next invoice.

Before you begin

Check the following prerequisites which need to be fulfilled:

You use SEPA Direct Debit as a payment method, via the Payment Service Provider PPRO or EBICS.
Frisbii supports two ways to run SEPA Direct Debit: through PPRO (a managed payment infrastructure) or through EBICS (a direct bank connection). The right choice depends on whether you want Frisbii to manage the banking layer for you, or whether you prefer to connect your own bank account.
You have invoice number enabled under Configurations → Finance and accounting → Invoices and credit notes.
You have a dunning plan set up under Configurations → Finance and accounting → Dunning management.

What happens when a chargeback occurs

When Frisbii receives a SEPA chargeback notification, it takes the following steps automatically:

Frisbii moves the invoice from Settled → Pending.
It re-opens the invoice and shows a "Chargeback occurred" indicator on the invoice detail page.
Frisbii records a reversal transaction.
It creates a negative transaction entry linked to the original, capturing the chargeback reason code, event ID, and timestamp.
Frisbii deactivates the SEPA payment method.
It marks the customer's SEPA Direct Debit mandate as inactive to stop further failed collection attempts.
Frisbii retries payment if an alternative method exists.
If the customer has another active payment method mapped to their subscription, Frisbii automatically tries to collect the outstanding amount from it.
Frisbii triggers the dunning flow if no payment succeeds.
If no alternative method exists, or if the retry fails, the invoice enters your standard dunning sequence — the same as any other unpaid invoice.

Open the Invoice detail page to review the full chargeback history: the original payment, the reversal event, and the current outstanding amount all appear there.

Configuration

1 Enable chargeback processing

Go to Configurations → Finance and accounting → Invoices and credit notes.
In the SEPA chargeback handling box, activate Enable SEPA chargeback handling.
In the right-hand corner, click on Save.

→ Frisbii now processes all incoming SEPA Direct Debit chargebacks automatically.

2 Pass the chargeback fee on to your customer (optional)

Banks charge a return fee (“Rücklastschriftgebühr”) when they reverse a SEPA debit. You can choose to pass this on to your customer.

Go to Configurations → Finance and accounting → Invoices and credit notes.
In the SEPA chargeback handling box, activate Pass chargeback fee to customer.
In the right-hand corner, click on Save.

→ Frisbii adds the fee to the customer's next invoice whenever a chargeback occurs.

3 Activate webhook (optional)

If any third-party system needs to get notified about a SEPA chargeback occurred, you can activate a webhook to be sent.

👩‍💻 Need more information about webhooks?
Find more technical details here: Events

Go to Configurations → Integration and tools → Webhooks.
In the right-hand corner, click on Configuration.
Activate sepa_chargeback_processed event.
The webhook is triggered when SEPA chargeback handling is enabled and the disputed invoice is being retried. The invoice_dispute_resolved event is also triggered simultaneously, as SEPA disputes are always resolved automatically in the customer's favor.

What to do next

Open the Invoices page and look for invoices showing the "Chargeback occurred" indicator.
Check the customer's payment methods and add a new one if needed so future collection attempts can go through.
If you use e-invoicing, confirm that Frisbii issued the credit note correctly under Payments → Credit notes.
Track the dunning progress for affected invoices under Subscriptions or directly on the invoice detail page.

SEPA payment reason codes: What they mean

This section explains the reason codes you may see when a SEPA payment (credit transfer or direct debit) is rejected, returned, or cancelled. These codes come from the ISO 20022 standard used across European banks and payment schemes. → Source

What to do if you see one of these codes

Check the reason code and short description in your payment or transaction overview.
Look up the code below to understand, in plain terms, why the payment failed or was returned.
Codes about account, name, or bank details usually mean the payment information needs to be corrected before resending.
Codes about funds, limits, or mandates usually need to be resolved with the payer's or recipient's own bank.
If you're unsure what action to take for a specific code, contact support with the code and transaction reference so we can investigate.

Note
A handful of codes below (in the “Technical & EBICS signature statuses” and “National clearing-system specific codes” sections) relate to bank-to-bank file processing and are unlikely to appear directly to end customers, but are included here for completeness since they are configured in the system.

Account issues

Code	Reason	What it means
AC01	Incorrect Account Number	The account number given for this payment is invalid or missing.
AC02	Invalid Debtor Account Number	The payer's account number is invalid or missing.
AC03	Invalid Creditor Account Number	The recipient's account number is invalid or missing.
AC04	Closed Account Number	The account has been closed.
AC05	Closed Debtor Account Number	The payer's account is closed.
AC06	Blocked Account	The account is blocked, so no payments can be posted to it.
AC07	Closed Creditor Account Number	The recipient's account is closed.
AC08	Invalid Branch Code	The bank branch code is invalid or missing.
AC09	Invalid Account Currency	The account currency is invalid or missing.
AC10	Invalid Debtor Account Currency	The payer's account currency is invalid or missing.
AC11	Invalid Creditor Account Currency	The recipient's account currency is invalid or missing.
AC12	Invalid Account Type	The account type is missing or invalid.
AC13	Invalid Debtor Account Type	The payer's account type is missing or invalid.
AC14	Invalid Creditor Account Type	The recipient's account type is missing or invalid.

Bank & routing issues

Code	Reason	What it means
AGNT	Incorrect Agent	One of the banks involved in processing the payment is incorrect.
AG01	Transaction Forbidden	This type of transaction is not permitted on this account.
AG02	Invalid Bank Operation Code	The payment type code sent isn't valid for the receiving bank.
AG03	Transaction Not Supported	This type of transaction isn't supported or authorised on this account.
AG04	Invalid Agent Country	The bank's country code is missing or invalid.
AG05	Invalid Debtor Agent Country	The payer's bank country code is missing or invalid.
AG06	Invalid Creditor Agent Country	The recipient's bank country code is missing or invalid.
AG07	Unsuccesful Direct Debit	The payer's account couldn't be debited (no further reason given).
AG08	Invalid Access Rights	The transaction failed due to missing or invalid access rights.
RC01	Bank Identifier Incorrect	The bank identifier code is in the wrong format.
RC02	Invalid Bank Identifier	The bank identifier is invalid or missing.
RC03	Invalid Debtor Bank Identifier	The payer's bank identifier is invalid or missing.
RC04	Invalid Creditor Bank Identifier	The recipient's bank identifier is invalid or missing.
RC05	Invalid BICIdentifier	The BIC (bank identifier code) is invalid or missing.
RC06	Invalid Debtor BICIdentifier	The payer's BIC is invalid or missing.
RC07	Invalid Creditor BICIdentifier	The recipient's BIC is invalid or missing.
RC08	Invalid Clearing System Member Identifier	The clearing-system member identifier is invalid or missing.
RC09	Invalid Debtor Clearing System Member Identifier	The payer's clearing-system member identifier is invalid or missing.
RC10	Invalid Creditor Clearing System Member Identifier	The recipient's clearing-system member identifier is invalid or missing.
RC11	Invalid Intermediary Agent	The intermediary bank is invalid or missing.
RC12	Missing Creditor Scheme Id	The recipient's creditor scheme ID is invalid or missing.
CNOR	Creditor bank is not registered	The recipient's bank isn't registered under this BIC in the clearing system.
DNOR	Debtor bank is not registered	The payer's bank isn't registered under this BIC in the clearing system.

Amount & currency issues

Code	Reason	What it means
AM01	Zero Amount	The payment amount is zero.
AM02	Not Allowed Amount	The amount is higher than the maximum allowed for this type of transaction.
AM03	Not Allowed Currency	The currency isn't supported under the existing agreement.
AM04	Insufficient Funds	There isn't enough money in the account to cover the payment.
AM06	Too Low Amount	The amount is lower than the agreed minimum.
AM07	Blocked Amount	There aren't enough funds available to cover the amount.
AM09	Wrong Amount	The amount received doesn't match what was agreed or expected.
AM10	Invalid Control Sum	The total (control sum) of all instructed amounts doesn't add up correctly.
AM11	Invalid Transaction Currency	The transaction currency is invalid or missing.
AM12	Invalid Amount	The amount is invalid or missing.
AM13	Amount Exceeds Clearing System Limit	The amount exceeds the limit set by the clearing system.
AM14	Amount Exceeds Agreed Limit	The amount exceeds the limit agreed between the bank and the client.
AM15	Amount Below Clearing System Minimum	The amount is below the minimum set by the clearing system.
AM16	Invalid Group Control Sum	The control sum at message-group level is invalid.
AM17	Invalid Payment Info Control Sum	The control sum at payment-batch level is invalid.
AM18	Invalid Number Of Transactions	The number of transactions stated is invalid or missing.
AM19	Invalid Group Number Of Transactions	The number of transactions at group level is invalid or missing.
AM20	Invalid Payment Info Number Of Transactions	The number of transactions at payment-batch level is invalid.
AM21	Limit Exceeded	The amount exceeds the limit agreed between the bank and the client.
CURR	Incorrect Currency	The currency of the payment is incorrect.

Payer & recipient details

Code	Reason	What it means
BE01	Inconsisten With End Customer	The end customer's identification doesn't match the associated account number.
BE04	Missing Creditor Address	The recipient's address is missing or incorrect, but is required for this payment.
BE05	Unrecognised Initiating Party	The party that initiated the message isn't recognised by the end customer.
BE06	Unknown End Customer	The end customer isn't known at the stated bank, or no longer exists in its records.
BE07	Missing Debtor Address	The payer's address is missing or incorrect, but is required for this payment.
BE08	Missing Debtor Name	The payer's name is missing.
BE09	Invalid Country	The country code is missing or invalid.
BE10	Invalid Debtor Country	The payer's country code is missing or invalid.
BE11	Invalid Creditor Country	The recipient's country code is missing or invalid.
BE12	Invalid Country Of Residence	The country-of-residence code is missing or invalid.
BE13	Invalid Debtor Country Of Residence	The payer's country-of-residence code is missing or invalid.
BE14	Invalid Creditor Country Of Residence	The recipient's country-of-residence code is missing or invalid.
BE15	Invalid Identification Code	An identification code is missing or invalid.
BE16	Invalid Debtor Identification Code	The payer's identification code is missing or invalid.
BE17	Invalid Creditor Identification Code	The recipient's identification code is missing or invalid.
BE18	Invalid Contact Details	Contact details are missing or invalid.
BE19	Invalid Charge Bearer Code	The charge-bearer code (who pays the fees) is invalid for this transaction type.
BE20	Invalid Name Length	The name provided exceeds the length allowed for this payment type.
BE21	Missing Name	A name is missing or invalid.
BE22	Missing Creditor Name	The recipient's name is missing.

Direct debit & mandate issues

Code	Reason	What it means
CH03	Requested Execution Date Or Requested Collection Date Too Far In Future	The requested execution or collection date is too far in the future.
CH04	Requested Execution Date Or Requested Collection Date Too Far In Past	The requested execution or collection date is too far in the past.
CH07	Element Is Not To Be Used At B-and C-Level	A field was used that isn't allowed at this processing level.
CH09	Mandate Changes Not Allowed	Changes to the mandate aren't allowed.
CH10	Information On Mandate Changes Missing	Information about mandate changes is missing.
CH11	Creditor Identifier Incorrect	The creditor identifier is incorrect.
CH12	Creditor Identifier Not Unambiguously At Transaction-Level	The creditor identifier isn't unique at transaction level.
CH13	Original Debtor Account Is Not To Be Used	The original debtor account shouldn't have been used.
CH14	Original Debtor Agent Is Only To Be Used With Sequence Type FRST	The original debtor's bank should only be used for a first ('FRST') collection.
CH15	Element Content Includes More Than140Characters	The remittance information text is longer than the 140-character limit.
CH16	Element Content Formally Incorrect	The content of a field is formally incorrect.
CH17	Element Not Admitted	A field that was included isn't allowed.
CH19	Values Will Be Set To Next TARGETday	The dates will automatically be moved to the next TARGET business day.
CH20	Decimal Points Not Compatible With Currency	The number of decimal points isn't compatible with the currency used.
CH21	Required Compulsory Element Missing	A mandatory field is missing.
CH22	COREand B2Bwithin Onemessage	SEPA Direct Debit CORE and B2B schemes can't be mixed within one message.
MD01	No Mandate	There is no valid mandate for this direct debit.
MD02	Missing Mandatory Information In Mandate	Information required by the mandate is missing.
MD03	Invalid File Format For Other Reason Than Grouping Indicator	The file format is incomplete or invalid.
MD05	Collection Not Due	The creditor shouldn't have collected this direct debit.
MD06	Refund Request By End Customer	The end customer has requested a refund.
MD07	End Customer Deceased	The end customer is deceased.
MD08	No Mandate Service By Agent	The receiving bank doesn't offer this mandate service.
MD09	No Mandate Service On Customer	The account isn't set up for this mandate service.
MD10	No Mandate Service For Specified	The account isn't set up for this mandate service with this particular creditor.
MD11	Unrecognised Agent	The bank the message needs to be forwarded to can't be found.
MD12	Not Unique Mandate Reference	The mandate reference isn't unique for this creditor.
MD13	Incorrect Customer Authentication	There's a problem verifying the customer.
MD14	Incorrect Agent	One of the banks in the payment chain is incorrect.
MD15	Incorrect Currency	The currency specified is incorrect.
MD16	Requested By Customer	The payer has requested the cancellation or amendment.
MD17	Requested By Initiating Party	The creditor has requested the cancellation or amendment.

Date & timing issues

Code	Reason	What it means
DT01	Invalid Date	The date provided (e.g. settlement date) is invalid.
DT02	Invalid Creation Date	The creation date/time on the message header is invalid (e.g. it's a historic date).
DT03	Invalid Non Processing Date	The date falls on a non-processing day (e.g. a weekend or public holiday).
DT04	Future Date Not Supported	A future date was used, which isn't supported.
DT05	Invalid Cut Off Date	The payment was received after the agreed processing cut-off date.
DT06	Execution Date Changed	The execution date had to be changed for the transaction to be processed.
TM01	Invalid Cut Off Time	The payment was received after the agreed processing cut-off time.

Duplicate & control issues

Code	Reason	What it means
DU01	Duplicate Message ID	The message ID isn't unique.
DU02	Duplicate Payment Information ID	The payment batch ID isn't unique.
DU03	Duplicate Transaction	The transaction reference isn't unique.
DU04	Duplicate End To End ID	The end-to-end ID isn't unique.
DU05	Duplicate Instruction ID	The instruction ID isn't unique.
DUPL	Duplicate Payment	This payment is a duplicate of another payment already processed.
AM05	Duplication	The transaction appears to be a duplicate.
ARDT	Ebics Transaction has already been returned	This transaction has already been returned once before.

File format & processing issues

Code	Reason	What it means
FF01	Invalid File Format	The file format is incomplete or invalid.
FF02	Syntax Error	There's a syntax error in the file (details given separately).
FF03	Invalid Payment Type Information	The payment type information is missing or invalid.
FF04	Invalid Service Level Code	The service-level code is missing or invalid.
FF05	Invalid Local Instrument Code	The local instrument code is missing or invalid.
FF06	Invalid Category Purpose Code	The category-purpose code is missing or invalid.
FF07	Invalid Purpose	The purpose of the payment is missing or invalid.
FF08	Invalid End To End Id	The end-to-end ID is missing or invalid.
FF09	Invalid Cheque Number	The cheque number is missing or invalid.
FF10	Bank System Processing Error	The file or transaction couldn't be processed due to a technical issue at the bank.
TD01	No Data Available	There's no data available for download.
TD02	File Non Readable	The file can't be read (e.g. an unknown format).
TD03	Incorrect File Structure	The file format is incomplete or invalid.

Regulatory & reporting issues

Code	Reason	What it means
RR01	Missing Debtor Account or Identification	The payer's account or unique ID needed for regulatory reasons is missing or incomplete.
RR02	Missing Debtor Name or Address	The payer's name/address needed for regulatory reasons is missing or incomplete.
RR03	Missing Creditor Name or Address	The recipient's name/address needed for regulatory reasons is missing or incomplete.
RR04	Regulatory Reason	The payment was rejected for regulatory reasons.
RR05	Regulatory Information Invalid	Regulatory or central bank reporting information is missing, incomplete, or invalid.
RR06	Tax Information Invalid	Tax information is missing, incomplete, or invalid.
RR07	Remittance Information Invalid	The remittance information doesn't comply with the required structure for this payment type.
RR08	Remittance Information Truncated	The remittance information had to be shortened to comply with the rules for this payment type.
RR09	Invalid Structured Creditor Reference	The structured creditor reference is invalid or missing.
RR10	Invalid Character Set	The character set used isn't valid for the country/payment type.
RR11	Invalid Debtor Agent Service ID	A bank's proprietary service identification is invalid or missing.
RR12	Invalid Party ID	A required party ID for this country/payment type is invalid or missing.

Code	Reason	What it means
FRAD	Payment effected fraudulently	The payment was found to be fraudulent.
LEGL	Legal Decision	The payment was rejected on legal grounds.
EMVL	EMV Liability Shift	A card payment was found to be fraudulent and wasn't processed using EMV chip technology.
PINL	PIN Liability Shift	A card payment was found to be fraudulent and was processed without PIN verification.

Cancellations, recalls & investigations

Code	Reason	What it means
CUST	Requested By Customer	The payer asked for the payment to be cancelled.
CUTA	Cancel Upon Unable to Apply	The payment was cancelled following an investigation request, with no other resolution possible.
FOCR	Following Cancellation Request	The payment was returned as a result of a recall request.
NOOR	No Original Transaction Received	The original credit transfer this relates to was never received.
NOAS	No Answer From Customer	There has been no response from the recipient.
PART	Partial Rejection Of Bulks	Part of a batch of payments was rejected.
RJCT	Complete Rejection Of Bulks	The whole batch of payments was rejected.
ED01	Correspondent Bank Not Possible	It wasn't possible to route the payment via a correspondent bank.
ED03	Balance Info Request	Additional balance-of-payments information has been requested.
ED05	Settlement Failed	Settlement of the transaction failed.
RF01	Not Unique Transaction Reference	The transaction reference isn't unique within the message.
PY01	The Beneficiary Or The Ordering Bank Is Not Participant In The EBA	The transaction can't be processed because the recipient and/or the ordering bank isn't a participant in the clearing system.
SL01	Specific Service offered by Debtor Agent	Returned due to a specific service offered by the payer's bank.
SL02	Specific Service offered by Creditor Agent	Returned due to a specific service offered by the recipient's bank.
UPAY	Undue Payment	The payment collected or received wasn't actually due.

Technical & EBICS signature statuses (rarely customer-facing)

Code	Reason	What it means
DS01	Electronic Signatures Correct	The electronic signature(s) submitted are correct.
DS02	Order Cancelled	An authorised user cancelled the order.
DS03	Order Not Cancelled	The attempt to cancel the order wasn't successful.
DS04	Order Rejected	The order was rejected by the bank due to its content.
DS05	Order Forwarded For Post-processing	The order was correct and has been forwarded for further processing.
DS06	Transfer Order	The order was transferred to VEU (the EBICS multi-signature process).
DS07	Processing OK	The bank's server successfully completed all actions for the order.
DS08	Decompression Error	The file couldn't be decompressed successfully.
DS09	Decryption Error	The file couldn't be decrypted successfully.
DS0A	Data Sign Requested	A data signature is required.
DS0B	Unknown Data Sign Format	The data signature format isn't available or is invalid.
DS0C	Signer Certificate Revoked	The signer's certificate has been revoked.
DS0D	Signer Certificate Not Valid	The signer's certificate isn't valid (revoked or inactive).
DS0E	Incorrect Signer Certificate	The signer's certificate is missing.
DS0F	Signer Certification Authority Signer Not Valid	The certification authority of the signer's certificate is unknown.
DS0G	Not Allowed Payment	The signer isn't allowed to sign this type of operation.
DS0H	Not Allowed Account	The signer isn't allowed to sign for this account.
DS0K	Not Allowed Number Of Transaction	The number of transactions exceeds what's allowed for this signer.
DS10	Signer1Certificate Revoked	The certificate for the first signer has been revoked.
DS11	Signer1Certificate Not Valid	The certificate for the first signer isn't valid.
DS12	Incorrect Signer1Certificate	The certificate for the first signer is missing.
DS13	Signer Certification Authority Signer1Not Valid	The certification authority for the first signer's certificate is unknown.
DS14	User Does Not Exist	The user is unknown to the bank's server.
DS15	Identical Signature Found	The same signature has already been sent to the bank.
DS16	Public Key Version Incorrect	The public key version is incorrect, typically after switching signature formats without re-registering the key.
DS17	Different Order Data In Signatures	The order data and signatures don't match.
DS18	Repeat Order	The file couldn't be tested, and the whole order needs to be resubmitted.
DS19	Electronic Signature Rights Insufficient	The user's signature rights aren't sufficient to execute the order.
DS20	Signer2Certificate Revoked	The certificate for the second signer has been revoked.
DS21	Signer2Certificate Not Valid	The certificate for the second signer isn't valid.
DS22	Incorrect Signer2Certificate	The certificate for the second signer is missing.
DS23	Signer Certification Authority Signer2Not Valid	The certification authority for the second signer's certificate is unknown.
DS24	Waiting Time Expired	The waiting time expired because the order was incomplete.
DS25	Order File Deleted	The order file was deleted by the bank's server.
DS26	User Signed Multiple Times	The same user signed more than once.
DS27	User Not Yet Activated	The user hasn't been technically activated yet.
ID01	Corresponding Original File Still Not Sent	The signature file was sent, but the corresponding original file hasn't been sent yet.
TA01	Transmisson Aborted	The file transmission was unsuccessful and had to be aborted for technical reasons.
TS01	Transmission Successful	The technical transmission of the file was successful.
TS04	Transfer To Sign By Hand	The order was passed on with an accompanying note, to be signed by hand.
MS02	Not Specified Reason Customer Generated	No reason was specified by the end customer.
MS03	Not Specified Reason Agent Generated	No reason was specified by the bank.
NARR	Narrative	The reason is given as free text rather than a code.

National clearing-system specific codes

Code	Reason	What it means
XD19	IBAN check failed	The IBAN failed the ISO 13616 validity check (the debtor or creditor account is incorrect). Used when the country code is valid but the country-specific IBAN structure or check digit is wrong.
XD75	National clearer code	A technical reject/return code used within the German SEPA Direct Debit clearing system.
XT13	Unsupported or missing field	The transaction includes at least one unsupported field, or is missing a required field. The problematic field is flagged in the error.
XT27	National clearer code	A technical reject/return code used within the German SEPA clearing system (credit transfers, direct debits and card clearing).
XT33	National clearer code	A technical reject/return code used within the German SEPA clearing system (credit transfers and direct debits).
XT43	National clearer code	A technical reject/return code used within the German SEPA Direct Debit clearing system.
XT53	Creditor scheme ID check failed	The creditor scheme identifier failed a structure/check-digit validation.
XT73	Invalid country code	Neither character of the country code is a valid ISO or SEPA country code (checked on the debtor, debtor account, creditor, or creditor account).
XT74	National clearer code	A technical reject/return code used within the German SEPA clearing system (credit transfers and direct debits).
XT75	National clearer code	A technical reject/return code used within the German SEPA clearing system (credit transfers and direct debits).
XT76	Invalid error code	An invalid error code was used in the return/refund message.
XT77	National clearer code	A technical reject/return code used within the German SEPA clearing system (credit transfers and direct debits).
XT78	National clearer code	A technical reject/return code used within the German SEPA Direct Debit clearing system.
XT79	National clearer code	A technical reject/return code used within the German SEPA Direct Debit clearing system.
XT80	National clearer code	A technical reject/return code used within the German SEPA Direct Debit clearing system.
XT81	Field not permitted in SDD	An XML field was used in a SEPA Direct Debit message that's only permitted for SEPA Core, without prior agreement.
XT85	No Settlement Cycle available	No settlement cycle is available for this SEPA Credit Transfer.
XT87	Routing mismatch on return	The return message didn't follow the same processing route as the original transaction, or the sending party doesn't match the original instructing/instructed agent.
XT90	Invalid use of a Technical BIC	A technical BIC was used incorrectly in this SEPA Credit Transfer.
XT99	National clearer code	A technical reject/return code used within the German SEPA clearing system (credit transfers, direct debits and card clearing).