Can a transfer be rejected?
Reviewed November 13, 2026 · 1 min read · How we check sources
Yes, but rarely. The current issuer may ask the entity to confirm that it authorized the move, and if the entity says no, the request ends. A record that has ended cannot move, and an open challenge can hold a transfer. Proof of the requester's authority prevents most rejections.
The confirmation step is the system's guard against hijacking. Without it, anyone could move a company's LEI to a provider of their choice and then change its data, such as its addresses or parent companies, in a record that banks and regulators rely on.
Other grounds are narrower. A record that has ended, such as RETIRED or MERGED, cannot move, and a transfer can be held while an open GLEIF data challenge or data correction is resolved. Silence is different from refusal: an unanswered confirmation usually delays the transfer rather than ending it, although some issuers close the request after a while.
The fix is the same paper used at registration: proof that the requester is authorized, usually a director listed in the registry or a letter signed by one. Sending it to the new provider at the start, and warning the registered contact to expect an email, removes most causes of rejection.