Unable to update Citibusiness Checking transactions due to 102 error
If you see Error 102 when connecting or updating your Citibusiness Checking account in QuickBooks Online, it usually indicates a communication issue between QuickBooks and your bank’s website. This often happens if the bank has changed its website, requires a new login action, or has temporary server maintenance.
Here are the steps to resolve this issue:
1. Verify your bank credentials Sign in to your Citibusiness account directly outside of QuickBooks to ensure your password is current and that there are no new security prompts, messages, or alerts requiring your attention. If you are forced to change your password or accept new terms of service on the bank’s site, you will need to update your credentials in QuickBooks.
2. Update your bank login in QuickBooks
- Go to Banking (or Transactions) and select the Banking tab.
- Find the Citibusiness account in the list.
- Select the Edit (pencil) icon, then choose Edit sign-in info.
- Enter your updated User ID and Password, then select Update.
3. Check for bank notifications Sometimes a bank will place a hold on data access until a specific notification is read. Look for any messages in your bank portal regarding security updates or data sharing agreements.
4. Manually import transactions (WebConnect) If the error persists, you can manually download your transactions from the Citibusiness website and upload them to QuickBooks so you can continue accounting while the connection is restored.
- Sign in to your bank’s website and locate the download or export section.
- Select QuickBooks WebConnect as the format (usually a
.qbofile) for the desired date range. - Save the file to your computer.
- In QuickBooks Online, go to the Banking (or Transactions) menu and select Upload transactions (or Upload from file).
- Follow the on-screen prompts to browse for your file and upload it.
Note: If you manually import transactions while the bank feed is down, you may see duplicate transactions once the automatic connection is restored. You can resolve this by using the Exclude feature in the banking feed for any duplicated entries.