Error importing IIF File

ErikD · ‎December 18, 2018

Getting this error on the End Trans line. The IIF file has been used for years and now we're getting this error after upgrading to 2019.

[ERROR] Expected '!ENDTRANS'. [15152]

Here's a larger look at the file and errors.

!CUST   NAME   BADDR1   BADDR2   BADDR3   BADDR4   PHONE1   EMAIL   CONT1   CTYPE   TAXABLE   NOTEPAD   COMPANYNAME   NOTE
CUST   St George Test Gallery LLC (2776371)   635 Test. George Blvd   Saint George   UT   84770   [removed] [email address removed]                   St George Test Gallery LLC
CUST   St. George Test Gallery LLC (2776410)   1081 E. Test     Saint George   UT   84790   [removed] [email address removed]                   St. George Test Gallery LLC
!TRNS   TRNSTYPE   DATE   ACCNT   NAME   CLASS   AMOUNT   DOCNUM   MEMO   CLEAR   TOPRINT   NAMEISTAXABLE   PAID
; [ERROR] Expected '!ENDTRANS'. [15152]
TRNS   INVOICE   09/04/2018   Accounts Receivable   St. George Test Gallery LLC (2776410)   St. George Test Gallery   97.15   1-40001   Invoice 40001   N   N   Y
!SPL   TRNSTYPE   DATE   ACCNT   NAME   CLASS   AMOUNT   DOCNUM   MEMO   CLEAR   QNTY   PRICE   INVITEM   TAXABLE   EXTRA
SPL   INVOICE   09/04/2018   Labor   St. George Test Gallery LLC (2776410)   St. George Test Gallery   -89.95   1-40001   Labor   N   -1   89.95   Labor   N
SPL   INVOICE   09/04/2018   Shop Supplies Sales   St. George Test Gallery LLC (2776410)   St. George Test Gallery   -7.20   1-40001   Shop Supplies Sales   N   -1   7.20   Shop Supplies Sales   N
SPL   INVOICE   09/04/2018   Sales Tax Payable   Sales Tax Vendor   St. George Test Gallery   0.00   1-40001   Sales Tax Payable   N           Sales Tax Payable   N   AUTOSTAX
ENDTRNS
!TRNS   TRNSTYPE   DATE   ACCNT   NAME   CLASS   AMOUNT   DOCNUM   MEMO   CLEAR   TOPRINT   NAMEISTAXABLE   PAID
; [ERROR] Expected '!ENDTRANS'. [15152]
TRNS   INVOICE   09/06/2018   Accounts Receivable   St. George Test Gallery LLC (2776410)   St. George Test Gallery   352.51   1-40002   Invoice 40002   N   N   Y
!SPL   TRNSTYPE   DATE   ACCNT   NAME   CLASS   AMOUNT   DOCNUM   MEMO   CLEAR   QNTY   PRICE   INVITEM   TAXABLE   EXTRA
SPL   INVOICE   09/06/2018   Labor   St. George Test Gallery LLC (2776410)   St. George Test Gallery   -299.90   1-40002   Labor   N   -1   299.90   Labor   N
SPL   INVOICE   09/06/2018   Parts Sales   St. George Test Gallery LLC (2776410)   St. George Test Gallery   -26.49   1-40002   Parts Sales   N   -1   26.49   Parts Sales   N
SPL   INVOICE   09/06/2018   Shop Supplies Sales   St. George Test Gallery LLC (2776410)   St. George Test Gallery   -26.12   1-40002   Shop Supplies Sales   N   -1   26.12   Shop Supplies Sales   N
SPL   INVOICE   09/06/2018   Sales Tax Payable   Sales Tax Vendor   St. George Test Gallery   0.00   1-40002   Sales Tax Payable   N           Sales Tax Payable   N   AUTOSTAX
ENDTRNS
!TRNS   TRNSTYPE   DATE   ACCNT   NAME   CLASS   AMOUNT   DOCNUM   MEMO   CLEAR   TOPRINT   NAMEISTAXABLE   PAID
; [ERROR] Expected '!ENDTRANS'. [15152]

Anonymous · ‎December 19, 2018

