Skip to main content
Prochem S.A. logo

Prochem S.A. — Investor Relations & Filings

Ticker · PRM ISIN · PLPRCHM00014 LEI · 259400Y049RUPUFT3G15 WAR Professional, scientific and technical activities
Open in API
Filings indexed 713 across all filing types
Latest filing 2022-04-28 Regulatory Filings
Country PL Poland
Listing WAR PRM

About Prochem S.A.

http://www.prochem.com.pl/

Prochem S.A., established in 1947, is an engineering company specializing in the design and implementation of investment projects. The company provides comprehensive, end-to-end services, from initial pre-investment concepts and design to turnkey delivery of facilities. Its core areas of operation encompass industrial investments, general construction, and environmental protection. Prochem serves clients across various key sectors, including oil and gas, chemicals, and energy. The company leverages extensive experience and modern technologies, such as Building Information Modeling (BIM), to deliver complex technical and organizational solutions for large-scale projects.

Recent filings

Filing Released Lang Actions
podpis
Regulatory Filings Classification · 95% confidence The provided document text consists entirely of XML structures related to digital signatures, specifically referencing 'Signatures', 'SignedInfo', 'SignatureValue', 'X509Data', and 'QualifyingProperties'. This structure is characteristic of an XML Digital Signature (XML-DSig) block, often used to secure regulatory filings submitted electronically via systems like the SEC's EDGAR or similar international filing systems. The presence of a ZIP file reference ('259400Y049RUPUFT3G15-2021-12-31-pl.zip') and the signing time ('2022-04-28T15:56:24Z') suggests this is the signature block attached to a primary filing document, likely an Annual Report (10-K) or an Interim Report (IR) from a Polish entity (indicated by CN=COPE SZAFIR, C=PL). Since the text itself is only the signature metadata and not the substantive content of a financial report, and it is a specific regulatory artifact, the most appropriate general classification for a non-content-bearing, mandatory regulatory attachment is 'Regulatory Filings' (RNS), as it doesn't fit the specific content categories (like ER, IR, 10-K) directly, but is a required component of the submission process.
2022-04-28 Polish
podpis
Regulatory Filings Classification · 95% confidence The provided document text consists entirely of XML digital signature blocks ('Signature', 'SignedInfo', 'KeyInfo', 'QualifyingProperties'). This structure is characteristic of documents that have been digitally signed for authenticity and integrity, often accompanying official regulatory filings in electronic formats (like XBRL or XML filings). The presence of multiple signatures, signing times (2022-04-28), and references to a ZIP file ('259400Y049RUPUFT3G15-2021-12-31-pl.zip') strongly suggests this is the signature metadata for a primary financial report covering the period ending 2021-12-31. Since the document itself is not the content of the report but the cryptographic wrapper, and given the year-end date (2021-12-31), the underlying document is most likely an Annual Report (10-K equivalent for the jurisdiction, which appears to be Polish based on issuer names like 'Krajowa Izba Rozliczeniowa S.A.'). However, since the text provided is *only* the signatures and not the report content, and there is no explicit mention of '10-K' or 'Annual Report' content, the most accurate classification for the *provided text* which announces the integrity of an attached file is a general Regulatory Filing (RNS), or potentially a Report Publication Announcement (RPA) if this XML block was the entire submission wrapper. Given the complexity and the clear reference to a specific year-end filing package (implied by the ZIP name), classifying it as the underlying report type (10-K) is often done when the signature block is the only provided context for a major filing. However, strictly following Rule 2 (Menu vs Meal), this is metadata *about* a filing, not the filing itself. Since RNS is the fallback for miscellaneous regulatory announcements, and this is a specific type of regulatory metadata, RNS is appropriate. If the underlying document was known to be the full 10-K, we would choose 10-K. Given the context of Polish filings often using XML signatures for annual reports, I will lean towards the most comprehensive annual filing type, 10-K, assuming this metadata pertains to the official annual submission, as the date points to a year-end filing.
2022-04-28 Polish
ESEF SSF GK Prochem S.A.
Annual Report (ESEF) Classification · 100% confidence FY 2021
2022-04-28 Polish
podpis
Regulatory Filings Classification · 95% confidence The provided document text consists almost entirely of XML structures, specifically a digital signature block (XML Signature/XAdES) containing elements like <Signature>, <SignedInfo>, <SignatureValue>, <KeyInfo>, and <Object> with <QualifyingProperties>. This structure is characteristic of digitally signed documents, often used to verify the authenticity and integrity of official electronic filings or documents. Crucially, the document text does not contain typical financial reporting language (like 'Balance Sheet', 'Income Statement', 'Management Discussion', 'Earnings Release', or specific quarterly/annual period references). Instead, it is the signature metadata itself. Given the options, this content does not fit neatly into any specific financial report type (10-K, IR, ER, etc.). It is a technical component of a filing. The most appropriate general category for miscellaneous or technical regulatory attachments that don't fit elsewhere is 'Regulatory Filings' (RNS), as this often serves as a catch-all for non-standard regulatory components or attachments. However, since the document is extremely long (over 6 million characters, though truncated), it suggests this XML signature block is likely an attachment or part of a much larger filing. If this were the *entire* document, RNS would be the best fit. If it's an attachment to a primary filing, classifying the primary filing would be ideal, but based *only* on this text, RNS is the most logical fallback for a technical/regulatory artifact.
2022-04-28 Polish
sprawozdanie z badania SF Prochem S.A.
Audit Report / Information Classification · 99% confidence The document text is titled "Raport Sprawozdanie z badania rocznego sprawozdania finansowego za rok obrotowy zakończony w dniu 31 grudnia 2021 roku" (Report on the audit of the annual financial statement for the financial year ended December 31, 2021) and contains extensive sections detailing the 'Opinia' (Opinion), 'Podstawa opinii' (Basis for opinion), 'Kluczowe sprawy badania' (Key audit matters), and 'Odpowiedzialność biegłego rewidenta' (Auditor's responsibilities). This content is characteristic of a formal Audit Report or the audit section within a larger annual filing. Since the definition for Audit Report/Information (AR) specifically covers 'Standalone audit reports, applied accounting principles, and results of internal or regulatory stress tests (excluding full Annual Reports)', and this document is explicitly an audit report ('Sprawozdanie niezależnego biegłego rewidenta z badania'), the classification should be AR. It is not the full 10-K, but the specific audit opinion/report. FY 2021
2022-04-28 Polish
podpis
Regulatory Filings Classification · 95% confidence The provided document text consists entirely of XML Digital Signature blocks ('<Signature>'). These blocks contain cryptographic information, references to a file named 'prochemsa-wd-sf_2021-12-31_pl.xhtml', and signing times (e.g., 2022-04-28). The presence of multiple signatures and references to an XHTML file strongly suggests this is metadata or an attachment related to a primary filing, rather than the filing content itself. The document length is relatively short (15355 chars, but the visible content is just signatures). Since the content is not the actual financial report but rather the digital proof of its authenticity, and it references a specific file ('prochemsa-wd-sf_2021-12-31_pl.xhtml') which likely contains the core report data (possibly an Interim Report or Annual Report based on the date '2021-12-31'), this structure is characteristic of a filing that has been submitted and digitally signed. Given the structure is purely technical/metadata and not the narrative report, the most appropriate classification is the general fallback for regulatory submissions that don't fit a specific content type, or a Report Publication Announcement if it were announcing the attached file. However, since this is the raw signature block, it is most likely part of a larger submission package. Without the actual content, and given the technical nature, 'RNS' (Regulatory Filings) is the safest general classification for submission metadata that isn't a specific report type.
2022-04-28 Polish

Browse filings by year

11 years

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.