paypal credit card charges duplicated

On QM2020 I have Paypal set up as an online account. Pulls all data from Paypal just fine.
I have Paypal set up to charge my MasterCard for online payments. This is convenient on sites where I don't want to create an account. On eBay I accept Paypal, and this activity is mostly what I want to track in Quicken.
Here's the problem. These charges come through once on my MasterCard (via Paypal) and a second time on Paypal.
I can manually delete Paypal charges that are handed off to MasterCard, but this is laborious.
Any suggestions? I can't find anything useful at Paypal.

Best Answer

Answers

  • Northbynortheast
    Northbynortheast Member ✭✭
    Thanks for your thoughts. Either solution will work. The challenge is doing it automatically. With one entry in MasterCard, you have to manually find and delete all the credit card payments in PayPal. With two, you have to manually enter the credit from MasterCard to PayPal (since PayPal doesn't include these in its statements or online updates) and change the MasterCard entry from a charge to a transfer. Whew! PayPal does not make it easy!!
  • torylynn
    torylynn Member
    This duplication scenario has always been a drawback for me. Sometimes I accept payment via PayPal and then spend right from the PayPal balance. So, I do want to connect and track my PayPal account.

    It makes more sense to track the credit card related spending within the connected credit card account.

    Knowing that a lot of people are dissatisfied with the duplication scenario that has been going for years, why not code in an option to ignore any transactions except for those with "PayPal Balance" in PayPal's "Paid With" column.

    I believe the PayPal API actually even offers a GUID for transaction type. It's such a minor change request to satisfy an exception that annoys a lot of clients.

    "Forget YNAB.. I can track EVERYTHING in Quicken! Even PayPal.. but ARGH I have to deal with this duplication scenario they could fix with a couple lines of code..." ;)
    i
This discussion has been closed.