How Tally watches your bank connections

Tally detects broken and silently stale feeds, chases the reconnect with the company owner, and escalates when the connection cannot be saved.

Two Ways A Feed Fails

You do not have to notice a dead bank feed. Tally checks connections on its daily run, opens an incident, chases the owner for a reconnect, and tells you when the chase is over.

It reports an error. The bank login expired or the credentials changed. Tally records the cause — a login-required or invalid-credentials error means this needs the company, not your firm.

It reports healthy and delivers nothing. This is the dangerous one, because nothing looks wrong. Tally compares each feed against its own baseline activity rate and flags a feed that has gone silent — for example, "reports healthy but delivered nothing for 9 days (baseline 4/day)." It opens a stale-feed incident and retries the sync immediately.

A stale feed waits one retry cycle before any outreach, because a quiet day at the bank is not an outage.

The Reconnect Chase

Once an incident is open, Tally sends the reconnect outreach to the company owner itself and steps up the ladder on a schedule, reporting each send:

Sent reconnect outreach (rung 2) to Blue Harbor Dental for First National.

Incidents in progress show as Waiting on clients — the ball is with the owner, not with you.

When It Escalates To You

Two things end the automatic chase:

Ladder exhausted. Every reminder rung has been sent with no reconnect. Tally's line for this is blunt: this needs a phone call.
Repeat breaker. A feed that broke several times in 30 days is reported as an institution problem worth moving the account or contacting the bank about.

An exhausted ladder means texting has failed, not that the connection is unimportant. Every day it stays down is a day of missing evidence for coding and reconciliation.

Gaps After Recovery

A reconnected feed does not always backfill. When Tally sees that a feed recovered but a date window never arrived from the bank, it requests the statement to fill the gap rather than leaving a hole in the evidence.

Check that window yourself before reconciling that period. See Find missing bank transactions.

What You Still Do

Take the phone call when the ladder is exhausted — see Reconnect a bank that needs attention.
Confirm the owner's cell phone in Company Settings if outreach is not landing.
Check register mapping survived after a reconnect.
Decide whether a repeat-breaking institution is worth keeping connected.

Never send bank credentials or one-time codes through a request, a text, or a support ticket. The owner authenticates with the bank through Plaid; nobody at your firm needs those values.

If a feed is down and Tally has not opened an incident, create a support ticket with the company, institution, account mask, and the last date activity arrived.