Safari paypal receipts do not propagate tags or attachments when entering via the banking transactions confirmation screen?

Hi there, @rgood@mac.com.

Thanks for reaching us here in the Community today. One way to determine a browser-related problem is to use another browser. If it works, that means you need to troubleshoot your main browser (Safari). 

To do this, you'll need to clear its cache. You'll want to follow the steps based on the Safari you've used: 

• Safari for Mac
• Safari for iPad and iPhone

If the issue persists, you can clear Intuit-specific cookies to refresh website preferences that might be causing problems when you use QuickBooks. 

Here's how: 

1. Open Safari, then select Safari beside the apple icon to the top left.
2. Select Preferences, then select Privacy, then Manage Website Data.
3. Type “Intuit” in the search bar to find Intuit cookies.
4. Select Remove All, then select Remove Now.
5. Select Done, then restart Safari for the changes to take effect.

If you're still experiencing the same issue, ensure you're using a supported, up-to-date browser.

for future reference, read these articles for more detailed information about PayPal in your QuickBooks Online account:

• Use the Connect to PayPal app
• Connect to PayPal FAQ

Visit again and leave a comment below if you need anything else. Take care!

I did try another browser, Chrome, same result.  I am using the most up to date os and safari.  Your documentation explicitly states it supports Safari.  Requiring us to test on another browser implies that you do not actually support Safari.  

This is a serious bug as it results in lost data.  If it was my job was to support users and I saw a problem replicated that lost data on a supported browser I would want to fix it, not tell the user it was their problem.

I have tested on Chrome as well.

This is a significant bug as it results in lost data.  

Safari is a supported browser for QBO, testing on other browsers should not be a requirement when reporting a bug, that is the job of QBO, not your users.

3 years later and this is still  a problem.  Can't belive that QB has not dealt with this issue.  Complete farce of a software that we are using.

Still doesn't work.  3 years later......