QB Desktop IIF Import of TRNS Ignores the NAME

DanCooperstock · ‎September 16, 2024

I'm trying to import bank transaction (type TRNS) into QB Desktop from an IIF file, but the NAME field is always ignored (it's not put into the Payee field like it should be). The type is DEPOSIT.

I have tried first importing those names as OTHERNAME records, or as CUST records, earlier in the same IIF file, but it doesn't help. (They do get imported from those records!) Even if the values I'm using for the NAME field are already stored in QB as Customers, and I import the field, the NAME is ignored and nothing is put into the Payee field.

Here's the file I'm importing (the version that tries to create the customers first):

!CUST NAME

CUST 1234567[removed][removed][removed]890

CUST Bob's Burger

!ACCNT NAME ACCNTTYPE

ACCNT TD BANK

ACCNT Advantage Income INC

ACCNT Service Charges EXP

ACCNT General Donations INC

ACCNT Library Donations INC

!TRNS TRNSID TRNSTYPE DATE ACCNT CLASS NAME AMOUNT MEMO

!SPL TRNSTYPE DATE ACCNT CLASS AMOUNT NAME

!ENDTRNS

TRNS 20240913-74-2 DEPOSIT 04/02/2024 TD 1234567[removed][removed][removed]890 99.00 eTransfer

SPL DEPOSIT 04/02/2024 Advantage Income -40.00 1234567[removed][removed][removed]890

SPL DEPOSIT 04/02/2024 General Donations General -60.00 1234567[removed][removed][removed]890

SPL DEPOSIT 04/02/2024 Service Charges 1.00 1234567[removed][removed][removed]890

ENDTRNS

TRNS 20240913-74-7 DEPOSIT 04/27/2024 TD Bob's Burger 14.50 eTransfer

SPL DEPOSIT 04/27/2024 General Donations General -10.00 Bob's Burger

SPL DEPOSIT 04/27/2024 Library Donations General -5.00 Bob's Burger

SPL DEPOSIT 04/27/2024 Service Charges 0.50 Bob's Burger

ENDTRNS

TRNS 20240913-74-12 DEPOSIT 08/28/2024 TD Bob's Burger 0.50 eTransfer

SPL DEPOSIT 08/28/2024 General Donations General -1.00 Bob's Burger

SPL DEPOSIT 08/28/2024 Service Charges 0.50 Bob's Burger

ENDTRNS

Does anyone have any ideas how to get this to work? Thank you.

Trish_T · ‎September 17, 2024

Hi DanCooperstock,

You've spent a lot of valuable time on this and I would like to see this resolved, so you an get back to what you love. When importing the .IIF file, rather than selecting Import IIF, click on Import it for me, I'll fix it later option. This uses a different import code, so the Name field isn't ignored.

Give this a try and keep us posted on the outcome. It will help other Community members who may have the same issue, so they can complete the upload process without concerns.

View solution in original post

Amanda-B · ‎September 16, 2024

Hey there, DanCooperstock.

Thanks for joining us here in the Community! I recommend taking a look at this article as it provides detailed information. Please keep in mind that at this time Intuit doesn't offer technical support for IIF files. You'll need to contact the apps technical support if you're using a third party app for your files.

If you have any other questions, feel free to reach back out.

DanCooperstock · ‎September 16, 2024

That doesn't help - the import was being accepted without errors, it just wasn't saving the NAME field data as the Payee.

I thought this area was for community support, not just support from Intuit staff, that's why I asked it here, hoping someone else in the QB user community would have an answer. I was aware from past support issues that Intuit doesn't directly support issues about IIF files.

I'm a developer and this issue is about exporting data from a program we sell, for import into QB Desktop. Not getting this working will be a reason that discourages our users from using QB for their accounting!

If you have any other suggestions about how I can get support for IIF issues please let me know! Thank you.

On Beta · ‎September 16, 2024

@DanCooperstock

Which QB Desktop year version do you run?

DanCooperstock · ‎September 16, 2024

I'm using a QB Desktop 2024 Pro trial version.

On Beta · ‎September 16, 2024

IIF offers limited functionality and they don't have any roadmap to improve it. You should consider using a third-party importer tool or converter app.

DanCooperstock · ‎September 17, 2024

I understand the limitations of IIF, what bothers me is this apparent bug. There is absolutely no reason it should not be importing the NAME field as the Payee.

I suspect any 3rd party tool would either not be royalty free or too expensive to bundle with our very inexpensive application, but if you have an affordable 3rd-party importing suggestion I'd be happy to hear about it!

Deity Alpha · ‎September 17, 2024

What file formats can you download from your banks other than IIF? csv, pdf or else?

DanCooperstock · ‎September 17, 2024

Deity Alpha, this has nothing to do with bank downloads. This is an export file that code we wrote in a program we sell to churches and charities creates, for import of transactions into QB.

Trish_T · ‎September 17, 2024

Hi DanCooperstock,

You've spent a lot of valuable time on this and I would like to see this resolved, so you an get back to what you love. When importing the .IIF file, rather than selecting Import IIF, click on Import it for me, I'll fix it later option. This uses a different import code, so the Name field isn't ignored.

Give this a try and keep us posted on the outcome. It will help other Community members who may have the same issue, so they can complete the upload process without concerns.

DanCooperstock · ‎September 17, 2024

YES! Thank you Trish!

"Import it for me, I'll fix it later" works properly. That is truly bizarre. Sounds like a bug, hope it can be fixed. But now I can document that in my Help about importing into QB Desktop from our export files, and leave this problem.

Trish_T · ‎September 17, 2024

Hi DanCooperstock,

I'm so happy to hear this workaround was a success. Enjoy the rest of your day!

Topics

Training

Community

Resources

QB Desktop IIF Import of TRNS Ignores the NAME