Skip to main content
Welcome to Deloitte
If we have selected the wrong experience for you, please change it above.

European Union Travel Compliance Changes - Impact Analysis

The EU is increasing scrutiny over cross-border travel compliance

Europe’s digital shift: Why accurate business travel compliance matters more than ever

There is a significant shift underway in how European Union member states monitor and enforce cross-border business travel compliance. It is not happening through one single reform or headline change. Rather, it is being built organically through border systems, social security processes, digital portals and verifiable credentials. Compliance with the Posted Workers Directive (PWD) and A1 certificate obligations has always been a legal requirement. However, for businesses whose systems and processes may not have kept pace with the complexity of these obligations, the changing landscape means that any gaps will soon be easier to identify by the EU authorities.

Setting the scene: what the PWD requirements currently ask of businesses

Before looking at what is changing, it is worth revisiting what the current rules require. Many businesses will be keen to understand whether their existing processes are well prepared for the changes now taking shape across the EU's compliance and enforcement infrastructure.

The PWD does not, strictly speaking, relate to travel. It is focused on the cross-border provision of services, the fair operation of labour markets and posted workers’ rights. In broad terms, it applies where an employer sends a worker to an EU Member State temporarily to carry out a service on its behalf. Some jurisdictions also apply these requirements to employers outside the EU, which can create an unexpected obligation for business travel from outside the bloc. Where the rules apply, the host country’s core employment conditions, including minimum pay, working time and health and safety, generally need to be observed. In all Member States, subject to exemptions, the employer is also required to make an administrative notification before the posting begins.

The line between ‘business travel’ and ‘posting’ is not always straightforward. Attending a meeting, will often, but not always, fall outside the scope of a posting. Delivering a multi-day hands-on implementation at a client site will usually be much closer to the core risk area. The more difficult cases are the ones in between: the sales engineer spending three days configuring a system, the consultant running a paid workshop and leaving a deliverable, or the IT specialist travelling for a go-live. These are the scenarios where the correct classification can be genuinely difficult. Where a filing obligation exists, it applies regardless, and businesses need confidence that their processes are identifying these cases accurately.

Historically, enforcement in some jurisdictions was inconsistent, largely paper-based and mostly reactive. Authorities often found it difficult to evidence who had been where, for how long and doing what, in order to understand where organisations may have been non-compliant. As a result, gaps in processes were less likely to be identified by businesses, or result in enforcement action, which may have reduced the urgency for some organisations to invest in robust systems. That environment is set to change significantly in favour of the EU authorities.

The three forces reshaping the enforcement landscape

On 10 April 2026, the EU's Entry/Exit System (EES) became fully operational across Schengen borders. For non-EEA/Swiss travellers arriving from outside the Schengen Area, this is a significant development. Now, EES digitally records entry and exit, passport details, biometrics, date and location, and retains that data for up to three years, or five years where an overstay is detected. Importantly, this data does not sit only at the border. Under the EES Regulation, designated authorities, including those responsible for preventing and detecting criminal offences, can access the system. The wider direction of EU inter-agency cooperation also means that labour inspectorates are increasingly likely to benefit from this intelligence, whether directly or through structured information-sharing arrangements.

Consider what this means in practice. Previously, proving that a non-EEA/Swiss national had been in a particular Schengen Member State for a particular period required manual evidence: passport stamps, hotel receipts, travel records and internal data. EES creates an authoritative digital record of presence. It does not apply to EEA/Swiss nationals, but it does apply to a significant population of travellers arriving from the UK, the US, India and other major markets, many of whom are regularly deployed to EU clients by technology and professional services firms. There is also a wider risk. If non-compliance is identified for a non-EEA/Swiss national whose presence is evidenced digitally, enforcement authorities may then look more broadly at the employer’s mobile workforce, including EEA/Swiss nationals whose travel patterns can be evidenced through other records.

A further layer will be added by ETIAS, the European Travel Information and Authorisation System. Originally scheduled to start operating in the final quarter of 2026, but now delayed until at least 2027, this system will require visa-exempt non-EEA/Swiss travellers to obtain pre-travel authorisation before travelling to the Schengen area. Carriers will check this authorisation and border authorities will enforce it. Each application will also create a structured digital record of intended travel. This matters because EES records actual presence after the event, while ETIAS captures travel intent before arrival. Together, they create a clearer audit trail from intended journey to confirmed entry and exit.

Neither EES nor ETIAS directly creates a PWD filing obligation. However, that is not the key point. The relevant question is what happens when a labour inspectorate can evidence that a worker was present in a Member State for a defined period and there is no corresponding posting declaration. There may be legitimate reasons why presence does not require a declaration, such as personal travel, genuine business meetings in some locations, or conference attendance. However, once presence is digitally evidenced, the employer needs to be able to demonstrate why the trip was outside scope. The absence of a declaration does not, on its own, prove non-compliance, but it creates a clearer and more scalable starting point for inquiry.

