Re: QFX Import and Reconciled Transactions

On Fri, 16 Feb 2018 11:07:05 + (UTC) "David T. via gnucash-user" wrote: > RW, > The QFX specification includes an ID field against which gnucash > matches. If subsequent imports keep trying to match existing > transactions, it may be that your bank is reusing the

Re: QFX Import and Reconciled Transactions

RW, The QFX specification includes an ID field against which gnucash matches. If subsequent imports keep trying to match existing transactions, it may be that your bank is reusing the IDs. This has been seen before.  David On Fri, Feb 16, 2018 at 14:59, R

Re: QFX Import and Reconciled Transactions

David, Thanks for the information. I guess what I was hoping was that there might be something that could be done to tweak the matching process (on the part of the user), to make transactions that are reconciled, with a "Y" in the R column, off limits to future matching (and possible updates

Re: QFX Import and Reconciled Transactions

Hi David, Agreed that the process of importing of transactions to an account is a separate and distinct process from that of reconciliation with an external statement. Given that however, the import process, if it matches an existing transaction in your accounts will classify a transaction as

Re: QFX Import and Reconciled Transactions

Please do not confuse importing transactions with reconciliation. While you must develop a procedure that is efficient, the OFX import is very error prone and needs to be checked against another reference. David C On Feb 15, 2018 6:16 PM, "DaveC49" wrote: > Any

Re: QFX Import and Reconciled Transactions

Any matching procedure on an import is not going to be perfect. Make the criteria too tight and almost nothing is matched. Too loose and everything is matched, so it is always a compromise. I have found the order in which I process the OFX imports from my various accounts can have some impact on