QIF import question

First of all, thanks for creating Manager. It looks like a great program. I’m testing it right now and am trying to figure out importing bank statements.

I can get a CSV from the bank which I can convert to QIF without too much difficulty.

First attempt: It worked and I thought all was well, but then I realized I forgot to remove commas from the bank’s Description field, so the exported CSV didn’t convert cleanly to QIF. (The spreadsheet app figures out which commas are delimiters and which are plain punctuation). As a result some original import file entries (here supposing there was a comma after “Jones”) look like this (malformed example, substituting fake info):

D7/21/2024
T M.D. JPM99ao5khud"
P"Zelle payment to Dr. Bill Jones
M-$30.00
N$42556.34
^

… when they should look like (corrected example):

D7/21/2024
T-$30.00
PZelle payment to Dr. Bill Jones MD JPM99ao5khud
MCHASE_TO_PARTNERFI
^

In Manager’s Payments, this entry should appear in the table like:
Date | Paid from | Description | Payee | Amount
2024-07-21 | Chase 5555 | Zelle payment to Dr. Bill Jones MD JPM99ao5khud CHASE_TO_PARTNERFI | | $ 30.00

(Manager combines [P]ayee and [M]emo fields into its Description field, and leaves its own Payee field blank. This is ok for my purposes.)

The malformed entries cannot be found via a search.

Second attempt: I culled all the entries with commas in their Description into its own spreadsheet, cleaned them up, export to CSV and convert to QIF. All the entries look correct now.

On import I’m told there are 11 duplicate entries. The number of Receipts and Payments from the first import plus the number of records in the second import is the same as the total number of entries in the original spreadsheet. So why/how are 11 (considered) duplicate? I look through the spreadsheet that produced this second import and try to find an obvious 11. I have groups of 12s and 13s, but no 11s.

I don’t finish the import just yet (thank you for the preview step!).

I take about 13 entries from the second import file and make it its own file. The import process tells me there is one duplicate. I narrow it down to a certain transaction. Only this transaction triggers the duplicate detector. The other entries are clean.

Go back to the second import file and pull out all the entries like the one that got flagged and test just those. Now I have found eight of 11 entries that are flagged as duplicate. Progress!

Then on an file of 12 of these entries, there is one duplicate. Split the file in two. The first half has one duplicate. I check the second half and it has… also one duplicate. I check the original file again and it has… only one duplicate. Are there two duplicates or one?

I go back to the first spreadsheet and clean everything up from the start: removing commas, extra spaces and periods for good measure (Manager seems to remove extra spaces on import anyways which I think is great). Export to CSV, convert to QIF. Import into a test Business with test Bank Account. The correct number of records and correct total amount is shown.

I guess my question comes down to this: should I trust the first import and try to add the missing entries (about a third of the total number)? Or just delete the current Bank Account and its Receipts and Payments and start over from a clean base? Fortunately I haven’t done too much work on the first import’s entries. What really happens on the backend if you try to import a QIF with entries messed up as in my example?

Results of some further testing…

  • Into a new Business, I imported my original first import, and the second import that says there are 11 duplicates. The total of Receipts and Payments is indeed 11 short.
  • I verify all the entries in the second import are in fact in Manager. This reveals the 11 that are not!
  • I tried to import just those eleven pasted into a new QIF file. Manager still claims they are duplicates.
  • I retyped the file by hand and try that: still 11 duplicates.
  • I made a backup of the Business, converted it to text, and searched for particular unique strings (e.g. JPM99bd4j52a) that either should or should not be in the file somewhere. I can find ones that should be (spot-checked) but not a single one of the 11 that are not (though Manager somehow suspects they duplicate some entry).
  • I manually added the 11 missing entries. On search for the unique string it only finds one result. The number of entries and grand total for the Bank account is now correct.

Good news:

  • If the importer thinks an entry is invalid or a duplicate it does not import it. After trying to import only duplicates I compared that Manager backup with one pre-import and they are identical. Pretty sure the database is ok here.
  • Periods and apostrophes in the description do not seem to be invalid characters (wasn’t sure); I can find them in a text dump and search for the entries that have them.

Still wondering:

  • How does Manager determine if a new imported entry is a duplicate? :thinking:

The most basic check is if all of the following match an existing entry:

  • same account
  • same CLEARING DATE
  • same description
  • same amount

then it’s not imported.

1 Like

Thank you for the info!