Company registration number: the evidence fields that stop identifier mistakes

A company registration number should be stored as the start of a company-identity decision, not as the whole decision. The number may identify a record in a register, but the useful evidence is the combination of number, jurisdiction, register, entity name, status, retrieval time and the precise claim the record supports.

The current search results for this topic mostly answer two introductory questions: what the number means and where a business owner can find it. That is helpful for a founder completing a form. It is not enough for a product, KYB, credit or supplier-risk team that must decide whether an identifier belongs to the right legal entity, whether it is still current, and whether it proves only registration or something broader.

The practical rule is simple: never accept a bare number as a portable company identity. A UK company number, a California entity number, a Delaware file number, an Australian ACN, a Singapore UEN and an Indian CIN are all useful, but each comes from a different legal and data environment. Some identify companies only; some cover wider entity types; some have check digits; some are reused in public portals with status limits; and some must be paired with a state, local register or foreign-qualification context.

A company registration number is the identifier assigned by the relevant company or business register when an entity is registered or incorporated. In the UK, Companies House says a certificate of incorporation confirms that the company legally exists and shows the company number and date of formation. The same official guidance says the certificate states the name, registered number, incorporation date, company type and registered-office jurisdiction.

The phrase is not identical across markets. In the UK, the same concept may appear as a company number, Companies House number or CRN. In Australia, ASIC issues a 9-digit Australian Company Number to every registered company and distinguishes it from the Australian Business Number issued by the tax authority. In Singapore, the Unique Entity Number is a standard identification number used by entities ranging from companies to societies when they interact with government agencies. In India, public company master data is organised around the Corporate Identification Number as well as company name, status, class and registration date.

The number does not normally prove beneficial ownership. California’s Secretary of State is explicit that ownership, telephone numbers, email addresses, subsidiaries and associated businesses are not made part of the business-entity record. A register record can therefore support legal existence, status or filed attributes, while leaving ownership and control to other evidence paths.

That distinction matters when a form asks for one identifier but a workflow silently substitutes another. An EIN may be necessary for US tax, payroll or banking tasks, but it is issued by the IRS and should not be treated as a state formation number. A DBA, business licence, tax account and securities-filing identifier may all be legitimate identifiers; they simply answer different questions.

The US is the clearest place to see why a bare “company registration number” field breaks. The Small Business Administration explains that registration depends on business structure and location, that most states require registration with a Secretary of State, Business Bureau or Business Agency, and that an entity may need foreign qualification in additional states where it conducts business. In other words, a company can have a home-state formation record and separate authority records elsewhere.

That makes the identifier incomplete unless the system also stores the state and registration role. Delaware’s public information page says its search can be performed by name or file number and returns both active and inactive entities; it also warns that search results are not entity status and that status checks are a separate paid service. New York says its corporation and business-entity information is updated daily and includes current name, organisation date, jurisdiction, county, service-of-process address and current status. California describes an entity number as the identification number assigned at registration, but also notes that certain other entity types are not included in the same search database.

A practical US data model should therefore separate formation jurisdiction from operating registration. A Delaware LLC registered to do business in California may present a California entity number on a local filing, a Delaware file number on its formation record, an EIN for tax, and perhaps a CIK if it files with the SEC. None of those numbers should overwrite the others. The matching question is not “which one is the company number?” but “which identifier supports this exact claim in this exact jurisdiction?”

The safest sequence is retrieval, comparison, then verification. Retrieval means locating the record in the official register or a sourced data product. Comparison means checking the number against the legal name, jurisdiction, entity type, status and any known address or officer information. Verification means deciding whether that evidence supports the specific business claim, and recording what remains missing or contradictory.

A worked example shows the boundary. Retrieved on 2026-09-17 from Companies House, Global Data Intelligence Limited appears with company number 09410808, registered office in Northampton, active status, private limited company type, incorporation date 28 January 2015, last accounts made up to 31 January 2026 and last confirmation statement dated 6 March 2026. That supports a claim that this UK legal entity exists on the register under that number at the retrieval date. It does not, by itself, prove ultimate beneficial ownership, current commercial trading volume, authority of a particular employee, or the accuracy of every filed detail. CompanyProof uses this kind of distinction when treating company facts as claims that need evidence, timing and limits.

For manual review, the reviewer should keep a screenshot or downloaded register extract where permitted, the canonical record address, the retrieval date and the fields relied on. For an API workflow, the same evidence should become structured metadata: source name, source record, source retrieval time, source-updated time where supplied, entity identifier, jurisdiction, match method and decision outcome.

