Employee Schengen compliance: why spreadsheets break down

A spreadsheet can work for a small travel programme. Review it when the scheduling team can no longer keep the dates complete, recalculate proposed visits and identify who approved each change.

---

Where spreadsheets actually work fine

For a company with one or two employees who travel to the EU a handful of times a year, a spreadsheet with entry and exit dates is genuinely a reasonable starting point. The 90/180 calculation isn't complicated in principle — it's addition and a date range. Even at low volume, the calculation needs to be correct and the records complete. A named owner and a check before each booking matter more than the file format.

When to reassess the process

An operations manager should review the tracker when:

• several people book or change travel without one agreed update route;
• personal Schengen trips are missing from the record;
• a saved days-remaining figure is reused instead of recalculated;
• nobody can show that the whole proposed visit was checked; or
• the team cannot identify which workbook or version is current.

If those controls still work reliably, there is no automatic need to replace the spreadsheet.

---

Where it breaks down

The window moves each day. A formula that sums a calendar quarter or year does not check the Schengen rule. For each date being checked, the workbook needs to count presence in the 180-day period ending on that date, including the date itself. Stale formulas or incomplete ranges can produce a wrong answer as trips are added.

Personal travel gets missed. Business travel is usually recorded because it's expensed or booked through a travel system. Personal travel to the same countries — a family holiday in Spain, a weekend in Amsterdam — draws from the exact same 90-day allowance but often isn't captured anywhere a compliance spreadsheet can see it.

Updates can be missed between owners. A scheduler, manager, assistant or traveller may change a booking. Without an agreed route for updating the tracker, the next approver can be working from incomplete dates even when each individual booking looks reasonable.

The forecast may be missing or skipped. A workbook can check future trips if it is designed to test every day of the proposed stay. The process fails when it only holds historical totals, formulas are not maintained or the pre-booking check is skipped. Ask whether the scheduling team can run and record that check consistently.

Country rules and edge cases change. Andorra, Monaco, Vatican City and San Marino require different treatment, and Romania and Bulgaria began counting toward the shared short-stay allowance on 31 March 2024 before their internal land-border checks ended on 1 January 2025. A spreadsheet without a documented update process can quietly retain an outdated country policy.

---

What a reliable system actually needs to do

A dependable shared process needs to:

1. Recalculate the rolling window automatically, for every employee, as of today — not as of when someone last updated a formula.
2. Combine business and personal travel into one record per employee, since both draw from the same allowance.
3. Support a single source of truth that multiple people can add trips to without creating silent duplicates or gaps.
4. Check proposed trips before they're booked, not just report on trips that already happened.
5. Keep the country policy current, including effective dates and the separate treatment of nearby microstates.
6. Surface risk before it becomes a problem — flagging employees approaching their limit rather than requiring someone to go looking.

---

What this looks like in ComplyEur

This is close to a description of what ComplyEur does day to day: every employee's rolling 90/180 position is recalculated automatically as trips are added, personal and business travel share the same record, the Trip Forecast tool checks a proposed trip against the current position before it's booked, and alerts flag anyone approaching their limit rather than waiting to be asked. Import from existing spreadsheets is supported directly, so switching over doesn't mean re-entering a year of travel history by hand.

Moving to software still needs a named record owner, complete travel dates and a route for correcting errors. Automation does not discover a missing holiday or decide whether the planned work is permitted.

---

Key takeaways

• A spreadsheet can support Schengen tracking if the calculation is correct, the records are complete and a named person maintains them.
• The rolling 180-day window needs to be recalculated for each relevant date rather than summed over a fixed period.
• A spreadsheet process needs an explicit way to collect relevant personal-travel dates and check proposed trips before approval.
• A dependable system needs automatic recalculation, a single combined record, and a pre-booking check — not just a historical log.

For worked examples of the rolling-window calculation, the complete guide to the 90/180-day rule works through it with real dates, and the free calculator will run it on your own trips without a signup.

Spreadsheets are one of five approaches covered in our honest comparison of Schengen compliance tools — including cases where staying on a spreadsheet is a reasonable choice.

See ComplyEur's plans or read the FAQ for more on how import, forecasting, and alerts work together.

Sources and review date

• GOV.UK guidance on calculating Schengen stays (opens in a new tab)
• European Commission short-stay calculator (opens in a new tab)
• Council decision applying the remaining Schengen rules to Bulgaria and Romania from 31 March 2024 (opens in a new tab)

Sources last checked: 2026-09-07.