Skip to main content
Ipopema Securities S.A. logo

Ipopema Securities S.A. — Investor Relations & Filings

Ticker · IPE ISIN · PLIPOPM00011 LEI · 259400QHG4C6452WLF35 WAR Financial and insurance activities
Filings indexed 693 across all filing types
Latest filing 2024-03-29 Regulatory Filings
Country PL Poland
Listing WAR IPE

About Ipopema Securities S.A.

https://www.ipopema.pl/?lang=en

Ipopema Securities S.A. is a financial firm specializing in investment banking and brokerage services for institutional clients. The company provides comprehensive financial consulting for the preparation and execution of public and private capital market transactions. Its brokerage division offers securities trading services on the secondary market. The firm's offerings are supplemented by company analyses and equity research.

Recent filings

Filing Released Lang Actions
Sprawozdanie biegłego rewidenta z badania skonsolidowanego sprawozdania Grupy Kapitałowej IPOPEMA za 2023 rok - podpis
Regulatory Filings Classification · 95% confidence The provided document text consists entirely of XML digital signature blocks (Signatures, SignedInfo, SignatureValue, KeyInfo, X509Certificate, etc.). This structure is characteristic of an electronically signed document, often used for regulatory filings or official corporate documents in XML format (like XBRL or XHTML). The presence of a certificate issued to 'Krajowa Izba Rozliczeniowa S.A.' (Polish National Clearing House) and references to 'Ipopema_Securities_2023_BSSF_MSSF_SzB_PL.xhtml' suggests a Polish financial filing. However, the text itself is not the content of a financial report (like 10-K, IR, ER) but rather the cryptographic proof of its authenticity. Since the content is purely metadata/signature information and does not describe financial results, management changes, or shareholder votes, it does not fit the specific content-based categories (10-K, ER, MANG, etc.). Given the options, this structure is most likely part of a regulatory submission or a document that requires verification. Since it is not the report itself, and it is a specific type of regulatory artifact (a signature block), the most appropriate general category for non-standard, verified regulatory components that don't fit elsewhere is 'Regulatory Filings' (RNS). It is not an announcement of a report (RPA) because the document *is* the signed artifact, not a short notice pointing to it. The document length (5105 chars) is substantial enough to contain the full signature block, not just a header.
2024-03-29 Polish
Sprawozdanie biegłego rewidenta z badania skonsolidowanego sprawozdania Grupy Kapitałowej IPOPEMA za 2023 rok
Audit Report / Information Classification · 95% confidence The document text provided is an HTML structure containing CSS styling and metadata, which appears to be the result of converting a PDF document using a tool like pdf2htmlEX. The title tag reads "Ipopema_Securities_2023_BSSF_MSSF_SzB_PL.xhtml". The content itself is highly technical, related to document rendering, and does not contain typical financial report narratives, tables, or explicit regulatory headers (like 10-K, AR, ER, etc.). Given the nature of the input—a raw, converted document structure that doesn't fit any specific financial reporting category (like Annual Report, Earnings Release, etc.)—and the fact that it is a document file that has been processed, the most appropriate classification is the general fallback category for miscellaneous or non-standard filings. Since the document is not a standard report but rather a file representation, and it doesn't announce a report (ruling 2 does not apply as the length is very large, suggesting the content *is* the report, albeit in a raw format), I must choose the best fit. As it is not a standard report type, I will use the Regulatory Filings (RNS) category as the fallback for non-standard or miscellaneous documents that don't fit the specific definitions. FY 2023
2024-03-29 Polish
Ocena Rady Nadzorczej sprawozdań finansowych i sprawozdania Zarządu
Audit Report / Information Classification · 95% confidence The document text provided is highly technical, containing HTML structure, CSS styling, and references to 'Consolia XBRL Tools v2.10.22.0' and a title 'Raport' (Report in Polish). The document length is substantial (498,959 chars), indicating a full report rather than a brief announcement. The presence of XBRL tools strongly suggests a structured financial filing. Given the length and the nature of the content (even though truncated, the structure points to a comprehensive document), it is likely a major periodic report. Since the text does not explicitly mention '10-K' or 'Annual Report' but is a comprehensive report, and it is not clearly an Interim Report (IR) without more context, I must rely on the structure. However, the presence of XBRL tools is common across many SEC filings (10-K, 10-Q, etc.). Since the document is very long and appears to be a full report, and without explicit quarterly markers, the most appropriate classification for a comprehensive annual filing is 10-K, or if it's a non-US filing that mirrors an annual report, AR. Given the Polish language snippet ('Raport'), AR (Audit Report / Information) or 10-K (Annual Report) are possibilities. Since the length suggests a full report, and it's not explicitly an earnings release (ER) or a short factsheet (FS), I will lean towards the comprehensive reporting categories. If this were a US filing, 10-K would be the default for a full annual report. Since the context is general and the document is clearly a full report, I will select AR as a strong candidate for a comprehensive report that isn't the primary 10-K, or if it is a foreign equivalent. Given the ambiguity and the length, I will re-evaluate based on the definitions. 10-K is for the official yearly report. AR is for standalone audit reports. Since the text is too generic to confirm it's the full 10-K, but it is a large report, I will check for keywords. The text is mostly boilerplate HTML/CSS from a PDF conversion tool. Without clear financial statements or management discussion, classifying it as the full 10-K is risky. However, the sheer size (nearly 500k characters) strongly suggests a major filing. I will default to 10-K as the most comprehensive annual filing type, assuming this is the primary annual disclosure, as AR is usually reserved for standalone audit opinions. Q3 2024
2024-03-29 Polish
Oświadczenie Rady Nadzorczej w sprawie Komitetu Audytu
Audit Report / Information Classification · 95% confidence The document text provided is highly technical, containing HTML structure, CSS styling, and references to 'Consolia XBRL Tools v2.10.22.0' and a title 'Raport' (Report in Polish). The content itself is heavily truncated and appears to be the underlying structure of a rendered document rather than the narrative content of a standard financial filing (like a 10-K, ER, or IR). Crucially, the document length is very large (420,769 chars), suggesting it is a comprehensive report, but the provided text is mostly metadata and rendering instructions. However, the presence of XBRL tools and the general nature of corporate reporting suggest this is a formal filing. Since the text does not contain specific keywords for Annual Report (10-K), Earnings Release (ER), or Interim Report (IR), and given the context of a large, structured report, I must look for the most appropriate general category. If this were the actual content of a comprehensive annual filing, it would be a 10-K. If it were a comprehensive quarterly filing, it would be an IR. Since the text is mostly structural noise from a PDF conversion tool, and I cannot definitively identify the period or content type (e.g., 'financial statements' or 'MD&A'), I must rely on the fallback or the closest structural match. Given the massive size (suggesting a full report) and the lack of specific announcement language (ruling out RPA/RNS based on the 'Menu vs Meal' rule for short announcements), I will tentatively classify it as a comprehensive report. Since the text is in Polish ('Raport') and lacks US SEC identifiers, classifying it as a 10-K is risky. However, in the absence of clear quarterly indicators, the Annual Report (10-K) is the default for comprehensive yearly filings. Revisiting the definitions: The document is clearly a 'Report' ('Raport'). If it is a full annual report, it's 10-K. If it's a full interim report, it's IR. Without content, I cannot distinguish. I will check for any hints of 'financial statements' or 'MD&A'. The embedded text is too fragmented. Given the ambiguity, and the fact that it is a large, structured report, I will default to the most comprehensive category, 10-K, while noting the low confidence due to the corrupted text. *Self-Correction based on context*: The document is likely a full financial report, but the text is corrupted/structural. If it were a standard filing, the large size points to 10-K or IR. Since I cannot confirm the period, and the text is not an announcement, I will select the most likely comprehensive filing type, 10-K, as it is the primary annual filing. *Final check*: The text is too generic and structural to confirm 10-K over IR. If this were a real database entry, the metadata (like filing date/period) would be key. Lacking that, and seeing a large report structure, 10-K remains the best guess for a comprehensive filing. Q3 2024
2024-03-29 Polish
Oświadczenie Zarządu w sprawie sprawozdań
Audit Report / Information Classification · 95% confidence The document text provided is highly technical, containing HTML structure, CSS styling, and references to 'Consolia XBRL Tools v2.10.22.0' and 'pdf2htmlEX'. The title tag is 'Raport' (Report in Polish). The document length is very large (513,492 chars), suggesting it is a full, comprehensive report rather than a brief announcement. The content itself, although truncated and heavily encoded, appears to be the body of a formal filing, likely a periodic financial report given the context of XBRL tools often used for SEC/regulatory filings. Since it is a large, comprehensive report and not explicitly identified as a 10-K (Annual Report), the most appropriate classification for a comprehensive, non-annual financial report is the Interim/Quarterly Report (IR). The presence of XBRL tools strongly suggests a regulatory filing containing detailed financial statements. Q3 2024
2024-03-29 Polish
Informacja Zarządu dotycząca firmy audytorskiej
Audit Report / Information Classification · 95% confidence The document text provided is highly fragmented and appears to be the raw HTML/CSS/JavaScript structure generated by a PDF conversion tool (pdf2htmlEX), rather than the content of a financial report itself. Key indicators are the presence of extensive CSS styling, font definitions (like @font-face), and the title tag reading "Raport" (Report in Polish). Crucially, there is no discernible financial data, regulatory boilerplate (like SEC headers), or specific filing narrative (like 10-K, ER, or IR). Given the nature of the input—a technical rendering wrapper—and the lack of substantive content, it cannot be classified as a specific financial filing type (10-K, ER, IR, etc.). The most appropriate classification for a document that is essentially a container or a placeholder for a report, or a document that doesn't fit any specific category, is the general fallback category. However, since the document length is very large (375,164 chars), it suggests the *underlying* document was substantial, even if the provided text is just the wrapper. If we must assume this wrapper *is* the document being filed, it is not a standard SEC filing. If we assume this is the *result* of converting a report, and we cannot see the report content, we must rely on the structure. Since there is no announcement text (Rule 2), we cannot use RPA or RNS based on that rule alone. Given the ambiguity and lack of content, RNS (Regulatory Filings - general fallback) is the safest choice for an unclassifiable document structure. FY 2023
2024-03-29 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.