Loss of transaction data when importing to bank feeds

I understand how important this issue to be resolved as soon as possible, @djfabdan. I'm here to help you get your issue resolved positively.

If there are more than the limited details to be imported, some of your transaction data may have been reduced or completely removed. Because the transaction data is too large or long to be imported, you are unable to copy and paste the missing data.

In QuickBooks Desktop each field for the data file has a maximum number of characters that can be entered and in this case, the payee and the memo fields are only limited to 32 characters. 

For more details about character limitations you can refer to this article: Character limitations for fields for QuickBooks

I'd recommend sending feedback to our Product Development team with regards to this matter. In order for them to enhance and give you the best QuickBooks experience. Your opinions with us will be highly appreciated.

Here's how:
 

1. Go to the Help menu and then select Send Feedback Online.
2. Choose Product Suggestion.
3. Add the type of feedback.
4. Type in your feature suggestion.
5. Once done, click Send Feedback.
   
   

Then, you can visit our QuickBooks Online Feature Requests website to track the status of your submitted feedback.

However, if your transactions aren't more than the maximum character, it'll be great if you could provide some screenshot. This way, we can investigate further about this issue and provide you with a resolution that fits your situation.

I've also added this following articles to help you fix import issues and data damage in QuickBooks Desktop:
 

• Fix Web Connect import errors
• Fix data damage on your QuickBooks Desktop company file
   

Keep me posted on how everything goes or if you need anything else. I'm just around. Take care!

This may be happening because when using bank feeds, which uses OFX files, the payee and memo are limited to 32 characters. If the bank puts a bunch of junk before the payee name or pertinent parts of the memo, then there's not much room left for what you care about.

Is there a workaround?

It's a terrible problem that, to me, doesn't make any sense.

The original bank statements have all the info I need to quickly decide exactly what the transaction was and where it needs to reconcile.

And the register where the transactions go certainly have ample space to hold all that data (if I type it in manually-but that defeats the purpose)

@djfabdan 

Does your bank provide other file formats for download? You can use the converter tool and import it as a QBO file

ASCII, Web Connect Quicken and Web Connect QuickBooks are my 3 options.

ASCII, web Connect Quicken and Web Connect Quick Books are my 3 options.

The converter tool only supports QIF, OFX, QFX, CSV, and PDF

https://www.moneythumb.com/?ref=110

It can do CSV.

What's the process for getting the CSV into bank feeds?

All I've ever done is the Web Connect files, and only those a few times.

As a software architect, I can tell you that this problem is not acceptable.   It is not hard to update file length ingestion field lengths.  I don't see the point of having QuickBooks if we have to keep going back to the banking data.  What really is scary is that you don't know it's missing unless you do a full reconcile. You have to do a full reconcile anytime you want to use the tool. Good grief. That is totally unacceptable QB. 

I am currently missing May, June, July, August of 2021 and then for the months where there is some data there are random records missing. 32 Byte limits are not an excuse.  Fix it.  I have tried the updates everything.  No luck.