The short answer
Recover a disconnected bank feed by recording the last confirmed complete point, obtaining authoritative statement coverage for the gap, restoring access without deleting prior imports, importing in a controlled window, and reconciling added, modified, removed, and overlapping transactions before routine automation resumes.
Key takeaways
Bound the gap with two verified anchors
Record the account reference, provider item or connection ID, first observed failure, last successful update time, last reconciled statement line, and current statement cutoff. The feed’s error time and the first missing bank transaction may differ.
Plaid documents cursor-based synchronization with added, modified, and removed transaction sets. That provider behavior illustrates why recovery must track change types and a stable cursor or checkpoint instead of blindly appending a new download.
Stage the backfill and test overlap
Preserve the existing imported population. Load the recovery set into a staging view or bounded review process, compare stable provider identifiers where available, and use date/amount/description only as secondary signals.
| Population | Evidence | Acceptance question |
|---|---|---|
| Before-gap anchor | Last reconciled statement line and import checkpoint | Is coverage known complete through this point? |
| Gap population | Bank statement plus provider added/modified/removed data | Does every statement item have one governed outcome? |
| Overlap window | Several days on both sides of the gap | Were duplicate or changed records detected? |
| Ledger effect | Existing and proposed postings | Will backfill duplicate a manual entry? |
| Resume point | New cursor/checkpoint and successful update | Can routine sync continue without skipping the gap? |
Reconcile before handing control back to automation
Match the authoritative bank statement to the ledger through the recovery cutoff, then reconcile provider records to both. Resolve removed, renamed, pending-to-posted, duplicated, and manually entered items according to the accounting process. Do not delete history simply to make counts agree.
Record the restored credential owner, new checkpoint, unresolved items, reviewer, and next monitoring time. Reconnection is a technical event; completeness is a reconciliation decision.
Operational checklist
Mark your progress, then save a working copy. Selections reset when you leave this page. A checked box is not an approval or evidence of completion.
0 of 7 marked
Edge cases
Sources and references
Follow each source to check the underlying claim. Access checks and professional review are different steps.