When you need to prove tax residency for an audit, one uncomfortable fact governs everything: the burden of proof is on you, not the tax authority. You claim you were somewhere for 183 days or fewer - and it is your job to show it. Any day you cannot document is typically treated as a day spent in the taxing jurisdiction, counted against you. This guide explains what evidence actually persuades an auditor, why records kept at the time beat anything you reconstruct later, and how to keep an audit-ready day log with attached proof on your iPhone.
Why the burden of proof falls on you
In most residency disputes the taxing authority does not have to prove you were present. You have to prove you were absent. If you assert that you spent fewer days in a state or country than its threshold, the auditor starts from a simple, unforgiving default: every day you cannot account for with credible evidence is presumed to be a day inside their jurisdiction. Gaps are not neutral - they fill in against you. Where a change of domicile is in play, the bar is higher still: New York, for example, requires clear and convincing evidence that you truly abandoned your old domicile.
This is why casual travellers get caught out: they remember the shape of their year but cannot prove its edges, and the edges are where a residency case is won or lost. Because any part of a day usually counts, an arrival at 11 pm or a departure at 6 am can be the difference between clearing a threshold and crossing it. New York, for instance, treats any part of a day in the state as a full day, and you need not even reach your home to be counted - so dated evidence of when you arrived and left matters as much as where you slept. (Narrow exceptions exist, such as travelling straight through to an airport, but they are read strictly.)
How auditors actually test your days
A residency auditor does not take a single record at face value. They reconcile multiple independent data sources and look for a consistent story across all of them. Your travel tickets should line up with your card spending, which should line up with your phone location, which should line up with toll and building-swipe records. When those sources agree, your position is strong. When they contradict each other, such as a card swipe in one city on a day you claim you were in another, that contradiction is where an audit gets expensive.
Two principles follow from this, and they shape everything below:
- Consistency beats volume. A handful of records that all point the same way is more persuasive than a mountain of documents that conflict.
- Contemporaneous beats reconstructed. A record created at the time you were somewhere is far more credible than one you piece together later from memory, because it could not have been tailored to the outcome you now need.
Evidence that actually proves where you were
The strongest cases are built from records generated automatically by third parties, the kind you did not create for the purpose of the audit. These are the evidence types auditors weight most heavily:
- Boarding passes and travel tickets: flights, trains, ferries and buses, with dated departure and arrival points.
- Credit- and debit-card transaction locations: a dated, geolocated trail of where you actually spent money.
- Mobile-phone and cell records: call, data and cell-tower logs that place your handset in a location on a given day.
- Toll and transit records: highway toll tags, congestion-charge logs and public transit taps that timestamp your movements.
- Building and office swipe records: access-card logs showing when you entered a home building or workplace.
- Receipts: dated, itemised proof of a purchase in a specific place.
- Hotel bills: nights booked and paid for, tying you to a location overnight.
- Dated photos: images with reliable date and location metadata.
No single item is decisive. The goal is a web of records that corroborate one another so that, day by day, an auditor can see where you were without having to trust your recollection. Automated border systems are only tightening this: the EU's new Entry/Exit System, which becomes fully operational on 10 April 2026, records every non-EU traveller's entry and exit electronically, so Schengen day counts are now logged for you and overstays are flagged instantly.
Prove your days with Tax Residency Tracker
The hardest part of an audit is not knowing the rules. It is producing evidence for days you barely remember. Tax Residency Tracker is built to solve exactly that, by creating the record while you travel instead of leaving you to rebuild it under pressure:
- An automatic, dated location history. Background GPS detection creates a dated stay for each country and US state as you cross borders, even when the app is closed. Because it is written at the time you are there, it is a contemporaneous record, which is far more persuasive than a reconstruction you assemble from memory after the audit letter arrives.
- Proof attached to every stay. Attach camera photos, library photos, scanned documents, PDFs and files directly to each stay, be they boarding passes, hotel bills or receipts, so the evidence lives alongside the day it supports instead of scattered across apps and inboxes.
- Export that hands over the whole package. Export your stays and daily records as CSV, with country and US-state detail and a Documents folder of your attachments, so your accountant or the auditor receives a dated day count and the proof behind it in one exportable record, for a tax year, a quick range or a custom period.
- Alerts before you cross a line. Threshold alert notifications warn you as you approach a limit, on warning ladders such as the Substantial Presence Test at 90, 45, 21, 14, 7, 3 days remaining, Schengen as you near 90 days, and per-state or custom per-country thresholds, so you never blunder over a line you would later have to explain.
- Private and on your device. Everything is processed on-device and never uploaded, so your full travel history stays yours while remaining audit-ready.
- Records that survive a new phone. Optional iCloud sync moves your data across your own devices through your private iCloud, so years of history are not lost the day you replace your handset.
The practical effect is that the day an audit starts, you are not scrambling to reconstruct anything. You already have a dated log with evidence attached, ready to export. Tax Residency Tracker is iPhone-only and free to download; the day-counting model picker and CSV export are premium features.
Frequently asked questions
Who has to prove where I was in a residency audit?
You do. In most residency audits the burden of proof sits with the taxpayer, not the tax authority. If you claim you were under a threshold, you have to evidence it, and any day you cannot document is usually treated as a day spent in the taxing jurisdiction, counted against you.
Why does a record kept at the time matter so much?
Because it is contemporaneous. A log written while you were actually somewhere could not have been shaped to fit the answer you later need, so auditors give it far more weight than a timeline you reconstruct from memory after the fact. The app's automatic, dated location history is exactly this kind of record.
How many years of records should I keep?
More than you think. Residency audits commonly look back several years, so keeping documented days for a run of past years, not just the current one, is prudent. An automatic archive that syncs across your devices means you are not depending on old emails or fading memory.
What if my records disagree with each other?
Contradictions are the single biggest risk in an audit, because auditors reconcile multiple sources and weigh the inconsistencies against you. Keeping one consistent, contemporaneous day log with proof attached reduces the chance that a stray card swipe or ticket tells a different story from the rest.
Next, see how audits play out in a high-scrutiny state with the New York 183-day rule and statutory residency, how to track state residency for taxes, how to count days for tax residency, or browse all tax-residency guides.