Generic Import Transaction Matcher empty - revisited

[Andrea Carpani]

Il giorno mar, 22-11-2005 alle 22:53 -0500, James Roman ha scritto:

> Thanks for the response. I am leaning towards using perl as well. I was
> planning on changing FITID to DTPOSTED+daily sequence number. 

The problem with daily sequence number is that you could have exported
to OFX only some transactions through a filter and calculating the value
could be difficult.

DTPOSTED form me is:

<DTPOSTED>20050913000000

and stays the same for the whole day :(

On the other hand MEMO has some uniqueness: transaction endpoint
coordinates and, sometimes, HH:MM of transaction.

> I think
> your suggestion has merit, though. I didn't like the idea of being at
> the mercy the export program with the sequence number. 

True, it doesn't sound very safe.

> I think that the
> only required fields (other than the bogus FITID) are DTPOSTED, TRNAMT
> and TRNTYPE. Using these three fields seems like it might be the most
> complete. 

With the exports I get from my bank MEMO is quite good, while TRNTYPE,
as Reiser noted, doesn't change very much.

> I'm going to think about this for a day or two. All my transactions are
> listed at the same date stamp for DTPOSTED. I want to consider some sort
> of odd situation, like whe you first sign up for automatic deposits,
> when they deposit one dollar, and then take it back immediately.
> Additionally, I wonder what would happen if I had multiple accounts with
> a bank.
> 
> Let me know how your solution comes along.

I'm using my perl script to add FITID calculated as:

$T{FITID} = md5_hex("$T{DTPOSTED}.$T{TRNAMT}.$T{MEMO}");

I still have to understand the basics of gnucash, so I still have to
know if it works well or not. At least I can import my data :)

-- 
Andrea Carpani <ml at carpani.net>