Current bank feed issues

On occasion, a bank feed can encounter an error that affects a large number of users with that bank feed - this is different to a bank feed error specific to just one user. Our bank feed provider, Yodlee, keeps us up to date with these known bank feed issues and we'll keep you posted on this page. You can also learn more about Yodlee, bank feeds and what to expect here: Expectations of our bank feed service

Note

If your bank feed is showing an error but doesn't fall under one of the following banks, check out our user guides: Troubleshooting bank feeds and Bank feeds with persistent issues. If you are still having any difficulties, please contact our support team for assistance!


There are known issues affecting the following bank feeds

Investigations in progress

Widespread 525 errors for some New Zealand bank feeds

  • Kiwibank (New Zealand)
  • ASB Bank (New Zealand)
  • New Zealand Home Loans Transact (Kiwibank)
  • Rabobank Online Savings (New Zealand)
  • Student Loan (New Zealand)

UPDATE: November 26, 2019

Great news! After urgently investigating, this issue is now resolved. We expect these feeds will now sync without any error messages occurring.

November 26, 2019

We've seen an increase in 525 errors for these feeds, and this is now considered a widespread issue. Our apologies for the inconvenience caused.

While we've yet to receive further confirmation regarding the cause of the errors, we are treating this with the highest priority, and continue to urgently investigate with Yodlee.

We'll keep you in the loop every step of the way, to ensure you are up to date with the latest details.

Capital One Credit Cards

Support has been removed 

November 26, 2019

We have been made aware of a change that our bank feed provider, Yodlee has made to the Capital one bank feeds. Yodlee say that they have shifted the Capital One Credit Cards feed support to a new feed named: Capital One.

You may have seen our message about this a few months ago. Since that message, it looks like Yodlee had managed to keep the feed active by redirecting things from the old feed to the new feed, but recently we have had a large influx of notifications that the Capital One Credit Cards feed had been deactivated. That has resulted in some users seeing their Capital One Credit Card feed disappear from the PocketSmith Account Summary completely.

To add the new feed, head over to the Accounts > Account Summary page and add the new bank feed, and then delete the old one.

You'll need to then search for Capital One, selecting the option "Capital One - Bank, Loans, Credit Cards, and Mortgage".

Check out our Learn Centre to find out more about: 

The accounts which are available to be linked will show on the Accounts > Account Summary page within the Ready to link section. Check out our Learn Centre documentation to find out more about Establishing your bank feed accounts in PocketSmith

Please note that we have seen some users encounter trouble once they add the new Capital One feed. This is either in the form of no accounts being found or an account being found, but no transactions being gathered. If you experience either of these issues, please contact us and we will open an investigation with Yodlee.

Apologies again and please let us know if you have any questions.

Loans.com.au

Feed Sync Errors

November 19, 2019

We have had users report to us that they are seeing various errors due to a significant site change to the Loans.com.au online banking site.

We have informed Yodlee and they are working on updating things now.

Charles Schwab

Duplicate Transactions

UPDATE: November 26, 2019

There was a brief moment where users were seeing a 412 error on their Charles Schwab account. This secondary issue now seems to be resolved and we are continuing to see if a solution can be found for the duplicate transaction issue.

November 19, 2019

We have been getting reports from users reporting duplicate transactions in their Charles Schwab accounts.

Yodlee have been investigating and this is what they have found:

Observations :
1. We observed that after posting the transactions the online banking site is changing the transaction date.
2. These changes are noticed between a period of 1-5 days and sometimes even as long as between 20-30 days.
3. This is resulting in duplicate transactions.
4. For some transactions, the date has been changed 3 times.

For example :

  • The transaction, EXAMPLE TRANSACTION with amount 22.22, initially had the transaction date 31-Oct-19
  • However (after 5 days) on 06-Nov-2019 the date was changed to 30-Oct-19
  • Again, on 08-Nov-2019 the end site changed the date to 31-Oct-19, and again to 30-Oct-19 later on, the same day.

The Yodlee engineering team has deleted the duplicates. However, this issue may continue if Charles Schwab's behaviour (changing the date after posting the transactions) remains the same.

Customer action required: Kindly ask the PocketSmith customer to contact the Charles Schwab support team to confirm why the dates are being changed for the same transactions, more than once after being posted. 

Also, it would be appreciated if some logical explanation can be provided so that Yodlee can adapt accordingly to prevent such duplicates in the future.

America's First FCU

Site Temporarily Unavailable

