Why is the field validation on the new 365 site still not ISO Compliant

Tow

Dear BOI,

Why are the Reference (End To End ID) field's character set and length validation on the new 365 site still not ISO20022 / PAIN.002 Compliant? 


It causes great difficulties when making payments which require exact references be entered.  

Is it too much to allow 35 characters and the SEPA basic Latin character set?

If your are spending €1Bn+ on new systems at least get the customer facing front end right.

Bank of Ireland: Megan

Tow wrote: »

Dear BOI,

Why are the Reference (End To End ID) field's character set and length validation on the new 365 site still not ISO20022 / PAIN.002 Compliant? 


It causes great difficulties when making payments which require exact references be entered.  

Is it too much to allow 35 characters and the SEPA basic Latin character set?

If your are spending €1Bn+ on new systems at least get the customer facing front end right.

Good afternoon,

Thank you for reaching out to us here on Boards.ie.

Bank of Ireland complies with the Irish Payment Services Organisations (IPSO) industry agreement for SEPA transfers by providing the payers reference in the statement narrative. 

The 'payment reference' field is the End-To-End sent by the payment originator. All extended payment information on 365 online is fully compliant with SEPA requirements.

Thanks for sharing your feedback. I will be sure to share it with the relevant department.

Many thanks,
Megan

Tow

Dear Megan,

Thank you for your reply. Please provide for following for the Banking 365 Payment Reference (End To End Id) field, when making/setting up a credit transfer:

A) The maximum length customers can enter?
The complete character set a customer can enter?

Bank of Ireland: Richard F

Tow wrote: »

Dear Megan,

Thank you for your reply.  Please provide for following for the Banking 365 Payment Reference (End To End Id) field, when making/setting up a credit transfer:

A) The maximum length customers can enter?
The complete character set a customer can enter?

Hi Tow,

The maximum length of this would be 25 characters. This reference can be a combination of letters and numbers. Hope this helps.

Thanks,
Richard

Tow

Bank of Ireland: Richard F wrote: »

Tow wrote: »

A) The maximum length customers can enter?
The complete character set a customer can enter?

The maximum length of this would be 25 characters. This reference can be a combination of letters and numbers. Hope this helps.

The ISO 20022, EPC's SEPA SCT Standards (and BPFI formally known as IPSO) etc. specify a maximum length of 35 characters for the Reference (End To End ID).

1. Why are BOI limiting Banking 365's Credit Transfer Reference (End To End ID) to 25 characters when it should be 35?

2. Why are BOI not allowing other characters which are in the SEPA specification? Example - (Hyphen)

3. Why do BOI still insist on inserting 'Banking 365' in front of the already limited length Reference field? This was a quick fix in 1996 when 365 started.

4. Why do we still not have a drilldown for Credit Transfers details? This was done for Debits, when SEPA was introduced.

Fixing these issues would be a start at improving Banking 365.

Bank of Ireland: Tara

Hi Tow,

Apologies for the delay, we've forwarded your queries to our online team and will get back to you here as soon as we have a response. 

Thanks
Tara

Bank of Ireland: Tara

Tow wrote: »

The ISO 20022, EPC's SEPA SCT Standards (and BPFI formally known as IPSO) etc. specify a maximum length of 35 characters for the Reference (End To End ID).

1. Why are BOI limiting Banking 365's Credit Transfer Reference (End To End ID) to 25 characters when it should be 35?

2. Why are BOI not allowing other characters which are in the SEPA specification? Example  - (Hyphen)

3. Why do BOI still insist on inserting 'Banking 365' in front of the already limited length Reference field? This was a quick fix in 1996 when 365 started.

4. Why do we still not have a drilldown for Credit Transfers details?  This was done for Debits, when SEPA was introduced.

Fixing these issues would be a start at improving Banking 365.

Hi Tow,
 
Thanks for your patience and sorry for the delay getting back to you. We have answered your questions below as much as we can, as they are related to our internal systems we are limited in the information we can share.


1.      Why are BOI limiting Banking 365's Credit Transfer Reference (End To End ID) to 25 characters when it should be 35?
 This is due to how our internal systems are set up  This has been raised with our development team for consideration with any future enhancements.  

 
2.      Why are BOI not allowing other characters which are in the SEPA specification? Example - (Hyphen)
A business decision was made about this due to issues with special characters in the system when entered in the Reference Field. It is possible to include these characters in messages entered in the Remittance Field.  
 
3.      Why do BOI still insist on inserting 'Banking 365' in front of the already limited length Reference field? This was a quick fix in 1996 when 365 started.
This narrative is included to help customers reconcile the source channel of the Debit. This may appear as Banking 365 or B365. Standing Orders would have SO at the start and ATM transactions would have ATM appear at the start, etc.
 
4.      Why do we still not have a drilldown for Credit Transfers details? This was done for Debits, when SEPA was introduced.
This is available for incoming credit transfers and SEPA direct debits. We do plan to add the function to view additional details on the outbound payments in the future and we’ll let customers know when this is available.

Thanks again, 
Tara