in quicken simplifi PayPal (Personal) is only showing "debit card transaction" where the payee should be. (Paypal Business works fine). how do i get the payee to show?
Hello @Kuhzah,
Thanks for reaching out! Payee information is usually sent to us by the financial institution. If it is showing up as "debit card transaction", that may be what is being sent when downloading transactions. You can create a transaction rule that changes the payee from "debit card transaction" to whatever you need it to be, however.
Here is how you can create a transaction rule in Quicken Simplifi: https://support.simplifi.quicken.com/en/articles/4792733-how-to-use-transaction-rules-in-the-web-app#h_22b9a65773
I hope this helps!
I also recently started syncing my PayPal account info into Simplify and have this same issue. On the PayPal website, the transactions have the correct payee info, but when they get imported to Simplify they all have a generic "debit card transaction" (and all associated with Unknown category). This makes using Simplify with PayPal pretty much useless. The suggestion to create a rule is bogus. - There's no way to determine the Payee via rules and I'm not going to manually update every transaction. There is nothing we as users can do to fix this. Does Simplifi not strive to work with it's business partners to improve the customer experience? I already know the answer. Here's a better answer: [removed - speculation]
But they won't. Ask me how long their integration with CoinBase has been broken. š
Interesting observation: When adding an account and you search for paypal, there are 2 choices that show up: 1) PayPal 2) PayPal Credit, MasterCard and Crypto
I tried both and here's what I saw: With (#1) debit card transactions all have payee listed as "debit card transaction" as noted above. Regular PayPal transactions (via web) show the correct payee. How it looks in Simplifi:
How it looks in PayPal:
With (#2) debit transactions are duplicated- one with the correct payee and the other not, and web transactions are also duplicated with one listed as a (+) income amount (which is incorrect). Also, the account balance is not coming across. (says $0.00 which is incorrect). How it looks in Simplifi:
Between the two, I'm not sure which is worse. #2 seems closer to usable if they could fix the duplicate Tx issues.
Hello @RobBBB,
Thank you for the reply. Regarding PayPal in Quicken Simplifi, we will want to make sure that we focus on whichever instance is correct for your account type, based on the information in our support article here: https://support.simplifi.quicken.com/en/articles/6997452-new-and-improved-way-to-connect-to-your-financial-institution-oauth-api#h_f8d2a07731
If you are inquiring about debit card transactions, then you most likely have a Checking account, and will need to use the "PayPal" instance in that case.
As for the issue you brought up regarding the "Debitcard Transaction" Payee showing for certain transactions, based on your screenshots, it appears that this may be because PayPal is sending this information this way based on the type of purchase. If you open the Transaction detail window for one of these transactions, can you verify what the "Appears on your statement as.." information shows? Let us know!
Ok, thanks Jon. FWIW I am only using the "new" PayPal OAuth connection type. (I only tried the other out of curiosity). It's the debit card transactions that are not coming across with the correct payee. One bit of confusion is nowhere does PayPal ever refer to this as a "Checking" account. It's just a paypal account. Whatever kind of weird voodoo they do on the backend to allow you to also have a Debit MasterCard attached to the account is transparent to the user, but clearly the debit transactions are somehow "different" than regular PayPal transactions. (Notice the icons are different?) Anywayā¦ Here is a screenshot of the transaction detail window for one:
As shown in the previous screenshots, the correct payee is shown on the PayPal side (and strangely enough comes across correctly with the old connection type but duplicated). I think I illustrated the issue pretty clearly. I understand you are saying this might be what PayPal is sending you but it's clearly wrong, and makes using Simplifi with PayPal frustratingly pointless. This is un-usable:
I would hope that the tech team at Quicken has some sort of technical inroads at PayPal and could work together with them to solve this problem.
Thank you for the reply. After checking with my team, it looks like the "Appears on your statement as" info is provided directly by the financial institutions for Quicken Simplifi.
Quicken Simplifi uses the āAppears on your statement asā information exactly as itās provided by your financial institution. This is what we rely on to display and help identify the payee. If certain details arenāt included in that data, we donāt have a way to retrieve or add them on our end. If the information shown in Quicken Simplifi doesnāt match what you see on your bank or card statement, that difference would need to be reviewed by the financial institution, since they control the data thatās shared.
In this case, I would have you contact PayPal Support, since this is the information being sent over. Please let us know how things go!
> ā¦ I would have you contact PayPal Supportā¦let us know how things go! Tell me you've never contacted PayPal Support without telling me you've never contacted PayPal supportā¦ š¤£ I hear what you're saying but you also are overlooking the fact that the correct transaction details DO come across correctly on the OLD integration point (but it has other issues). So, clearly they are sending it in that case. But alas, I will chalk this one up to just another broken integration that'll likely never get fixed. šŖ
ā¦and not to be a jerk or anything, but a certain "unnamed competitor" of yours [removed] works fine with PayPal:
ā¦ just sayin'
Thank you for the feedback. I can certainly understand the frustration here. If you are not able to get anywhere with PayPal support, and if you can get a ticket number from their side, this could help us move things along on our end. Let us know!
@RobBBB
Take this with a grain of salt because it's not my field, but sometimes the data a financial program (Simplifi) shows depends on which aggregator API property it (Simplifi) decides to use to access the payee info. The other program you mentioned may be getting better information because it is using a different API property (or a different aggregator altogether).
I don't know what aggregator Simplifi uses to access PayPal transaction data. But for some of them there are multiple properties on the transaction object that represent the payee (or merchant) in different ways.
For example, on the Plaid transaction object there are these:
name
merchant_name
original_description
In other words, it could be a PayPal problem but it could also just be a less-than-optimal API selection by Simplifi.
