Skip to content
← Share and support customer ideas for Xero

Settings and activity

1 result found

  1. Contacts - Add IBAN in account number and Swift in Routing number

    65 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    19 comments  ·  For small businesses » Contacts & communication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    working on it  ·  AdminKelly Munro (Community Manager, Xero) responded

    Thanks everyone, we thoroughly appreciate your feedback on changes when adding or editing a contact. 


    Since the initial release, our team have made an update and you'll find you can now enter IBAN and SWIFT into account number without it throwing errors. 


    Currently, if you save information into the account number field it'll spread across the bank account prefix and bank account number fields - The thing to note is that this will not impact processing of batch payments and will be one field when exported for batch payments.


    We understand it’s not the perfect solution and are looking at further enhancing this - I'll keep you updated here. 

    An error occurred while saving the comment
    Umberto DiVenosa commented  · 

    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.