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 solves this with the Copy Connection and Hide/Unhide features.
The Modern Workflow (Recommended)
- Connect the bank once under the first client entity — all accounts under the login come in
- Use Copy Connection to copy that bank connection to the second client entity (no re-login or re-authorization needed)
- In each client, use Hide on the accounts that belong to the other business
Result: each LedgerSync client shows only its own accounts, both fed by a single authorized bank connection. Hidden accounts are excluded from statements, transactions, the Rules Engine, dashboards, and the API — and can be unhidden at any time without reconnecting.
Why Not Just Connect the Login Twice?
The bank will reject or break the second connection. Banks enforce one active data-sharing authorization per login per application. Copy Connection works within that rule — there is still only one authorization at the bank; LedgerSync distributes its data to multiple clients on your side.
Need Help?