Skip to main content
mBank S.A. logo

mBank S.A. — Investor Relations & Filings

Ticker · MBK ISIN · PLBRE0000012 LEI · 259400DZXF7UJKK2AY35 WAR Financial and insurance activities
Open in API
Filings indexed 2,223 across all filing types
Latest filing 2025-02-28 Audit Report / Informat…
Country PL Poland
Listing WAR MBK

About mBank S.A.

https://www.mbank.pl/indywidualny/

mBank S.A. is a universal financial institution that provides a comprehensive range of banking services to retail, corporate, and private banking clients. The company's product portfolio includes personal and business accounts, loans, deposits, payment cards, and insurance products. Active in the capital markets, mBank also offers investment banking services. The institution is recognized as a pioneer in digital finance, having established one of the first fully internet-based banks. It continues to lead in the development of mobile and online banking solutions, focusing on delivering modern, accessible financial technology to its customers.

Recent filings

Filing Released Lang Actions
Ocena Rady Nadzorczej na temat Sprawozdań Finansowych za 2024
Audit Report / Information Classification · 1% confidence The document text is extremely long (282,495 characters) and appears to be the full content of a complex financial report, likely in an HTML/XML format generated by a mandatory reporting system ("Asseco CMR (Comprehensive Mandatory Reporting) 1.58.1"). The presence of extensive structured data, tables, and detailed financial narratives, combined with the large size, strongly suggests this is a comprehensive annual or interim report, rather than a brief announcement. Since the document is comprehensive and not just an announcement of a report, the 'MENU VS MEAL' rule directs us away from RPA/RNS. Given the depth and length, it is most likely an Annual Report (10-K) or a comprehensive Interim Report (IR). Without explicit headers like '10-K' or '10-Q', and given the context of mandatory reporting, the classification leans towards the most comprehensive yearly filing, the 10-K, or the comprehensive periodic filing, IR. However, the presence of Polish language metadata ('xml:lang="pl"') and the sheer volume of data are typical of a full statutory filing. Since the text contains complex financial figures and detailed operational descriptions (implied by the length), and is not explicitly labeled as a quarterly report, I will classify it as the most comprehensive filing type available, the Annual Report (10-K), as it represents the full scope of mandatory reporting. Revisiting the definitions: 10-K is the 'Official yearly report covering company activity and full financial performance.' IR is the 'Comprehensive financial report for a period shorter than a year (e.g., half-year).' Since the document is massive and appears to be a full statutory filing, 10-K is the best fit for a 'full' report unless specific quarterly markers are present, which are not immediately obvious in the truncated text. If it were a quarterly report, it would be classified as IR. Given the ambiguity between a very large IR and a 10-K, and the general nature of 'Comprehensive Mandatory Reporting', 10-K remains the strongest candidate for a full-year filing. However, upon closer inspection of the content structure (which includes many references to financial figures and market movements typical of earnings/results), and recognizing that many large filings are often Interim Reports (IR) when not explicitly marked as 10-K, I will lean towards IR as a safer classification for a comprehensive, non-10-K statutory filing, unless the text explicitly confirms it is yearly. Since the text is too long to be an ER or a simple factsheet, and it is a full report, IR is highly probable for a comprehensive period report. Q3 2024
2025-02-28 Polish
Ocena Rady Nadzorczej mBanku na temat sytuacji mBanku za 2024
Governance Information Classification · 1% confidence The provided document text is extremely short, truncated, and appears to be the raw HTML/XML structure of a document, including font definitions and metadata, rather than the substantive content of a financial report. The document length is 566,740 characters, but the visible text is minimal and structural. Crucially, the text does not contain any specific financial reporting keywords (like '10-K', 'Earnings Release', 'Audit Report', 'Financial Statements') nor does it contain language indicating the release of a specific report (like 'attached is the full report'). Given the nature of the input (structural boilerplate) and the rule about short documents announcing reports, this is most likely a placeholder or an announcement wrapper that failed to load the main content. In the absence of specific content, the most appropriate fallback for a general regulatory/filing artifact that doesn't fit other categories is 'Regulatory Filings' (RNS). However, since the input is clearly a structural shell, and we must classify based on the definitions, if this were a real-world scenario where the full document was unavailable but this shell was filed, RNS is the best fit. Given the extreme truncation and structural nature, confidence is low, but RNS is the designated fallback.
2025-02-28 Polish
List Przewodniczącej Rady Nadzorczej mBanku do Akcjonariuszy
AGM Information Classification · 1% confidence The document text provided is extremely short (less than 5000 characters, as indicated by the metadata) and appears to be the raw HTML/XML structure of a document, including font definitions and base64 encoded data, rather than the content of a financial report itself. The presence of extensive font definitions and the structure strongly suggest this is a wrapper or a very minimal file. Given the context of financial reporting, such a small, non-content-rich file that likely accompanies a main filing, or is a placeholder, is best classified under the general regulatory fallback category. Rule 2 (The 'MENU VS MEAL' Rule) suggests that if a document is short and implies another report exists (though not explicitly stated here, the structure suggests it's not the full report), RPA or RNS should be considered. Since there is no clear announcement text, RNS (Regulatory Filings) is the most appropriate fallback for miscellaneous or structural files that don't fit the specific content-based categories (10-K, ER, IR, etc.).
2025-02-28 Polish
Podpis Prezesa Zarządu do Listu Prezesa Zarządu mBanku do Akcjonariuszy
Regulatory Filings Classification · 1% confidence The provided document text consists almost entirely of XML signature blocks (Signature, SignedInfo, Reference, KeyInfo, X509Data, etc.) and cryptographic data (DigestValue, SignatureValue, Certificates). This structure is characteristic of digitally signed regulatory filings or documents where integrity and authenticity are paramount, often found in XBRL or similar structured data submissions. Crucially, the reference URI within the signature block points to a file named: "mBank-ListCEO-2024-12-31-0-pl.xhtml". The presence of 'ListCEO' strongly suggests a document related to a list of Chief Executive Officers or senior management changes, which aligns with the 'Board/Management Information' category (MANG). Since the document itself is the digital signature wrapper and not the content of the report, and it clearly references a management-related document, the most appropriate classification is MANG, assuming the signature is attached to or is the primary indicator of the underlying management document. If this were purely a signature wrapper without content clues, RNS (Regulatory Filings) might be considered, but the specific filename reference points directly to MANG.
2025-02-28 Polish
List Prezesa Zarządu mBanku do Akcjonariuszy
AGM Information Classification · 1% confidence The document text begins with HTML structure tags and contains a <title>CEO letter</title>. The content itself is heavily truncated, but the presence of 'CEO letter' in the title strongly suggests this is a communication intended for investors or stakeholders, often accompanying a formal filing or serving as a standalone update. Given the context of financial reporting, a CEO letter is most commonly found within an Annual Report (10-K), an Interim Report (IR), or sometimes as part of an Investor Presentation (IP) or Earnings Release (ER). However, since the document is extremely long (423,573 chars) and appears to be a full document structure (indicated by the extensive base64 encoded font data and HTML/XML structure), it is highly unlikely to be a simple Report Publication Announcement (RPA) or a brief Regulatory Filing (RNS). The presence of a 'CEO letter' title within a large document structure points towards a comprehensive report. Without seeing the body content, the most appropriate classification for a document explicitly titled as a CEO letter, which is a key component of annual reporting, is the Annual Report (10-K), or potentially an Investor Presentation (IP) if it were structured as slides. Given the context of mandatory reporting implied by the 'Asseco CMR' generator metadata, 10-K is a strong candidate for a comprehensive annual document containing a CEO letter. If it were a quarterly report, it would be classified as IR. Since 'CEO letter' is a hallmark of the annual review, I will lean towards 10-K, acknowledging the ambiguity without full text.
2025-02-28 Polish
Podpis Audytora do Sprawozdania Audytora z badania Jednostkowego Sprawozdania Finansowego mBanku S.A. za 2024
Audit Report / Information Classification · 1% confidence The provided document text consists entirely of XML Digital Signature elements (Signature, SignedInfo, Reference, DigestValue, KeyInfo, X509Data, etc.). This structure is characteristic of a digitally signed file, often used to verify the authenticity and integrity of an underlying document. The reference URI points to "mBank_sprawozdanie_z_badania_2024_Bank.xhtml", which translates from Polish to "mBank_report_from_audit_2024_Bank.xhtml". The presence of 'sprawozdanie z badania' (report from audit) strongly suggests the underlying document is an Audit Report. However, the text provided is *only* the signature block, not the report content itself. According to Rule 2 (The 'Menu vs Meal' Rule), if the document is short and announces/contains the signature for a report rather than the report content, it should be classified as a Report Publication Announcement (RPA) or a general Regulatory Filing (RNS). Since this is a specific type of regulatory attachment (a digital signature block for an audit report), and RPA is for announcing the publication of reports, RNS is the most appropriate fallback for a non-content regulatory artifact that doesn't fit the specific report types (like 10-K or AR). Given the strong indication of an Audit Report ('sprawozdanie z badania'), classifying it as AR (Audit Report / Information) is also plausible if we assume the signature block implies the presence of the full report, but the strict interpretation of the provided text being *only* the signature block favors a filing/announcement category. Since 'AR' is defined as 'Standalone audit reports, applied accounting principles, and results of internal or regulatory stress tests', and this is the signature *for* such a report, I will classify it as AR, assuming the signature is attached to the report itself, which is common in regulatory filings where the signature block is submitted alongside the main document. FY 2024
2025-02-28 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.