QBO Bank feed problem - FNB Bank - from 12June2023...FIXED!
This error has been fixed, but bank feed errors will remain a potential issue and so the fixes will be good to refer to in future. Some banks still do not feed into QBO - eg with their business accounts, and the manual import solution remains the work-around ✌️
QBO is currently having trouble with the FNB bank connection. It is a widespread issue and they are attending to it.
If you make use of FNB I advise that you do not try reset your connection at all at this time, as it will not be pulling transactions in.
Please give it a week at least.
Examples of current problems:
Error 119
Bank account names read like this: “&#XX; &#XX; &#XX; ”
Imported transactions have a similar prefix and annex to the description (if you’re lucky enough to actually get any to pull through).
Workaround:
In the interim I advise that you log into your internet bank and download exports of your bank accounts and then import those into you banking portal on QBO – right block dropdown arrow – select: upload from file
Then see the instruction block…drag and drop the bank export into the block (or click on select file and go browse for it)
You will see that CSV and OFX are 2 of the available formats. I find that with SA banks using OFX is the most reliable, but if you routinely have csv exports saved (like I always do as a backup) then it won’t be a problem to trim it to only include the lines you want and then import the csv.
Have this method as a permanent go-to fix for when bank feeds go down.
Things to look out for with a csv:
Ensure that the importing file has the correct number signage: positive numbers are receipts into the bank (debits) and negative numbers are for payments out of the bank (credits).
Date format: this is the biggest issue I get with csv’s, and the reason I prefer OFX format. Your file will have a date format. Your excel (or similar) program will have a date format and your PC or Mac will have one too. Then QBO has its own that has been setup. This is a permanent bug-bear that causes hassles all over the place with importing and there is no simple solution/fix, as these different setups do not obey the setup instruction and do not recognise what they should a lot of the time…so just check the date on the import screen and fix it if it’s wrong before pulling it into your books. If you need to then import one line and get the date right then do the rest in a separate import afterwards, learning from the first attempt.
✌️Rob