Bank Connection History Log
Overview
LedgerSync has added a new icon to the Bank Account Summary page that lets you view the full history of any bank connection — from the moment it was first added all the way through any breaks, reconnections, and MFA requests.
Where to Find It
On the Summary page for any client, you'll now see a new History icon next to each bank account row. Click it to open the connection history log for that account.
What the History Log Shows
Each entry in the log is timestamped and will reflect one of the following events:
- Added — The date and time the bank connection was first set up in LedgerSync
- Broken (Username/Password) — When the connection broke due to a password change or invalid credentials
- Needs MFA — When the bank required a multi-factor authentication token to continue fetching data
- Reconnected — When the connection was successfully restored
Why This Is Useful
Track the full lifecycle of a bank connection See a clean, chronological record of every significant event for each bank account — no more guessing when a connection was first added or when it last broke.
Measure how quickly broken connections get resolved By comparing the "Broken" timestamp against the "Reconnected" timestamp, you can see exactly how long a bank was offline. This makes it easy to spot connections that sat broken for days or weeks without action.
Monitor your team's follow-through Managers and administrators can use the history log to verify that employees are actively following up on broken connections and not letting them lapse. It creates accountability without requiring manual check-ins.
See whether clients are responding If a broken bank requires the client to reconnect on their end, the history log will show whether (and when) they followed through. This helps you identify clients who need an additional nudge via SMS or email.
Practical Example
You notice a client's Chase connection has been showing as broken. Opening the History Log, you can see:
- Connection was Added on October 3, 2025
- Broken (Username/Password) on January 14, 2026
- A reconnection invite was sent, and the client Reconnected on January 17, 2026 — a 3-day turnaround
This gives your team a clear record and confirms the issue was resolved promptly.
Need Help?
- Email: support@ledgersync.com
- Live Chat: Available during business hours in the app
Related Articles
What Bank Connection to Choose - Ex/ Mastercard API, Ledgersync Premium, MX
Purpose LedgerSync offers multiple bank connection options to ensure you can access the financial data you need. Choosing the correct connection type helps ensure reliable access to: Bank statements Transactions Check images This article explains ...Why LedgerSync Requires Full Account Owner Access to Fetch Bank Statements
What Is Bank Restricted Access? Many financial institutions offer a feature called restricted access (sometimes called "read-only access," "accountant access," or "third-party access"). This is a limited login credential that a bank account owner can ...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 ...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 ...How to Add a Bank Feed Connection in LedgerSync
Overview Adding a bank feed connection in LedgerSync allows you to aggregate bank statements, transactions, and check images seamlessly. Follow the steps below to set up a bank connection based on your specific needs. Steps to Add a Bank Feed ...