FieldproxyAI-native field service software

Multi-country operations

How do I run field service across several countries, currencies and languages?

Treat country as a field on the customer, the site, the technician and the rate card, then give every quote, purchase order and invoice its own currency, stored beside the rate used to convert it into your base currency. Let each person pick their own app language, and keep one shared record underneath so the office reads it in theirs. Decide your exchange rate source and your tax rule per country before the first job abroad, because both are hard to change once documents exist.

  • Country belongs on the customer, the site, the technician and the rate card. Hourly rates differ by country, so a single price list breaks.
  • Each document keeps its own currency and the exchange rate used. Never overwrite an old invoice when rates move.
  • Pick one rate source and one rate date (job date, invoice date or payment date) and apply it everywhere.
  • Language is a per-person setting, not a per-company one. Store the job once and show it in each reader's language.
  • Tax is decided by where the work happens and who the customer is. Ask your accountant per country before the first job.

Book your demo

60 minute video call ยท Step 1 of 2: your details, then pick a time

Number of employees

This page covers running operations across borders. It does not replace local tax or employment advice, and your accounting package still owns the ledger and revaluation.

Facts checked as of November 2026. Sources at the end of the page.

Step by step

How to run field service across countries, step by step

The pattern below works in any system. The order matters: settle the money rules first, then the people and the screens.

1. Pick a base currency and lock it before you start

Your accounting package decides this for you. QuickBooks Online says that once Multicurrency is on you cannot turn it off or change your home currency, and it is available on Essentials, Plus and Advanced but not EasyStart. Xero sets the base currency when the organization is created, and its US pricing page lists multiple currencies under the Established plan only.

2. Put country on every record that carries a rate

Add a country (and a currency) to the customer, the site, the technician or subcontractor, and the price list. Dynamics 365 Field Service shows the pattern: a price list has its own Currency field, items use the Currency Amount pricing method, and the work order picks up a price list, often from the billing account.

3. Build one rate card per country

Hourly rates, call-out fees, overtime multipliers and travel allowances differ by country, so a single price list cannot serve all of them. Keep a rate card per country and currency, and let the job choose the card from the site's country, not the technician's home country.

4. Choose one exchange rate source and one rate date

Pick a published source and stay with it. Xero applies the rate for the day a transaction is created and lets you override it on an invoice, bill or payment. QuickBooks Online updates rates every 4 hours and accepts your own manual rates. Salesforce, with Advanced Currency Management, uses dated rates, so a record converts at the rate in force on its date. Decide whether that date is the job date, the invoice date or the payment date, and write it down.

5. Store the currency and the rate on each document

Every quote, purchase order and invoice keeps its own currency, the amount in that currency, the rate used and the amount in base currency (for example currency, amount, fx_rate, base_amount). Salesforce notes that previous rates are not stored for ordinary conversions after you edit them, so a stored rate on the document is the only reliable record.

6. Set each person's language and time zone

Language and time zone belong to the person, not the company. Use standard language tags (BCP 47) and mark right-to-left text properly, as the W3C advises for Arabic and Hebrew. Store job times in UTC with the site's IANA zone, such as Europe/London, so daylight saving rules are applied for you; the IANA database is updated when countries change their rules (release 2026f in October 2026 changed Cuba's autumn clock change).

7. Set the tax rule for each country before the first job

Where the work happens and who the customer is decide the VAT or GST treatment. In the UK the B2B general rule is that a service is supplied where the customer belongs, with exceptions such as land-related work. Inside the EU, B2B services are usually reverse charged by the customer, again with exceptions.

8. Report by country as well as by customer

Revenue, cost, jobs closed and technician hours should group by country and currency, with a base-currency column. Without that, a head office cannot see which country makes money.

Why it goes wrong

Why multi-country field service falls apart

These are the situations owners described on our sales calls, told by trade and size.

Email and spreadsheets stretched to ten countries

An IT managed-services company that sends on-site engineers to customers in about 10 countries, with up to 2,000 technicians onboarded and 200 to 500 tickets a month, ran live updates by email and an internal spreadsheet. Rates per hour differ in each country, and parking, food and overtime had to be cross-referenced by hand. They expected to send about 300 invoices where one project invoice would do.

A tool built for one country

A commercial refrigeration and mechanical contractor working through subcontractors said it seemed uncommon for field operatives to work in several countries, languages and currencies at once, and found no tool that did it. Their need was a currency per customer, per contractor and per supplier.

Paperwork nobody in the office can read

A UK vertical lift machine supplier with about 70 subcontractors said the job sheets come back as badly handwritten photos in a foreign language that the office cannot read, and that simple translation does not work on them.

