The authority publishes
An official registry releases or changes a record, filing or document.
Refresh cadence & data freshness
Company data freshness, explained source by source.
Registries publish on different schedules, and a company record can move through retrieval, digitisation, entity resolution, corporate linkage and enrichment at different times. Zephira keeps those layers—and the available freshness evidence—visible.
Refresh commitments are defined against the selected jurisdictions, fields and delivery method. Four clocks · one recordOperational freshness model
01
SourceThe authority publishes
An official registry releases or changes a record, filing or document.
02
CollectionThe source is checked
The publication becomes retrievable through the applicable source access route.
03
ProcessingThe record becomes usable
Fields are normalised; documents, entities and relationships are processed.
04
DeliveryThe update reaches the workflow
The selected access method exposes the latest available Zephira record or change.
The interval between stages depends on the source and agreed access model.
Source-dependentNo universal registry intervalField-awareDifferent layers move differentlyTimestamped where availableEvidence, not one vague dateContract-definedCadence scoped to the workflow
More than one clock
A single “last updated” label can hide four different events.
Freshness becomes meaningful only when the source, collection, processing and delivery moments are kept distinct.
The source is checked
The publication becomes retrievable through the applicable source access route.
The record becomes usable
Fields are normalised; documents, entities and relationships are processed.
The update reaches the workflow
The selected access method exposes the latest available Zephira record or change.
Data-layer cadence
Different company-data layers refresh differently.
A missing update is not proof that nothing changed. The source may not have published the change, or the field may not be available in that jurisdiction.
| Data layer | Typical trigger | What timing depends on | Available freshness evidence |
|---|---|---|---|
| Legal identity & status | Registry publication or recorded change | Official publication and source access | Named registry and retrieval or last-checked context where retained |
| Directors, officers & shareholders | Appointment or ownership filing | Local disclosure, filing delays and paid extracts | Source plus filing or reference date where supplied |
| Filed financials | Accounts become available | Company filing, document retrieval, digitisation and quality checks | Accounting period, filing and document lineage |
| Corporate linkages | Supporting entity or relationship changes | Contributing records can update at different times | Relationship source and processing context |
| Firmographic enrichment | Identified enrichment source update | An independent source and matching cycle | Enrichment label and source context |
Delivery clock
Freshness must be read in the context of the access method.
The same governed company layer can be searched, queried, delivered in bulk or monitored. Each route has a different operational pattern, but none changes when an authority publishes.
Company searchShows the latest company record available in the interface, with provenance where available.REST APIReturns the latest Zephira record available to the endpoint; it is not a blanket live-registry promise.Bulk data feedsFull and change-delivery patterns are scoped by dataset, market and agreement.MCP for AI agentsUses the same governed company layer. MCP changes the access protocol, not the source clock.Company monitoringSupported events and fields are checked or delivered under the configured workflow, where the source permits.
Evidence behind “current”
Freshness metadata should explain the record—not decorate it.
Not every official source supplies every timestamp. Zephira returns the evidence available to the record and distinguishes source facts from processing and enrichment.
- Source registry
- The authority behind the official record
- Jurisdiction & identifier
- The legal entity the evidence belongs to
- Filing or reference date
- When the source event or document applies
- Accounting period
- The period described by filed financials
- Retrieved / last checked
- Collection context where available and retained
- Processing label
- Digitisation, resolution, linkage or enrichment state
Define the requirement
Scope the cadence your workflow actually needs.
No honest global promise can replace a source-by-source assessment of the markets, fields, events and update window that matter.
- 01Jurisdictions
Name the registries and markets the workflow depends on.
- 02Fields & events
Define the company attributes and changes that matter.
- 03Access method
Choose search, REST API, bulk, MCP or monitoring.
- 04Update window
Agree a feasible cadence against the selected sources.
How often is Zephira company data refreshed?
There is no single global interval. Refresh timing depends on the official registry, field, source access conditions, processing required and delivery model. Zephira confirms the feasible cadence for the requested scope.
Is every API response retrieved live from the registry?
Not necessarily. The API returns the latest Zephira record available to the endpoint. Available provenance and retrieval context explain the record state; live or renewed source checks must be confirmed for the specific source and workflow.
Why can structured financials appear after the filing date?
The filing must first be published and retrieved. Its document fields can then require digitisation, mapping and quality validation. The accounting period, filing date, retrieval time and processing availability are different events.
Do ownership and corporate linkages update with the main company record?
Not always. Relationships can depend on multiple filings and entities, and may be recalculated after the supporting records have been processed.
Which freshness timestamps are available?
Filing or reference dates, accounting periods, retrieval or last-checked context and processing labels may be available. Exact metadata differs by source and delivery schema.
Can Zephira support a custom refresh schedule?
Where the source and selected delivery method support it, bulk, monitoring and enterprise schedules can be defined during a coverage review. The required jurisdictions, fields and acceptable window must be confirmed first.
Does monitoring prove the original verification was current?
No. Monitoring protects the record after the initial retrieval. It is a separate ongoing control, not a reason that the original verification passed.
What is company-data refresh cadence?
company-data refresh cadence is part of Zephira's registry-sourced company-data platform. Refresh timing depends on source publication, retrieval, document processing and the delivery model selected for each workflow.
Who uses company-data refresh cadence?
Compliance, risk, data, product and AI teams use company-data refresh cadence when they need structured company facts with clear provenance.
Where does the data for company-data refresh cadence come from?
Official company registries and filed company documents are the starting point. Source context is retained so users can trace material facts.
Freshness review