How to Track Your Days Abroad for Tax Purposes (2026 Guide)
Most people who get into trouble with tax residency didn't fail to understand the rules — they failed to prove they followed them. The gap between "I know I didn't exceed 183 days" and "I can prove I didn't exceed 183 days" is where audits are won and lost.
Why spreadsheets fail
The spreadsheet is the default tool most digital nomads reach for. It feels adequate — you have a list of countries, dates in, dates out, a formula counting the days. What could go wrong?
The problem is not the format. The problem is the nature of the evidence.
A spreadsheet can be created, edited, and backdated at any time. A tax authority auditor reviewing your records has no way to verify that your spreadsheet was maintained in real time, rather than constructed last Tuesday when you received the audit letter. They know this. You know this. And so the spreadsheet, by itself, proves nothing except that you are capable of opening Excel.
A real scenario
A Finnish expat claimed non-residency based on a spreadsheet showing 178 days in Finland. During audit, Vero cross-referenced mobile network data, credit card transactions, and border crossing records. The spreadsheet had 11 missing entries. The actual count was 193 days. She owed three years of back taxes.
Beyond the authenticity problem, spreadsheets have other structural weaknesses:
- No midnight captures: if you crossed a border at 11pm, did your spreadsheet record which side of midnight you were on?
- No coverage for short trips: a weekend trip that went unrecorded can flip a 181-day count to 185
- Hard to audit: 365 rows of dates is not the same as a verified geographic record
- No jurisdiction logic: a spreadsheet counts days — it doesn't know that for Finland, a 6-month continuous stay triggers residency even without 183 calendar days
- No alerts: you only know you've exceeded a threshold after you've exceeded it
What tax authorities actually want to see
When a tax authority — the IRS, HMRC, Vero, or any equivalent — asks you to prove your days of presence, they are looking for contemporaneous evidence. That means records created at the time the events occurred, not reconstructed after the fact.
The strongest forms of evidence, in rough order of persuasiveness:
Passport stamps
The gold standard. Country of entry, date, and in many cases time. Not always reliable for EU internal travel or countries that have moved to e-gates.
Timestamped GPS / location data
Automatically captured location records with timestamps are the electronic equivalent of a passport stamp. Difficult to falsify if continuously generated.
Boarding passes and booking confirmations
Shows you were on a plane between two points on a specific date. Does not prove where you slept or how long you stayed.
Credit card statements
Useful corroborating evidence. Each transaction is geolocated and timestamped. Not complete — cash transactions, company cards, and shared expenses create gaps.
Hotel and accommodation receipts
Shows presence at a location on specific nights. Does not cover stays with friends, Airbnb payments on a different card, or nights in transit.
Retrospective spreadsheet
The weakest form of standalone evidence. Useful only as a summary that is corroborated by the stronger forms above.
Tax authorities don't need every single form of evidence — they need enough corroborating sources that a coherent, consistent story emerges. Where they look for inconsistencies is between different data sources. If your spreadsheet says you were in Portugal on August 12th but your credit card shows a transaction in Germany that day, that inconsistency becomes a problem.
Manual methods and their limits
Many people try to supplement their spreadsheet with manual methods:
Calendar apps
Easy to update after the fact. No location verification. Doesn't capture midnight boundaries.
Photo metadata
Useful corroborating evidence but incomplete. You don't take a photo every day. Metadata can be edited.
Email receipts
Covers accommodation and travel but not every day. Significant gaps for long stays in one place.
Fitness tracker GPS
Not designed for tax purposes. Data formats are not exportable in a tax-ready form. No jurisdiction logic applied.
The common thread across manual methods is that they are incomplete by design. They were built for other purposes. Tax residency tracking requires continuous, uninterrupted coverage — especially for the moments that matter most: midnight on day 182, the overnight flight that crosses midnight, the day you weren't sure whether you'd crossed the border yet.
What a proper tracking system needs
A compliant day-tracking system for tax residency has specific requirements that are different from any other kind of location tracking:
Automatic and continuous capture
Location must be recorded without requiring you to remember to check in. The most common cause of gaps is human memory. GPS pings on a schedule — including mandatory captures at midnight — remove this failure mode.
Midnight boundary capture
For tax purposes, a 'day' is typically a calendar day. To prove which country you were in on a specific date, you need evidence of your location at or near midnight. A system that only logs your location when you open an app cannot guarantee midnight coverage.
Jurisdiction-specific counting logic
Not all days are equal across jurisdictions. A day that counts for Finland's 183-day test may be treated differently under the US SPT formula. Your tracking system needs to know the rules of each jurisdiction you're monitoring, not just the raw day count.
Tamper-evident audit trail
Records should be stored in a way that demonstrates they have not been modified after capture. Timestamps should be server-side, not derived from local device time.
Exportable in useful formats
Your accountant needs to be able to work with your data. A PDF summarising your movements and a CSV day log by country are the formats that actually get used during tax preparation and audits.
Threshold alerts
The system should tell you when you're approaching a threshold — at 30 days remaining, 15, and as you approach zero. Knowing on January 1st that you have 88 days of US SPT capacity remaining changes your planning. Finding out in December that you exceeded it does not.
Starting earlier than you think you need to
One of the most consistent mistakes among digital nomads is waiting until they think they might be approaching a threshold before starting to track properly. By then, the damage is already done.
If you start tracking on day 150 of a 183-day limit, you have no defensible record for the first 150 days. You may be able to reconstruct it from boarding passes and credit card statements, but reconstruction is laborious, incomplete, and will not be treated the same way as contemporaneous records.
The right time to start tracking is before your first border crossing of the year — ideally before you begin a period of multi-country travel at all. The cost of tracking when you don't need to is trivially small. The cost of not tracking when you did need to can be tens of thousands of euros.
Key takeaways
- Spreadsheets are retrospective constructs — they don't prove where you were, only what you claim
- Tax authorities look for contemporaneous, timestamped evidence from multiple corroborating sources
- Manual methods (calendars, photos, receipts) all have structural gaps
- A compliant system needs: automatic capture, midnight boundaries, jurisdiction-specific logic, tamper-evidence, exportable formats, and threshold alerts
- Start tracking from the first day of the year, not when you think you might be getting close