Video: Countdown to Slovakia 2027: Preparing for Mandatory E-Invoicing and Digital Reporting | Duration: 1720s | Summary: Countdown to Slovakia 2027: Preparing for Mandatory E-Invoicing and Digital Reporting | Chapters: Session Welcome (1.14s), Slovakia E-Invoicing Mandate (56.58s), Implementation Timeline (164.815s), Applicability and Scope (327.065s), Transaction Scope (471.565s), Reporting Obligations (601.3s), Pebble Network Model (677.78s), PEPPOL Network Requirements (841.435s), Regulatory Updates (1066.525s), EU Directive Context (1231.735s), Q&A and Conclusion (1315.785s)
Transcript for "Countdown to Slovakia 2027: Preparing for Mandatory E-Invoicing and Digital Reporting": team here at Source. Lots on the agenda today, so I'll be brief. Today's session is being recorded, and we'll be sending link straight to your inbox once it's ready. The q and a panel is open, so please drop your question in as we go. We'll do our best to answer as many as possible live. Anything we don't get to, we'll follow-up with you directly after this session. You'll also notice the related content box docs on your screen. That's where you can grab today's slides and explore any additional resources we put together for you. And one last thing, if you run into any technical difficulties, hit the question mark icon at the bottom of your screen, and someone will be on hand to help. Now it's my pleasure to hand over to today's speaker, Stanislava Filchiva from our regulatory analysis team. Hello. Thank you, Serene. Hello, everyone. Thank you all for joining today's session. Most Slovakia's move to mandatory invoicing. My name is Stanislava. I'm part of the Solvos Regulatory team and I have an extensive professional background in finance and accounting before moving obviously to e invoicing and tax digitization space. I'm happy to have you all on board today. Before we dive in, a quick look at where we are headed. We will start with the big picture, the key dates and milestones between now and 2030, Then we'll get concrete about who's actually affected by the mandate, which businesses, which transactions. From there, we'll open up and discuss the pepl five corner model. We'll cover the latest regulatory developments ongoing in the country, including a draft amendment that's still being debated. And we will close with practical steps you can start on now, let's see. Whether you've been tracking this, for months or just recent to the topic, I hope we'll be able to, cover today all questions you may have. So let's start, at the beginning with, the timeline. Where, has this mandate come from? Where is it going? So Slovakia's move to mandatory invoicing hasn't happened overnight. It's been unfolding in stages since, 2025. It started with an act enacted in 2025, which lays the ground, full legal architecture for this transition. From, 01/01/2026, the beginning of this year, we're in what's called the voluntary phase. Businesses can start onboarding to the compliant network and test their systems. Even though nothing is mandatory yet, this is like a transition year. The biggest milestone is 01/01/2027. Basically, the mandatory go live date. From that point, domestic b two b and b two g invoicing and transactional reporting become a legal requirement, in the country. Then there is a second further out milestone, starting 07/01/2030 when the permanent regime takes effect and the mandate extends to cross border invoicing and digital reporting aligned with the European Union's VAT in the digital age directive or shortly known as VIDA. So here they are two go lives, date go live dates here, domestic one in 2027 and an EU wide one, a wide one in 2030. So what does go live actually mean in practice starting as of January 2027? There are four important things to remember buzzwords so to say. Scope it's b to b and b to g or business to business and business to government domestic transactions format. Invoices need to follow European norms sixteen nine three one using PEPO BIS billing three as the structured syntax, so PDF won't cut it anymore. Network. Slovakia uses decentralized five corner PEPPOL model, which we'll take a look at in short. Timing. Reporting happens either in real time or in five days depending on whether you are the supplier or the buyer side. Again, we're gonna take a look at this, shortly as well. So in one sentence, from 01/01/2027, all domestic, b to b, b to g transactions between established businesses in Slovakia, suppliers and buyers, are in scope of the e invoicing and e reporting obligation. Now, let's take a look at who does this actually apply to. This slide bundles together three separate questions and it's worth that we look at them separately. First, sending invoices. You must issue electronic invoices only if two things are both true for your business. You're established in Slovakia and you're registered as a VAT payer. Both, boxes need to be ticked, so to say, in order for you to fall into the obligation as a supplier. So this is the group, that drives the 2027 go live. A taxable person who is not registered, VAT payer is not caught up by this issuance mandate during the transitional period. I'm saying between 2027 and 2013. Second we have the receiving side so any recipient established in Slovakia who receives goods or services from a supplier obliged to issue an electronic invoice must be able to receive it via Pepo or the so called delivery service regardless of the recipient's own VAT registration status. So here for recipients, the scope is a bit broader. The only requirement is for the recipient to be established in Slovakia no matter of their VAT registration status. Businesses who are non VAT registered will fall also into the receiving complication, then they need to comply. The third point, reporting to the tax authority. From 2027, it's the same group as issuance basically who are in scope of the digital reporting. These are established VAT registered businesses. From 2030, the scope widens to include VAT registered businesses that are not established in Slovakia. Specifically for reverse charge, cross border supplies, intercommunity acquisitions, and triangulation transactions. Starting 2030, the scope broadens up. Let's take a look at the transactions in scope. So again we have here the transitional phase from January 27 until 2030 and from two thousand and thirty July onwards. From first of January twenty seven, only domestic transactions are in scope, B2G and B2B supplies between parties that are established and are in scope. Out of scope for now are business to consumer invoices, VAT exempt supplies. You can see the list on the screen. Cross border transactions as well are currently for the transitional phase out of scope. The 2030 is the same domestic logic, it's just extended outward to intra community European Union transactions. These transactions are added to in scope, again, aligned with VAT in the digital age. The exclusions remain, so basically B2C invoices, some simplified invoices up to contribute to your role, other transactions where no invoice is required at all. Again, everything is listed on the screen. Regarding the digital reporting, this process simply mirrors the invoicing scope with the intra EU cross border transactions added to the reporting picture from 07/01/2030. There is a distinction that usually confuses a lot of people. Invoicing and digital reporting are two separate obligations. So you can issue perfectly compliant electronic invoice and still have a separate duty to report data about it to the tax authorities in real time. The good news is that the way, Slovakia is setting up the obligation, for most of the businesses, this reporting will happen automatically. Looking at the supplier and the buyer side, so if you're the supplier, the reporting obligation is triggered the moment the invoice is issued. If you're the buyer, under the current law, you have five calendar days from receiving the electronic invoice. Though they will they are proposals for changes, but we're gonna take a look at this separately. How the report is made actually happens. So there are two ways to use a certified delivery service or a pepl access point. Your provider, in this case, your provider passes the data to the tax authority and at the same moment it delivers the invoice to the buyer. Basically, the taxpayer and the supplier side don't need to do anything extra for this. But if a taxpayer decides not to use a delivery service, then they're on their own, they need to submit the data separately PEPPOL network. So that mention of pebble bring us to the technical backbone of all of these, the pebble network and its five core model. There are three terms you will hear constantly repeating. So let's take a look at them now separately just to make them clear. The European norm, starting with the European norm, sixteen nine three one is basically the European semantic standard. It defines what data an invoice must contain and how it's structured regardless of the country. This is the rule, let's say. And PEPO BIS billing three is a specific syntax. Slovakia has chosen to carry, that data on its network so basically the European norm is the language and we can consider the PEPO BIS format as the dialect, the way the data is structured. At the end we have delivery service and it's not just a general term it's a defined legal concept in SovaClo with specific requirements for service providers. Who is in charge of all this? The Financial Directorate of the Slovak Republic, FRSR shortly. They act as the national pebble authority, which means that they accredit the service providers operating in the country, runs the central directory that routes messages between, the access points and taxpayers, and oversees ongoing network compliance. Slovakia, as already mentioned, decided to adopt a five, corner model. In the nutshell, each trading partner needs to engage with, a service provider at their end. So corner one is the supplier, corner two is the supplier's access point provider, corner three, you can see this on the right hand side, is the buyer's access point provider, and corner four is the buyer themselves. So that's the basic, standard for Cornell exchange. Let's call it as we know it in other countries like, let's say, Belgium. The what makes the, Slovakia's model five corner is the tax authorities own access point operated by the tax authorities themselves, FRSR, sitting inside the same pebble network as everyone. Their role is to collect the data that is reported by the supplier side, in this case, the access point of the supplier, and at the buyer side, the access point of the buyer. Five things matter most about how this work in practice. One, this is a post issuance. It's not a real time clearance. There are countries where the tax authority approves an invoice before, the invoice is considered issued. This is not the case. Here the data flows to the tax authority in parallel with no approval gate, which typically slows down delivery and the whole turnaround time of an invoice. This is a pure reporting without a validation like a semantic validation by the tax authorities. Two, it's, the reporting, that runs rights on delivery. So when your provider sends the invoice to the buyer's provider, at the same moment in parallel, they will fulfill the digital reporting complication to FRSR automatically. The same for the buyer side access point who will have up to five days to report the transactional data to the tax authorities. Three, it's, the way the five corners are orchestrating between each other. Here again, PEPPOL may sound standard. We have PEPPOL in Belgium and in other European countries, but each country has their specifics around the network. So here the specific the difference than the Belgium, obligation is that access points have the obligation to exchange between each other acknowledgments, which means that anytime of the transaction, that access points and their customers, the supplier or the buyer, will know what's the status of the invoice. So this is, an a mandatory acknowledgment that has to be exchanged between the access points. It doesn't feel like a inbox just drop the invoice and you never know what happens. So this is one of, the differences to the Belgium PEPO network. 4.4, the identity, in the system is provider specific. So the taxpayers' identity is provider specific and it's verified through the process of appointing an access point through the tax authority portal. So each taxpayer will need to go into the tax authority portal and appoint, through a special process, their access point chosen access point. Five, there is an alternative method provided. Again, something similar to Belgium. Non PEPO exchange is allowed only upon recipients' consent, so both sides need to agree. But, FRSR clearly favors PEPO as the default method and they actively encourage adoption by taxpayers. Something that's worth flagging is that every taxpayer in scope must be onboarded on Pepo. There is no option for non onboarding on PEPPOL even if taxpayers decide to use an alternative method. So PEPPOL is mandatory to the the onboarding PEPPOL is mandatory then in addition, there might be a separate, transmission channel. With the mechanics covered, let's turn something that's very much still moving. These are the latest regulatory, development. All information which I shared with you so far is enacted law, but there is amendment draft amendment on the table, proposing two changes. This draft is still in inter ministerial comment procedure. So it's not enacted yet. It's not, mandated. So the first proposed change concerns penalties in the first quarter after go live. The draft amendment proposes a relaxation. The tax authorities would be precluded from penalizing suppliers for invoice format or timing issues within the first quarter from January 1, until March 31. But there is an important caveat that the relaxation explicitly would not cover transmission channel failures. Mistakes in what you produce or when, for example, invoices, XML doesn't fully conform with the European norm or the pebble structure, a required data field is missing or it's wrong. This might get some breathing room not to be penalized, but a failed connection to the network will likely not fall within this relaxation period. So, there should be an attempt for the invoice to be exchanged, let's say. The second proposed change concerns buyer side reporting, and I already mentioned that. Right now under the enacted law, buyers must report receipt data within five calendar days. The draft would remove the buyer side obligation completely for the twenty twenty seven, two thousand and thirty transitional period. So what, during this period, transitional period, only the supplier side will be required to report transaction data. This does not include the obligation for the buyer to receive electronic invoices so the recipients will still have to be able to receive electronic invoices. So our recommendation and the most sensible one for everyone is to plan for the law that is still enacted today and, not to build the compliance, not to rely on this that it will become, an enacted law. So if it becomes an enacted law, it's just a bonus for everyone. But until then, let's assume it does not exist. So zooming out, for a moment, how does Slovakia's approach fit the bigger EU picture? The European video directive entered into force on 04/14/2025 and that's actually why Slovakia can mandate domestic b two b invoicing without separate European Commission approval. Vidoo gives this opportunity, to member states starting 2025. That's why we see obligations popping up quite quick between legislation and go live date. That's the reason there is the abolished approval of the European Commission. We can say that Slovakia is, one of the member states forerunners so to transpose, VIDA directive international law. So as you can see the they introduced domestic, mandatory domestic invoicing and also, they are already ready with their legislation as the 07/01/2030 when the, mandatory intercommunity invoicing need to be issued in, e invoice in electronic invoices. So all of this raises, the practical question, what do you do between now and go live? So there are five stages which I would also consider a checklist. So for stage one, we would recommend confirm your scope, verify your registration, status in the country, and map which of your transactions will actually require structured invoices, analyze data, check your, trading partners' master data to make sure that they tie with the reality. Stage two, select the Nexus point, your certified service provider, their Visa list on the Ministry of Finance website where you can see the ones which are, which are credited for now. Make sure that they are compliant and, of course, that they will serve, that they will serve you best. Meaning, it's not only the invoicing, but make sure that they will be able to cover also the in reporting part. Stage three is just a practical step of authorizing the ASP on the tax authority portal. After which in stage four, you'll be, listed in the directory as, recipient via PEPPOL. And stage five, the last one, the the last one is integrating, Go Live. So just to summarize the, five takeaways. The clock is running. January 27 is fixed. The scope is broad, but it's defined. PEPPOL is the backbone. So this the five corner model is how the tech the data actually flows in the country. There are two draft proposals pending but not enacted, so go for what is it what it is enacted. And the end preparation can't wait. So between selecting a provider and testing integration, leave time so you don't rush at the end for the call update. So that's everything I wanted to walk you through today. Thank you for your attention, and it's time for questions. So, Serene, the floor is yours. Back to you. Yes. Brilliant. Thank you, Stanislava. We covered a lot of ground today, and I know we have quite a few questions coming in. Let's take a couple before we close out, and we'll make sure everyone else gets a written response after the session. Yes. There are some great questions here, and let's take a few. So I'm starting with the first one. Can we pick an accredited provider we like, or do we have to match whatever our customers use? Thank you for this question. Practical question. And the question is the answer is positive. You can, appoint any accredited provider you feel will be able to serve your needs, will be able to meet your digitization needs not only to cover the current mandate but make sure to extend in case it evolves, to be able to cover also future obligation. This is actually one of the points of the five corner model. It's built so in such a way so that businesses can choose different providers, and they can still exchange invoices with each other without any frictions. So you don't need to match your trading partner's choice. It's important to that you're given freedom to choose the service provider who can best handle your compliance processes, not only in the country, but eventually also outside of the country. Okay. Then, I'm moving forward with the second one since we have four minutes left. We already send invoices electronically today as PDFs or in an older edit formats edit fact formats, doesn't that already count? Yeah. This is, like, always a question which always pops up in any country, not only Slovakia, so thank you for asking it. No. These formats on its own don't count, don't cover the obligation. So the mandate requires, structured electronic invoice. So either The dish. In the PEPPOL network that would be the PEPPOL billing three. This is for the country, the Ministry of Finance and tax authorities are encouraging for taxpayers to use. So it's not a PDF. It's not a legal, legacy EDI format. Actually, there is, FAQ, there is a question answered through the FAQs, the tax authority website. I encourage you also to take a look. There are some practical advices there. In cases there are taxpayers who produce already edifact, they recommend that the edifact or this legal a legacy EDI format to be converted in a European norm compliant document. Only once this is done, this will be the valid electronic invoice. This will count as the invoice original, the European norm compliant format. The same logic applies to PDF. Of course, it's readable by persons who understand that they're still in a turnaround within each country, but nevertheless, they are not original invoices. They are not structured for automated, processing, so they won't satisfy the obligation for in scope transactions. So, unfortunately, there are some additional steps to be done if you if that's your process today to be, compliant with the future. Okay. Yeah. Thank you, Before we sign off, a reminder to check the related content box. Today's slides are there along with the links to further reading. Thank you so much for your time today. It's been a pleasure having you with us. If today's session has sparked further questions or you'd like to talk through what Slovakias mandates means specifically for your business, our team is always happy to happy to chat. You can reach us at EMAinfo@Solas.com. We hope to see you at a future session. Take care, everyone. Thank you, everyone. Thank you.