The short answer
Snapshot provider and locally approved account metadata by stable identity, compare type, subtype, currency, unofficial currency, ownership/use, and balance semantics across versions, classify provider correction, bank change, local mapping defect, identity replacement, or unknown, then hold incompatible aggregation and reporting until the time boundary and downstream effects are reconciled.
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
Compare semantic fields, not just connection health
Record provider account ID, connection ID, masked identifier, official and display names, type, subtype, ISO or unofficial currency, ownership/use mapping, balance field used, and snapshot time. Do not retain full account numbers or credentials.
Plaid documents these as provider fields and notes nullable or unofficial currency cases. The provider record does not determine the account’s approved property or accounting use.
Disposition each drift
| Drift | Possible explanations | Immediate control | Acceptance evidence |
|---|---|---|---|
| Type/subtype | Provider correction, product conversion, mapping change | Stop incompatible rule | Bank/provider evidence plus local approval |
| Currency | Bank change, provider correction, wrong identity | Stop aggregation/conversion | Currency boundary and downstream retest |
| Name/mask | Cosmetic change or identity replacement | Compare stable IDs and transactions | Supported continuity or separate identity |
| Balance semantics | Available/current/null behavior changed | Label report limitation | Field contract and report test |
Trace changed meaning into downstream uses
Inspect reconciliations, dashboards, conversion logic, thresholds, transfer eligibility, and owner reports that consumed the changed field. Preserve the earlier snapshot and correct or annotate dependent outputs.
Do not infer currency conversion or account eligibility from a provider label.
Close with a semantic boundary and reconciled downstream uses
Name the population, cutoff, evidence version, owner, decision, unresolved exceptions, next checkpoint, and downstream records updated. Preserve the earlier state rather than replacing it with a clean current screen.
Reopen the record when a late event, changed source, new affected item, or downstream consequence invalidates the signed conclusion.
Edge cases
Sources and references
Follow each source to check the underlying claim. Access checks and professional review are different steps.