R-message BE05: Creditor unknown to the debtor

Published on · Updated on

BE05: Creditor unknown to the debtor

SEPA return code BE05 — belongs to the BE group (acreedor desconocido).

TL;DR

  • Meaning: Creditor unknown to the debtor.
  • Category: Acreedor desconocido.
  • Common cause: the debtor does not recognise the creditor (cid not whitelisted in their banking app).
  • How to fix it: verify the mandate is on file and active. if the debtor denies it, the charge is treated as unauthorised.
  • Bank fee? Typically yes (depends on your bank contract).

When it appears

The debtor does not recognise the creditor (CID not whitelisted in their banking app).

How to fix it

Verify the mandate is on file and active. If the debtor denies it, the charge is treated as unauthorised.

XML example

This code lives inside the <RsnInf> block of the return message (pain.002 or camt.054):

<Rtr>
  <RsnInf>
    <Rsn>
      <Cd>BE05</Cd>
    </Rsn>
    <AddtlInf>Return because of creditor unknown to the debtor</AddtlInf>
  </RsnInf>
</Rtr>

Prevention

Before sending the batch to your bank, validate it with our SEPA XML Validator. Catch the errors your ERP misses and reduce BE-type returns.

Conclusion

BE05 is a acreedor desconocido type return. Follow the steps above to fix and re-issue.


Frequently Asked Questions

Does `BE05` carry a bank fee?
Almost always. Your bank charges a return fee per your contract.
Can I retry the collection?
It depends on the cause. Fix the reason above before retrying.
How do I prevent it?
Validate the batch before sending it and keep IBAN, mandates and CID up to date. Our [SEPA XML Validator](/sepa-direct-debit-xml-validator) catches most of these errors pre-submission.

Validate your SEPA XML file before uploading

Try it now →
Was this article helpful?

Related articles

Showing the first four on mobile.