Summary

  • LAPSED describes an LEI registration that missed renewal; the entity’s operating status occupies a separate field. The official definition does not establish that the business has stopped operating.
  • Daily files, annual revalidation and the acceptance requirements of a particular transaction are different things. Preserving those distinctions makes a refusal easier to explain and cheaper to route to the right remedy.

A renewal date is a poor coroner. It can tell you that a task was not completed on time. It cannot, by itself, tell you that a company has died. Yet attach the word LAPSED to a business identifier, paint it red and the temptation to treat the whole business as invalid becomes considerable.

The Legal Entity Identifier, or LEI, is a 20-character identifier linked to reference information about a legal entity. Its commercial purpose is to let different records point to the same subject. Renewal maintains the information around that subject. One supplies continuity; the other supplies a discipline for keeping the evidence current. Destroying continuity whenever maintenance falls behind is an expensive way to misunderstand both.

The interesting power sits downstream. A registry supplies a fact about a record. A buyer, platform or other data user decides what that fact will do to a transaction. It is at that handoff that an overdue confirmation can acquire a much larger job description.

The registry kept two columns for a reason

GLEIF’s LEI-CDF 3.1 specification separates EntityStatus from RegistrationStatus. The former concerns the legal entity. ACTIVE records that, at its last report or update, the entity reported itself legally registered and operating. INACTIVE records an established end to legal registration or operation, including circumstances such as closure or merger.

LAPSED belongs to RegistrationStatus. The registration has not been renewed by NextRenewalDate, and public sources do not establish that the entity has ceased operating. Turning that into “the company no longer exists” requires the user to add a conclusion. The field did not supply it.

Other statuses do other work. RETIRED concerns cessation without merger. DUPLICATE identifies the non-surviving duplicate registration that should no longer be used. ANNULLED concerns a registration found erroneous or invalid after issuance. A single internal bucket called “invalid company” discards the very distinctions needed to decide what should happen next.

Green is no excuse for lazy reading either. ISSUED refers to a validated, issued registration identifying an entity that was operating at the last update. ACTIVE has its own time qualification. Neither word watches the bank balance or promises delivery of the next order. A dated reference is useful evidence. Removing the date does not improve it.

Fresh delivery, older facts

The maintenance chain described in GLEIF’s data-quality programme starts with the registering entity. It supplies accurate information and notifies its managing issuer of changes. The issuer verifies the data against an authoritative local source, such as a national business register. Annual renewal brings the entity and issuer back to review and revalidate the reference data at least once a year.

The distribution machinery runs faster. Issuers publish their managed record files daily; GLEIF publishes aggregated files daily and runs daily automated quality checks on published data. A file collected this morning is not a fresh investigation of every company inside it. The envelope is new. The facts retain their own dates.

LastUpdateDate records the managing issuer’s latest information update. NextRenewalDate records the next renewal and recertification deadline for the entity. Registration-authority references and the local entity identifier provide a route back to the underlying register. Legal-entity events can also distinguish the date an event becomes legally effective from the date it enters the record. Those details are useful when someone needs to reconstruct what changed, rather than merely announce that the screen changed colour.

There are therefore separate clocks: when information was checked, when a file was delivered and when a particular business operation requires acceptable evidence. A daily download does not collapse the three into one.

A missing parent is not automatically a hidden parent

The Policy Conformity Flag adds another specific test. A conforming record has timely renewal and complete reporting about direct and ultimate parents, or an accepted reason for not reporting that information.

The accepted exception is part of the designed outcome. An absent parent name on a screen does not, on its own, prove concealment. Conversely, non-conforming means renewal or updating is needed. Which one matters. Sending a customer back to renew a record already renewed will not identify a missing relationship disclosure. It merely gives an unresolved problem another lap of the building.

GLEIF distinguishes this flag from its technical data-quality programme. Compliance with file formats and lifecycle rules, compliance with these reporting conditions, and the commercial health of a business are different questions. One reassuring badge cannot do the work of all three.

The refusal belongs to someone

The official LEI Search guide explicitly separates LAPSED from entity inactivity. It makes the corresponding distinction for Level 2 relationships: missed renewal does not establish that a relationship has ended. Users decide whether a state is acceptable for their use case; some use only ISSUED registrations or PUBLISHED relationships.

Where a particular transaction requires current registration, that requirement must be met. The reason for stopping can remain precise: the required renewal evidence is missing. Calling the company nonexistent adds a different claim. Both descriptions might stop the transaction today, but they send tomorrow’s repair down different corridors. One asks for current confirmation. The other can send staff towards closure, replacement and reconstruction.

Consider a hypothetical procurement system that severs a supplier’s identity link whenever it sees LAPSED. After renewal, old purchase orders, invoices and contracts must be reconciled with a new supplier record. Some of that extra work was created by the buyer’s own rule. An external source supplied the status; the buyer chose to treat a remediable condition as a break in identity.

Actual rejection and correction records are missing, so there is no measured loss total to attach to this mechanism. Its direction is clear enough: a specific deficiency narrows the remedy, while a blanket verdict expands the clean-up. “Identity invalid” is an efficient way to circulate a problem among people who have not been told what to fix.

Public LEI search is free and requires no registration. It exposes separate statuses and a change history. A person with evidence can also raise a data challenge, which goes to the issuer to consider with the entity whether the record should change. These are tools for checking and correcting decisions. A user who retains only a final red light, stripped of its date and source field, has chosen to throw some of those tools away.

The point of a common identifier is to avoid meeting the same company for the first time at every desk. Keeping evidence current and keeping identity continuous are compatible ambitions. Rebuilding the customer’s past because a renewal is late is not a sophisticated substitute for either. It is bureaucracy charging the market to repair its reading comprehension.