© 2024 Banking & Payments Federation Ireland. All rights reserved.
It is also possible for you to switch your account, where you request to have your account moved from your existing provider to a new provider. Banks and credit unions provide a switching service, but not all providers do. If your new provider does and you would like to switch, you will be supported to open your new account in this way.
The process is set out in the Central Bank of Ireland’s (CBI) Code of Conduct on the Switching of Payment Accounts with Payment Service Providers (the Switching Code). You can access the Switching Code here.
However, please note that there are very important actions that you as a customer must do (and only you as a customer are authorised to do) to ensure the process can be completed successfully. More information is provided below.
If you would like to switch your account, you must first decide where you want to move your account to. Once you have decided which provider you would like to open your new account with, you should request the new provider’s switching pack which will give you all the information you need to switch your account. Your new provider will also tell you what you need to know about the process and answer any questions you may have.
You will need to fill out an Account Transfer Form (ATF) (also known as a “switcher/switching form”), which you can find online from the new provider’s website (details are below) or you can call into a branch to get the form in paper format.
If you decide to switch your account, you can decide to follow an “Option A” switch – where you switch your account to a new provider and close the old account as part of the switch – or an “Option B” switch – where you switch your account to a new provider but keep the old account open. However, because Ulster Bank and KBC Bank are leaving the Irish market, you may wish to instruct them to close the old account later if you choose an “Option B” switch.
If you would like to know more about the switching process, please click here to see a step-by-step guide
If you choose to switch your account, you will need to make sure you do the following:
Ensure that you do not generate any pending transactions on your account once the process has commenced, especially if you choose an “Option A” switch.
If there are pending transactions on your account, it may result in the switch being delayed or cancelled. In order to avoid your switch request being rejected for pending transactions, you should:
§ Choose a switch date which is a quiet time on your account – from the switch date all transactions such as direct debits and standing orders will no longer be processed on your old account.
§ Be aware that debit card transactions on your old account may take a couple of days to settle so you should stop using the debit card on your old account in advance of the switch date. You should activate and commence using the debit card on your new account in advance of the switch date, to ensure continued access to your funds during the switch.
§ Be aware that any cheques you have written for payment from your old account which have not been presented to the old bank for payment before the switch date will be returned unpaid by your old bank.
§ Be aware that any ATM withdrawals from the old account can only proceed if the old account and the debit card are still active. Once they are no longer active, you will not be able to withdraw money at an ATM from the old account.
If, however, you choose to follow an “Option B” switch, you will still be able to access your existing account. However, you may wish to close the account later.
Your new provider will advise you of any additional steps you may need to take to ensure the switch completes successfully.
To open a new account with a new provider, you will need to follow the usual steps of verifying your identity and providing proof of your address.
To do this, you will need to provide at least one form of photo ID and at least one document proving your address. Your new provider will advise you about the documents that will meet this requirement.
You will also need to contact any companies that you might have a subscription with (e.g., Netflix, Spotify) or any company that you have agreed to pay with your debit card (known as a “recurring card payment”). These payments are attached to your debit card and these companies will need to know your new card details to process any upcoming payments. They are not part of the switching process, so you need to provide your new details to these companies yourself.
You may also need to update your card details on any other payment platforms that you may use e.g., Google Pay or Apple Pay.
Your new account will be available to you once the account has been opened. Subject to the switching request being successful, your existing provider must transfer the balance, send a list of Standing Order details to your new provider, and inform Direct Debit Originators of your new account details within 7 working days. Your new provider must ensure that the account is up and running within 10 working days. Any Standing Orders you may have will also be set up on your new account 10 working days from your chosen switch date.
Cookie | Type | Duration | Description |
---|---|---|---|
_ga | Persistent | 2 years | Google/Analytics Cookie. Registers a unique ID that is used to generate statistical data on how the visitor uses the website. |
_gat | Session | Expires when browser is closed | Google/Analytics Cookie. Used by Google Analytics to throttle request rate. |
_gid | Session | Expires when browser is closed | Google/Analytics Cookie. Registers a unique ID that is used to generate statistical data on how the visitor uses the website. |
cli_user_preference | Persistent | 1 year | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. | |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . | |
cookielawinfo-checkbox-analytics | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Analytics" category . | |
cookielawinfo-checkbox-functional | 1 year | The cookie is set by the GDPR Cookie Consent plugin to record the user consent for the cookies in the category "Functional". | |
cookielawinfo-checkbox-necessary | Session | Expires when browser is closed | This cookie is used to check if necessary cookies can be placed. It works only in coordination with the primary cookie. |
cookielawinfo-checkbox-non-necessary | Session | Expires when browser is closed | This cookie is to check if non-necessary cookies can be placed. It works only in coordination with the primary cookie. |
cookielawinfo-checkbox-others | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to store the user consent for cookies in the category "Others". | |
cookielawinfo-checkbox-performance | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to store the user consent for cookies in the category "Performance". | |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. | |
Google Maps Cookies | Third-party | Most of the cookies expire 10 years after your last visit to a page containing a Google Map. | If you are logged into a Google account, Google may set a number of cookies on any page that includes a Google Map. They include a mixture of pieces of information to measure the number and behaviour of Google Maps users. Various unique identifiers, except for PREF which stores your options such as preferred zoom level. View Google's Privacy Policy. |
Google reCAPTCHA | Third-party | These are essential site cookies, used by the google reCAPTCHA for the prevention of spam. These cookies use an unique identifier for tracking purposes. Click here for an overview of privacy at Google | |
Twitter Cookies | Third-party | If you are logged in on Twitter, Twitter detects with every call-up to our website and for the entire duration of your stay on our website which specific sub-page of our website was visited by you. This information is collected through the Twitter component and associated with the respective Twitter account of the data subject. If the data subject clicks on one of the Twitter buttons integrated on our website, then Twitter assigns this information to the personal Twitter user account of the data subject and stores the personal data. | |
viewed_cookie_policy | Persistent | 1 year | The primary cookie that records the user consent for the usage of the cookies upon ‘accept’ and ‘reject.’ It does not track any personal data and is set only upon user action (accept/reject). This cookies stores your cookies preferences so the cookie banner doesn't pop up again. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. | |
vuid | 2 years | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. | |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. | |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. | |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. | |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. | |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
cli_user_preference | 1 year | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Analytics" category . |
cookielawinfo-checkbox-functional | 1 year | The cookie is set by the GDPR Cookie Consent plugin to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | Expires when browser is closed | This cookie is used to check if necessary cookies can be placed. It works only in coordination with the primary cookie. |
cookielawinfo-checkbox-non-necessary | Expires when browser is closed | This cookie is to check if non-necessary cookies can be placed. It works only in coordination with the primary cookie. |
cookielawinfo-checkbox-others | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to store the user consent for cookies in the category "Others". |
cookielawinfo-checkbox-performance | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to store the user consent for cookies in the category "Performance". |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 1 year | The primary cookie that records the user consent for the usage of the cookies upon ‘accept’ and ‘reject.’ It does not track any personal data and is set only upon user action (accept/reject). This cookies stores your cookies preferences so the cookie banner doesn't pop up again. |
Cookie | Duration | Description |
---|---|---|
Google Maps Cookies | Most of the cookies expire 10 years after your last visit to a page containing a Google Map. | If you are logged into a Google account, Google may set a number of cookies on any page that includes a Google Map. They include a mixture of pieces of information to measure the number and behaviour of Google Maps users. Various unique identifiers, except for PREF which stores your options such as preferred zoom level. View Google's Privacy Policy. |
Google reCAPTCHA | These are essential site cookies, used by the google reCAPTCHA for the prevention of spam. These cookies use an unique identifier for tracking purposes. Click here for an overview of privacy at Google | |
Twitter Cookies | If you are logged in on Twitter, Twitter detects with every call-up to our website and for the entire duration of your stay on our website which specific sub-page of our website was visited by you. This information is collected through the Twitter component and associated with the respective Twitter account of the data subject. If the data subject clicks on one of the Twitter buttons integrated on our website, then Twitter assigns this information to the personal Twitter user account of the data subject and stores the personal data. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | Google/Analytics Cookie. Registers a unique ID that is used to generate statistical data on how the visitor uses the website. |
_gat | Expires when browser is closed | Google/Analytics Cookie. Used by Google Analytics to throttle request rate. |
_gid | Expires when browser is closed | Google/Analytics Cookie. Registers a unique ID that is used to generate statistical data on how the visitor uses the website. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
vuid | 2 years | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
Cookie | Duration | Description |
---|---|---|
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |