Bank feed coverage and gaps

Feed coverage finds the date ranges where an account has no bank data, so a missing week is named rather than invisible — and points you to a statement upload to fill it.

Banking → Feed Coverage.

Bank feeds come through Plaid (see Connecting your bank and credit cards (Plaid)) — a single aggregator; there is no multi-aggregator failover, so if Plaid loses your bank the feed stops until you reconnect or import statements. When a feed stops — a bank changed its login, a connection expired — the missing days are invisible until you go looking. This page looks for you.

Check for gaps reads each active bank and card account and shows how many transactions it has and the date range they cover, then a badge: complete, or the number of gaps. A gap is a silence much longer than that account's usual spacing between transactions (at least three weeks). Each gap is listed as Missing from → to, with Upload to fill it from a statement file and Resolved when it is genuinely quiet. An account needs a few transactions before gaps can be judged.

On the Command Center a gap becomes a Missing bank data item waiting for input when the Command Center rescans — see The Bookkeeping Command Center.

Filling a gap. Banking → Imports takes CSV, OFX, QFX and QBO files (and QIF), mapped once and saved as a template — see Importing a bank export file (CSV, OFX, QIF). When the connection itself has failed, reconnect it under Banking → Connections, which shows each connection's last sync.