UPDATE: November 26, 2019

Yodlee have now marked this investigation as resolved.

Please let us know if you are still seeing any errors and we will investigate further.

UPDATE: November 19, 2019

Yodlee have another update to release tomorrow. Please let us know how a sync attempt goes a few days after tomorrow.

UPDATE: November 12, 2019

Yodlee have released another update today, please try sync this feed for a few days and let us know if you are still seeing an error.

November 5, 2019

We have seen a number of users experiencing errors on their America's First FCU feeds. Yodlee are aware of the issue and plan to have an update out by the end of the week.

Please let us know how a sync goes during the weekend.

Commerce Bank

409 or 403 errors

UPDATE: November 26, 2019

Thanks for your patience while Yodlee continue to work towards a resolution of this issue. We've still yet to receive an ETA for a fix, unfortunately. Rest assured, we'll keep you in the loop with any developments as we receive them.

UPDATE: November 12, 2019

Just a quick update to let you know that Yodlee are still working hard to solve this issue. They don't have an ETA a this stage but we will let you know as more information is passed to us.

UPDATE: October 29, 2019

Thanks for testing the Commerce bank feed over the weekend.

Yodlee are continuing to work on more changes and we will let you know as we know more.

UPDATE: October 22, 2019

Yodlee have set a tentative ETA for an update for the end of this week.

Please let us know if you are still seeing errors after this weekend.

UPDATE: October 15, 2019

While we still don't have any more information as to what has caused this issue, please be assured that Yodlee are still working hard on a solution to this error.

We will let you know next time we have any news.

UPDATE: October 7, 2019

Yodlee are still searching for a solution for this issue. We don't have any ETAs yet but we will let you know as soon as we have more concrete information for you.

October 1, 2019

We have been seeing reports from users saying they are seeing a 403 or 409 errors on their Commerce bank feed.

Yodlee are actively looking into the cause of the issue and we will let you know once we know more.

PNC Bank

426 error

UPDATE: November 19, 2019

Yodlee have let us know that they have further updates to make and they will be released at the end of this week.

Please let us know how a sync attempt goes.

UPDATE: November 12, 2019

Yodlee are still on track for the update they have planned on November 15th. Please test your PNC feed for a few days after the 15th and then let us know if you are still seeing errors.

UPDATE: November 5, 2019

Yodlee have updated their tentative ETA to November 15th now.

We will keep an eye on this and will let you know if anything changes.

If you are seeing a 429 error, we may have a solution for you.

Yodlee have been advising users seeing a 429 error to enable multi-factor authentication as it is a requirement for users wanting to use bank feeds to have this enabled.

The message they see is this: "In order to link to your PNC account, we require verification of account ownership as an additional security measure. Account ownership must be verified using a one-time passcode sent directly to your mobile device. First, please sign on to PNC Online Banking to enrol a mobile number. After you have enrolled a mobile number, you may proceed to complete your account link request using a one-time passcode to verify account ownership."

UPDATE: October 29, 2019

We have had an update from Yodlee. Since the changes released at the end of last week, Yodlee have been working on a new batch of updates. They have set a tentative ETA for the end of next week but we will update you if that changes.

UPDATE: October 22, 2019

Yodlee have let us know that they have an update they are working on. They believe it will be released at the end of this week.

During the weekend, please try sync your feeds and let us know how you go.

UPDATE: October 15, 2019

We have started to get reports from our users that they are seeing 412 errors on the PNC Bank type.

We have been reporting these to Yodlee to see if this is related to the changes related to the recently implemented multi-factor authentication.

We'll let you know as we find out more.

UPDATE: October 1, 2019

Yodlee have found that PNC have recently implemented multi-factor authentication and now require users to enter a passcode as part of login requirements.

If you haven't entered a passcode yet, or haven't been asked to enter a passcode, this may be the cause of the error.

Please let us know if you are still having issues.

September 24, 2019

We have been receiving reports from users that their PNC bank feed is failing with a 426 error.

Yodlee have been investigating and have found that PNC bank has been blocking some of their connections causing this error.

They have now elevated this to a wide spread issue status as they work with PNC Bank directly to restore their bank feed connections.

Recently resolved

SunSuper (Australia)

403 error

November 12, 2019

We have been getting reports from several users that SunSuper is failing with a 403 error. Yodlee are aware of this issue and they are searching for a solution now.

We will update you once we have more information.

Commonwealth Bank CBA (Australia)

