Hi everyone, thanks for your on-going involvement in the idea here.
We understand many of our customers are trading internationally. While we haven't been able to deliver a solution as yet, this is still high on our radar.
Right now, depending on the country selected when setting up organisations will have different field options - Sort code in UK, BSB code in AU and Routing number in US. This explains the differences some in the conversation have mentioned. I appreciate it's not a solution but for the time being any extra detail (IBAN or any other banking detail) for the contact could be added as a note to the contacts record that can be looked up before making payments.
For our UK customers that have set up international bill payments - Though not direct from Contacts you can edit and save international payment details for a supplier through the flow of making foreign currency payments.
Within the contacts space in Xero, this is very much a piece of work we intend build a solution for, and while I can't give any timeframes as yet we'll share any progression with you all here.
Hi everyone, thanks for your on-going involvement in the idea here.
We understand many of our customers are trading internationally. While we haven't been able to deliver a solution as yet, this is still high on our radar.
Right now, depending on the country selected when setting up organisations will have different field options - Sort code in UK, BSB code in AU and Routing number in US. This explains the differences some in the conversation have mentioned. I appreciate it's not a solution but for the time being any extra detail (IBAN or any other banking detail) for the contact could be added as a note to the contacts record that can be looked up before making payments.
For our UK customers that have set up international bill payments - Though not direct from Contacts you can edit and save international payment details for a supplier through the flow…
I have been using the [Account Number] field to put the IBAN of my suppliers for the past number of months.
With this and filling the BIC in the [Details] field, I could easily generate [Batch Payments] files which I would then use to create {Payment Files} via a 3rd party application.
Since last week we can no longer use "letters" in the [Account Number] field. So with the 1500 suppliers that are there with their current IBAN, I can continue generating these batch payment files but I can no longer [Update] the IBAN/Account Number.
It does not make sense. If Xero is trying to have data consistency, first they should have thought about it years ago. Then Why keep some [Account Number] fields with letters as a legacy issue without allowing them to be edited?
Doing such a critical change for users should have been communicated and given notice of so as to find an alternative/solution as opposed to making such a change overnight which actually downgrade the service as opposed to improving it.
Who cares what data format is put in these fields anyway? Customers should be able to use them as they want as none of these fields are critical to the application's way of working.
I have been using the [Account Number] field to put the IBAN of my suppliers for the past number of months.
With this and filling the BIC in the [Details] field, I could easily generate [Batch Payments] files which I would then use to create {Payment Files} via a 3rd party application.
Since last week we can no longer use "letters" in the [Account Number] field. So with the 1500 suppliers that are there with their current IBAN, I can continue generating these batch payment files but I can no longer [Update] the IBAN/Account Number.
It does not make sense. If Xero is trying to have data consistency, first they should have thought about it years ago. Then Why keep some [Account Number] fields with letters as a legacy issue without allowing them to be edited?
Doing such a critical change for users should have been communicated and given notice of so as to find an alternative/solution as opposed to making such a change overnight which actually downgrade the service as opposed to improving it.
Who cares what data format is put in these fields anyway? Customers should be able to use them as they want as none of these fields are critical to the application's way of working.