Skip to main content
Decora S.A. logo

Decora S.A. — Investor Relations & Filings

Ticker · DCR ISIN · PLDECOR00013 LEI · 2594002F8HC0D6K6JI94 WAR Manufacturing
Open in API
Filings indexed 882 across all filing types
Latest filing 2024-04-26 Environmental & Social …
Country PL Poland
Listing WAR DCR

About Decora S.A.

https://decora.pl/en/

Decora S.A. is a manufacturer specializing in interior decoration and finishing products. The company is a leading European producer of flooring solutions, with a product portfolio that includes advanced flooring systems, such as vinyl flooring, and a comprehensive range of accessories like underlays, skirting boards, and floor profiles. Recognized as a 'FLOOR EXPERT,' Decora S.A. focuses on developing technologically advanced and high-quality products through its dedicated research and development efforts. The company is a major producer of floor underlays in Europe.

Recent filings

Filing Released Lang Actions
Raport_zrownowazonego_rozwoju_Grupy_Kapitalowej_DECORA_za_2023_wraz_z_Listem_Prezesa_Zarzadu_podpis
Environmental & Social Information Classification · 1% confidence The document text consists almost entirely of XML digital signature blocks (Signatures, SignedInfo, Reference, DigestValue, X509Data, etc.). The key piece of information is found within the `DataObjectFormat` description inside the signature properties: `filename="GK_DECORA_Raport_zrownowazonego_rozwoju_wraz_z_Listem_Prezesa_Zarzadu_2023_12_PL.xhtml"`. This translates to "Report on Sustainable Development together with the Letter of the Management Board 2023 12 PL". A report focusing on 'Sustainable Development' (Raport zrównoważonego rozwoju) aligns best with Environmental, Social, and Governance (ESG) reporting. Comparing this to the definitions: - 10-K (Annual Report) is too broad/incorrect form type. - AR (Audit Report) is incorrect. - SR (Environmental & Social Information) is the best fit for a Sustainable Development Report. Since the document provided is the *signature block* of the report, and not the report content itself, I must check the 'MENU VS MEAL' rule. However, the document length is 21,294 characters, which is substantial, suggesting it might be the full document or a significant portion, not just a short announcement linking to the report. Given the explicit content title ('Report on Sustainable Development'), classifying it as the content type (SR) is more accurate than classifying the signature block as a Report Publication Announcement (RPA) or Regulatory Filing (RNS), especially since the length suggests substance. Therefore, the document is classified as Environmental & Social Information (SR).
2024-04-26 Polish
Raport_zrownowazonego_rozwoju_Grupy_Kapitalowej_DECORA_za_2023_wraz_z_Listem_Prezesa_Zarzadu
Regulatory Filings Classification · 1% confidence The document text provided is extremely long (over 11 million characters) and appears to be the raw HTML/XML structure of a rendered document, including extensive CSS styling and font definitions. The presence of HTML tags, CSS, and the sheer volume strongly suggests this is a full, rendered corporate filing, not a brief announcement. Given the length and the nature of the content (which, despite being truncated, implies a comprehensive document structure), it is highly likely to be a major regulatory filing. Since the text itself does not explicitly contain headers like '10-K' or 'Annual Report', but represents a complete, complex document, and considering the context of financial reporting databases, the most appropriate classification for a very large, comprehensive filing that isn't explicitly identified as a 10-K or IR is often the general 'Regulatory Filings' (RNS) or, if it were a known comprehensive report, 10-K or IR. However, without specific content keywords (like 'Item 1. Business' or 'Consolidated Financial Statements'), classifying it as a specific report type is difficult. Given the 'MENU VS MEAL' rule, this is clearly the 'meal' (the full report content structure) rather than an announcement. Since it is a massive, complex document structure, and we must choose from the provided list, and it is not clearly an IR, 10-K, or ER, the most robust classification for a large, complex, unidentifiable filing structure is the fallback category.
2024-04-26 Polish
Sprawozdanie_z_badania_DECORA_SA_2023_podpis
Regulatory Filings Classification · 1% confidence The provided document text consists almost entirely of XML structure, specifically containing elements like "Signatures", "SignedInfo", "SignatureValue", "KeyInfo", and "QualifyingProperties". This structure is characteristic of an XML Digital Signature block, often used to secure regulatory filings submitted electronically to bodies like the SEC (e.g., XBRL/iXBRL filings). The document length is very large (4,044,895 characters), indicating it is a substantial filing, not a brief announcement. The presence of XML/XBRL tags suggests it is the content of a formal regulatory submission. Given the options, this is not a standard narrative report (10-K, IR, ER) or a simple announcement (RPA, RNS). However, since it is a large, structured, and signed document, it represents the core content of a filing. The presence of the XML structure itself, especially when truncated, often points towards the underlying data format of a major filing. Since the content is clearly a signed, structured document, and not just an announcement *about* a document, we must look for the most appropriate category for comprehensive, structured data. If this were a complete 10-K or IR, we would expect narrative text. Since the visible text is dominated by digital signature metadata, it strongly suggests this is the underlying data file of a submission. In the context of standard SEC filings, the most comprehensive annual report is the 10-K. If the content is primarily the structured data (XBRL/iXBRL) that underpins a filing, and we cannot definitively identify the narrative wrapper (like a 10-K cover page), the classification leans towards the most comprehensive report type or a general regulatory filing. However, the presence of the XML signature block is the most defining feature. This block is mandatory for many electronic filings. Given the massive size and the technical nature of the content (digital signature verification data), this is most likely the content of a major regulatory filing that has been signed. Without narrative context, classifying it as the comprehensive Annual Report (10-K) or an Interim Report (IR) is a strong possibility if the underlying data relates to those periods. Since the document is extremely large and signed, it is highly likely to be a primary report. Let's re-examine the definitions. None explicitly cover 'XBRL Data File'. The content is the *signed* data. If this were an Annual Report (10-K), the text would contain the full narrative. If it were an Interim Report (IR), it would contain the quarterly narrative. Since the visible text is purely technical signature data, it is the *proof* of filing integrity for some underlying report. In the absence of narrative, and given the technical nature, the safest classification for a large, signed, structured document that doesn't fit narrative categories is often the comprehensive report it represents, or the general regulatory fallback (RNS). Given the sheer size (4MB), it is definitely a full report, not just an announcement. The structure strongly suggests an iXBRL filing. Since the options don't perfectly match 'iXBRL', and 10-K is the primary annual filing, we default to the most comprehensive report type if the size warrants it, or RNS if it's too ambiguous. The presence of the signature block is common across all major filings (10-K, 10-Q/IR, Proxy). Given the ambiguity of the *narrative* content, but the certainty of it being a large, signed, structured filing, I will lean towards the general Regulatory Filing (RNS) as the most accurate description of the *visible* content type (a signed data block), unless there is a strong indicator for 10-K or IR. Revisiting the context: This is the raw, signed XML/iXBRL data. This data is the substance of a filing. If we assume this is the content of the most common large filing, 10-K, it's a possibility. However, the visible text is *only* the signature block and the start of the HTML/CSS wrapper for the iXBRL rendering. This technical structure is common to many filings. RNS is the best fallback for non-narrative, technical regulatory artifacts that aren't clearly a specific report type. *Self-Correction based on typical database behavior*: When the content is dominated by the digital signature wrapper of an iXBRL document, it is often the underlying data for a major filing (like 10-K or IR). Since the document is massive, it's not a short announcement. I will classify it as the most comprehensive report type, 10-K, assuming the underlying data relates to the annual cycle, as this is the most common large filing, while acknowledging the high technical nature. *Final Decision*: The document is extremely large and contains complex digital signature metadata, indicating a complete, formally submitted regulatory filing (likely iXBRL). While the specific report type (10-K vs IR) is obscured by the signature block, 10-K represents the most comprehensive annual filing. *Revisiting the structure*: The document starts with XML signatures and then transitions into HTML/CSS styling (`<style type="text/css">`, `body`, `.pf`, etc.) which is typical for an iXBRL rendering. This confirms it is a structured filing. Given the ambiguity between 10-K and IR based solely on the signature block, and the fact that this is the *content* of a filing, I will select the most general comprehensive report, 10-K, as the default for large, signed, structured data, or RNS if it's purely technical metadata. Since the size implies a full report, 10-K is a reasonable high-confidence guess for the underlying document type. Let's check for keywords that might point to 10-K vs IR. None are present in the truncated text. I will use RNS as the fallback for a document whose primary visible content is technical metadata (the signature block) rather than the report narrative itself, as RNS covers general regulatory announcements/filings that don't fit specific narrative categories. *Final Final Decision*: The content is the signed, structured data of a filing. This is a regulatory artifact. RNS is the best fit for non-narrative, technical regulatory documents that don't clearly map to 10-K or IR based on visible text. Confidence is moderate due to the signature block obscuring the actual report content.
2024-04-26 Polish
Sprawozdanie_z_badania_DECORA_SA_2023
Audit Report / Information Classification · 1% confidence The document text provided is heavily truncated and appears to be the raw HTML/CSS structure generated from converting a PDF file, indicated by the presence of `<html`, `<head>`, `<title>: Decora_SA_2023_BSF_PL.xhtml`, and extensive CSS styling related to PDF rendering (`pdf2htmlEX`). The title suggests a financial statement or report for 'Decora_SA' from '2023'. The file extension 'BSF' often stands for Balance Sheet/Financials. Given the massive document size (over 3 million characters) and the content being the underlying structure of a report rather than an announcement, this is highly likely the full financial report itself. Since it is a comprehensive report (implied by the size and 'BSF' in the title) and not explicitly an Annual Report (10-K), the most appropriate classification for a comprehensive period report (like a half-year or full-year financial statement document) is Interim / Quarterly Report (IR), or if it's the full annual set, it would lean towards 10-K, but without explicit '10-K' headers, IR is a safer bet for a comprehensive financial document that isn't the 10-K wrapper. However, given the context of 'BSF' (Balance Sheet/Financials) and the Polish language context (PL), this is a statutory financial filing. If this were the full annual filing, it would be a 10-K equivalent. Since the definition for 10-K is 'Official yearly report covering company activity and full financial performance,' and this appears to be the core financial data, I will classify it as 10-K if it represents the full annual performance, or IR if it's interim. Since the title contains '2023' and no explicit period (like Q1, H1), and it's a large financial document, I will lean towards the comprehensive annual filing category (10-K) as the most likely intent for a major statutory filing, although IR is also plausible if it's a non-US equivalent of a comprehensive report. Given the ambiguity between a full annual report and a comprehensive interim report based only on the title fragment, and the lack of explicit regulatory headers (like '10-K'), I will select 'IR' (Interim / Quarterly Report) as the general category for comprehensive financial statements that aren't explicitly labeled 10-K, acknowledging that for a non-US entity, this often covers the full year's statutory accounts. FY 2023
2024-04-26 Polish
Oswiadczenie_Zarzadu_do_jednostkowego_raportu_rocznego_2023
Audit Report / Information Classification · 1% confidence The document text provided is extremely short (only containing HTML/CSS structure and metadata) and does not contain any substantive financial or regulatory content such as financial figures, reporting periods, or specific form identifiers (like 10-K, ER, IR, etc.). The document length is 1,027,205 characters, but the provided snippet is just the boilerplate HTML/CSS structure for rendering a PDF viewer, which is common for documents that are being displayed online. Given the lack of content and the nature of the provided text (which appears to be the wrapper/viewer code rather than the report content itself), it is impossible to classify the actual filing type. However, based on the context that this is a 'Financial Document Classifier' and the input is a truncated view of a very large document (1M+ characters), the most appropriate action is to use the general fallback category for regulatory filings that cannot be specifically identified, or to acknowledge the inability to classify due to missing content. Since the prompt requires a classification code, and the text provided is essentially empty of content clues, I will default to the most general regulatory filing code, RNS, as a placeholder for an unclassifiable regulatory document, while noting the extremely low confidence due to the missing content. Revisiting the 'MENU VS MEAL' rule: This rule applies when a short document announces a report. Here, the document is large (1M chars), but the *provided text* is just the viewer shell. If the actual content were present, it would be classified based on that. Since the content is missing, I cannot classify it as 10-K, IR, etc. RNS is the best fallback for an unidentifiable regulatory document. Q3 2024
2024-04-26 Polish
DECORA_SA_sprawozdanie_z_dzialalnosci_2023_podpis
Audit Report / Information Classification · 1% confidence The provided document text consists entirely of XML digital signature blocks (specifically XAdES format, indicated by namespaces like 'ds' and 'xades'). These signatures reference a file named "DECORA_JSzD_2023_12_31_PL.xhtml" and contain timestamps from April 2024. This structure strongly suggests the document is not the primary financial report itself (like a 10-K or IR), but rather a container or metadata file confirming the authenticity and integrity of another document, likely a regulatory filing or report related to the period ending December 31, 2023. Since the content is purely technical validation/signature data and not the report narrative or financial tables, it falls best under the general 'Regulatory Filings' category (RNS) as a supporting document, or potentially a specialized 'XLSX' if the underlying file was a data supplement, but RNS is the most appropriate fallback for non-standard, technical regulatory artifacts. FY 2023
2024-04-26 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.