Unavailable information should not be filled by implication. If a register does not disclose owners, mark ownership unavailable from that source and route the case to attestation, filed documents, shareholder records or enhanced review. If the number matches a dissolved or foreign-qualified record, preserve that status rather than replacing it with a parent or home-state entity because the name looks similar.

Company registration number formats by country are useful as input validation, not as proof of existence. A format rule can reject an impossible ACN, a mistyped UK number or a Singapore UEN in a field that expects another country’s identifier. It cannot confirm that the entity exists today, that the record is active, or that the number belongs to the counterparty in front of you.

Some official formats are relatively precise. ASIC says an ACN is a unique 9-digit number issued to a company and explains that it is distinct from the ABN. UK tax guidance says a CRN is made up of up to eight numerals or normally a two-letter prefix followed by up to six alphanumeric characters, and that accurate CRNs matter for data matching and risk assessment. California has recently moved newly registered corporations, LLCs and LPs to a 12-character ID beginning with “B”, while older entity numbers continue to exist.

Other identifiers are deliberately wider than companies. Singapore’s UEN covers many registered entity categories, not only companies. Canada’s business number can be found through tax or registry routes and may arise through CRA registration, federal incorporation or certain provincial registrations. India’s company master data combines CIN with registration state, registrar and status fields. A global intake form must therefore store the identifier type, not only the identifier value.

The control is to build a validation stack. First, check syntax for the declared country and identifier type. Second, search the issuing register or an authorised source. Third, compare returned fields to the submitted business. Fourth, record whether the result proves registration, status, tax identity, licence, public-company filing or another narrower fact.

Teams often inherit a single text field called registration_number. That may work for one domestic market, but it creates avoidable ambiguity once the product accepts foreign suppliers, multi-state US entities, branches, partnerships, charities or tax identifiers. The fix is not to ask the customer for more unexplained numbers. The fix is to ask for the purpose of the number and preserve the source context.

Use this checklist when turning a registration-number field into evidence that a reviewer can defend later:

• Store country and subnational jurisdiction separately. For US records, state is usually essential; for some countries, local court, province or issuance agency may also matter.
• Store identifier type. Examples include company number, state entity number, file number, ACN, UEN, CIN, EIN, ABN, VAT number, business licence and LEI.
• Store issuer and source. Use the official register where practical; if an aggregator supplies the record, keep its source, retrieval time and registry reference.
• Keep legal name, previous names, entity type and status as returned fields, not as one normalised label.
• Separate retrieved from verified. A record can be retrieved successfully while the match remains unresolved because the address, status or entity type conflicts with the submitted counterparty data.

The strongest implementation pattern is claim-based. Instead of asking whether a company is “verified”, ask which claim each identifier supports. This avoids two common errors: treating a tax number as proof of incorporation, and treating a registry number as proof of ownership or authority.

For example, an LEI can be valuable in financial-market workflows because GLEIF describes it as a unique 20-character code linked to reference information about a legal entity. But an LEI is still a distinct identifier system and should be connected back to the local registry evidence where the decision depends on legal existence, local status or filed company data.

A company-data API or internal registry service should return unresolved states, not just failed states. “No record found” is different from “record found but inactive”; “official source unavailable” is different from “identifier format invalid”; and “ownership not disclosed by this register” is different from “ownership contradicted”. Those differences decide whether the next step is customer correction, registry refresh, manual review, document request or rejection.

The public web is crowded with introductory definitions and country lists. The harder question, and the one enterprise teams need answered, is this: what evidence must sit beside the company registration number so that a later reviewer can understand exactly what was proven?

The answer is a compact receipt. It should say: identifier 09410808; identifier type Companies House company number; jurisdiction United Kingdom, England and Wales where applicable; entity name Global Data Intelligence Limited; source Companies House; retrieval date 2026-09-17; observed status Active; fact supported legal existence and current register status at retrieval; facts not supported ultimate ownership, complete compliance or authority of any individual to act.

Recent registry and reporting changes make this more important rather than less. The UK government’s September 2026 reporting-overhaul announcement points towards more digital corporate reporting. Open registry data and APIs can make retrieval faster, but they also expose weak assumptions: stale snapshots, changed formats, mismatched states, missing ownership and identifiers that look right in one jurisdiction but mean something narrower in another.