Thank you for this explanation of my failed backup file import. This means that I cannot use the desktop version 17 method to import bank files. I will await further developments. Thanks again.
Are you suggesting Intuit may have modified a standard or changed the software it licenses to banks for exporting statements? If that is what has happened, that supports my original idea that the statement formats might have changed without announcement.
As 2 of us could not import the old files into the new version of Manager, That tends to suggest that it is not the problem. But who knows.
waiting on @lubosâs input.
1 Like
If a bank format file change had occurred then that would imply that those 2018 files wouldnât be able to be imported into any version of Manager, however, that hasnât happened, a 2018 bank format file can be imported into a 2017 Manager version.
Can we stick to the facts and not the speculation
Iâll admit all the details make my eyes swim. But I canât find any explicit statement supporting what you said in the quote above. I find reports that 2017 statements can be imported into 2018 versions of Manager. Can you point me to such a report?
As above
This comment is not supported by the same user in post 24:
"It also doesnât explain why i canât import last years files (2017) into the current (2018) version (of Manager).
Desktop users can use the downgrade to 2017 method.
As a cloud version user, I am automatically updated and therefore cannot import anything but QIF files. No other Intuit format works.
In technology, speculation is known as âtrial and errorâ. Advancements in technology are not possible without trial and error. As I have been called our for non participation and letting this thread die. I will soon begin reciting poetry to keep it alive.
You were not âcalled outâ for non-participation, @owen. I cited the date of one of your earlier posts for two reasons:
- To identify in which post you had referred to a different file type than what had been discussed more recently, and
- To explain why it seemed your problem might have been resolved and, therefore, not be related to the one mentioned by others.
Thank you.
My tax free, export only, no inventory, cash payables, prepaid receivables, accounting system is very simple except for income tax filing which is highly dependent on bank activity. I am poorly qualified to discuss accounting software, so I will mostly lurk in the background.
Thanks to all for your ongoing hard work on this problem.
@Hiflyer @owen, could you send the bank statement file you are trying to import to bugs@manager.io ?
Yes but not to the open forum. sorry, missed where you wanted me to send it. Am sending now.
bee
Try importing your QFX file in the latest version (18.3.13). Should be fixed there.
Thank you Lubos,
I have downloaded 18.3.13 and imported multiple files. It shows the imports. Appears you have fixed my problem
to @brucanna, @nktech1135,
Give it a shot and see if it fixes your import problems.
Owen, I am not clear if the cloud version is also updated.
I have successfully imported a .qbo file in the cloud version.
Thank youâŚ
Just did a successful import into cloud version of âwebconnect for quickbooks 2015 and aboveâ from another bank.
I have gained a whole new appreciations for this forum and all who participate. Thanks for the guidance and patience you have given me.
Works like a charm.
Iâm curious, what was the issue?
Not that i really need to know, iâm just technically inclined enough to be curious.
Well, the bank statement file format looks like itâs XML
<STMTTRN>
<TRNTYPE>CHECK
<DTPOSTED>20180123120000
<DTUSER>20180123120000
<DTAVAIL>20180123120000
<TRNAMT>-2450.00
<FITID>4063666793
<CHECKNUM>1028
<REFNUM>2902539492
<SIC>000000
<NAME>CHECK
<MEMO>#1028
</STMTTRN>
but itâs not really as itâs missing closing tags. The latest version is just more forgiving and will accept the file even if itâs malformed XML.
Thanks for the explanation and the fix.