Overview

Each bank connection in LedgerSync has a status history. It lists the connection's status changes, such as breaks, requests for a security code and reconnections, usually starting with the entry recorded when the connection was added. It is available for MasterCard, MX and Statements & Checks connections.

Where to Find It

1. Go to Bank Connections > Summary.
2. Select the bank connection.
3. Click the history icon next to the connection's name, after the pencil and copy icons. Its tooltip reads Connection Status History.

The history opens in a window titled with the connection's name followed by "Status History".

What the History Log Shows

The log has these columns:

• Logged At
• Status
• Detected By
• Added By
• Error Details

Entries are listed newest first. To narrow the list, use Select Status and Select Date Range at the top of the window.

The Status column shows one of these statuses:

• CONNECTED: the connection is working. The entry recorded when a connection is added usually shows this status.
• RECONNECTED: the connection works again after a problem.
• BROKEN: the connection failed.
• NEEDS_REAUTH: someone needs to sign in to the bank again.
• MFA_REQUIRED: the bank asked for a security code (multi-factor authentication).
• MFA_RESOLVED: the security code step was completed.
• DISCONNECTED: the connection was disconnected.
• INTERNAL_ERROR: a failure that could not be classified further. It does not necessarily mean a problem on LedgerSync's side.

Only MasterCard connections record MFA_RESOLVED. On MX and Statements & Checks connections, a connection that works again is usually recorded as CONNECTED.

The Added By column is filled in only on the entry that records when the connection was added. It shows a badge, such as Client or Accountant, and the login of the person who added the connection. If LedgerSync did not record who added it, the column shows the login of the client the connection was added under, followed by "connection owner". On all other entries, and when that client no longer exists, the column is empty.

Why This Is Useful

Track the lifecycle of a bank connection

See a chronological record of each connection's status changes, so you can tell when a connection last broke and when it started working again.

See how quickly broken connections get resolved

Compare the time of a BROKEN entry with the time of the next CONNECTED or RECONNECTED entry to see about how long the connection was not working. This makes it easy to spot connections that stayed broken for days or weeks, including ones waiting for a client to sign in to the bank again.

Need Help?

Email: support@ledgersync.com