RemoteTravel
For Advisors & Firms

Audit-ready travel evidence
for every client.

Your clients log travel as it happens. When a residency question comes in, the day counts and dates are already there. One record, in order, per client.

Book a 30-min setup callSee the sample record

Pick a time, talk directly to a founder. No prep needed. Prefer email? Write directly: partners@remotetravel.app

Exhibit ASample data

Schedule of days of presence

M. Tan (fictional) · Calendar year 2025 · Tax home: Singapore

Singapore

Goal ≥ 183 · tax home

194Residency Maintained

Thailand

Limit 180 in the year

155Approaching Limit

Indonesia

Limit >183 in any 12 months

12Non-Resident
365 less 171 days outside = 194 days Ties out

Last trip logged 13 Oct 2025, 19:56

The travel data you need usually doesn't exist.

A residency review turns on days of presence. Most clients can't tell you theirs.

Clients guess

Ask for last year’s travel and you get calendar screenshots, a few boarding passes, and dates that don’t add up. You end up auditing your own client’s memory.

The hours are hard to bill

Rebuilding a travel history from bank statements and airline emails takes days. Clients push back on the fee because it looks like admin, not advice.

You certify it anyway

The filing position rests on day counts someone assembled by hand. If they’re wrong, that’s the client’s problem first, and then yours.

Inside the record

What the record is made of.

Firms receive the record in their own format. The data points underneath are what carry it. Here is each one, and what it is worth when a position is reviewed.

Captured per trip

Entered by the client in seconds, kept from day one.

Jurisdiction

The country each day of presence is attributed to, the first fact any residency test asks for.

Feeds: Day counts per jurisdiction, the tests tracked for that client.

Entry date

Fixes the day presence begins, so counts are built from dated boundaries rather than memory.

Feeds: Day counts, rolling windows.

Exit date

Closes the trip into a complete, checkable date range.

Feeds: Day counts, margins against each test.

Route, transport, and reference

How the client moved: carrier and flight, coach, or train number on each movement, the detail a reviewer matches against tickets.

Feeds: The movement log, document matching.

Logged timestamp

Since day one

Shows the trip was recorded near the time of travel, which is what separates a contemporaneous record from one assembled the week before a review.

Feeds: The credibility of every other field.

Stored on every trip since day one. Showing it on shared records is in development.

Derived for review

Computed from the trips. Never hand entered.

Day counts per jurisdiction, per year

Arithmetic over the trip dates, so every total traces back to the trips behind it.

Feeds: The summary schedule, threshold status.

Margin against the test applied

The position against the exact rule set for that client, as a limit to stay under or a goal to keep: 183, 180, or 182 in a year, 183 in any 12 months, Schengen 90 in 180.

Feeds: Threshold warnings, review season summaries.

Threshold warnings

Raised while the year can still be steered, so a threshold becomes a question to you in June, not a finding in review.

Feeds: The mid-year call to you, before a limit is crossed.

Tracked alongside

The context a reviewer asks about next.

Visa and travel document expiry

Keeps the right to be somewhere next to the record of being there. Reminders go to the client, so an expiring status surfaces before it undermines a position.

Feeds: The documents block of the record.

Not collected

By design

No passport numbers, no ID scans, no names. A record of movements and dates stays easy for a client to share.

Set per firm

Which tests are tracked, how part days are counted, and how the output is laid out are set with the founding team at onboarding, before your first client logs a trip. Records can be white-labeled under your firm's branding. Tell us how your reviewers want it. Contact us.

In development

Two things on the way for rebuilding a client's past travel. Neither is shipped yet.

Rebuild from the photo library

Drafts past trips from the dates and places already stored in a client's photo gallery, marked as reconstructed, for you to verify against documents.

Paste a booking email

A client pastes a confirmation email and the trip's dates and destination fill in.

Ask the recordIn development

When the letter arrives

A residency query asks three things. Your firm will ask the record directly and watch it answer from the log, math shown. Every number below is the sample year's real arithmetic.

State your days of presence for 2025.

Answers computed from the record, never estimated. Rule interpretation stays with the advisor.

See the full sample record

A system of record for days of presence.

Trips go in as they happen. Day counts, thresholds, and dates come out, per country and per year.

Show the working

Every trip has dates. Every year has a running day count per country. When someone asks how a number was reached, you can show them.

Nothing to deploy

Clients use the free app on their own accounts. No procurement, no IT project, nothing for your firm to install or maintain.

Clients will actually use it

It asks for countries and dates. No passport numbers, no ID upload. The privacy conversation takes one sentence.

RemoteTravel started after its founder spent four days rebuilding 18 months of travel history for an IRAS query. This is the record we needed then.

How it works

1

Clients log trips

A trip is a country and two dates, past or upcoming. That is the whole ask. No spreadsheets to chase, no year-end questionnaire.

2

Day counts update themselves

Each entry counts against every country’s threshold for the year, with warnings before a limit is reached. Standing is visible all year, not reconstructed in March.

3

The answer is already written down

When the query letter arrives, the client’s year is structured, dated, and complete.

What your client sees in week one.

The ask you are making of a client is small. This is all of it.

Add trip

Country

Japan ▾

Entry

15 Mar

Exit

28 Mar
Add trip

Day one. A trip is a country and two dates, entered in seconds.

Your status · 2026

Singapore · Tax home27 days to goal
156of 183 days
JapanWithin limit

Same minute. Day counts and thresholds update with every entry.

Documents

PassportValid

Expires in 4 years

Long-stay visa45 days left

Renewal window opens soon

Week one. Expiry reminders run without being asked.

White label

Issued under your name.

The schedule your clients' reviewers see carries your firm's branding, not ours. Your name on the record, your working paper conventions, your client relationship.

  • White-labeled records. Part of firm setup, configured at onboarding.

  • The client app in your firm's brand. Your clients log trips in an app that carries your identity. Being built with founding firms now.In development

Book a 30-min setup call

Default

R

RemoteTravel

Schedule of days of presence · 2025

Your firm

YF

Your Firm LLP

Schedule of days of presence · 2025

Same record, same timestamps, your letterhead.

Spend audit season advising.

The reconstruction work disappears. What's left is the part clients actually pay you for.

Book a 30-min setup callTry the client app

Try it as your own first user. If the record holds up, booking the call takes a minute.

Frequently asked questions

Put your clients on the record.

Book a 30-minute call and we walk through how rollout would work for your practice: which clients to start with, what they see, and what you get at review time.

Book a 30-min setup call

You talk directly to a founder. Prefer email? Every message gets a reply, usually within one business day.

partners@remotetravel.app