Loans account type 412 error

UPDATE: November 12, 2019

We have continued to see reports that this is resolved. However, we will continue to look out for any new reports from users.

UPDATE: November 5, 2019

While we have seen most users report that the bank feed error has been resolved, Yodlee are still detecting a small number of users having errors.

If you are one of these users, please let us know and we can investigate your specific case.

UPDATE: October 29, 2019

Yodlee have let us know that they have some updates on the horizon. They believe they will be released in the next couple of days so please try syncing your feed a few days from now and let us know how things go.

October 16, 2019

We have been receiving reports from users who have been seeing 412 errors on their CBA Loans feeds. Yodlee are aware of the issue and they are working on a resolution.

Only the Loans account type has been affected, other account types continue to sync successfully.

Please let us know if you are still seeing errors next week and we will let you know if anything changes.

UBank (Australia)

Transaction Errors

UPDATE: November 12, 2019

Most of our users are reporting that they are able to sync successfully but we are still seeing a few users with errors.

Please let us know if you are one of those users.

UPDATE: November 5, 2019

Since the last update, Yodlee have made further changes once they found users were still seeing errors.

Let us know if you are still having trouble after these updates.

UPDATE: October 29, 2019

We have been getting reports from Yodlee that the issue has been resolved.

We have been getting confirmation from our users so we will treat this as resolved.

If you are still seeing issues, please let us know and we can continue to investigate.

UPDATE: October 15, 2019

Yodlee have reported that this issue is now resolved.

We have had some reports from users confirming this but we also have some users still experiencing issues.

If you are still seeing errors or duplicate transactions, please let us know and we can continue investigating.

October 7, 2019

We have been receiving a number of reports from users that they are seeing errors on their UBank bank feeds.

Yodlee have just informed us that they believe the cause of this is due to a change in the UBank login page.

Yodlee are now working on updating the bank feed to cater to this change. We will let you know once we have more information.

ANZ (Australia)

Site Temporarily Unavailable

UPDATE: October 29, 2019

We have been getting more reports now that the various issues on the ANZ (Australia) feed are being resolved. We are also aware that we have some users still experiencing issues and we will continue to investigate as reports come in.

Hopefully the trend continues and we have all the issues resolved soon!

UPDATE: October 15, 2019

We are still receiving reports from users with errors and transaction errors on their ANZ feeds.

We will continue to work with Yodlee on the individual issues you bring to us and hopefully Yodlee can stabilise the feed soon.

UPDATE: October 7, 2019

Yodlee are releasing another update today, please let us know how a sync attempt goes over the next few days.

UPDATE: October 1, 2019

Yodlee say that they have an update due to be released mid this week. Please let us know how a sync goes in the days following the update.

UPDATE: September 24, 2019

We have been seeing more reports from users that the duplicate transactions have been removed.

Please let us know if you notice any new duplicates being created.

UPDATE: September 17, 2019

We continue to see reports of duplicate transactions and other irregularities for this feed and we, with Yodlee will continue to investigate the cause of this.

We will let you know once Yodlee have more information for us.

UPDATE: September 10, 2019

Over the past week, we have been receiving reports from users that they are seeing duplicate transactions.

We are continuing to investigate what is going on so please let us know if you are also seeing duplicates.

UPDATE: September 3, 2019

We have been receiving updates from users that they are now able to sync their feeds successfully. We are now viewing this as resolved but if you are still experiencing issues, please let us know.

UPDATE: August 20, 2019

We are seeing mixed results from our users. Some have been able to sync successfully, but others are still seeing errors.

Please let us know if you are one of those users still seeing an error and we can investigate further.

UPDATE: August 13, 2019

Yodlee are reporting this is resolved now, and we are getting similar reports from our users. Please let us know how a sync attempt goes.

UPDATE: August 6, 2019

Yodlee are releasing some changes today. Please let us know how a sync attempt goes after a few tries over the next few days.

UPDATE: July 30, 2019

We have been receiving mixed updates from our users about the state of this bank feed. We have a number of users who are now able to sync their feed, but we also have a number still encountering an error.

Please let us know if you are one of those people and we can open an investigation for your specific case.

UPDATE: July 23, 2019

We have been receiving reports from users who have been seeing 403 and 414 errors on their ANZ bank feeds. Yodlee are looking to things and estimate an update will be released at the end of this week.

Please let us know if you are still seeing errors next week and we will let you know if anything changes.

Still need help? Contact Us Contact Us