What Founders and Finance Teams Need to Know
If you are building or operating an electronic money institution, EMI accounting in the Czech Republic is not just ordinary bookkeeping with a fintech label. A Czech EMI sits at the intersection of the Payment Systems Act, CNB supervision, the Czech Accounting Act, and the sector-specific accounting decree for banks and other financial institutions. That means finance teams must think about statutory accounting, regulatory reporting, safeguarding, and internal controls as one connected system rather than as separate workstreams.
In the Czech Republic, the Czech National Bank is the supervisory authority for electronic money institutions, and CNB materials for payment institutions and EMIs sit under Act No. 370/2017 Coll. on Payment Systems. The CNB also makes clear that applications and notifications in this sector are filed electronically and that applicants should use the prescribed forms and methodology.
Why EMI accounting is different from ordinary company accounting
The core reason is simple: an EMI does not just sell a service. It issues electronic money, handles client-related flows, maintains safeguarding arrangements, and operates under prudential supervision. At EU level, the e-money framework requires EMIs to protect customer funds and to maintain own funds, so the accounting setup has to support more than tax filing or annual accounts. It has to produce a reliable picture of liabilities, safeguarded assets, fee income, operational expenses, and control evidence.
Czech accounting law also sets a high baseline. The Accounting Act requires accounting records to give a true and fair view, to be complete and conclusive, and to be based on documentary evidence. In other words, EMI accounting in Czech Republic is expected to be auditable, traceable, and aligned with the real economic substance of the institution’s activity.
The Czech accounting framework EMIs usually work under
For EMIs, the most important local accounting layer is not only the general Accounting Act, but also Decree No. 501/2002 Coll., the implementing decree for banks and other financial institutions. Its scope expressly includes electronic money institutions and payment institutions, and the decree sets rules for the structure of financial statements, accounting methods, and the chart of accounts. It also cross-refers, where relevant, to the general business-entity decree for topics such as cash-flow statement preparation and certain asset-accounting details.
That matters in practice because many founders assume an EMI can be accounted for like a standard Czech s.r.o. with only a few extra compliance notes. In reality, the accounting model is more specialized: the finance function needs a ledger design that can separate house money from customer-related balances, support reconciliations, and feed both statutory statements and CNB supervision. The legal architecture strongly suggests that the Czech market expects a finance setup closer to regulated financial services than to ordinary SME bookkeeping. This is an inference from the way the Payment Systems Act, the Accounting Act, and Decree 501/2002 fit together.
What finance teams need to get right first
The first issue is classification. Not every inflow is revenue, and not every balance on an EMI platform belongs in the same bucket. The accounting system has to distinguish between the institution’s own funds, operational cash, fees and commissions, liabilities connected with issued electronic money, and safeguarded client-related balances. The law does not hand you a one-line shortcut for all commercial models, so the classification logic has to match the actual product design and money flow. That is exactly why EMI accounting in the Czech Republic should be designed together with legal, compliance, and product teams.
The second issue is reconciliation discipline. If a company issues electronic money and maintains safeguarding arrangements, then the general ledger, payment operations, customer sub-ledgers, and safeguarding accounts must reconcile cleanly and regularly. From a control perspective, this is not just a best practice. It is the operational backbone for producing reliable statutory accounts and defensible supervisory reporting. That conclusion follows directly from the Accounting Act’s requirements for completeness and proof, combined with the prudential nature of the EMI regime.
The third issue is evidence quality. The Czech Accounting Act explicitly requires accounting entries to be supported by accounting documents and reliable records. For an EMI, that means finance cannot depend on screenshots, ad hoc exports, or manual spreadsheets that no one controls. The month-end close has to rest on system-generated data, approved adjustments, and clear ownership of reconciliations.
EMI accounting and CNB reporting are not the same thing
A common mistake is to treat statutory accounting and CNB reporting as identical. They are related, but they are not the same. The CNB states that payment institutions and electronic money institutions submit supervisory statements through the SDAT system and that the methodology there covers all required statements for those sectors. The CNB also notes that supervisory statistics are based on CNB decrees and directly applicable EU reporting rules.
In practice, this means an EMI needs a reporting architecture that can translate accounting data into supervisory outputs without constant manual rebuilding. If the general ledger cannot support CNB reporting, the institution ends up running parallel data worlds: one for accountants, another for compliance, and a third for operations. That is expensive, risky, and usually the fastest way to create inconsistencies under supervision.
Safeguarding is an accounting issue, not only a legal one
Founders often talk about safeguarding as if it belongs only to the legal or compliance team. It does not. For EMI accounting in the Czech Republic, safeguarding changes how finance should think about money segregation, reconciliation cycles, disclosure logic, and control evidence. Under the EU e-money framework, EMIs must protect funds received in exchange for electronic money, and material changes in safeguarding arrangements must be notified to the competent authority in advance.
From an accounting and control angle, that means your team needs a documented approach to how safeguarded balances are identified, how they are matched to outstanding e-money liabilities or relevant customer-related positions, how breaks are investigated, and who signs off on those controls. The law sets the prudential expectation; the accounting function turns it into a repeatable process.
AML, operations, and accounting must connect
Another reason EMI accounting in the Czech Republic is more demanding than ordinary bookkeeping is the AML link. Czech AML law remains a major part of the control framework for obliged entities, and EMIs operate in a supervised environment where transaction monitoring, customer due diligence, escalation, and suspicious activity workflows matter. Finance therefore cannot work in isolation from compliance. Adjustments, reserves, chargebacks, blocked funds, investigations, and suspicious-transaction handling all have accounting consequences or evidence consequences, even when the legal trigger sits outside the ledger.
The practical takeaway is that EMI finance teams should design a close process that speaks to compliance: unusual balances, frozen transactions, reconciliation breaks, and manual postings should not be invisible to AML or risk functions. In a regulated institution, clean accounting is part of the control environment, not just part of finance hygiene.
DORA now affects the accounting environment too
Since 17 January 2025, DORA has applied as the EU framework for digital operational resilience in the financial sector, and the CNB has said it expects affected entities to comply with the new duties from that date. The CNB specifically highlights ICT risk management, incident reporting, resilience testing, and third-party ICT risk as key areas.
For accounting, that means EMI finance can no longer treat system resilience as “someone else’s problem.” If the ledger, payment engine, reconciliation tooling, document storage, or reporting interfaces are disrupted, month-end close and regulatory reporting can fail with them. In other words, EMI accounting in the Czech Republic now sits inside a broader digital-resilience expectation, not just inside a classic bookkeeping framework.
The most common accounting mistakes EMIs make
The first mistake is treating issued e-money and client-related flows like ordinary revenue or ordinary cash. The second is building the ledger too late, after product and operations are already live. The third is relying on manual reconciliations that do not scale. The fourth is assuming the annual financial statements will somehow “sort everything out,” even though the real pressure comes from daily controls, monthly close, and supervisory reporting. These are practical inferences, but they follow naturally from the Czech and EU framework governing EMIs, accounting records, and supervisory data submission.
A more subtle mistake is underestimating the difference between tax accounting, financial accounting, and regulatory reporting. Czech EMIs may have all three in motion at once. A finance model that works only for corporate tax or payroll will usually be too narrow for CNB supervision and too weak for safeguarding evidence.
What a good EMI accounting setup looks like
A strong setup usually has five features. First, a chart of accounts and posting logic built around the actual EMI business model. Second, documented reconciliations between ledger, operational systems, and safeguarding balances. Third, close cooperation between finance, compliance, and operations. Fourth, reporting outputs designed to serve both statutory accounts and CNB supervisory returns. Fifth, governance over systems and data quality that is strong enough to survive audit, supervision, and DORA-style operational scrutiny. This is not a statutory quote, but it is the most practical reading of the current Czech and EU rule set.
Conclusion
EMI accounting in the Czech Republic is not simply bookkeeping for a payment startup. It is the financial-recording layer of a regulated institution. The Czech Payment Systems Act defines the EMI perimeter, the CNB supervises the sector and collects supervisory data, the Accounting Act requires a true and fair view supported by reliable evidence, and Decree 501/2002 provides the specialized accounting framework for financial institutions that includes EMIs.
That is why the right question is not “Who can file our accounts?” but “Can our accounting model support a real EMI?” If the answer is yes, the finance function becomes a strategic asset. If the answer is no, accounting quickly turns into one of the biggest hidden risks in the business.
Start a Real EMI
We help you structure, document, and defend your capital so it meets ČNB expectations — not just the legal minimum.
Book EMI Strategy CallFAQ: EMI Accounting in Czech Republic
What is EMI accounting in Czech Republic?
It is the accounting framework used by an electronic money institution operating under Czech law, combining the Czech Accounting Act, sector-specific accounting rules, CNB supervision, and EMI-specific prudential requirements.
Which accounting rules usually apply to a Czech EMI?
At the core are the Czech Accounting Act and Decree No. 501/2002 Coll. for banks and other financial institutions, whose scope expressly includes electronic money institutions.
Does EMI accounting include CNB reporting?
It should support it, but statutory accounting and CNB supervisory reporting are not identical. EMIs submit supervisory statements through the CNB’s SDAT methodology framework.
Why is safeguarding important for EMI accounting?
Because safeguarded funds, customer-related liabilities, and reconciliations must be reflected in a controlled and well-documented accounting environment. EU law makes safeguarding a core EMI obligation.
Does DORA affect EMI finance teams?
Yes. Since 17 January 2025, DORA has applied to affected financial entities and brings obligations around ICT risk, incidents, resilience testing, and third-party ICT risk, all of which can affect ledger integrity and reporting continuity
