Recommended Posts

On 19/05/2024 at 15:32, Jason Doster said:

One additional thing I'm seeing. The account field cannot be more than I think 25 characters it look like. The IIF generator will chop off the account name if it is too long, and when it's imported, another account is created to the chopped. That's happening with only a handful of accounts who's name's are too long. If no fix is possible, I'll just shorten up about 5 of my account names. Thx!

I add the character limit back in for 4.5 beta. The issue with the last implementation was that it checked for 31 characters regardless of subcategories. It can be 31 characters PER account. 

it did not take into consideration subcategories, so it thought Business:Subscription Serv - Business:Software Subscriptions was one big account, thus chopping it off at 31 characters. It now calculates 31 Character account names per : (colon)

I downloaded CSVtoIIF451Latest.exe.

I imported my bank's .csv file no problem. (Transactions from January 1 2024 through today.)

Then I exported (printed) a tab delimited file using an earlier month from the same account. (QBD Premier manufacturing and Wholesale Edition 2021)

I used "Create/Edit Rules" and imported the tab delimited file and I created the .json file no problem.

Then I did some manual editing of transactions within the main app.

Exported the .iif

Imported to QB and only 9 transactions succeeded with over 100 failed.

So I thought, OK, let's skip the manual editing part and start over. Maybe I am doing something wrong.

This time I exported a tab delimited file using all of 2023. I then went through and cleaned that up only keeping stuff that had value, removing the # on each rule, etc.

This all seemed to work, so I exported the .iif file.

Imported the .iif to QB and BAM, QB was gone. It just crashed and went a way.

Tried it again and same thing. Needless to say, nothing was imported. I am at a stand still. 

I should mention, I firewalled QB so that it cannot communicate with the Internet. I am trying to freeze at 2021 -- obviously they have already sun-set my banking feeds.

Thanks -C

On 14/09/2024 at 19:30, King_Poop_Scoop said:

I downloaded CSVtoIIF451Latest.exe.

I imported my bank's .csv file no problem. (Transactions from January 1 2024 through today.)

Then I exported (printed) a tab delimited file using an earlier month from the same account. (QBD Premier manufacturing and Wholesale Edition 2021)

I used "Create/Edit Rules" and imported the tab delimited file and I created the .json file no problem.

Then I did some manual editing of transactions within the main app.

Exported the .iif

Imported to QB and only 9 transactions succeeded with over 100 failed.

So I thought, OK, let's skip the manual editing part and start over. Maybe I am doing something wrong.

This time I exported a tab delimited file using all of 2023. I then went through and cleaned that up only keeping stuff that had value, removing the # on each rule, etc.

This all seemed to work, so I exported the .iif file.

Imported the .iif to QB and BAM, QB was gone. It just crashed and went a way.

Tried it again and same thing. Needless to say, nothing was imported. I am at a stand still. 

I should mention, I firewalled QB so that it cannot communicate with the Internet. I am trying to freeze at 2021 -- obviously they have already sun-set my banking feeds.

Thanks -C

Sent you a message

On 24/10/2024 at 15:07, Dangit said:

I do a lot of buying using my credit card from new vendors each month.  Would it be possible to create an export of the new vendors so I can upload them to QuickBooks.

Actually when importing the iif into quickbooks, you can select this "I'll do it later option"

image.png.96140ae287dc5f39bffa3921361f8b19.png

This is the pre 2019 option which will automatically add the venders in.

Just make sure you backup your company file first.

  • 2 weeks later...

Hi there,

I last used this tool in early September. Today when I went in to do things the way I did last time, I get a message that my rules file is incompatible. I haven't done anything to it, it just says it's not compatible. I downloaded the newest version of the software and same problem. I had invested quite a lot of time adding things to my rules file so I am not sure what happened. It looks like I'm going to have to download the newest version and just start from scratch. I already did this as a test, and it does look like the way the rules are laid out in the text file is completely different than before. If you have any tips, I'd love to hear them.


Thanks!

Hi,

I think I misspoke - the .json file that is coming up as incompatible is apparently an automatch file. When I use the new beta version for testing, I see that a rules file is created as well as an automatch file. From what I can vaguely remember, I only had one json file in that directory before, hence my confusion as to why it is no longer compatible.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.