Revisions to the EU's social security coordination rules were formally adopted by the EU parliament and Council of Europe on 28 September 2026. These are the rules that determine which country’s social security system applies to cross-border workers. Formal adoption is still underway, but the direction of travel is clear and changes to the rules impacting A1 applications and certificates will likely come into effect from 1 November 2028.

Under the revised rules, prior notification to home-state authorities, in practice an A1 application, will be required before work activity takes place in another Member State, subject to limited exceptions. Short-term activities, broadly defined as up to three consecutive days of work within any thirty-day period, may be exempt from that notification requirement in most sectors. Workers will also need to have been affiliated to their home-country social security system for at least three months before a posting begins. We will need to understand how this is implemented for new joiners who are immediately required to travel internationally for project work, which is a common scenario for senior hires and specialist project roles.

On its own, this is a social security change not an update to the PWD legislation. In practice, however, the two frameworks often apply to the same travel patterns and increasingly sit within the same enforcement conversation. Where a worker crosses a border to carry out substantive work, the questions “which country’s social security applies?” and “was a posting declaration required?” often arise together. The new social security requirements, particularly the need to make an A1 application before the posting, also create structured digital records. Each notification becomes a data point, and those data points can often be compared with other compliance records.

Perhaps the most directly relevant development for PWD compliance is one that has received less attention in the business press: the European Commission's proposal for a single digital declaration portal (eDeclaration) for posted workers. The European Parliament gave its approval in October 2026 for the regulation of this platform, enabling streamlining of the PWD process. This aims to reduce administration and increase compliance for both EU and non-EU service providers.

The concept is straightforward. It would create a single EU-wide portal, available in all official languages, through which posting declarations can be made using a standard form. The stated purpose includes reducing non-compliance and facilitating inspections. That wording matters. The portal is not only designed to make filings easier for businesses. It is also designed to create structured, searchable data that helps labour authorities identify who filed, who did not file and whether the overall compliance picture is consistent.

Alongside this, the European Social Security Pass (ESSPASS) project is developing digital, verifiable credentials for portable documents, including A1 certificates, which evidence home-country social security coverage. The ambition, aligned with the EU Digital Identity Wallet framework, is to enable real-time verification by inspectorates, institutions and, in a commercial context, potentially the client being visited. The direction is clear: the ability to produce evidence quickly and reliably will become increasingly important.

Why existing compliance processes need to be reassessed

Many organisations have compliance processes that are designed to manage business travel holistically, however the legislation and obligations are constantly evolving. Ensuring all requirements are identified and completed requires a sophisticated, coordinated approach within the organisation. Accurate compliance has always been a legal requirement. What is changing is the ability of enforcement authorities to identify where processes have not delivered the right outcome, and that shift makes it essential for businesses to review whether their current systems are fit for purpose.

Consider a technology firm that sends a consultant from the UK or US to a client in Belgium for a ten-day system implementation. If the trip is categorised internally as business travel and no PWD declaration is made, a compliance gap may exist. An A1 or Certificate of Coverage may be in progress because HR identified the social security point. EES records entry and exit. Once live, the eDeclaration portal will make the absence of a filing easier to identify where one might be expected. An inspector, using digital data rather than manual checks, may then be able to link presence, absence of declaration and social security activity into a more coherent compliance picture.

No single system creates that picture on its own. Taken together, however, these systems create a level of visibility that did not previously exist. While EES and ETIAS only apply to non-EEA/Swiss nationals, if a potential failure is identified through that population, it could lead to a wider review of PWD compliance across all travellers. In the short term, that review may be limited to one jurisdiction. Over time, the direction of travel points towards more cross-border data sharing and more scalable enforcement.

The change is structural. Enforcement has historically been reactive, involving site visits, complaints or targeted activity in higher-risk sectors such as construction or food processing. Digital infrastructure supports a different model: pattern-based, data-driven targeting. Repeated entries linked to the same employer, workers present for periods that exceed internal thresholds, or inconsistencies between social security documents and posting declarations are all patterns that will become easier to identify. The underlying legal obligations have not changed, but the ability of authorities to see into areas where compliance processes may have fallen short is improving materially. Businesses that are not confident their systems and policies will achieve accurate compliance should treat this as the point where action is due.

What businesses can do: practical steps to ensure compliance processes are fit for the future state

The positive point is that clearer EU direction and improved technology give businesses both the reason and the opportunity to build more robust programmes. The starting point should be practical and focused on the areas where compliance obligations are most commonly triggered.

The most significant change many organisations can make is to build a meaningful activity classification into the travel approval process. The question is simple but important: is the traveller going to carry out a service, or to discuss one? Meetings, negotiations, governance and oversight are often outside the scope of compliance requirements, although the exact nature of the activities are key. Configuration, training delivery, auditing, hands-on implementation and embedded consulting are much more likely to create PWD obligations and A1 applications in due course.

