The article outlines the steps in creating and modifying renaming rules. It also provides common fixes for common issue with renaming rules.
When you download transactions into your Bank Feeds, they are usually categorized as:
To add transactions using renaming rules:
Note: This is only applicable if Create rules automatically and Always ask before creating a rule options under your Preferences are checked.
This issue occurs of the downloaded transactions have generic names or description like “Check,” “Payment,” or “Online transfers” and QuickBooks creates rules as you enter or add transactions and then apply these rules to the remaining unmatched transactions.
Unlike Quicken, QuickBooks doesn't’t have the reverse renaming rule functionality. However, you have two options to prevent having transactions with incorrect payees (or accounts).
Option 1: Choose to manually create renaming rules
This option prevents QuickBooks from automatically creating renaming rules if you are in Express Mode.
Note: Since QuickBooks will no longer create any rule as you add transactions to your register, you need to manually create renaming rules. Also, you need to edit/delete any incorrectly created rules to avoid issues when you download transactions in the future. Refer to the Setup Renaming Rules section of this article for steps on creating and modifying renaming rules.
Option 2: Switch to the Classic (Register) Mode
Refer to Switch between banking modes for instructions.
Option 1: Manually correct each transaction
Option 2: Restore a backup
If you have created a backup copy of your company file before entering/adding the downloaded transactions, you can restore the backup and start over.
Currently, renaming rules will not apply to funds transfer and deposit transactions. In order to automatically match deposits, you need to switch to the Classic (Register) mode and use payee aliasing function.
To switch to Classic Mode:
To know more about payee aliasing:
When editing a renaming rule in online banking, you may receive the error “Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue. There is no row at position X.”
If you receive this error message, either your Microsoft.NET Framework 3.5 is damaged or not installed on your computer. Repairing on reinstalling the Microsoft.NET Framework may resolve the issue.
Error GetQBAccountSpecialType, An unknown QuickBooks account was used usually happens because of damaged renaming rules.
Solution: Delete and recreate all Bank Feeds rules
Note: Test the resolution by trying to use batch action. If you no longer receive the error, recreate your renaming rules.