What to do now
Treat bank-feed reauthorization as two linked handoffs: an authorized account holder restores the connection and scope, then an operator verifies account identity, coverage, checkpoint, and missed changes before routine reconciliation resumes. A successful login is not evidence that the correct accounts or full gap were restored.
Key takeaways
Prepare a minimum-information reauthorization request
Record the connection ID, institution, masked account references, last successful update, observed error, requested scope, authorized account holder, operator owner, expiry or deadline, and safe support channel. Never copy passwords, tokens, or full account data into the handoff.
Plaid documents an update-mode flow for restored authentication or authorization. That is an illustrative provider mechanism; use the current instructions and consent terms for the actual provider.
Use separate acceptance gates for access and data
The account holder should not be asked to certify transaction completeness, and accounting should not be asked to handle credentials it is not authorized to use.
| Gate | Owner | Evidence | Do not infer |
|---|---|---|---|
| Authority ready | Account/integration owner | Current authority and requested scope | Any staff member may reconnect |
| Provider restored | Authorized account holder | Provider success and selected accounts | Transactions are complete |
| Identity verified | Operator | Masked accounts match inventory | Similar names are the same account |
| Gap recovered | Accounting/data owner | Checkpoint and missing-change review | Newest date proves full coverage |
| Routine resumed | Control owner | Reconciliation accepted and monitoring set | Connection status alone is enough |
Record a clean transfer back to routine ownership
Verify account additions, removals, permission changes, and missed transactions. Link the recovery interval to the bank-feed disconnect record and resolve duplicates or manual postings before advancing the checkpoint.
Close with the final account population, consent or authorization date where available, first successful sync, reconciled-through date, unresolved items, and next monitoring owner.
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.