Hi All,

I was wondering if its possible to control which fields are imported into where/duplicated fields.
I have a number of different institutions that I download data from, and they all offer some form of QIF or OFX.
The problem I face is that Skrooge sometimes imports the transaction description as a payee, sometimes as a comment.
This becomes difficult for using search and replace rules to categorise as its unsure which field to use. It also means a lot of transactions without payees.

If the transaction description is imported as the payee I can simply use a search and replace rule to duplicate this into the comment, if needed.
If the description is imported in the comment, Skrooge does not allow a search and replace to set the payee to another field in the transaction, only to fixed text or one of the known payees.

Does anyone know any way to get around this?

Thanks in advance,
Chris

Hi Chris,

I checked the implementation of both OFX and QIF import and I can tell you that:
1-QIF import imports the payee (letter P in QIF file) correctly.
2-OFX import imports the payee correctly too.

After, it's possible that OFX and/or QIF files are not correctly generated by your bank.

You can use the "Search & Process" module to transfer one attribute in an other one.

Hi Smankowski,

Thanks again for the quick replies!
Hmm, yeah, i'm pretty sure it's my banks implementing their OFX/QIF incorrectly.

The main problem I've had with the approach you've described is that I can't set the payee to another field value, it only allows a static text value in the search and replace field replace with field.

ie, I can't tell the search and replace to copy the comment field to the payee field as the payee field in the search and replace only accepts fixed text...

thanks,
Chris

Hi,

If I remember well (I will check this evening at home), since version 1.7.0, the "search & process" function is able to set the payee with the comment value.

Do you use the 1.7.0 version ?

UPDATE: I confirm, since 1.7.0 you can update the payee with the comment content.