Keep bank connections healthy

This responsibility keeps the bank and card feeds used for accounting connected, current, and free from duplicate intake. It checks the live connection status before advising on a problem or treating a requested change as complete.

A connection needing reauthorization, nearing expiry, or reporting an error requires a company member to sign in again with the bank. A revoked connection is fully off and cannot be repaired; it must be connected anew if the company wants to resume importing transactions. A request link is temporary, so an expired link must be replaced rather than reused.

Changes are confirmed only when the bank feed shows the intended result: a healthy new or repaired connection, the agreed set of accounts, or a disconnected feed. Completing the bank’s sign-in process alone is not confirmation. Disconnecting stops future imports but does not remove transactions already received.

Before adding a connection, overlapping accounts from other sources are identified. The company must choose one primary source for each overlapping account; otherwise the same transactions could be counted twice. Mercury uses its dedicated connection route when its more detailed card, statement, and historical coverage is needed.