Guide
Document settings
A document has three separate settings that control how it reads, once a document is generated: the translation language (which set of translated texts is used), the date/number locale (how numbers and dates are written), and the currency (how money is written). They are independent — changing one never changes another.
Where to find it
Open the Document tab in the side panel with nothing selected. Each setting shows a live example, generated the same way the document itself is generated — never a hand-written sample.
Translation language
If the template has translations configured (Manage data → Translations), this chooses which one renders. The example lists the template's own translated keys, resolved for the chosen language — including the same fallback to the default language a missing key uses when the document is generated. If the template has no translations yet, this control has nothing to offer and is disabled; add a language in Manage data → Translations first.
Leaving this unset does not mean "no language" — it means "decide automatically": the
translation whose language matches the date/number locale below is used (a locale of lv-LV
picks Latvian, de-CH picks German (Switzerland), or German if the template has no Swiss translation), and when
none matches, the fallback language chosen in Manage data → Translations. The default locale,
en-GB, picks the template's en-GB translation, else its en translation, when it has one. "Currently resolves to" shows the
result as you change either setting. Changing the translation language never changes the
date/number locale or the currency.
Date/number locale
A locale such as en-GB, de-DE, or lv-LV controls how numbers, currency amounts and dates are
written wherever a document uses format(...) or formatDate(...) — for example, whether a
thousands separator is a comma or a period, and whether a date reads "16 Sept 2026" or
"Sept 16, 2026". The example amount and date update live as you type, using the exact formatter
the document itself calls at generation time.
Currency
A three-letter ISO code such as EUR, USD, or GBP controls the currency symbol and formatting
format(amount, 'currency') produces. It has no connection to Ristmark's own billing currency —
this only affects the documents this template generates.
What happens to a template that has never set these
It uses the defaults: number/date formatting in en-GB, currency formatting in EUR, and a
translation language chosen automatically, as described above.
Generation-time overrides
Two things can be changed for a single generation without touching the template. The document's
data (a /v1 API call, or a preview with edited sample data, can supply different field
values), and the translation language (an API call can name a language: one of the
template's languages, written as a full code such as fr or de-CH; a region the template lacks
falls back to its plain language, and the response says so; an unknown language is refused).
The date/number locale and the currency always come from what is saved on the template here. If your workflow needs, for example, an invoice generated in two currencies from the same template, duplicate the template for now — a per-request override of those two is not yet part of the generation API.
If something looks wrong
- The translation language is greyed out. The template has no translations yet; add a language in Manage data → Translations first.
- Amounts show the wrong currency symbol. Check Currency here. It is separate from the locale and from the translation language.
- A date reads the wrong way round. The Date/number locale decides day-first or month-first;
en-USwrites the month first,en-GBthe day. - The preview shows English but I chose another language. The template has no text for that language yet, so the fallback language is used; the example under the setting shows exactly which keys fall back.