R-message AM05: Duplicate collection

AM05: Duplicate collection

SEPA return code AM05 — belongs to the AM group (duplicado).

TL;DR

Meaning: Duplicate collection.
Category: Duplicado.
Common cause: the debtor’s bank spots two identical collections (same amount, same date, same umr).
How to fix it: review your batch: any duplicate is returned. identify and remove one before retrying.
Bank fee? Typically yes (depends on your bank contract).

When it appears

The debtor’s bank spots two identical collections (same amount, same date, same UMR).

How to fix it

Review your batch: any duplicate is returned. Identify and remove one before retrying.

XML example

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

<Rtr>
  <RsnInf>
    <Rsn>
      <Cd>AM05</Cd>
    </Rsn>
    <AddtlInf>Return because of duplicate collection</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 AM-type returns.

Conclusion

AM05 is a duplicado type return. Follow the steps above to fix and re-issue.

Frequently Asked Questions

Does `AM05` 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.