Does a register match prove that someone can sign the transaction documents?

No. Entity identity and signing authority are separate questions requiring their own evidence and legal review.

Reconcile entity identities in an EU acquisition data room

Executive summary

Use stable register identifiers to connect documents to entities. Keep name changes, branches, subsidiaries, and similarly named companies distinct in the diligence record.

Record the issuing register and retrieval date.

Distinguish a branch from a separate company.

Keep identity evidence separate from authority to sign.

Start with the transaction perimeter

An acquisition data room can contain documents from several group companies using similar trading names. Establish which entities are being acquired and which are included only as counterparties or group support companies.

Ask the deal team for its entity list and compare it with the supplied constitutional and register material. Preserve disagreements rather than silently standardising every name to the transaction shorthand.

Create stable identity fields

Record legal name, jurisdiction, register, registration identifier, registered address, and source date. Add former names and branch information in separate fields. The European e-Justice company search provides a route to information from participating registers through BRIS.

A register extract is evidence about the information it contains. It is not a complete assessment of contractual obligations, beneficial ownership, or signing authority.

Resolve a name-change example

Suppose an older customer agreement names a company under its former name while the closing checklist uses the current name. Match the identity through source evidence before treating the contract as belonging to another group entity.

If the identifiers do not match, request clarification. A similar address or shared director may suggest a connection, but it does not establish that two names describe the same legal person.

Connect identity to contract review

Tag each agreement with the verified contracting entity and preserve the name appearing in the document. This allows the team to compare the transaction perimeter with the actual obligation holder.

Keep guarantees, assignments, and novations visible. A group-level commercial summary can otherwise make a subsidiary obligation look as though it belongs directly to the target parent.

Hand over exceptions before closing

List unresolved identity questions with the affected document, evidence requested, and consequence for the transaction. Assign them to the relevant local adviser or deal owner.

Save the reviewed extracts and dates in the matter file. Refresh the information where the transaction process requires current evidence, and document the scope of that refresh rather than implying that an old download is current.

Sources and next steps

This is an editorial workflow guide for legal professionals. The suggested checks are our practical recommendations, not a statement that a regulator requires a particular software workflow.

European e-Justice: finding a company through BRIS

Explore Review Matrix and File Library, or review Judicio's regional coverage and limitations. Check the underlying source and your organisation's approved process before relying on an output.