Accounting accounts could not be loaded means Institution could not read the destination list needed for mapping. Keep the existing bank connection and retry the list before creating another account.
- Choose Retry account list beside the message, or Refresh accounts when using the import account picker.
- Confirm that you are still signed in and viewing the intended company. Wait until the list finishes loading.
- Compare the refreshed accounts with the statement, then continue mapping or importing only after you can identify the correct destination.
An empty list caused by a failed request is different from a successfully loaded list with no eligible accounts. The displayed error helps you distinguish them. Do not treat a temporary failure as proof that earlier account records were deleted.
If the failure repeats
Record which company and workflow you were using, whether saved accounts or connected bank accounts failed, and the exact visible message. The import picker can keep saved accounts available even when the connected bank list fails.
If you had already saved a mapping before the list failed, refresh the connection state as well. Check the mapped count to avoid repeating work that the server may have completed.
Was this article helpful?
Tell us whether this answered the question you came with.