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 Hide/Unhide Accounts.
The Problem
Most major banks do not allow the same bank login to be connected multiple times — they treat redundant connections as a potential security breach. So if your client’s login covers Business A’s checking account and Business B’s checking account, and you keep Business A and Business B as separate LedgerSync clients, one connection cannot naturally serve both.
Solution Part 1 — Copy Connection
The Copy Connection feature copies an existing bank connection from one client to another, without requiring the bank login to be re-entered or re-authorized.
- Connect the bank once under the first client (e.g., Business A) — all accounts under that login come in
- Go to the bank connection and select Copy Connection
- Choose the destination client (e.g., Business B)
- LedgerSync copies the connection — Business B now has the same bank connection with all its accounts
Solution Part 2 — Hide the Accounts That Don’t Belong
After copying, each client has all accounts from the shared login — including ones that belong to the other business. Use Hide to exclude them:
- In Business A, find the accounts that belong to Business B
- Select Hide on each of those accounts
- Repeat in Business B for the accounts belonging to Business A
A hidden account is excluded from all LedgerSync functions — statements, transactions, the Rules Engine, dashboards, and the API — without being permanently deleted.
Hide vs. Delete: Hiding is reversible — use Unhide at any time to bring the account back with no reconnection needed. Deleting removes the account permanently and re-adding it requires the client to re-authorize the bank.How to Unhide an Account
- Go to the client’s bank connection / account list
- Locate the hidden account (hidden accounts are shown in a separate/hidden state)
- Select Unhide — the account immediately resumes across all LedgerSync functions
Other Uses for Hide
- Excluding a personal account that came in with a business login
- Excluding closed or dormant accounts from dashboards and reports without losing history
- Keeping an account out of the LedgerSync API feed for API customers
Need Help?
Contact LedgerSync Support at support@ledgersync.com
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 ...How to set up the same bank login but split among two Ledgersync client accounts?
Overview What happens when a client owns two business entities and both businesses share the same bank login? Most major banks do not allow the same login to be connected twice — they treat redundant logins as a potential security breach. LedgerSync ...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 ...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 ...