Re: [GNC] gnucash-user Digest, Vol 193, Issue 42 - re: QFX Import Matching

classic Classic list List threaded Threaded
6 messages Options
kvn
Reply | Threaded
Open this post in threaded view
|

Re: [GNC] gnucash-user Digest, Vol 193, Issue 42 - re: QFX Import Matching

kvn
Sorry if this is not the correct way to respond.  New to GnuCash mail
list and I get the digest, not individual topics.

QFX Importing has never worked properly for me either, from the time I
started using GnuCash 5 or 6 years ago, maybe more.  The importer skips
common entries constantly, not always the same vendor, so it will enter
some but skip others.  Not the same amount either, just certain random
transactions. I don't reconcile for months at a time and when I do I
have to manually enter anywhere from 10% to 50% of my transactions.

I download the transactions from my bank, import the QFX file, go to
reconcile and then have to find all the missing transactions. This is
especially difficult with my Debit card, which I use for all my daily
and personal transactions.

Bayesian is on and the thresholds are low.  The transactions are in the
bank's QFX file. GnuCash version 2.6.12 on Linux 16.04, but also on
previous Linux releases and GC versions.

Thanks for any insight



On 4/11/19 10:56 AM, [hidden email] wrote:

> Send gnucash-user mailing list submissions to
> [hidden email]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> or, via email, send a message with subject or body 'help' to
> [hidden email]
>
> You can reach the person managing the list at
> [hidden email]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gnucash-user digest..."
>
>
> Today's Topics:
>
>     1. Re:  QFX import matching (Derek Atkins)
>     2. Re:  Gnucash Price updating (David T.)
>     3. Re:  Downgrading to 2.6.21 (Greg Feneis)
>     4. Re:  Downgrading to 2.6.21 (Colin Law)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 11 Apr 2019 11:16:00 -0400
> From: Derek Atkins <[hidden email]>
> To: Keith Bellairs <[hidden email]>
> Cc: gnucash-user email group <[hidden email]>
> Subject: Re: [GNC] QFX import matching
> Message-ID: <[hidden email]>
> Content-Type: text/plain
>
> Hi,
>
> Keith Bellairs <[hidden email]> writes:
>
>> Thanks for the hint, David. But its more broken than that. Many/most of my
>> imports match correctly. The groceries one has been manually assigned
>> dozens or hundreds of times and the match algo always fails. Do any of the
>> parameters in the preferences make a difference?
>>
>> The memo field in the imported qfx file is kind of long for this company:
>> BUFFALO M BUFF HARDWICK VT POS PURCHASE/PIN DDA 098894
>> and it is always the same. It has a special character in it. Somehow it
>> baffles the import matcher.
>>
>> Sorry, I forgot the basic info, but the matcher has failed this way for
>> (probably) years:
>> Gnucash 3.4
>> MacOS 10.14.3
> Are you sure you have Bayesian Matching turned on in your preferences?
>
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
> -derek
>

_______________________________________________
gnucash-user mailing list
[hidden email]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

Re: [GNC] QFX Import Matching

Adrien Monteleone-2
The only change to how you replied I’d offer:

Instead of appending the actual subject to the Digest subject is to copy-paste over it, thus the subject reads as if you had not used digest mode at all.


Regards,
Adrien

> On Apr 11, 2019, at 12:33 PM, kvn <[hidden email]> wrote:
>
> Sorry if this is not the correct way to respond.  New to GnuCash mail list and I get the digest, not individual topics.
>


_______________________________________________
gnucash-user mailing list
[hidden email]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

Re: [GNC] gnucash-user Digest, Vol 193, Issue 42 - re: QFX Import Matching

David Cousens
In reply to this post by kvn
The OFX importing is working fine for me /My baks exports in OFX format. QFX
is just a proprietary version of OFX used by Intuit so there should be no
basic problems. Some banks do not correctly implement the OFX format but as
you can import some transaction that might not be the problem. I think
GnuCash will spit the dummy if it doesn't parse the import format correctly.

The next source of problems can be the import matching. In some cases the
Import matcher will identify a new transaction with an existing transaction
and will as a result not import it. This can be becasue the importer has to
allow a date range within which to match as well as matching on other
information. Other sources of problems can be an incorrect date format
selected for import but this would normally reject all transactions.

The import matcher also has problems matching importing data which has a
numerical or transaction ID in the description which changes with each
transaction imported. This tends to override other data which matches.

The first step is to determine which transactions are not being imported. If
all the transactions to be imported are appearing in the import matcher
window, then the file is parsing and correctly importing the data.

