Generic Import Transaction Matcher empty - revisited

James Roman digitect at comcast.net
Mon Nov 21 18:16:12 EST 2005


I think that mine is a little bit more difficult to fix. The date
identifier worked for the initial import, but none after. I did an
export from another bank account for my business. After viewing the 2nd
bank export, it became clear what the problem was. My 1st bank exports
do not have valid <FITID> entries. These look like they should be unique
numbers (and fairly long at that). In the export files that I have, the
numbers correspond to the number of transactions in the export file
(I.E. transaction 1 has FITID=1, etc.)

Since I don't expect my bank to fix this problem soon, I'll have to come
up with an way of modifying these numbers to make them unique. Ideally,
I should probably come up with a way that if I exported overlapping date
ranges, it would identify them as the same transaction. Anyone have any
suggestions how I might accomplish this? 

On Sun, 2005-11-20 at 23:50 -0800, Brian Dolbec wrote:

> 
> I remember that someone else had problems importing stuff.  It turned
> out the date identifier did not match a gnucash known type.  It
> prevented everything from working to find matches.  Check the import
> file in an editor to see if it looks alright.  Check the archives for
> the thread if that might be your problem as well.  I believe he did a
> search & replace on the identifier for it to work.
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.gnucash.org/pipermail/gnucash-user/attachments/20051121/bab28b07/attachment.bin


More information about the gnucash-user mailing list