The verification cadence: how often we check

Continuous verification is the operating commitment of this site. The cadence is set by the publication frequency of each underlying source and by the latency tolerance that the editorial design of the site can sustain.

FCA: daily

The FCA Financial Services Register supports programmatic access to its EMI-class export. The export is consumed on a 24-hour cycle. Any record whose status has changed at source - typically a status migration from authorised to withdrawn or vice versa - is reflected in the local view within that cycle.

EBA EUCLID: on golden-copy release

The EBA central register releases its golden-copy export on an irregular cadence, typically every two to four weeks. The site consumes each release within twenty-four hours of publication. Between releases, the local view reflects the most recent EUCLID snapshot.

National supplements: as appropriate

For a small number of jurisdictions - principally Lithuania and Malta - the national competent authority publishes its register on a faster cadence than EUCLID's central refresh. Where the faster cadence materially improves freshness, the national source is consulted directly and is used to amend the local view.

Bounded staleness

The practical consequence of the cadence is that an FCA record's reported status is, in the worst case, twenty-four hours stale. An EBA record's status may be up to four weeks stale relative to the home-state national register. Both numbers are bounded; there is no scenario in which a record's reported status would be older than the published refresh cadence permits.

What we publish at the page level

Each institution's detail page carries a 'last verified' timestamp showing the most recent refresh of the underlying source for that particular record. The timestamp is the most precise summary of the record's freshness; it is preserved on each refresh.