A driver app in one language only

A field-activation company in Saudi Arabia running thousands of site visits wanted the driver app and the portal in Arabic and English, with its own branding, so drivers and the client's staff each read their own language.

Rates move and history changes

When a system stores only the current rate, last quarter's invoices change value the day the rate changes. That is the most common finance complaint once operations span two or more currencies.

Ways to do it

Ways to handle multiple countries, currencies and languages

Five common approaches. Vendors change plans often, so confirm each point in your own account before you rely on it.

ApproachWhat it does wellWhere it falls short
Spreadsheet, email and one invoicing toolFree to start, and works for two or three countries with a handful of people.Rates, FX and language all live in people's heads. Nothing forces a job to carry its currency, and invoices are built by hand.
A separate instance per countryClean local tax, currency and language. Each country can run at its own pace.No group view. Technicians who travel need two logins, and head office rebuilds a consolidated report by hand.
US and Canada trade-focused FSM toolsStrong for home services in their home markets. Jobber's help centre has a Spanish version and a UK payments setup article, and ServiceTitan documents Canadian sales tax and Australian messaging.A first look found no page listing supported currencies for Jobber, ServiceTitan or Housecall Pro, so ask for multi-currency documents directly before you assume they exist. Housecall Pro says its QuickBooks Desktop support is for US versions only.
Enterprise platforms (Dynamics 365, Salesforce)Real multi-currency: price lists with their own currency in Dynamics, and Salesforce corporate currency with dated rates once Advanced Currency Management is on.Heavy to set up and administer. Salesforce says multiple currencies cannot be disabled once activated, so plan before you switch it on.
FieldproxyOne platform for jobs, quotes, POs and invoices, a language per person in 27 languages with Arabic right to left, and customer invoices that sync to Xero or QuickBooks. Fields and rate cards are built around your countries.Rate cards, currency fields and approval limits are configured with you, not a ready-made template. Revaluation stays in your accounting package.

Worked example

A worked example: one engineer, two countries, one invoice

Say a company with a UK head office dispatches an engineer to a customer in Spain. The Spain rate card is 70 euros an hour, and the engineer works 6 hours, plus a 45 euro train fare approved as an expense. The job totals 465 euros. Your base currency is pounds, and you set the rule that the rate is taken on the job completion date. If that day's rate is 0.86 pounds per euro, the base amount is 399.90 pounds. The invoice stays in euros for the customer, and the record keeps 465 euros, the 0.86 rate and the 399.90 pound base value.

Now say the rate moves to 0.88 the following week. Because the rate is stored on the invoice, the job is still worth 399.90 pounds in your report, and the customer pays 465 euros either way. The difference between the rate on the invoice date and the rate on the payment date is a currency gain or loss, and it belongs in your accounting package, not in the job record.

The ECB publishes euro reference rates at about 16:00 CET on working days, but it states they are for information and using them for transactions is strongly discouraged. The US Federal Reserve's H.10 release is weekly, on Mondays at 4:15 p.m. for the previous business week. Neither is a billing rate on its own; pick the source your bank or accountant accepts.

For UK VAT, the invoice must show the total VAT in sterling even when the net amounts are in another currency. VAT Notice 700 paragraph 7.6 gives three ways to pick the rate: the UK market selling rate at the time of supply, HMRC's period rate, or a commercial rate agreed in writing.

Checks

What to check before you choose a tool

Good signs

  • Currency is a field on the quote, purchase order and invoice, not only a company setting.
  • The exchange rate used is stored on each document and does not change later.
  • Price lists or rate cards can be set per country and per currency.
  • Each user picks their own language and time zone, including right-to-left languages.
  • Reports group by country and currency and show a base-currency total.
  • The accounting sync passes the document currency and rate across, not only a base-currency total.
  • Data hosting and access are explained for staff in other countries.

Red flags

  • One company-wide currency with a note field for the rest.
  • Translation only on the sales site, not in the technician app.
  • A price list that cannot differ by country.
  • Dates shown in the office's time zone for a technician working elsewhere.
  • The vendor cannot say which countries' tax rules it supports, or points to a US-only accounting version.

In Fieldproxy

Setting it up in Fieldproxy

Fieldproxy is described in one line: best for processes that don't fit a template, set up for you. So the fields and rules below are configured with you. Names marked e.g. are examples.

Country and currency on the records

Customers, sites, technicians and subcontractors carry a country and a currency (e.g. country, currency, rate_card). Quotes, purchase orders and invoices keep their own currency, the exchange rate and the base amount (e.g. fx_rate, base_amount), so reports can total in one currency. It is one price per company with unlimited users, so adding countries or people does not add seats. See /pricing.

