Company Registry Data Freshness: Which Date Matters?

Company registry data freshness is a question about a particular fact, not a single age attached to an entire company profile. A retrieval timestamp tells you when you obtained a result. It does not, on its own, tell you when an address changed, when a filing was processed or which period an account covers. Keep those meanings separate before describing the evidence as current.

For a supplier review, start with the question you need to answer. Confirming the registered address shown by a register today is different from reviewing accounts for an earlier financial year. This distinction helps you prepare a precise company registry lookup and explain the limits of the result.

Give each date a specific meaning

Avoid an unlabeled “last updated” value in a review note. Write what was dated and where that date came from. If a source supplies an update date, preserve its definition and scope: it may concern a document, a field or a dataset. Do not silently apply it to every fact in the company record.

For example, the Companies House filing history specification defines the date on a filing history item as the date that filing was processed. That is a useful event to record, but it should not be relabeled as the date on which every fact in the document became true.

The Companies House company profile specification separately identifies the end of the most recently filed accounting period through accounts.last_accounts.period_end_on. It also has fields for upcoming filing deadlines and the company's creation date. Those values answer different questions; none is a substitute for a record-wide freshness timestamp.

When an interface shows a date without explaining it, consult the source documentation or preserve the uncertainty. Guessing its meaning makes the resulting summary look more precise than the evidence supports.

Check how the data reached you

A direct lookup and a downloaded dataset need different context in an evidence log. The download time belongs to your copy; a snapshot cutoff belongs to the dataset. Record both when available, together with the route through which you obtained the material.

Companies House describes its company data product as a monthly snapshot. Its guidance says the contents are compiled through the end of the preceding month and released within five working days after that month ends. That schedule describes this particular product, not every Companies House service or every registry.

The practical implication is simple: downloading a snapshot again does not move its cutoff forward. Likewise, a newly generated report can incorporate older source material. Ask which dataset or document underlies the report and which dates were retained. If the delivery method is unknown, record that gap instead of assuming a live query occurred.

Read a fictional timeline without collapsing its dates

Consider a fictional supplier, Rowan Harbour Components Ltd. The company, dates and review below are invented solely to illustrate the method; they are not an Apiosk customer record or a real registry result.

Imagine that the available accounts cover a period ending on 31 March 2026. The filing history records processing on 20 October 2026. Your team retrieves the document on 9 November 2026. All three dates can be correct at the same time.

A useful note would say: “Accounts for the period ending 31 March 2026; filing processed 20 October 2026; document retrieved 9 November 2026.” Calling this “financial information as of 9 November” would remove the distinction that matters to the reader.

Now suppose the team retrieves the same document again on 12 November. Preserve the second observation if it matters to the review, but leave the accounting period and processing date intact. The new retrieval does not extend the financial period. If the question concerns a subsequent change in the supplier's circumstances, identify the additional evidence needed rather than reusing the download date as an answer.

Build an evidence log around the question

Use one entry per checked fact or document when their dates differ. A company-level row can become misleading if it combines an address observation with accounts covering a different period. The following fields form a practical starting point:

• Question and subject: the fact being checked, the legal entity and its registration number and jurisdiction.
• Source and delivery route: a usable record or document link, plus whether the material came from a lookup, report or bulk dataset.
• Retrieval time: when your team or system obtained the material, including the time zone if recording a time of day.
• Source dates: the original date labels and values, such as processing date, accounting period end or a documented update date.
• Dataset cutoff: the snapshot date or coverage period, where applicable; otherwise say that it was not supplied or does not apply.
• Assessment and next step: the question the evidence answers, any missing date or conflicting information, and the reason for a further check.

Keep the original values alongside your interpretation. An AI-generated summary should not replace them with one convenient timestamp. Our guide to source-backed company checks for AI agents explains how to preserve evidence when passing a result into another workflow.

Decide what warrants another check

Freshness should serve the decision being made. Define what your organisation needs to know at the point of onboarding and what changes would require another review. A supplier reporting a new registered address, a material delay before contracting or a conflict between two records gives you a specific question to investigate.

Do not assume that repeating an identical download resolves a discrepancy. First establish whether you need a different source, a newer snapshot or a different type of document. A missing update date is a limitation to describe; by itself, it proves neither that a fact is current nor that it is outdated.

When you do refresh a check, retain the earlier observation and explain what changed. This makes the review understandable later without inventing a universal expiry rule for all company information. The appropriate interval depends on the decision, the source and your applicable review requirements.

Prepare an Apiosk request with clear date expectations

Apiosk's public registry lookup page describes company identity, status and registration information. Its company filings page describes filings with dates and other recorded company information. When discussing a check, specify the fact and period you need, and confirm the relevant source coverage and the meaning of the dates returned.

As of 9 November 2026, the public website labels app access “Soon available.” Contact Apiosk to confirm access and suitability for your intended check. These public descriptions should not be read as a promise that every source provides a field-level update timestamp or a particular refresh interval.

This article was prepared with AI assistance and uses the linked official documentation to explain date meanings. The evidence log is a suggested working method, and the supplier example is fictional.