Skip to main content
← Back to all guidance

What happens if you overstay the Schengen 90/180 limit?

What a Schengen overstay can mean for an employee and employer, how EES helps authorities identify it, and how to check a trip before booking.

By James Walsh, Founder, ComplyEur

Published
02 August 2026
Updated
07 September 2026
Reading time
8 min read
What happens if you overstay the Schengen 90/180 limit?

The traveller-level and business-level consequences of exceeding the Schengen 90/180-day allowance, and why the margin for "we'll sort it out later" has narrowed.


The short answer

Overstaying the Schengen 90/180-day rule can result in an overstay record, removal, a fine, detention, or being prevented from re-entering. The outcome depends on the national law and the facts of the case; there is no single Schengen-wide penalty schedule.

For a business the fallout is broader than the penalty. An employee who cannot enter the Schengen Area is a resourcing problem on every live engagement they were assigned to, and the failure now sits in official EU records rather than in an internal spreadsheet nobody outside the company sees.

We say "can result in" deliberately. Enforcement varies substantially between member states and with the circumstances. ComplyEur is a tracking tool, not a legal service — for a specific situation, confirm the current position with immigration counsel or the relevant consulate.


What happens at the border

When someone leaves, or tries to re-enter, having exceeded their 90 days, border authorities have a range of options:

  • A fine, calculated under the individual member state's own rules.
  • A formal overstay record attached to the traveller's entry/exit history.
  • An entry ban or later refusal, restricting future entry when the relevant legal process and facts support it.
  • Referral for further immigration processing in more serious or repeated cases.

There is no single Schengen-wide penalty schedule. Each country sets its own fines and enforcement practice. A short overstay caused by documented unforeseen circumstances may be treated differently from a deliberate or repeated breach, but the relevant authority decides the outcome.

That discretion cuts both ways. It means a modest overstay may attract nothing worse than a fine and a warning. It also means you cannot plan around it, because the outcome depends on which border you happen to be standing at and who is on duty.

What an entry ban actually means

This is the consequence with the longest tail, and it is widely misunderstood as a country-level problem.

An entry-ban decision can lead to a refusal-of-entry or stay alert in the Schengen Information System (SIS), subject to the applicable legal rules and decision. Authorised border authorities across Schengen states can query SIS, so the effect may extend beyond the country that issued the decision.

The practical consequences run further than travel:

ConsequenceEffect
Wider refusal riskA valid SIS refusal alert can affect entry at other Schengen states, not just the issuing country
DurationSet under the applicable legal decision and individual circumstances
VisibilityA refusal alert may be available to authorised authorities across participating states
Future applicationsCan complicate later visa and travel-authorisation applications

For an employer, that table is the whole risk in miniature. A single border decision can remove someone from Schengen-facing work with little operational notice.


The day-count problem does not clear when they come home

This is the part that catches people out, and it follows directly from how the rolling window works.

Take an employee posted to a project from 5 January to 15 April 2026 — 101 consecutive days. Running that through the calculation:

Date checkedDays usedDays remainingStatus
5 April 202691−1In breach, still in country
15 April 2026101−11In breach, departure day
1 June 2026101−11Historical days still exceed the rolling allowance

They reached day 90 on 4 April and crossed the line on 5 April — ten days before anyone got on a plane. On 1 June, six weeks after returning, the position is unchanged at −11, because the entire trip is still inside the 180-day look-back window.

The earliest date this person could safely re-enter is 15 July 2026: three months after they came home. Anyone booking them a trip in May or June, reasoning that the long stint was over, would be booking a second breach.

The unlawful stay ends on departure. Its days remain in the rolling history, however, so a further trip can create another breach until enough old days have aged out. That arithmetic is separate from any entry ban imposed by an authority, which may prevent travel for a different and potentially longer period.


Why this is harder to absorb quietly since EES

Before the EU's Entry/Exit System went live in October 2025, officers often had to reconstruct travel history from passport stamps. Stamps can be difficult to read or incomplete, and totalling a rolling 180-day history manually takes time.

For travellers within its scope, EES electronically records external-border entries and exits and calculates the duration of the authorised stay from the data it holds. It is designed to identify travellers who may have exceeded that stay and to generate overstay alerts. The border authority still makes the applicable decision, and travellers have a formal route to request correction of inaccurate EES data.

Two things follow for employers:

Overstay identification is more systematic. Employers should plan on the basis that covered crossings are checked against an electronic history, while recognising that a record can still require correction.

