Skip to main content
August 11, 2023
Question

I am receiving an error when attempting to categorize transactions that states "Invalid data. Something you selected has been made invalid." Help?

  • August 11, 2023
  • 1 reply
  • 0 views
The error happens with any transactions on any account. It happens with transactions that are both manually uploaded or pulled in through an account sync.  

The complete error is as follows:

"Invalid data. Something you selected has been made invalid. Check the fields with accounts, customers, items, vendors, or employees.

1 reply

August 11, 2023

I'll make sure you'll be able to categorize transactions in QuickBooks Online (QBO), chris. 

 

The error message you encounter typically indicates that there's an issue with the data you enter or the way you categorize the transactions. Let's make sure the date you're trying to input is accurate. 

 

If everything is correct and the issue persists, we can perform some troubleshooting steps to fix this. It's possible this could have something to do with temporary internet files. Browsing applications store these types of records, but sometimes they can cause issues with certain web pages. 

 

Let's start accessing your account using a different or private browser. You can use either of these shortcut keys:

 

  • Google Chrome: Ctrl + Shift + N
  • Mozilla Firefox: Ctrl + Shift + P
  • Microsoft Edge: Ctrl + Shift + P
  • Safari: Command + Shift + N

 

Once logged in, try to categorize the transactions again. If it works, I recommend clearing your browser's cache. Doing so will remove the historical data and access QuickBooks with a clean slate. You can also switch to a different supported browser.

 

Once the issue gets fixed, you'll be able to review and categorize your transactions in QBO: Categorize and match online bank transactions in QuickBooks Online

 

Keep me posted if you have other banking concerns in QBO. You can leave a comment below, and I'll gladly help. Take care, and I wish you continued success!

August 12, 2023

The error persists. It also happens when using the android app. I tried clearing the cache but no luck.