Can hledger import use account mappings from previous transactions?

Is there any way to have hledger use account mappings from previous transactions when calling hledger import?

For example, say I import an expense with description "Foo" and I manually set account2 for that expense to expenses:shopping. With regular ledger, if I import another transaction with description "Foo" later on, ledger will automatically set account2 to expenses:shopping because it matches an existing transaction.

Is there anyway to get this behavior in hledger?

Right now I've been adding all the mappings to a CSV rules document, but writing an explicit rule for every single description/payee in my journal feels overkill. In a perfect world hledger would use my CSV rules files first, and then fall back to existing entries if no rule is found.

submitted by /u/-cvdub-
[link] [comments]
This is a companion discussion topic for the original entry at