Re: [GNC] CSV matching produces duplicates?

Original post about turning off Bayesian matching prompts: flywire wrote > It's not that hard to match most transactions and add accounts using a > spreadsheet or other tool leaving the rest for manual confirmation. It > would be reasonable to have a setting so they could be imported straight >

Re: [GNC] CSV matching produces duplicates?

It is true in that particular case of yours that the internal account and the name it is mapped to are the same. The difficulty is that the importer has to be able to cope with situations where "Assets:Cheque" in the external record may not necessarily be mapped onto the Assets:Cheque internal

Re: [GNC] CSV matching produces duplicates?

I can't read that file on my smartphone, but what are we supposed to do with it? Ask our bankers to change their csv format to match it? On Mon, May 17, 2021, 5:32 AM flywire wrote: > Sample account that shouldn't need manual matching: > > < >

Re: [GNC] CSV matching produces duplicates?

Sample account that shouldn't need manual matching: -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html ___ gnucash-user mailing list

Re: [GNC] CSV matching produces duplicates?

In my experience, my bank uses the word 'check' to describe every check that clears my bank account and my credit card company describes every purchase at Amazon as 'Amazon'. I could continue, but I certainly do not want all transactions with those descriptions transferring to the same respective

Re: [GNC] CSV matching produces duplicates?

For the transfer account, the second account in a transaction being imported, GnuCash does in fact work that way, i.e. it imports all transactions in which the transfer account has not been specified to an Imbalance account for the currency of the primary account in the transaction. The presence

Re: [GNC] CSV matching produces duplicates?

David, your response doesn't change: > For csv transactions GnuCash pretty well prompts with the correct account > each time, so [provide a setting] to accept all prompts. 1) From my experience it's unreasonable to assume user can assign accounts when they don't understand

Re: [GNC] CSV matching produces duplicates?

Not sure that the developers could make that suggestion work. It is much harder to find records which have been imported to the wrong account after the fact than it is to identify the correct account the first time it is imported at the time it is imported. The account names as specified in a

Re: [GNC] CSV matching produces duplicates?

Yes, this topic broke off the original thread, something to do with me replying from email. A chart of accounts imports easily, as expected with no issues or nagging. For csv transactions GnuCash pretty well prompts with the correct account each time, so set to accept all prompts. There is no

Re: [GNC] CSV matching produces duplicates?

Curious, if you fix them afterwards, outside of the matcher, how do you expect the matcher to learn what you have done? The place to correct the matcher is in the matcher. Anything outside of that, the matcher has no cognizance of. Or am I misunderstanding the request? Regards, Adrien On

Re: [GNC] CSV matching produces duplicates?

Maybe your message title is throwing us off. If you want to have Gnucash create new accounts on the fly during the import, that is almost possible except that it would create a huge mess of accounts that were not properly assigned to valid top level accounts (asset, liability, income, expense and

Re: [GNC] CSV matching produces duplicates?

> The matching of the account names... only happens... This doesn't change the suggestion of allowing the user to import the file, with accounts as coded, and fix tagged records afterwards (like any other software). To confirm "Car" account is "Car" account, wtf -- Sent from:

Re: [GNC] CSV matching produces duplicates?

The matching of the account names in the input records (whether transfer accounts or the main account for the transaction) to the GnuCash internal accounts only happens for the first time those accounts occur in an input data file. After that GnuCash remembers the assignment of external account

Re: [GNC] CSV matching produces duplicates?

Yes, there would be no matching decisions if it was coded in the input file but you won't be powering through it, GnuCash still requires user to verify each [iirc] account (which is coded in the input file). I'm suggesting user should be able to turn that checking off (since input file has been

Re: [GNC] CSV matching produces duplicates?

Are you suggesting that sometimes you don't need to make any matching decisions during the csv import process? If so, it is already fairly easy to power through the matching steps. In my case, there are nearly always many decisions to make on the 練 so that GnuCash is usually "bugging" me to

Re: [GNC] CSV matching produces duplicates?

That is a pretty reasonable summary of the position with CSV imports. The records in CSV do not contain the additional information that identifies a particular transaction uniquely that is present in the OFX file so its detection of duplicates is not as reliable as with OFX. The Bayesian

Re: [GNC] CSV matching produces duplicates?

David Cousens, As Elmar pointed out, clicking the 'A' box for an incoming transaction forces the import even if there is an existing match. That is worse than just accepting every transaction as new and going back and deleting duplicates later (this has essentially been my procedure for the

Re: [GNC] CSV matching produces duplicates?

Elmar, If a transaction has been matched and is marked to be either updated (U column checkbox selected) or cleared (C column checkbox selected), you have to deselect the selected checkboxes in the U (up[date) and C (Clear) column( previously labelled the R column in earlier GC versions) and then

Re: [GNC] CSV matching produces duplicates?

Elmar, It is possible to do some limited tuning of the matching algorithm. Edit-> Preferences->Import although the adjustment of the parameters and what their effects are is by no means intuitive or clear. The matching time window is hard coded in so I regularly get matches to regularly repeated

Re: [GNC] CSV matching produces duplicates?

Even if I know that the match exists, and I tell it that it does, it replies that the match does not exist.  So I have to either leave it red so it doesn't import, or accept the duplicate.  Which means keeping both windows open (the match window and the account window), and manually checking

Re: [GNC] CSV matching produces duplicates?

Isn't it still possible to manually override the automatic behavior on a transaction by transaction basis during the various types of imports? I know that is not wanted, but that is what we have to do to train the Bayesian matching. I am frustrated that the new matcher released in the 3.x series

Re: [GNC] CSV matching produces duplicates?

No - just taken from the bank as CSV directly.  I have another post where the OFX problem is described. On 3/3/21 5:40 PM, Christopher Lam wrote: You mean transactions imported via ofx then reimported with CSV? This may be https://bugs.gnucash.org/show_bug.cgi?id=798128 For now, it'll be

Re: [GNC] CSV matching produces duplicates?

You mean transactions imported via ofx then reimported with CSV? This may be https://bugs.gnucash.org/show_bug.cgi?id=798128 For now, it'll be best to narrow down your CSV import to exclude the already imported date range. On Thu, 4 Mar 2021, 5:59 am Elmar, wrote: > Version 4.4 from flatpak on