A rate card per country

Hourly rates, call-out fees and overtime multipliers for each country are kept as price lists in that country's currency, and the job picks the one that matches the site. The Dispatch agent (/agents/dispatch-agent) assigns the right technician by distance and skills, and a country field on the technician record lets you keep each country's work with its own people.

A language per person

Each person picks their own language on web and mobile, from 27, and Arabic runs right to left (/solutions/multi-language). A driver in Riyadh reads Arabic and the office reads English on the same job. The Vision agent (/agents/vision-agent) reads a photographed job sheet into the job's fields.

Travel and expenses against the job

A technician logs a travel cost or receipt on the job. It goes to the back office for approval before it is rebilled or paid (/solutions/approval-workflows), with the currency stamped on the expense.

Money to your accounts

Customer invoices sync to Xero (/integrations/xero) or QuickBooks (/integrations/quickbooks). Which currency and rate each side holds is agreed during setup, and revaluation stays in your accounting package.

Reports by country

Dashboards group jobs, revenue and hours by country and customer (/solutions/dashboarding-reporting), with a base-currency column, and the Scheduler agent (/agents/scheduler-agent) can email the monthly view to each country head.

Moving data between countries

Technician data and where it is allowed to go

When staff in one country can see technician records from another, you are transferring personal data across borders. Under the GDPR the European Commission can decide that a non-EU country is adequate, after which data can flow without further safeguards. The listed countries include Japan, Switzerland, Canada (commercial organizations), the United Kingdom, the United States (for participants in the EU-US Data Privacy Framework), Brazil and the Republic of Korea. Where there is no adequacy decision, the Commission's standard contractual clauses, issued 4 June 2021, are one pre-approved basis for the transfer.

In practice: decide which roles in head office can see which countries, and write it into the role permissions before go-live. Ask your vendor where data is hosted and how it is backed up. Check the lists above against your legal advisor's view for your own countries.

How switching works

How switching to Fieldproxy works

We move your data over and set the system up to the way you already work. Fieldproxy replaces the old tool; it does not run alongside it.

  1. Show us two countries end to end

    One real job in each of two countries: the rate card, the technician, the invoice and what your accountant needs from it.
  2. We set up countries, currencies and rate cards

    Country and currency fields, a price list per country, approval limits in your base currency, and each person's language.
  3. We connect your accounting package

    Customer invoices sync to Xero or QuickBooks with the currency and rate agreed, so your ledger and revaluation stay where they are.
  4. Go live with one country first

    Run a month in one country, check a sample of invoices against the ledger, then add the next country.

FAQ

Questions people ask

Do I need multi-currency turned on in my accounting package first?
Yes, before you invoice in a foreign currency. QuickBooks Online cannot turn Multicurrency off or change the home currency once it is on, and Xero lists multiple currencies on its Established plan in the US. Check the plan and the home currency before you connect any field service tool.
Which exchange rate should I use on an invoice?
Pick one source and one date rule and use it everywhere. Xero uses the rate for the day the transaction is created and lets you override it. For UK VAT, the rate must follow VAT Notice 700 paragraph 7.6, and the rate at the time of supply applies.
Can I pay technicians in a different currency from what I bill the customer?
Yes, and it is common. Keep the customer document in the customer's currency and the technician's pay or cost in theirs, and store the rate used on each, so margin per job can be shown in one base currency.
Can the technician app be in each person's own language?
In Fieldproxy each person picks their own language on web and mobile, from 27, and Arabic runs right to left. The job record stays the same; only what each person reads changes.
Can handwritten paperwork in another language be read?
A photo of a job sheet can be read into fields by the Vision agent (/agents/vision-agent), but handwriting in an unfamiliar script is the hard case. Ask for a sample on your own paperwork before you commit.
How do I handle time zones for engineers working abroad?
Store each job time in UTC with the site's IANA zone, for example Europe/London. The IANA database holds the daylight saving rules and is updated when countries change them, so the right local time is calculated for you.
Do I have to use one tax rule for all countries?
No. Tax follows where the work happens and who the customer is. In the UK the B2B general rule is that a service is supplied where the customer belongs, with exceptions such as land-related work, and EU B2B services are usually reverse charged. Ask your accountant per country.

Sources

Competitor details on this page come from the vendors' own pages and documentation, checked as of November 2026. Plans and prices change, so check the vendor's current page before you decide.

See it built on your workflow

Tell us how your jobs run today. We build a demo on your stages, forms and pricing before the call.