SaaS

SaaS internationalisation: languages, currencies, time zones

A practical guide to SaaS internationalisation: texts, dates, time zones and right-to-left support, localisation, multi-currency billing, and a checklist.

Your SaaS works well at home, and a first customer abroad is asking for a demo. Then the questions pile up: can the interface switch language, will invoices show the right currency, why did a reminder go out at three in the morning? SaaS internationalisation (often written internationalization, or i18n) is the work that makes a product ready for other markets before you adapt it to any one of them.

In this guide we cover what to build into the code, what to localise for each market, how to bill in several currencies, and which tax and data questions to settle with local advisers. A checklist at the end helps you judge whether you are ready.

SaaS internationalisation or localisation: what is the difference?

The two words describe two distinct jobs.

  • Internationalisation (i18n) is engineering. You build the product once so that languages, formats, currencies and time zones are settings, not assumptions written into the code.
  • Localisation (l10n) is adaptation. For each market, you translate the texts, adjust the content, set prices in the local currency and organise support.

The order matters. If you localise a product that was never internationalised, every new language means touching the code again, and every fix has to be made twice. Internationalise once, and each new market becomes mostly translation and configuration.

If you are still building your first version, you do not need to launch in five languages. Our guide to launching a SaaS MVP explains how to keep the first release small; keeping texts out of the code and storing times in UTC from day one costs little and saves a painful rework later.

What to build into the product

Texts out of the code

Every word a user sees, from button labels and error messages to emails and PDF documents, belongs in translation files, not in the code. Plan for:

  • Plurals and grammar: “1 file” and “2 files” follow different rules in different languages; Arabic has six plural forms. Use a library that handles plural rules rather than adding an “s”.
  • Text length: a German or French label is often noticeably longer than the English one. Design buttons and tables that can grow.
  • Whole sentences: never assemble a sentence from fragments (“You have” + 3 + “new claims”). Word order changes from one language to another.

Dates, numbers and names

Formats depend on the user’s locale, not on the language alone. 07/10/2026 is 7 October in London and 10 July in New York. Decimal separators, thousands separators and the position of the currency symbol differ too. Let the platform’s locale functions format them, and store raw values (ISO dates, numbers) in the database.

Names and addresses vary as well: not everyone has a first name and a last name, and postcodes are not always numeric. Keep these fields flexible.

Time zones

The rule is simple: store every time in UTC, show it in the user’s time zone. The hard cases are elsewhere:

  • Scheduled jobs: a “daily report at 8 am” must run at 8 am in each customer’s time zone, not on the server’s clock.
  • Daylight saving: clocks change on different dates in different countries, and some countries do not change at all. Use the time zone names of the standard database (Europe/Paris, Australia/Sydney), never fixed offsets such as +02:00.
  • Dates without a time: a due date or a birthday is a date, not a moment. Store it as a date, or it may shift by a day for users on the other side of the world.

Right-to-left (RTL) support

Arabic and Hebrew read from right to left, and so must the application: menus, icons with a direction, progress bars, tables and forms are mirrored. Inside the app, also check mixed text (an Arabic sentence that contains a reference number or a product name), input fields, and generated documents such as PDF invoices, which are often the last thing to be fixed.

We cover the website side of this, layout and search engines included, in our article on multilingual website SEO. Our own website runs in four languages, including Arabic from right to left.

Software localisation: content, support and documents

Translation is only part of software localisation. To feel local, a product also needs:

  • Native translators and a glossary: machine translation is a useful first draft, but a native speaker who knows your domain should review it. A glossary keeps the same term for the same idea across the app, the help centre and the emails.
  • Localised documents: invoices, contracts, notifications and onboarding emails, each with its own template per language.
  • Support in the customer’s language and hours: decide which languages your team answers in, and when. A help centre in the local language often matters more than live chat.
  • Local examples and defaults: sample data, default currency, week start (Monday or Sunday) and paper size (A4 or Letter).

Start with one new market, then add the next: every language you add must be kept up to date with each release.

Multi-currency billing

Showing a price in euros is easy; billing correctly in several currencies takes more care.

  • Set price lists per currency rather than converting on the fly. A round price in each currency is easier to sell and to explain than an odd converted amount.
  • Store amounts with their currency: an integer in the smallest unit (cents) and an ISO currency code (EUR, AUD, AED). Never store a bare number.
  • Record the exchange rate used for each invoice if your accounts are kept in another currency, and decide who bears the difference.
  • Refund in the original currency, and keep credit notes linked to their invoice.
  • Check your payment provider: which currencies and local payment methods it supports, and in which currency it pays you out.

Most subscription billing platforms handle part of this. Your job is to decide the rules before you configure them.

Tax and data: the questions to settle with local advisers

This is where we stop and point you to specialists. As of October 2026, rules on sales tax registration and data transfers vary by country and change regularly. Before you open a market, ask a local tax adviser and lawyer to confirm:

  • whether you must register for VAT, GST or another sales tax there, and from what level of sales;
  • what an invoice must contain, and whether electronic invoicing is mandatory;
  • whether customer data may be stored or processed outside the country, and on what conditions;
  • which consumer or contract rules apply to your terms of service and cancellation policy.

This article gives practical pointers as of October 2026. It does not replace advice from a tax adviser or lawyer in each country where you sell.

Checklist: is your SaaS ready for a new market?

Area Ready when…
Texts Every visible text, email and document lives in translation files
Formats Dates, numbers and currencies are formatted by locale
Time Times are stored in UTC; scheduled jobs follow each customer’s time zone
Right-to-left Screens, mixed text and PDFs have been tested in Arabic, if you target it
Content A native speaker has reviewed the translations against a glossary
Support You know who answers in that language, and during which hours
Billing Prices exist in the local currency; amounts are stored with their currency code
Tax and data A local adviser has confirmed tax registration, invoice rules and data location

If your product is still installed on customers’ own computers, these questions come after a bigger one: read our guide to moving installed software to SaaS. Our SaaS development service covers both.

Frequently asked questions

When should a SaaS start internationalisation?

As early as the foundations allow. Keeping texts in translation files, storing times in UTC and amounts with their currency costs little in the first version and a lot to retrofit. Localisation itself can wait until a real market justifies it: one paying customer abroad, or a clear sales plan for a country. Building for many languages is cheap; maintaining many languages is not.

Is machine translation enough for software localization?

For a first draft, often yes. For a product customers pay for, rarely. Machine translation misses your domain’s vocabulary, the tone of your brand and the context of short labels such as “Open” or “Charge”. Use it to go faster, then have a native speaker review the result against your glossary, especially legal texts, invoices and onboarding emails.

Should we convert prices automatically or set them per currency?

Set them per currency for your main markets. Fixed local prices are clearer for customers, stable from one month to the next, and easier to put in contracts. Automatic conversion can work for occasional buyers from other countries, as long as the invoice shows the currency charged and your terms say how exchange rates apply.

In short

SaaS internationalisation means building once so that languages, formats, time zones and currencies become settings. Localisation then adapts content, documents, support and prices to each market, one at a time. Multi-currency billing needs rules before it needs software, and tax and data questions belong to local advisers. Start with the foundations, then open markets as customers justify them.

Planning to take your SaaS to a new country or a new language? Book a free 30-minute discovery call: we look at your product together and list what to prepare first.

Related servicesSaaS productsWebsites and web apps

Have a project in mind?

Let’s talk about it on a 30-minute discovery call, free and with no obligation.

Book a discovery call

Further reading

All articles