QuickBooks Verify Error on the Acct, Card, or Note Field
A verify warning about an account, card, or note field usually means an encrypted value will not decrypt, and the fix runs through the admin login.
Desktop users who run the Verify Data utility sometimes meet a warning that names the Acct #, Card #, or Note field on an other asset account. The message is not about a missing value. It means the software cannot read data it stored in encrypted form, and the accepted fix works through the admin login before the flagged field is cleared and retyped.
The symptoms you will see
The warning appears while Verify Data runs. You reach that tool from the File menu, under Utilities. The check stops, reports a problem with an account number, card number, or note field, and names the record it belongs to.
A matching entry usually sits in the log file, QBWin.log. It pairs the record’s stored field with a display name and reports that decryption failed. That line is the clearest sign the trouble lies with encrypted data rather than anything you typed.
Rebuild Data does not clear this one. Users report running it, verifying again, and seeing the same record flagged once more. The record named can be an account, a customer, an employee, or a vendor; the other asset wording in the message is just the record type where the check stopped.
Why does decryption fail?
Fields such as bank account numbers, routing numbers, card numbers, and some notes are stored in scrambled form inside the company file. That scrambled data is tied to the file’s admin credentials. A password change, an edit to the user list, a conversion, or a restore from backup can break the tie.
The underlying value is often intact. Verify flags it because the software cannot read the value back, not because the number itself is wrong. That is also why a rebuild will not touch it. The effect is the same in Pro, Premier, and Enterprise; only the menu names differ slightly.
The first repair runs through the admin account
Sign in to the company file as the QuickBooks Admin. If you are unsure which user holds that role, open the roles list; the admin appears there with an admin marking.
In Pro and Premier, go to the Company menu, choose Set Up Users and Passwords, then Set Up Users. In Enterprise, go to the Company menu, choose Users, then Set Up Users and Roles. Select the default admin user, choose Edit User, and enter a temporary password. Save the change.
Saving that new password makes the software re-encrypt the protected fields under the new key. Give the process time to finish. If QuickBooks closes during it, restore your backup and move straight to the field repair below. If the process completes, repeat whatever step triggered the error. A warning that returns means the field itself still needs the manual repair.
Clear the field, save, then re-enter it
Open the record named in the warning or in the log. Go to the flagged field and clear it. Do this even when the contents look correct, and even when the field looks empty; select the field and clear it once more. Confirm with OK.
Reopen the same record and type the correct value back in. Save again. Then repeat the pair of edits for every name the warning or the log lists. Work through the list one record at a time so you know which ones are done. When the last one is finished, run Verify Data once more. A clean pass confirms the repair.
Which fields tend to trip the check?
On bank accounts, the account number and the routing number are the usual culprits. On income and expense accounts, it is the note field. The display name in the log may not match the label you see on screen, so match records by name rather than by label.
Before you begin
Take a fresh backup first. We recommend making that copy before you touch the password or any record. Both the re-encryption pass and the field edits write to the company file, and a current backup gives you a safe way back. The temporary password exists only to force the re-key; you can set a password you intend to keep through the same menu afterwards.