Travellers should be required to select from a defined list of activity types, with that selection linked to an automated compliance workflow. This helps prevent a common failure point: a technical specialist being treated as a business traveller when, in substance, they are carrying out posted worker activity. Capturing the purpose of travel is also important for immigration analysis, as it supports the assessment of whether a business visa or work permit is required.

Historically, PWD and social security have often been managed by different teams, with different advisers and different timelines. That separation is becoming harder to sustain. The revised social security coordination rules, the A1/ESSPASS direction and the eDeclaration proposal all point towards greater convergence. An A1 application and a posting declaration are increasingly likely to be compared, and a mismatch between the two may create an obvious red flag.

Under the new social security rules, this could become one of the biggest practical risks for clients. Intra-EU travel will come into sharper focus through A1 filings. Travel that previously left limited external evidence because of the Schengen area may now create a clear compliance record. If an organisation focuses on A1s without considering PWD, authorities may have a clearer route to identify gaps in the wider compliance process.

Bringing the workstreams together, even if this is done in stages, can materially reduce the risk of inconsistency that digital enforcement is now better placed to detect.

For trips that genuinely are business visits, such as internal meetings, sales discussions or conference attendance, there may be no PWD filing obligations and the A1 requirement may also fall away under the revised framework. However, with EES creating a clear record of presence for non-EEA/Swiss travellers, “they were only there for meetings” needs to be evidenced, not just stated. Meeting agendas, attendee records and confirmation that no billable deliverable was performed on-site are practical examples of evidence that can support a classification that no action was required for these trips. Even where businesses already assess pre-travel requirements and take appropriate action, retaining an audit trail for “no requirement” cases will likely be a change for many organisations.

Field service, including maintenance, repair, technical support and on-site troubleshooting, is one of the most under-managed areas of compliance. Trips are often short and unplanned, which is exactly why they can fall outside existing pre-travel controls for PWD. Social security changes within the EU mean that similar considerations will need to be applied in this area and will require action in many cases. These are also trips where the “doing” test is usually clear: a technician travelling to repair equipment is carrying out a service.

A pre-designed compliance workflow for field service deployments and highly mobile project workers is therefore important. This could include pre-approved declaration templates, document checklists, ownership points and clear thresholds for when a filing is required. This is more manageable than it may first appear and directly addresses one of the more structurally exposed areas of many travel programmes. 

The planned launch of ETIAS will introduce a new operational step for visa-exempt non-EEA/Swiss nationals. Carriers will check ETIAS status before boarding, so there is a clear travel disruption risk if authorisation is not obtained in time. It also creates additional compliance visibility, because ETIAS will form part of the structured digital record of a worker's intended travel. Preparing the relevant traveller population in advance, including traveller education and integration into travel management processes, is both operationally sensible and compliance-focused.

This is likely to be the most important step. If an organisation’s current processes do not consistently identify and act on filing obligations across all relevant travel, it should assess whether those processes are adequate given the direction of enforcement capability. The question is not whether enforcement has historically reached a particular type of trip, but whether the organisation's systems will produce the right compliance outcome when that trip is subject to scrutiny.

A structured review of the most common cross-border travel patterns, activity types, worker nationalities and destination Member States will usually identify a small number of scenarios where the compliance processes may not be delivering the correct outcome. Addressing those proactively is likely to be significantly less costly than responding after an authority review or client challenge.

The bottom line

The EU's digital transformation agenda is not, at its core, designed to make life harder for businesses. It is intended to reduce fraud, protect workers and create a more level playing field across borders. The eDeclaration portal is intended to make compliance easier. ESSPASS is intended to make verification faster. EES and ETIAS are primarily border management tools.

However, the cumulative effect is clear: better presence data, more structured declarations, more verifiable credentials and more consistent cooperation between authorities. Together, these changes create an enforcement environment that is much better able to identify non-compliance.

The question for businesses is not whether they should comply with PWD obligations and the developing requirements for A1 applications within the EU. That has always been clear. The more practical question is whether the current systems and processes will deliver accurate compliance in an environment where gaps are increasingly visible, evidence is more durable and enforcement tools are catching up with the policy intent.

For organisations that act now, the investment is more manageable and the advantage can be significant. Clients, regulators and procurement teams will increasingly expect evidence of a mature, digitally ready compliance programme. For those that do not address process gaps, the consequences could extend beyond an individual penalty in a single jurisdiction. The digital processes within the EU create a durable data record that can form the basis for broader and more sustained regulatory scrutiny.

The practical next step is to review where current travel, social security and posting processes are not joined up, and to focus on the scenarios where repeated travel, client-facing activity or short-notice deployment are most likely to give rise to compliance obligations.

Did you find this useful?

Thanks for your feedback