Dashboard — What Does “Review Accounts” Mean?

Overview
The LedgerSync dashboard displays your bank connections in several status categories. One category that is easy to confuse is "Review Accounts." This is separate from "LedgerSync Errors" and indicates a different type of situation — one that typically does not require any client action.
Review Accounts vs. LedgerSync Errors — What’s the Difference?
| Status | What It Means | Action Required? |
|---|
| LedgerSync Errors | Connection is broken and needs action: invalid credentials, MFA required, password changed, connection token expired | Yes — client or accountant must fix the connection |
| Review Accounts | Bank returned a specific status code indicating the account is closed, inactive, zero-balance, or similarly restricted — this is an account-level state, not a connection failure | Usually no — review if the account should be kept or removed |
Common Reasons an Account Appears in Review Accounts
- The bank account has been closed by the client
- The account is a zero-balance or dormant account that the bank has restricted
- The bank returned error codes 913, 38006, 946, or 324 (or similar codes in the same category)
- The account exists but the bank is not currently exposing data for it
What to Do When You See Review Accounts
- Check with the client — is this account still active?
- If the account is closed: the connection can be deleted in LedgerSync. This will not affect any other data or connections for that client
- If the account is still active but showing in Review Accounts, contact LedgerSync Support — the bank may need to be re-authorized or the connection may need to be refreshed
Review Accounts do not count toward your "LedgerSync Errors" total on the dashboard. They are tracked separately so you can prioritize your actual broken connections without closed accounts inflating the error count.
Need Help?
Related Articles:
Related Articles
If a bank has already been connected, will all new accounts be auto added to Ledgersync?
If a client already connected a bank to Ledgersync and the client adds new accounts under the same login details, will the new accounts be added automatically in Ledgersync? It’s a very good question and the answer depends on the type of connection ...
Copying a Bank Connection Between Clients & Hiding Accounts (One Login, Multiple Businesses)
Overview Many business owners run several companies under a single bank login. Banks only allow that login to be connected once — so how do you split the accounts across separate LedgerSync clients? Two features solve this: Copy Connection and ...
MX Bank Connection — Overview, Setup, and FAQ
Overview MX is LedgerSync's second full bank data aggregator, available alongside the Mastercard API. MX is fully deployed and actively used across the platform — it is not a beta feature. If your bank is not supported by the Mastercard API, or if ...
What is the best way to manage my clients broken bank feed connections? (Video)
Handling Broken Bank Feed Connections: During this video we help demonstrate the two different ways you can notify your client about a broken bank feed. Why do BANK FEEDS usually break? The most common reason a bank feed has been interrupted is due ...
Bank Connection Notes — How to Add Shared Notes to a Bank Connection
Overview The Notes feature lets you attach persistent, shared notes to any bank connection in LedgerSync — whether it is connected via Mastercard, MX, or FDE (document-based extraction). Notes are visible to all users in your firm and are a great way ...