Skip to main content
IDM S.A. logo

IDM S.A. — Investor Relations & Filings

Ticker · IDM ISIN · PLIDMSA00044 LEI · 259400WNWSDRYM87YQ43 WAR Financial and insurance activities
Open in API
Filings indexed 584 across all filing types
Latest filing 2024-04-25 Audit Report / Informat…
Country PL Poland
Listing WAR IDM

About IDM S.A.

https://idmsa.pl/

IDM S.A. is a financial services company specializing in corporate consulting and capital advisory. The company provides a wide range of solutions for businesses seeking alternatives to traditional bank financing. Its services include strategic planning, advisory for mergers and acquisitions, and support for corporate transformations. IDM S.A. assists clients with capital operations, including transactions in the non-public market, pre-IPO preparations, and the issuance of securities such as stocks and bonds. With over two decades of experience, the firm has managed numerous successful capital-raising operations, focusing on delivering customized solutions tailored to the specific needs of each client.

Recent filings

Filing Released Lang Actions
zal19_6_oswiadczenie_sprawozd_2024-04-25_pl.xhtml.xades
Audit Report / Information Classification · 1% confidence The provided document text consists almost entirely of XML signature blocks, specifically containing elements like <Signature>, <SignedInfo>, <SignatureValue>, <KeyInfo>, and <QualifyingProperties>. This structure is characteristic of a digitally signed document, often used to verify the authenticity and integrity of an official filing or report. Crucially, the document text does not contain the narrative content, financial tables, or management discussion typical of a full report (like 10-K or IR). Instead, it references a file named '6_oswiadczenie_sprawozd_2024-04-25_pl.xhtml' within the DigestValue, which translates roughly to 'statement/report 2024-04-25'. Since the document itself is just the signature wrapper and not the content of the report, and given the context of corporate filings, this is most likely an announcement that a report has been signed and published, or it is the signature block accompanying a regulatory filing. However, without the actual content of the referenced report, and given that the text is purely technical metadata (the signature), it does not fit neatly into content-specific categories like ER, IR, or 10-K. It is a technical artifact of a filing process. The most appropriate general category for a technical or miscellaneous regulatory artifact that doesn't fit specific content types is 'Regulatory Filings' (RNS), or potentially 'Report Publication Announcement' (RPA) if we assume the signature implies the report is ready/published. Given the highly technical nature (XML signature), RNS is a safer fallback for non-content filings. FY 2024
2024-04-25 Polish
zal22_6_oswiadczenie_sprawozd_2024-04-25_pl.xhtml
Audit Report / Information Classification · 1% confidence The document text provided is extremely short (truncated to 15000 chars, but the total length is 2.4M chars, suggesting the visible text is just the HTML/CSS wrapper for a PDF conversion) and contains only HTML structure, CSS styling, and metadata tags (like 'title: Raport'). There is no substantive financial content, regulatory headers (like 10-K, AR, ER), or specific reporting period details visible in the provided snippet that would allow for classification as a specific financial report type (10-K, IR, ER, etc.). The document length is very large (2.4M chars), which usually indicates a full report, but the visible text is only boilerplate conversion code. Given the lack of content and the nature of the visible text being a wrapper for a document rendered via pdf2htmlEX, the most appropriate classification based on the provided context is the fallback category for miscellaneous or unclassifiable regulatory filings, or if we assume the underlying document is a report but we cannot read it, we must rely on the structure. Since the structure itself is not a standard filing format but a conversion artifact, and we cannot read the content, the safest classification is the general regulatory filing fallback, RNS, as per Rule 2: 'Regulatory Filings is the fallback for documents that do not neatly fit anywhere else.' However, since the document is clearly a large report that has been converted, and we cannot read the content, we must default to the most general category that covers filings not explicitly defined. RNS is the best fit for an unreadable/unclassifiable filing. FY 2023
2024-04-25 Polish
zal08_6_oswiadczenie_sprawozd_2024-04-25_2_pl.xhtml.xades
Regulatory Filings Classification · 1% confidence The provided document text consists almost entirely of XML digital signature blocks (Signature, SignedInfo, Reference, DigestValue, KeyInfo, X509Data, etc.). This structure is characteristic of a digitally signed document, often used to ensure the integrity and authenticity of regulatory filings or official reports in electronic formats (like XBRL or XHTML). The presence of Polish language elements ('oswiadczenie_sprawozd_2024-04-25_pl.xhtml') and references to Polish entities ('Enigma Systemy Ochrony Informacji Sp. z o.o.', 'Narodowy Bank Polski') suggests a filing from Poland. Since the content is the signature block itself and not the substantive report content (like an Annual Report or Earnings Release), and it doesn't fit specific categories like DIRS, DIV, or ER, the most appropriate general classification for a regulatory document whose content is primarily metadata/signature is the fallback category.
2024-04-25 Polish
zal21_5_oswiadczenie_firm_audytor_2024-04-25_pl.xhtml.xades
Audit Report / Information Classification · 1% confidence The provided document text consists almost entirely of XML digital signature blocks (Signature, SignedInfo, Reference, DigestValue, KeyInfo, X509Data, etc.). This structure is characteristic of a digitally signed file, often an attachment or the file itself being verified. The presence of references to files like "5_oswiadczenie_firm_audytor_2024-04-25_pl.xhtml" (which translates to 'statement of the audit firm') and the overall structure strongly suggest this is not the content of a standard financial report (like 10-K, IR, or ER), but rather the technical wrapper or metadata associated with a filing. Given the context of financial documents, a digitally signed document that doesn't fit a specific content category (like a presentation or a transcript) is best classified as a general Regulatory Filing (RNS), as it represents a submission mechanism rather than the report content itself. The document length is moderate (7399 chars), but the content is purely technical signature data, not narrative or tabular financial data. If the reference file name 'oswiadczenie_firm_audytor' (auditor's statement) were the primary content, 'AR' (Audit Report/Information) might be considered. However, since we only have the signature block, RNS is the most appropriate fallback for a technical/verification component of a filing. FY 2024
2024-04-25 Polish
zal15_5_oswiadczenie_firm_audytor_2024-04-25_pl.xhtml
Audit Report / Information Classification · 1% confidence The document text provided is extremely short and appears to be the raw HTML/CSS structure generated by a PDF conversion tool (pdf2htmlEX), indicated by tags like 'html', 'head', 'title: Raport', and extensive CSS styling. The actual content of the financial report is not present, only the container structure. The document length is very large (2.5 million characters), suggesting the full content exists but was truncated in the provided snippet, which only shows the header/style section. However, based *only* on the provided snippet, which contains no substantive financial data, keywords (like 10-K, Earnings Release, etc.), or regulatory identifiers, and given the context that this is likely an announcement wrapper or a poorly rendered file, the most appropriate classification based on the 'MENU VS MEAL' rule (Rule 2) for an unreadable or wrapper document that doesn't clearly state it's an announcement of a report is the general fallback category. Since the text is clearly not the report itself (10-K, IR, ER) but rather the underlying structure of a document rendered from a PDF, and it lacks any specific content to classify it further, 'RNS' (Regulatory Filings - general fallback) is the safest classification, although 'XLSX' (Financial Supplement Data) might be considered if the underlying file was known to be data, but the HTML structure points away from that. Given the ambiguity and lack of content, RNS is the best fit as a miscellaneous/unclassifiable regulatory artifact. Q3 2024
2024-04-25 Polish
zal17_5_oswiadczenie_firm_audytor_2024-04-25_2_pl.xhtml.xades
Audit Report / Information Classification · 1% confidence The provided document text consists almost entirely of XML digital signature blocks (Signature, SignedInfo, Reference, DigestValue, KeyInfo, X509Data, etc.). This structure is characteristic of digitally signed documents, often used for official regulatory filings or legal attestations where integrity and authenticity must be verified. The presence of references to files like "5_oswiadczenie_firm_audytor_2024-04-25_pl.xhtml" (which translates to 'statement of the audit firm') and the extensive cryptographic data strongly suggest this is the underlying structure of a formal report, rather than the report content itself or a simple announcement. Given the options, this structure is most commonly associated with the formal submission of an Audit Report or related information, especially when the content is heavily technical/metadata-focused rather than narrative financial results (like an ER or 10-K). If the document were a simple announcement (RPA/RNS), it would typically contain text stating the report is available. Since this is the raw, signed structure, 'Audit Report / Information' (AR) is the most appropriate classification, as it represents the attested core document structure. FY 2024
2024-04-25 Polish

Report missing filing

Can't find a specific document? Let us know and we'll add it within 24 hours.

We will notify you once the filing is added.
Report sent
Thank you. We will check the data and update it shortly.