OUSBI treats correction as part of the product, not an embarrassment to hide. Banking rules change, institutions merge, disclosures are revised and source conflicts occur. Material corrections should be traceable.
What counts as a correction
A correction is needed when a factual statement, data value, institution identity, product scope, source mapping or material explanation is wrong or materially incomplete. Pure formatting, spelling or layout changes do not need a public correction record unless they altered meaning.
What the correction record contains
For a material correction, the internal/public change record should identify the page or data record, previous wording/value, corrected wording/value, reason, source and correction date. If the source has an effective/version date, it is retained when relevant.
Disagreement is not automatically an error
A user, institution or advertiser disagreeing with a page does not by itself prove the page is wrong. OUSBI checks the source/evidence. If a correction is warranted, it is made regardless of whether the error was favorable or unfavorable to the institution.
Official-source conflict
When two credible official sources conflict, OUSBI can mark the fact CONFLICT and explain the scope/date difference rather than silently selecting the more convenient source. High-risk facts—such as eligibility, tax-ID requirements, fees, availability timing and transfer limits—receive review before being changed.
Source failure is not deletion evidence
A 404, timeout or failed fetch creates a review/fetch-error state. OUSBI does not automatically erase the public fact simply because a source cannot be fetched once. The source may have moved, changed URL or be temporarily unavailable.
How to request a correction
The public correction contact is not yet available in this release candidate. Public release remains on hold until a monitored correction/privacy channel has been verified. A correction request should identify the page, disputed statement and supporting source. Do not send account numbers, SSN/ITIN, passwords, unredacted bank statements or identity documents.
Sources and versioning
Related policies: /methodology/ and /editorial-independence/. A correction concerns the accuracy of this site; it is separate from a request for the institution to resolve your banking transaction.
This policy is reviewed when the evidence methodology, data coverage, moderation, commercial relationships or privacy practices change. The policy published at launch must describe the features and controls that are actually available.
Example: correction vs source update
If OUSBI incorrectly states that a transfer takes 2–3 business days when the bank’s current help page says outbound transfers may take 1–3 business days, that is a factual correction: the old wording, corrected wording, reason, source and date should be recorded. If the bank itself later changes a correct rule from 1–3 to another range, that is primarily a source/change-history event rather than evidence that the earlier OUSBI page was erroneous.
Frequently asked questions
Can an institution demand removal because it dislikes wording? Disagreement alone is not proof of error. Can a user request a correction? Yes, by identifying the page/statement and supporting source without sending sensitive account information. What if official sources conflict? OUSBI can label CONFLICT. Are spelling fixes public corrections? Usually not unless meaning changed. Does a broken source mean the fact is deleted? No; it triggers source review.
Correction priority
Safety- or money-impacting errors—eligibility, tax-ID requirements, fees, availability dates, transfer limits/status and regulator routing—take priority over cosmetic/editorial issues. A correction should propagate to all affected pages/data records so a fixed value is not left stale in a second location.
Related guides
How OUSBI verifies banking information: /methodology/
Privacy and data handling: /privacy/