There are two issues here:

First, the error is incorrect:

"; [ERROR] Expected '!ENDTRANS'. [15152]" should state:

"; [ERROR] Expected '!ENDTRNS'. [15152]"

Second, you're getting the error because you have not defined the ENDTRNS row. You need an ENDTRNS definition line that starts with !ENDTRNS just as you have !TRNS and !SPL defined.

Also, note that there is no need to repeatedly redefine the rows. One set of

!TRNS ...

!SPL ...

!ENDTRNS

definition rows at the top of the file is all that is needed.

While this needs to be fixed (would never have worked with any QB version), save yourself a lot of pain by following our recommendations: BRC - QuickBooks 2019 IIF Import Changes and Recommendations

View solution in original post

Anonymous · ‎December 19, 2018

There are two issues here:

First, the error is incorrect:

"; [ERROR] Expected '!ENDTRANS'. [15152]" should state:

"; [ERROR] Expected '!ENDTRNS'. [15152]"

Second, you're getting the error because you have not defined the ENDTRNS row. You need an ENDTRNS definition line that starts with !ENDTRNS just as you have !TRNS and !SPL defined.

Also, note that there is no need to repeatedly redefine the rows. One set of

!TRNS ...

!SPL ...

!ENDTRNS

definition rows at the top of the file is all that is needed.

While this needs to be fixed (would never have worked with any QB version), save yourself a lot of pain by following our recommendations: BRC - QuickBooks 2019 IIF Import Changes and Recommendations

chonres · ‎February 24, 2019

Thanks for this post. I discovered the hard way that the QB 2019 IIF import doesn't work with PayPal generated IIF files because PayPal doesn't include a TRNSTYPE field which QB thinks ought to be mandatory. PayPal has NEVER included this field and their IIF files have always worked just fine with older versions of QB. I'm glad to know the old import is still available.

MDivers · ‎March 14, 2019

Upgraded 2 days ago - and nothing else has changed and now my imported POS iif files have errors. When I examine the results - I get the Sales transaction by account but no payment accounts such as visa, amex, etc. Looks like QB is creating an error file and when I try to review the file I cannot open it with the QB Launcher that is suggested.

Mind you - nothing, nothing changed on the POS system.

Anyone help?

ShiellaGraceA · ‎March 14, 2019

Hi MDivers,

I suggest consulting our Technical Support Team so we can assist you further in reviewing the error in the QuickBooks Launcher.

To speak with one of our phone agents:

In your QuickBooks home page, press F1.
Click the Contact us link at the bottom.
In the Tell us more about your question field, type "import error".
Click Search.
Click Get Phone Number or Start a Message.

If you have any more questions, please don't hesitate to hit the Reply button.

BK · ‎May 29, 2019

We have the issue as well, one invoice type imports fine but the other errors out. Both worked with 16 and now 19 is quirky. The qb launcher which pops up to do error evaluation errors out as well. I opened it in notepad to see the error but it doesn't say anything where you could decipher why its erring out. Gonna just run the bypass route,

Angelyn_T · ‎May 29, 2019

Hi there, @BK.

I'd be glad to help you today so you'll be able to import your IIF file successfully.

As of now, I recommend contacting our Support team to check and verify this further securely. For the support's contact information, you may follow the steps provided by my colleague ShiellaGraceA, or you may check this link: Contact the QuickBooks Desktop Customer Support Team.

On the other hand, you may also check this article to learn more about the improved IIF Import in QuickBooks 2019: Improved IIF Import in QuickBooks 2019.

Please stay posted if you have any other QuickBooks or importing concerns, I'll be always here to help you. Have a great day ahead!

Anonymous · ‎May 30, 2019

RE: As of now, I recommend contacting our Support team to check and verify this further securely.

So, Intuit now fully supports IIF import after years of castigating it? Good to know.

Janice_Pcdc · ‎February 09, 2020

after hours of struggling I am glad I came here and now I know click on the "non recommended" way and its just like old times! If it aint broke don't fix it -- I wish they left the IIF import alone.. but at least now I know what to do.

Topics

Training

Community

Resources

Error importing IIF File