Use casem&a target screening

M&A target screening with official company records

Enrich an M&A target list with official company, ownership, filing and source-limitation evidence.

dossaro gives an agent repeatable register primitives for resolving target companies and collecting source-backed profile, ownership, document and filing evidence. The agent keeps the screening logic and produces the final longlist; dossaro supplies the evidence layer.

Updated July 28, 2026

Run this exact task

Install dossaro, then continue the research

The setup guide lets a capable agent add the remote MCP, start OAuth with the user and return to this task.

Install-and-run prompt
Review the dossaro MCP setup guide at https://dossaro.com/agent-setup/prompt.md, configure dossaro when possible, complete OAuth with the user, then perform this task: Screen this target list by resolving each legal entity, collecting relevant profile, ownership, document and filing evidence, recording source limitations per row, and producing a review queue without treating missing public evidence as a negative fact.

Direct answer

Official registers are most useful in M&A screening after a commercial longlist already exists. They help verify the legal entity behind each target, retrieve evidence, surface ownership or filing questions and create a review trail.

dossaro does not select acquisition targets or make an investment decision. It gives the calling agent structured source operations so the agent can apply the user's screening criteria consistently.

Define the screening contract

Specify the jurisdiction, target identifiers, required evidence and review conditions. Separate deterministic register checks from subjective commercial scoring.

Resolve every target

Match each row to a legal entity. Preserve ambiguous and unresolved rows instead of silently choosing the first similar company.

Collect relevant evidence

Depending on the mandate, collect:

  • legal name, number, status and legal form;
  • officer or representation evidence;
  • direct shareholder or disclosed-control evidence;
  • relevant filings and document references;
  • financial-publication metadata;
  • insolvency or regulatory evidence where supported.

Build the review queue

The agent should classify rows as confirmed, ambiguous, unavailable, source-limited or requiring document review. An empty field must not automatically become a disqualifying result.

Ownership-heavy mandates should use the private-company owner workflow. Document-heavy mandates should use company-register document research.

Inputs and outputs

Recommended input columns:

  • target name;
  • website or known identifier;
  • expected country;
  • screening thesis;
  • evidence requirements;
  • relevant date.

Recommended output columns:

ColumnMeaning
Resolved legal entityThe company actually checked
Register and identifierSource-native identity
Evidence summaryConfirmed public-register findings
Document referencesFiles requiring or supporting review
Ownership/control noteDated, source-backed observation
LimitationMissing, blocked, paid or ambiguous evidence
Review reasonWhy an analyst should inspect the row

The calling agent can render already researched rows as a table. Rendering does not query registers or validate facts.

Jurisdiction differences

The same question can require different evidence by country. A German target may require a shareholder-list document, a UK target may expose PSC and filing evidence, and a Polish target may rely on KRS extracts. The German Handelsregister page demonstrates this jurisdiction-specific routing.

Cross-border groups require separate entity resolution for every legal company. Shared names, domains or directors are leads, not proof of ownership.

Review limitations

  • Public data is not a substitute for management information or full transaction diligence.
  • Register coverage varies materially by jurisdiction and legal form.
  • Historical and current ownership can diverge from the latest public filing.
  • Missing records must remain limitations, not screening failures.
  • Batch research should preserve row-level source references and ambiguity.
  • Final target ranking and acquisition decisions remain with the user and calling agent.

Run this exact task

Install dossaro, then continue the research

The setup guide lets a capable agent add the remote MCP, start OAuth with the user and return to this task.

Install-and-run prompt
Review the dossaro MCP setup guide at https://dossaro.com/agent-setup/prompt.md, configure dossaro when possible, complete OAuth with the user, then perform this task: Screen this target list by resolving each legal entity, collecting relevant profile, ownership, document and filing evidence, recording source limitations per row, and producing a review queue without treating missing public evidence as a negative fact.

Capability graph