How To Do My Own Transaction Matching

[Michael Iles]

That's a good question. I've always discounted scheduled transactions
as not useful (in Quicken, GnuCash) but I'm willing to reconsider. My
reasons are:

1. Doesn't seem flexible enough. I don't usually know the exact date
that a transaction will happen on, e.g. an insurance payment comes out
once per month... is it always on the same day? I'm not sure. I often
don't know the amount either, e.g. for a payment on a line of credit:
the amount depends on the balance of the line of credit. Or I have
transactions that aren't scheduled but I still want to match, e.g. I
visit the grocery store once or twice a week and I want to
automatically match those against my grocery account in GnuCash, but I
don't know the date or the amount in advance.

2. Seems like it's the wrong way around. I would rather spend my time
categorizing existing transactions rather than proactively making
rules for future transactions. I don't want to spend time trying to
discern the rules the bank is following for their automatic payments,
e.g. same date every month, or every 14 days, or first business day
after a certain date, or whatever.

Just my thoughts.

Mike

On 11 December 2013 15:48, Tommy Trussell <tommy.trussell at gmail.com> wrote:
> On Mon, Dec 9, 2013 at 2:04 PM, Michael Iles <michael.iles at gmail.com> wrote:
>>
>> I would like to be able to do my own transaction matching and I'm
>> looking for advice on the easiest way to do it.
>>
>> (I find that with the built-in Bayesian matching I still have to
>> inspect every match, many matches aren't automatically made, sometimes
>> the matching history gets lost and I have to start over, etc.)
>>
>> My goal is to automate all of the regular transactions that happen in
>> my account, using heuristics like: (1) if a transaction labeled
>> 'insurance' is in one range then it's my car insurance, if it's in a
>> different range then it's home insurance; (2) utility bills usually
>> have extra numbers so I would look for substrings to match them; etc.
>>
>> (Aside: in my opinion, the perfect system for GnuCash would be the
>> ability to provide a list of regular expressions, along with the
>> destination account to use if the regex matches.)
>>
>
> I see that you have started some excellent and detailed discussion about the
> QIF and/or OFX importers and the Python, Guile and C bindings. However I
> would like to go back to your original statement and throw out one more
> observation --
>
> If your goal is to "automate regular transactions," why not use the
> Scheduled Transactions feature?
>
> It seems like you could have GnuCash automatically create ALL automatic
> regular transactions. (For example insurance, levelized utilities, and
> recurring service charges are three that tend to be very predictable.) Then
> if you choose to import OFX or QIF transactions from the bank, you would
> need only to ensure the automatic transactions match imported ones correctly
> to avoid duplicates.
>
>
>>
>> -----
>>
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
>
>