The Solution Bridge Blog
Quicken CC-901, CC-902 and CC-903: identify the connection before reauthorizing
Distinguish expired tokens, discontinued bank instances and refreshed sign-ins before reauthorizing the affected Quicken connection.
Applies to: Quicken Classic, Windows One Step Update terminology; U.S. support article updated October 6, 2026. Mac users should follow the linked Mac-specific route.
Similar connection messages can refer to different problems. Record the exact Quicken code and bank connection label before changing anything; a bank’s checking and credit-card services can use separate connection instances.
Quicken’s current support article associates CC-901 with an expired security token, CC-902 with a discontinued bank instance requiring the active connection, and CC-903 with sign-in information that needs refreshing. The article also explains that separate instances may need separate authorization.
Prepare before the bank sign-in
- Record the data file, exact error and affected account names.
- Identify the institution label for each connection.
- Retain the last successful download date and a current backup through your usual process.
- Have the authorized account holder perform sign-in through the native Quicken and bank flow.
The vendor’s process uses Reauthorize, then Sign In, followed by account selection and authorization. Review the scope carefully. Quicken warns that unchecking accounts can revoke their authorization and stop updates; do not remove access accidentally while concentrating on one account.
Check the whole affected group
Suppose a hypothetical user has checking under one institution label and a card under another. Reauthorizing the first connection does not establish that the second is repaired. Keep two rows in the follow-up list, record each result, and verify downloaded transactions against the existing account history.
If the flow fails, retain the error and follow the official next-step guidance for the relevant platform. Avoid cycling through destructive account changes or adding duplicate registers merely to clear a warning.
Our bookkeeping and accounting service can help organize the records and review questions behind this workflow.
Reauthorization questions
Do all three codes mean an incorrect password?
No. The vendor identifies distinct causes; use the exact code.
Should passwords be included in a support log?
No. Record the connection and error, never credentials.
Does a success message prove the books are complete?
No. Verify the affected accounts and downloaded date range separately.
Prepared by The Solution Bridge. Sources checked October 12, 2026. Educational guidance; verify current product instructions and applicable requirements.
Useful answers
Quicken FAQs
Are Windows and Mac error codes interchangeable?
Do not assume so. Identify the operating system and exact task, such as adding an account or updating an existing one.
What should I record before contacting support?
Note the code, time, affected institution, product version and whether the problem affects one account or several. Remove personal details from screenshots.
Should I share my bank login in the contact form?
No. Describe the issue without credentials or account numbers. Bank authentication should occur only in the appropriate authorized product flow.
Talk to The Solution Bridge
Let’s make your next step clearer
Tell us what you need help with. For software enquiries, include the product, version and exact message. Please leave out passwords, tax identifiers and financial documents.