CU Wire Data
Data standards

How we label, update, and protect the data.

CU Wire Data is built from official public records, reviewed enrichment, and CU Wire calculations. This page explains the standards customers can rely on without publishing the internal extraction map, transformation logic, or operating playbook.

Official recordsCore U.S. credit union financials come from regulator-published public filings.
Clear labelsWe distinguish source data, calculated ratios, peer context, editorial reporting, and reviewed enrichment.
Current periodsQuarterly surfaces are stamped so stale analysis does not silently carry forward.
Moat protectedPublic pages describe trust boundaries, not the proprietary collection and normalization recipe.

What customers can trust

  • Federally insured credit union coverage is tied to official public reporting periods.
  • Calculated fields are labeled as CU Wire calculations, not passed off as regulator-published figures.
  • Peer medians, percentile context, and ranges are separated from system-wide or institution-level comparisons.
  • Editorial items and market trackers are reviewed before they are counted in public totals.

Update posture

  • Quarterly financial data is refreshed after the official public release and reconciliation cycle.
  • Market, regulatory, merger, payments, vendor, and CUSO context is maintained on an operating cadence.
  • Corrections, source changes, and data-quality flags are handled as they are surfaced.
  • Paid data packages include period labels, schema notes, manifest details, and delivery checks.

What we do not expose here

  • Extraction recipes, source-by-source operating instructions, and internal source maps.
  • Private enrichment logic, unpublished editorial notes, or relationship-scoring methods.
  • Customer data, personal contact data, credentials, or non-public operational details.
  • Raw rebuild instructions that would reduce the product to a public shopping list.

What Data Access buys

Data Access customers buy licensed delivery convenience: normalized files, documented fields, stable identifiers, period labeling, authenticated delivery, and support around the package boundary. They do not buy editorial influence or special coverage.

Plain English: we show enough for buyers to understand quality, provenance, and accountability. We do not publish enough for a competitor to clone the collection system.