Video: VAT & Intrastat Across Europe: Key Regulatory Changes | Duration: 1800s | Summary: VAT & Intrastat Across Europe: Key Regulatory Changes | Chapters: Webinar Welcome (6.6s), Speaker Introduction (69.16s), Session Scope and Data Focus (106.235s), Framework and Validation (209.49s), Session Structure Overview (247.365s), Poland JPK Updates (303.05s), Form Updates (542.245s), Slovenia DDVO Updates (724.31s), Romania VAT Updates (845.725s), Portugal VAT Changes (970.7s), Intrastat Thresholds (1131.63s), Action Plan & Recap (1304s), Q&A Session (1478.285s), Planning for 2027 (1606.835s), Closing Remarks (1726.94s)
Transcript for "VAT & Intrastat Across Europe: Key Regulatory Changes": Hello, everyone, and welcome to today's webinar. VAT and interest debt across Europe, key regulatory changes. I'm Kripali from the EMEA marketing team here at Sivos, and I'll be your host for today's webinar. So before I hand over to our speaker, I'll cover off some housekeeping. The webinar is being recorded today, and the recording will be emailed to you afterwards. So, if you do want a copy of the slides, then please download them from the documents tab today during the webinar. There'll also be time for some q and a at the end of the webinar, so please submit your questions in the q and a panel as we go along. And also, please take a look at the document section where you'll find links to some blogs, sign up to our newsletter, and also, our forthcoming webinars as well, and the slides are over there too. Over to you, Andre. Hi, everyone. Thank you for joining us today. My name is Andre Garica, and I'm a compliance service manager at Solvos. I've been with the company for over nine years, and, I have experience with compliance, filing, as well as advisory. In my day to day work, I see how regulatory changes affect our clients in practice. So not only the rules themselves, but the systems, data, and processes behind every return. So that's the angle I'd like to take today. Before we go through the agenda, I just want to set up the scope of today conversation. I want to answer one practical question. What is changing VAT returns and interest declarations across Europe, and what should your company do about it? So we will look at six countries for VAT reporting, Poland, Austria, Spain, Slovenia, Romania, and Portugal. Then we will look at the 2026 interest thresholds in Austria, Denmark, and Slovenia. One idea will come back throughout the session. These changes are rarely about a new tax concept. They are about data. So talking about identifiers, fields, mappings, and validation. That's important because a VAT return can be rejected even when the tax treatment hasn't changed at all, even if your business activity is still the same. Let me put this more simply. You can be selling the same goods to the same customers at the same VAT rate as last year and still have your return rejected. Just because a field is missing or in the wrong format. So when we talk about change today, we think less about tax law and more about data. So what we are covering and what we are not today? We're looking at periodic map reporting and interest up. So this is not an overview of invoicing or real time reporting, even though I know it's the most discussed topic today. But the two are closely linked, and you'll see an example shortly when I cover Poland. And it's not the only one. For every country, I will cover three things. What changed, when it applies, and what you should check. I will also like to keep I will also like you to keep three simple questions in mind. First, does the source data exist? Second, is it mapped to the right field? Third, has the output been tested against the validation rows? If you can answer yes to all three, you are in good shape. If not, you have found your action. So here is how the session is organized. The presentation will be divided in three parts. Part one covers the reporting developments country by country. Part two covers interest at and what the new thresholds means for filing obligations. Part three is the road ahead with a short action plan you can take back to your team. I will spend more time where systems are most affected and less on changes that are mostly presentational. As I said earlier and is worth repeating, our role changing is not always an obligation changing. A new form can mean real configuration work even when the tax treatment stays the same. So part one, VAT reporting development. Let's start with Poland. Poland is the biggest topic today, so we will spend a little bit longer here. So from February 1, two new structures apply, JPK v seven m three for monthly fires and JPK v seven k three for quarterly fires. They replaced the previous version. The purpose is to connect back reporting to CCEF, the national e... Invoicing system. They add two things, CCEF invoice identifiers and elements linked to the deposit round system. In practice, this work as sales or purchase record entry. Each sale and purchase line must contain either the 35 character accept identification number or the appropriate indicators such as auth, BFK, or d d I where accept number is unavailable or does not apply. So a single header header level mapping or a free text workaround is not enough. Let me give you a practical example. Imagine a purchase register with hundreds of line. In the past, it might have been enough for the overall file to be correct. Now each of those lines has to carry its own reference, either the accept number or the right indicator. If one line is missing is... If one line is missing it, the problem sits in that line, not in the file as a whole. That's why this is a data question more than a tax question. Timing matters too because was phased in. Receiving invoicing to... Through XF has applied since 02/01/2026. For issuing larger taxpayers, those above the steadily 2024 sales test started on February 2026 as well. Most other taxpayers started from 04/01/2026 with some exceptions, including unlimited one for small taxpayers. Note that the JPK change is separate from the self issuing phase. Every taxpayer filing JPK b seven uses the new structure, including smaller businesses and foreign registered companies not yet required to issue invoices in SAF. I want to stress this point because, it's one of the most common misunderstandings. So many businesses assume that they are not yet issuing SAF. The JAPK change doesn't concern them. It does. The two timelines are separate. So for many businesses, this is no longer, a project. This lie. The focus moves from testing to monitoring production. And monitoring production is a different exercise from testing. In testing, you control the data. In production, you see what really happens, Unusual supplies, corrections, late invoices. That's where gaps tend to show up. There are three things to check. First, review your live ERP and bump up ins. Does the identifier travel from invoice issued or receipt through the ERP and taxing engine into the JPK file? Second, monitor production errors and exceptions indicator. Watch for invoices that fall back to an indicator more often than expected. Third, if you are... If you correct the mapping, regenerate and returns you already prepare. The question for your team is simple. Can every invoice be matched to accept reference or valid indicator? The key message in the integration, accept and VAT reporting are one data flow, so they need coordinator owners. Poland is the most structural change. The next two are about forms and calculations. Austria and Spain show how a form change can affect reporting logic, not just layout. Austria first and briefly. The practical rule is to use the right version of the u 30 VAT return with official instruction for each reporting period. Check which version applies and whether your validation rule changed with it. It sounds basic, but using the wrong version of our form is one of the easiest mistakes to make, especially when the same team files across several countries and several periods. Spain status more detail. Order HAC twenty seven twenty twenty six. Updated the VAT returns and the invoice register, the SII. The reason is specific. New rules for fuels, meaning petrol, diesel, and biofuels, they leave a tax warehouse. The principal liable must now guarantee the VAT on the later sale, and one way to do this is to pay VAT in advance. That is where the new return elements come from. Modelo three zero three has a new identification field and a new box, number 112, for the prepayment. The register of issued invoices gets a new field to flag fuel deliveries from a tax warehouse. Models three two two and three five three apply from February 2026. For Modelo three zero three, the changes apply also from February 2026 for monthly periods and from the second quarter for quarterly periods. Modelo three ninety applies for the 2026 annual return, and the register changes apply to transaction from February 2026 if you don't trade in fuel. The new box may stay empty, But the file format also change, so you still need the right form version. So this is a good example of the distinction I mentioned at the start. For many businesses, nothing changes in terms of tax, but the return itself has changed, so the system that produce it needs to change too. A rule changing for a specific tech sector can still mean work for everyone who files the return. Three checks. Identify the transaction that fee... Each revised field, confirm the star... The source tax codes, and regression test the output. A change meant for one field can affect another. So reconcile the ERP, your work papers, and submitted return. Slovenia is a smaller change than an older one, but it shows the same principle. The DDVO form was updated in May 2025. It isn't new this year, but it's a good example of how small change can still matter. There are two additions additions, and both are optional. The first is an ID of records filled. It is filled in with the tax authority. When the tax authority prefills the DDBO form, the VAR records that taxpayer has submitted. That applies to records from 07/01/2025. The second is a section for the preparer's name and phone number. It isn't mandatory, but it is recommended because it makes coordination easier. New EDAF schemas are published at the same time, so you may ask, why does this matter if the fields are optional? Because optional doesn't mean irrelevant. So in practice, this is often where problems come from. Mandatory fields get attention, but the return won't go through without them because the because the the return won't go through without them. Optional fields are easier to overlook, and then nobody knows who is responsible for them. A new field can change the file structure, the validation, and how the return is displayed or exported. Also, since 07/01/2025, Slovenia has required electronic input and output ledgers. So the return and the ledgers should be reconciled together. So three steps. Confirm your reporting solution support the updated form and schema. Decide who completes the optional fields and write it down. Check the return reconciled to the ledgers. Even small metadata changes need a clear owner. Next is Romania. Romania has two topics, and I want to keep them separate. So the first is the VAT rate change. The old 19%, 9%, and five percent raise... Rates were replaced by 2111% subject to transitional provision. This took effect in 2025. So it is background, not news, but it still matters because historic transaction and correction can fall under the old rates. Your tax codes need the right effective dates. Think about a correction to avoid issue before the rate change. If your system automatically applies today's rate, the correction may be wrong even though the system looks up to date. That's why the effective date on each tax code matters as much as the rate itself. The second is Raulifactura, the national invoicing system. From 01/01/2026, invoices within scope must be transmitted within five working days of issue. No later than five working days after the statutory deadline for issuing invoice. This applies to relevant invoices issued by established taxpayers. Why does this belong in about return session? Because the return is built from invoice data. If invoices are made incomplete or classified differently, your periodic VAT reporting will not match. And this is delinquent Poland. In both countries, invoicing the VAT return and the VAT return are no longer separate words. The return depends on the invoices, so the new... The two need to tell the same story. Here as well of reactions. Confirm which taxpayers and transactions are in scope. Use tax codes with the correct effective dates, update your instructions and training so everyone uses the same rates and documentation classification. Now we go instead to see a change that is applying well ahead, which is Portugal. Portugal is a two step change, actually. So, the key is knowing which phases applies when. It comes from Port area 29820261, published on 07/16/2026. It updates the periodic web return, annex r, and the adjustment annexes. Phase one applies to period starting on or after 07/01/2026, so it is already live. It adds fields for the new group regime, including the dominant entities tax number. The tax authority previews the group declaration, and the dominant entity confirms it. It also adds fields for adjustment linked to reduced rate housing tied to item two forty two of list one. Phase two applies to previous starting on or after 07/01/2027. Section c... Section six changes. Box 24 is removed, and three new boxes, 27, 28, and 29, split the figures by rate, reduced, intermediate, and standard. There are further box plates and new fields for etax free operations. The thinking behind this is that the tax authority already received received detailed data through Safdie and certified invoicing software. A more detailed return lets it prefilled taxable amounts and tax. In other words, the more detailed the tax authority already has, the more it can prefill and the more closely it can compare your return with what it already knows. That's a trend worth keeping in mind across Europe, not just in Portugal. So to summarize timeline, phase one is now live for periods from July this year. Phase two comes in July next year. Two different days, two different sets of changes, and you need to apply each one of the right period. Practical approach, make sure phase one works for current periods. Start planning mappings, validation, and work papers for 2027 now. Test each phase against the right return period. And before you implement, check the latest return and model and official instruction because technical details can still be clarified. Now with Portugal, we have completed the section on the VAT returns. So now we're gonna talk a little bit about interest start. So with interest start here, the change is a number. The 2026 thresholds, which have applied since January 2026. On the slide, figures are shown as arrival first, then departures. So this being Austria, for example, €5,000,000 for arrivals and €12,000,000 for dispatches. Arrivals were pre... Previously 1,100,000, so that is a big jump. Denmark, 42,000,000 kronor for arrivals and 11,800,000 kronor for dispatches. There is also a 16,500,000 kronor export level, which decides your filing group and your deadline. Slovenia, €300,000 for arrival and €280 for dispatches, up from €240,000 and €270,000. A higher threshold may take some businesses out of interest rates, but the important is not to treat that as automatic. Let me explain why. So a higher threshold sounds like good news, And for subinthesis, it is. But Intrathat looks at each flow separately and at your values over the year. So a business that drops out in January can be back by summer, let's say. So in this case, I would say there are four points to consider. So first, assess arrivals and dispatches separately, of course. Allstate is a good example. If you were below the 2025 threshold for a flow, you are exempt for that flow in 2026. But if you reach the threshold during 2026, the obligation starts again from the month you reach it. Second, check you're using the right type of threshold and any separate statistical threshold. Third, keep a record of your assessment and check the country's rule before you stop submitting. Fourth, if you're close to a threshold, keep monitoring cumulative values throughout the year. So for Intraste, the message is a little different from VAT. So it's less it's less about systems and more about monitoring and documentation. Know where you stand, keep checking, and record your decision. So with these examples, we are going to lead to a broader conclusion. Let's take a step back. So across all these example, three teams stand out. First, what compliance is becoming data dependent? Poland's accept numbers, Slovenia's record ID, and Portugal's rate split boxes all rely on data being carried accurately from source to return. Second, shared ownership. Invoicing, ERP, VAT reporting, and compliance operation need to work as one team. Poland and Romania show this best. Third, test for tax correctness, not just technical acceptance. A file can pass the schema and still contain the wrong mapping. If you look back at all the countries we covered today, every one of them fits at least one of these teams, and most of them fit all three. Here is a simple action plan. Keep a regular... Regulatory change inventory. For each change, record the owner, the implementation date, the affected data mappings, tests on typical and exceptional transaction, and the approval evidence. And the note on proportion start early, but match the effort to how settled the rules are. Portugal's twenty twenty seventh phase deserves planning now while details must still be clarified. So let's go back to where we started with the three questions. Is the source data there? Is it mapped? Is it tested? If you take these three questions back to your team and ask them for each change we discussed today, you'll quickly see where you stand and where your next action is. So before we move on to question, I hope that today has given you a clear picture, not just what has changed, but what to check-in your own process. And, and, yeah, and we come to the end of this webinar. So, I'll thank you for your time. I'm happy to take question, and, and now pass it over back to group Harley. Group Harley, I think I think you're muted. Sorry. Yeah. Thank you very much. Thank you again for the webinar. We do have a few questions. For anyone that has a few questions, please continue to submit them in the q and a box. The first one is we don't sell fuel, but do the Spanish changes affect us at all? Okay. Yeah. So so that's that's a fair question. So, partially covered during the presentation, but I will I will make it more clear. It's, it's exactly, a, a good example of a point I made at the start. So that, our rule changing isn't always an obligation changes. So, the new rules are aimed at fuel leading a tax warehouse. So if you don't trade in fuel, the new box on the Modelo three zero three, Box 112 will probably just stay empty for you. But the the thing is that the return itself has changed. So, there's a new field, and the file format has been updated. So even if nothing changes in terms of tags, the system that produce a return still need to use the right version of the form. So also in this case, my advice is to check. So are you using the the updated form for the right period, which is, February 2026 for monthly filers and the second quarter for quarterly filers? Then, have your tax codes stay mapped to the right boxes? And, and then have you checked the output again? So a a change meant for one field can sometimes affect others. So it's important to use their... Double check you read the right form, and then, adjustment may not affect the output. So, so, yeah, it's always worth a quick check rather than assuming that you are not affected. Great. Thank you. And the second question is Portugal's second phase isn't until July 2027, and some details may still change. Why should we start now? Yeah. I I understand why it might feel early, but this is one change today where, what I'm saying, planning planning really pays off. So so from July 2027, the... There is the one box, which is Box 24 will be removed and split into three new boxes and one for for each VAT rate. So reduced, intermediate to standard. So, there are also more, there are more box splits and new fields for eText free. So it's not just a a new form. Your system really will need to show the figures by rate, and that means real mapping was. So if you previously had, you are confident of adding the figures, altogether, talks regardless of the rate. It's important that your system is up to date to, to match, the current requirements. So, so, yeah, so the good news is that you don't you don't need to build everything everything now. Of course, the keys to make the effort fit out, settle the rules are. So start with the question that won't change. Does your system already separate your figures by rate? Which task code tax code will feed this new box, and who owns these on your side? So, then closer to the day, check the latest official model and instruction before you build anything finer, of course. And don't forget, obviously, about phase one, of course, already live, for figures from from July this year. So make sure that's also working properly. Great. Thank you. We are out of time. So we're not we're not able to answer any more questions. But we will get back to each and every single person that has asked us a question. Wanna thank you for today, for all your time, and thank you for joining us. If you haven't already, don't forget to take a look at the document section on your screen and also the download the, presentation, PowerPoint today, as you're online. If you if you do think of any more questions, then, you know, please submit them and, we will be in touch. You can submit these questions at amiainfo@sophos.com. Also, please take, some time to, fill in the form, and, we'll be in touch. Finally, thank you very much for joining us, and thank you to Andrea for, hosting the webinar. Thank you, and we hope to see you again next time. Thank you, everyone.