Intelligent import autofill

There's a problem with the way I planned this. Smart replace should also cover account transfers, which rules out the edit-in-import-table concept. I haven't thought this through yet, but the first idea to come to mind would be to remember values at import for each imported transaction, so that we can identify them later and make correct replacements.

A request for this on GS

Import rules would be very nice. I import all using CSV files, and most of the transactions are recurrent (groceries at the same store once a week for example), it would be nice to be able to automatically set the "To" here. It would be also nice to be able to set "From" and "Payee". The rules could be based on the "description", "payee", "to" and "from" field.

Smart replace should also cover account transfers ... the first idea to come to mind would be to remember values at import for each imported transaction, so that we can identify them later and make correct replacements.

The CSV lists from my bank actually show a unique transaction ID.
I tried feeding that column both to "Tansaction ID" and to "Check #".
However, moneyGuru does not recognize transfers from my checkings account to my savings account as one single transfer. I end up with two disjunct transfers: one is going from my checkings account and the other is coming into my savings account.

If this the feature you're contemplating, you could:

• Add import support for a transaction identifier ("Tansaction ID" is there allready but what it is used for, actually?)

• Simply check for unassigned transactions with same date and same amount on existing assets/liabilities during the import run, and (propose to) merge those transactions

I guess such a simple check does the trick for a personal finance app.
Your typical user would import transfers for two or three bank accounts only.
Identifying transactions between those boils down to matching up the unassigned, no?

Regexp replace for transfer targets would be just awesome. Ideally it would predict my success rate by telling me how many previously assigned transfers to my "groceries" account match the super fancy expression I am typing (and my failure rate, the matches with transfers assigned to other accounts).

Really like your work. Keep it up!

The transaction ID is used for automatically "binding" transactions to existing ones during imports. This feature comes from OFX import where it's not possible to have the same transaction ID from two different accounts. I agree that in the case of CSV imports, it could also be used to connect transfer accounts. However, I'm afraid this new feature could bring all sorts of new complications. I'd have to think about it. Meanwhile, I created #233 Use transaction IDs to bind imported entries to existing transactions from ot... for this feature.