Your records and the official record can disagree. If your internal tracking shows an employee at 70 days and EES shows 94, that gap can surface when the border authority checks the traveller. Our practical guide to how EES works covers the operational detail.

ComplyEur does not connect to or read EES. It estimates the traveller's position from the trip data supplied by the user, so incomplete records can still produce an incorrect planning result.


The business cost, not just the personal one

For the employee, the consequences are personal — a fine, a ban, disrupted travel, and a record that follows them into future applications. For the employer they are operational:

  • Project continuity. A consultant who cannot re-enter for a year has to be replaced on every live engagement, usually at short notice and usually mid-delivery.
  • Recurrence risk. If one overstay happened because of a tracking gap, everyone else travelling under the same process is exposed to the same gap. One breach is rarely isolated.
  • Documentation exposure. In a client audit or compliance review, "we had a tracking error and caught it" is a materially better position than "we had no reliable system for this".
  • Duty of care. The penalty lands on the employee personally, for travel the business asked them to undertake. That is uncomfortable to explain internally, and reasonable people will ask why the check was not being run.

None of this requires a dramatic breach. A team of EU-facing consultants each travelling eight or nine times a year can drift into overstay territory through entirely ordinary scheduling.


How overstays actually happen

They are rarely caused by one obviously risky trip. In practice the causes are mundane:

  • Personal travel not counted. A week in Portugal over Easter draws on exactly the same 90 days as a client visit to Frankfurt. It is also the hardest data to capture, because no expense claim ever generates a record of it.
  • The rolling window treated as an annual quota. Someone reasons "they've only used 60 days this year" — but the limit was never annual, and the window that matters may span two calendar years.
  • A stale figure. A days-remaining number that was correct in March, used to approve a trip in July.
  • Uncoordinated approvers. A line manager approves one trip, HR arranges another, a client books a third directly. No single person ever sees the combined picture.
  • Checking trip length instead of position. A 30-day trip looks obviously fine. It is not fine if the traveller has already used 70 days in the current window.

Every one of these is a data problem rather than a judgement problem. Nobody in this list decided to take the risk; they each answered a slightly different question from the one that mattered.


If it has already happened

This guide is about prevention, but if you are reading it because an overstay has already occurred:

  1. Establish the facts before acting. Reconstruct the actual travel history and calculate the real position. The free calculator will do the arithmetic on dates you already have.
  2. Take professional advice. This is the point where the question stops being arithmetic and starts being legal. An immigration solicitor can advise on disclosure, on how the specific member state tends to handle it, and on whether a ban can be appealed or lifted.
  3. Do not send them back to find out. Testing the position at a border is the worst available way to discover the answer.
  4. Check the rest of the team. If the process allowed one overstay, run the same calculation for everyone else travelling under it.

Catching it before it happens

The reliable prevention step is checking a proposed trip against the current rolling-window position before it is booked. That is a forecast, not a historical report: given this person's actual travel history, would these specific dates push them over?

ComplyEur's Trip Forecast runs exactly that check — enter proposed dates for an employee and get an immediate answer on whether they are safe, borderline, or would exceed the limit, based on their real recorded history. See how ComplyEur works, compare it honestly against the alternatives, or read the FAQ.


Key takeaways

  • Consequences can include fines, removal, detention, refusal of future entry, or an entry ban. Enforcement varies by member state and by circumstance.
  • An entry-ban decision can produce a SIS refusal alert with consequences beyond the issuing country, depending on the applicable decision and law.
  • Excess days remain in the rolling history after departure — calculate the earliest safe re-entry date and check separately for any official entry ban.
  • EES supports systematic overstay identification from electronic crossing records for travellers within its scope.
  • The business cost is usually operational — lost access, disrupted projects, duty-of-care questions — not just personal to the traveller.
  • Drift can cause an overstay: untracked personal travel, a stale figure, or several uncoordinated approvers can make a proposed trip unsafe even when its own duration looks ordinary.
  • The check that prevents them is against the rolling position on the proposed dates, not against the length of the trip.

Sources and review date

Sources last checked: 2026-09-07.

This guide explains how overstays arise and what generally follows. It is not legal or immigration advice. If an overstay has occurred, take professional advice on your specific circumstances.

About the author

James Walsh

Founder, ComplyEur

Founder of ComplyEur. Built the deterministic 90/180-day calculation engine behind the product.

Put the guidance into practice

Review ComplyEur options or speak with the team about your travel process.