3

According to the ISO 20022 standard, the tag is a unique reference, as agreed between the account owner and the account servicer, to unambiguously identify the transaction. This means that the tag should be unique for each transaction in a camt.053 file. However, some banks may not follow this rule strictly and may use the same for different transactions, especially if they are related to the same payment instruction. Therefore, it is advisable to check with your bank how they generate and use the tag in their camt.053 files.


According to the ISO 20022 standard, too, the tag is a unique reference, as agreed between the account servicer and the account owner, to unambiguously identify the entry. This means that the tag should be unique for each entry in a camt.052 or camt.053 file. However, some banks may not follow this rule strictly and may use the same for different entries, especially if they are related to the same transaction. Therefore, it is advisable to check with your bank how they generate and use the tag in their camt.052 and camt.053 files.


As you can see, both are similar:

Whereas stands for Account servicer reference and , End to End Identification from the incoming SEPA payment.


When looking into the file descriptions of Dutch banks (ING, RABO, ABNAMRO) they also write that both of them are unique. But there is a difference of course:

-The is filled with the banks assigned unique reference

-The is filled with the unique identifier assigned to the initiator of the SEPA transfer and this tag is not filled or Nonref / notprovided filled when a transaction occurs to and from or between the related savings account of the same bank.


Reviewing the "Usage rules as determined by the NVB", we can conclude that in NL we should definitely go for the tag and for sure not for . 


And when peeping on the SWIFT website www.swift.com I see the following explanation of the use of the tags:

-- The end-to-end identification must be reported when it is known by the reporting bank. For SEPA the EndToEndId can be 'NOTPROVIDED'.

-- The account servicing institution's reference for the transaction.


So that supports also using AcctsvcrRef,

 

Imho a safe option would be to have a choice / setting to check for one or the other. 


Could you evaluate this possibility to be included in the NL standard?


Thank you! 

Coen Overgaag.

STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team

Comments

V

Thanks for posting this Vanessa!.

Indeed in NL at least you can go wrong when importing bank statements in Payment Reconciliation Journal.

Bank statement lines are skipped from importing when the EndToEndID contains same content that was previously also imported in another statement. In NL for instance the standard word “Non-ref” is used when transferring money to one of the companies your own bank. 

This won't happen when system checks for the tag AcctSvcrRef.


Best regards,

Coen Overgaag

Category: Geographies and Localization