If the A (Add) column is checked then the matcher has identified the
transaction as a new transaction to add. If the background of the line for
the transaction is yellow, then the matcher is unable to assign an account
for the second split (transfer account) and you will have to assign an
account manually by double clicking on the transaction line and assigning an
appropriate account in the dialog which comes up. The background will then
turn green. If you import without assigning an account the Imbalance account
will be assigned as a transfer account to indicate that no transfer account
was assigned. Any transactions with splits to the Imbalance account indicate
a problem with the transaction which needs to be corrected

If the background was initially green, then the matcher has assigned the
transfer account on the basis of previously imported data. Check the
assigned transfer account is the one you want to assign to that transaction.

If the matcher matches a transaction to an existing transaction if it is an
exact match the transaction line background will be read and the checkbox in
the A column and U+R column will be unchecked and the R column will be
checked and the transaction will not be imported. If you do not think this
is correct, uncheck the R column, and check the A column and select an
appropriate transfer account and check it is correct as before.

 If the match is close enough but not exact then the U+R column will be
checked and the background will again be red. In this case the transaction
will be updated with the information that is different between the importd
and matching transaction. Again this can be overridden by unchecking the U+R
checkbox and selecting the A checkbox and setting an appropriate trasnfer
account if you believe the matcher decision is wrong.

Once all backgrounds are green (or red for lines not to be imported) you can
click OK to complete the import.



If you don't reach the above stages it is likely a problem with the file
format. If you can identify a specific transaction that isn't imported, then
locate and examine a record for a transaction of that type. You can
edit/examine the QFX file with any text editor. The OFX format specification
is described in a pdf which can be downloaded from
http://www.ofx.net/downloads.html.

If you find your bank has not correctly implemented the OFX/QFX standard,
then you can contact the bank, report the error to them and request they fix
it.  If you cannot find a problem with their implementation  then come back
for more help  perhaps with examples of the  data that is not importing
correctly.

David Cousens



-----
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
_______________________________________________
gnucash-user mailing list
[hidden email]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
David Cousens
Reply | Threaded
Open this post in threaded view
|

Re: [GNC] gnucash-user Digest, Vol 193, Issue 42 - re: QFX Import Matching

Andres Aviles
   David -

   Thanks for the info.  The issue is not with the import of data from my
   credit union. The fees are deducted from the amount that I collect
   before Square deposits the money in my account. The amount that Square
   deposited is importing fine but the fees are never deposited so they
   don't show up. I know what the fees are from my statement from Square.

   So what is the best way to manually enter and account for the Square
   fees for their service ?

   Thanks.

   Andy A.
   [hidden email]
   "Try to be a rainbow in someone's cloud" Maya Angelou
   Words to live by -
   * Love has no gender, love has no race, love has no disability and love
   has no age
   * Forget the bad, and focus on the good.
   * Love the people who treat you right, pray for the ones who don't.
   * Life is too short to be anything but happy.
   * Falling down is a part of life. Getting back up is living.
   * Forget yesterday - it has already forgotten you.
   * Don't sweat tomorrow - you h


   Sent: Friday, April 12, 2019 at 2:49 AM
   From: "David Cousens" <[hidden email]>
   To: [hidden email]
   Subject: Re: [GNC] gnucash-user Digest, Vol 193, Issue 42 - re: QFX
   Import Matching
   The OFX importing is working fine for me /My baks exports in OFX
   format. QFX
   is just a proprietary version of OFX used by Intuit so there should be
   no
   basic problems. Some banks do not correctly implement the OFX format
   but as
   you can import some transaction that might not be the problem. I think
   GnuCash will spit the dummy if it doesn't parse the import format
   correctly.
   The next source of problems can be the import matching. In some cases
   the
   Import matcher will identify a new transaction with an existing
   transaction
   and will as a result not import it. This can be becasue the importer
   has to
   allow a date range within which to match as well as matching on other
   information. Other sources of problems can be an incorrect date format
   selected for import but this would normally reject all transactions.
   The import matcher also has problems matching importing data which has
   a
   numerical or transaction ID in the description which changes with each
   transaction imported. This tends to override other data which matches.
   The first step is to determine which transactions are not being
   imported. If
   all the transactions to be imported are appearing in the import matcher
   window, then the file is parsing and correctly importing the data.
   If the A (Add) column is checked then the matcher has identified the
   transaction as a new transaction to add. If the background of the line
   for
   the transaction is yellow, then the matcher is unable to assign an
   account
   for the second split (transfer account) and you will have to assign an
   account manually by double clicking on the transaction line and
   assigning an
   appropriate account in the dialog which comes up. The background will
   then
   turn green. If you import without assigning an account the Imbalance
   account
   will be assigned as a transfer account to indicate that no transfer
   account
   was assigned. Any transactions with splits to the Imbalance account
   indicate
   a problem with the transaction which needs to be corrected
   If the background was initially green, then the matcher has assigned
   the
   transfer account on the basis of previously imported data. Check the
   assigned transfer account is the one you want to assign to that
   transaction.
   If the matcher matches a transaction to an existing transaction if it
   is an
   exact match the transaction line background will be read and the
   checkbox in
   the A column and U+R column will be unchecked and the R column will be
   checked and the transaction will not be imported. If you do not think
   this
   is correct, uncheck the R column, and check the A column and select an
   appropriate transfer account and check it is correct as before.
   If the match is close enough but not exact then the U+R column will be
   checked and the background will again be red. In this case the
   transaction
   will be updated with the information that is different between the
   importd
   and matching transaction. Again this can be overridden by unchecking
   the U+R
   checkbox and selecting the A checkbox and setting an appropriate
   trasnfer
   account if you believe the matcher decision is wrong.
   Once all backgrounds are green (or red for lines not to be imported)
   you can
   click OK to complete the import.
   If you don't reach the above stages it is likely a problem with the
   file
   format. If you can identify a specific transaction that isn't imported,
   then
   locate and examine a record for a transaction of that type. You can
   edit/examine the QFX file with any text editor. The OFX format
   specification
   is described in a pdf which can be downloaded from
   [1]http://www.ofx.net/downloads.html.
   If you find your bank has not correctly implemented the OFX/QFX
   standard,
   then you can contact the bank, report the error to them and request
   they fix
   it. If you cannot find a problem with their implementation then come
   back
   for more help perhaps with examples of the data that is not importing
   correctly.
   David Cousens
   -----
   David Cousens
   --
   Sent from:
   [2]http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
   _______________________________________________
   gnucash-user mailing list
   [hidden email]
   To update your subscription preferences or to unsubscribe:
   [3]https://lists.gnucash.org/mailman/listinfo/gnucash-user
   If you are using Nabble or Gmane, please see
   [4]https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
   -----
   Please remember to CC this list on all your replies.
   You can do this by using Reply-To-List or Reply-All.

