Accounting and records · Checklist · intermediate

Bank-connection account scope-change review

Reconcile accounts added to or removed from a bank connection before treating the feed as complete or intentionally narrowed.
By Aptoria editorial team · 3 min read · Updated 2026-09-18 · Last reviewed 2026-09-18
Technical content review: Codex technical editorial review. Reviewed intent separation, internal consistency, original artifacts, failure states, source limits, privacy minimization, and links. No accounting, banking, security, safety, legal, tax, or other professional approval is claimed.
This is a technical review, not independent human or professional review.
The short answer
Compare the prior and current account inventory using stable provider and masked bank identifiers, classify every addition, removal, replacement, merge, or unknown, determine the last and first covered timestamps, and reconcile missing or overlapping transactions before accepting the new feed scope.

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

Key takeaways

  • Connected does not mean the same accounts are connected.
  • Use stable identifiers, not display names alone.
  • Prove the time boundary for every changed account.

Capture before-and-after account inventories

Record connection ID, institution, consent or authorization reference, provider account ID, masked number, account type, currency, property/entity use, first and last transaction timestamps, and active status. Do not store credentials or full account numbers.
Separate a true bank account change from a provider identifier rotation or display-name change.

Disposition every membership change

Account scope-change register
ChangeQuestionContinuity proofDecision
AddedNew account or newly granted scope?First available timestamp and prior sourceAccept, backfill, or hold
RemovedClosed, revoked, hidden, or provider error?Last available timestamp and alternate evidenceRetire, restore, or investigate
ReplacedSame real account with new provider identity?Overlapping masked identity and transactionsMap with evidence or keep separate
UnknownInventory cannot explain differenceIndependent bank/account-owner confirmationDo not accept completeness

Reconcile the changed time window

For each account, compare statement or approved bank evidence with feed transactions across a window that spans the old last-seen and new first-seen timestamps. Identify missing, duplicate, pending-to-posted, reversed, or recategorized items.
A narrowed authorization may be intentional. Record the effective scope and downstream reports that must stop expecting the removed account.

Close with account membership and time-bound transaction continuity

Name the reviewed population, cutoff, evidence version, decision owner, unresolved exceptions, next checkpoint, and downstream records updated. Preserve the superseded state; a clean current screen is not a substitute for the correction or exception history.
Reopen the record if the population, authority, source version, external outcome, or dependent report changes after sign-off.

Edge cases

  • Two accounts share the same display name: use provider and masked bank identities.
  • A closed account still receives late transactions: keep a bounded follow-up source.
  • Authorization intentionally narrows: update completeness assertions and report scope.

Sources and references

Follow each source to check the underlying claim. Access checks and professional review are different steps.

Revision history

2026-09-18
Initial Phase 5 operational article with distinct intent, original artifact, source limits, and AI-assisted technical review.
Report a correction to this resource