Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Get 50% OFF QuickBooks for 3 months*
Buy nowSolved! Go to Solution.
We've found that recent versions of QuickBooks ignore the \n characters in memo fields when importing using the standard flow. Starting with QB 2019 Intuit significantly changed (and messed up) IIF import in an effort to make it better. While that failed fantastically, they've done little to fix it since.
Still, there is a way to make it work again like it used to. See this page for steps, and for a long list of issues with the new import code, which (thank goodness) continue to not exist in the old code, which you can access:
This issue could have been related on how the file was formatted, chrish2.
Correct .IIF format must be followed exactly to ensure your transactions import successfully. If not, this may lead to an error or the data will import incorrectly.
To ensure everything is handled correctly, you might want to view the instructions and recommendations stated in this article: IIF Overview, import kit, sample files, and headers.
Lastly, here's more details about the new and imporved IIF Import in the later versions of QuickBooks Desktop: Latest Changes about importing.
Be sure to drop your questions again if you require further assistance.
Yes, putting "\n" within a Memo/Description field on a form that can show it in multi-line format will work. For example, for an item description on an invoice or other sales form.
Thank you for your reply.
It didn't work. We are using the memo field as shown here...
!SPL SPLID TRNSTYPE DATE ACCNT NAME CLASS AMOUNT DOCNUM MEMO
SPL 134 INVOICE 12/27/2019 Consulting Income -62.50 "10/03/2019\nSR# 80782: Looked into Domain questions"
Everything comes in fine but the Invoice description still shows the \n...
10/03/2019\nSR# 80782: Looked into Dom...
I tried it with and without the quotes and also tried to use the character excel puts in a CSV when a field has an embedded carriage return. All to no avail. Any ideas?
BR, thanks for your reply. I just posted a response with the data being given and the result. The \n is not being perceived as a carriage return. The invoice import process being used is the newest and they are 100% successful except for this. Can you see something I am missing? I exported lists and they come out with \n as you would expect.
Hello, @chrish2.
To get further assistance with the format of your .IIF files in QuickBooks Desktop, I suggest reaching out to our Product Support team. They have the tools to get into your account in a secure environment.
You can arrange a callback to talk to them. Follow the steps below:
Here's the contact the QuickBooks Desktop Customer Support Team article for more information about this.
Let us know if there's anything that we can help by leaving a comment below. Have a wonderful day!
I already contacted them. They said they don't support IIF import questions or issues. Help!
Thanks for reaching back out to us, @chrish2.
Per our technical support plan, we don't offer assistance in creating or importing .IIF files.
I recommend using a third party app instead. You can go directly to this link: https://desktop.apps.com/home.
There are available apps in QuickBooks that can allow you create IIF files to works with the system.
You can drop your questions again if you require further assistance. I'll be there in a moment.
We are a developer and prefer the IIF over the SDK because the data comes from an external data source as a file. Rather than constructing an XML file or parsing the IIF ourselves, I just hoped the import worked as advertised. With regard to \n, it doesn't. I knew Intuit would offer no help but hoped another developer might have some insight.
Good evening, @chrish2.
Thanks for your feedback on the product. I'm going to let my Development Team know that you suggested bringing a memo field to transactions when you import from an IIF file. I understand that connecting a third-party app can be a hassle. The app you decide to integrate with your Quickbooks, you can contact them to get more information on how it's going to work.
If you have any other concerns or questions, please let me know. I'm all ears and happy to lend a helping hand. Have a great day.
RE: The \n is not being perceived as a carriage return.
Not sure. That is how it is done in QB. We do it all the time and have included this code in our apps like the BRC IIF Transaction Creator Pro . It works every time.
We are using the BRC IIF Creator and have run into the same problem. BRC support has been helpful in trying to resolve this - they are able to upload our IIF file into QB 2021 and see the \n as a line feed. When we import the IIF into our QB's, is just shows the "\n" and does not line feed. Wondering if Chrish2 or anyone else has figured this out? Thanks for any help.
We've found that recent versions of QuickBooks ignore the \n characters in memo fields when importing using the standard flow. Starting with QB 2019 Intuit significantly changed (and messed up) IIF import in an effort to make it better. While that failed fantastically, they've done little to fix it since.
Still, there is a way to make it work again like it used to. See this page for steps, and for a long list of issues with the new import code, which (thank goodness) continue to not exist in the old code, which you can access:
Same problem here. (using 2021 Premier) I tried the option at the bottom of the import window "import without review (not recommended) Import it for me I'll fix it later" It works fine accepts the \n and puts in the line break.
You have clicked a link to a site outside of the QuickBooks or ProFile Communities. By clicking "Continue", you will leave the community and be taken to that site instead.
For more information visit our Security Center or to report suspicious websites you can contact us here