References

   1. http://www.ofx.net/downloads.html
   2. http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
   3. https://lists.gnucash.org/mailman/listinfo/gnucash-user
   4. https://wiki.gnucash.org/wiki/Mailing_Lists
_______________________________________________
gnucash-user mailing list
[hidden email]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

Re: [GNC] gnucash-user Digest, Vol 193, Issue 42 - re: QFX Import Matching

Adrien Monteleone-2
This thread is an excellent example as to:

A) What happens when people do not correctly respond to digest messages
B) Why no matter what, digests are a really bad idea

It appears (from my perspective) that you, Andy, are replying to David who is replying to someone other than you. (David is old hat here, so I’m sure it is not his reply workflow creating the confusion)

Conversations can get quite confusing in such a situation.

Is his response to your exact issue or someone else’s?

Regardless of that, I just sent a response on your other thread that was specific to the question of how to handle processor fees. Since you started that specific topic, perhaps it is best to shift all such discussion there.

Regards,
Adrien

> On Apr 12, 2019, at 2:03 AM, Andres Aviles <[hidden email]> wrote:
>
>   David -
>
>   Thanks for the info.  The issue is not with the import of data from my
>   credit union. The fees are deducted from the amount that I collect
>   before Square deposits the money in my account. The amount that Square
>   deposited is importing fine but the fees are never deposited so they
>   don't show up. I know what the fees are from my statement from Square.
>
>   So what is the best way to manually enter and account for the Square
>   fees for their service ?
>
>   Thanks.
>
>   Andy A.
>   [hidden email]
>   "Try to be a rainbow in someone's cloud" Maya Angelou
>   Words to live by -
>   * Love has no gender, love has no race, love has no disability and love
>   has no age
>   * Forget the bad, and focus on the good.
>   * Love the people who treat you right, pray for the ones who don't.
>   * Life is too short to be anything but happy.
>   * Falling down is a part of life. Getting back up is living.
>   * Forget yesterday - it has already forgotten you.
>   * Don't sweat tomorrow - you h
>
>
>   Sent: Friday, April 12, 2019 at 2:49 AM
>   From: "David Cousens" <[hidden email]>
>   To: [hidden email]
>   Subject: Re: [GNC] gnucash-user Digest, Vol 193, Issue 42 - re: QFX
>   Import Matching
>   The OFX importing is working fine for me /My baks exports in OFX
>   format. QFX
>   is just a proprietary version of OFX used by Intuit so there should be
>   no
>   basic problems. Some banks do not correctly implement the OFX format
>   but as
>   you can import some transaction that might not be the problem. I think
>   GnuCash will spit the dummy if it doesn't parse the import format
>   correctly.
>   The next source of problems can be the import matching. In some cases
>   the
>   Import matcher will identify a new transaction with an existing
>   transaction
>   and will as a result not import it. This can be becasue the importer
>   has to
>   allow a date range within which to match as well as matching on other
>   information. Other sources of problems can be an incorrect date format
>   selected for import but this would normally reject all transactions.
>   The import matcher also has problems matching importing data which has
>   a
>   numerical or transaction ID in the description which changes with each
>   transaction imported. This tends to override other data which matches.
>   The first step is to determine which transactions are not being
>   imported. If
>   all the transactions to be imported are appearing in the import matcher
>   window, then the file is parsing and correctly importing the data.
>   If the A (Add) column is checked then the matcher has identified the
>   transaction as a new transaction to add. If the background of the line
>   for
>   the transaction is yellow, then the matcher is unable to assign an
>   account
>   for the second split (transfer account) and you will have to assign an
>   account manually by double clicking on the transaction line and
>   assigning an
>   appropriate account in the dialog which comes up. The background will
>   then
>   turn green. If you import without assigning an account the Imbalance
>   account
>   will be assigned as a transfer account to indicate that no transfer
>   account
>   was assigned. Any transactions with splits to the Imbalance account
>   indicate
>   a problem with the transaction which needs to be corrected
>   If the background was initially green, then the matcher has assigned
>   the
>   transfer account on the basis of previously imported data. Check the
>   assigned transfer account is the one you want to assign to that
>   transaction.
>   If the matcher matches a transaction to an existing transaction if it
>   is an
>   exact match the transaction line background will be read and the
>   checkbox in
>   the A column and U+R column will be unchecked and the R column will be
>   checked and the transaction will not be imported. If you do not think
>   this
>   is correct, uncheck the R column, and check the A column and select an
>   appropriate transfer account and check it is correct as before.
>   If the match is close enough but not exact then the U+R column will be
>   checked and the background will again be red. In this case the
>   transaction
>   will be updated with the information that is different between the
>   importd
>   and matching transaction. Again this can be overridden by unchecking
>   the U+R
>   checkbox and selecting the A checkbox and setting an appropriate
>   trasnfer
>   account if you believe the matcher decision is wrong.
>   Once all backgrounds are green (or red for lines not to be imported)
>   you can
>   click OK to complete the import.
>   If you don't reach the above stages it is likely a problem with the
>   file
>   format. If you can identify a specific transaction that isn't imported,
>   then
>   locate and examine a record for a transaction of that type. You can
>   edit/examine the QFX file with any text editor. The OFX format
>   specification
>   is described in a pdf which can be downloaded from
>   [1]http://www.ofx.net/downloads.html.
>   If you find your bank has not correctly implemented the OFX/QFX
>   standard,
>   then you can contact the bank, report the error to them and request
>   they fix
>   it. If you cannot find a problem with their implementation then come
>   back
>   for more help perhaps with examples of the data that is not importing
>   correctly.
>   David Cousens
>   -----
>   David Cousens
>   --
>   Sent from:
>   [2]http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
>   _______________________________________________
>   gnucash-user mailing list
>   [hidden email]
>   To update your subscription preferences or to unsubscribe:
>   [3]https://lists.gnucash.org/mailman/listinfo/gnucash-user
>   If you are using Nabble or Gmane, please see
>   [4]https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
>   -----
>   Please remember to CC this list on all your replies.
>   You can do this by using Reply-To-List or Reply-All.
>
> References
>
>   1. http://www.ofx.net/downloads.html
>   2. http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
>   3. https://lists.gnucash.org/mailman/listinfo/gnucash-user
>   4. https://wiki.gnucash.org/wiki/Mailing_Lists
> _______________________________________________
> gnucash-user mailing list
> [hidden email]
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>


_______________________________________________
gnucash-user mailing list
[hidden email]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

Re: [GNC] gnucash-user Digest, Vol 193, Issue 42 - re: QFX Import Matching

David Cousens
In reply to this post by David Cousens
reply to wrong post



-----
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
_______________________________________________
gnucash-user mailing list
[hidden email]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
David Cousens