Currency and language solve different problems. Currency defines the unit of the obligation. Language helps the customer understand the document. Neither one decides tax, converts amounts, or makes a PDF compliant with a country’s structured e-invoice mandate.
This is the exact support boundary in Invoice Master as of July 12, 2026.
Per-document currency
Each invoice and quote stores a selected currency, and the backend supports a broad list of ISO-style currency codes. The selected currency follows the document’s line items and totals. This lets one organization issue, for example, one invoice in EUR and another in USD.
Invoice Master does not fetch live or historical exchange rates, maintain a home-currency ledger, show realized exchange gains or losses, or convert a report into one economic currency. If the contract, tax return, or books require another-currency value, document the approved rate source and calculation outside the application.
Three supported application languages
The current interface supports English, German, and Spanish. PDF labels can follow the active profile or request language, so standard labels such as invoice headings and totals can appear in the supported locale.
This is application localization, not automatic translation of document content. Product names, line-item descriptions, footnotes, payment terms, and custom fields remain exactly as the user enters them. If a customer needs German text, someone must write or review that German text.
The application also disables browser translation in places, so do not design a workflow around a browser silently translating a customer-facing document.
A safe bilingual document pattern
When both parties agree, keep the legally controlling language clear and use short paired descriptions:
Accessibility audit / Barrierefreiheitsprüfung — July 2026
Avoid machine-translating tax declarations or contract terms without review. A mistranslated “reverse charge,” warranty, or late-payment clause can change meaning. For important language, use a qualified translator or local adviser.
Organization settings can define default footers, custom fields, and line labels, while individual documents can add their own notes. Invoice Master offers five PDF layouts; it is not a free-form multilingual template engine with conditional paragraphs by country.
Currency display is not currency conversion
Agree these points before invoicing:
- the invoice currency;
- whether the customer may pay in another currency;
- who bears bank and intermediary fees;
- which exchange-rate source and date apply if conversion is required;
- which amount counts as full settlement; and
- how withholding or tax certificates will be handled.
Do not add an informal exchange-rate note that conflicts with the legal obligation. The selected document currency should match the quote or contract unless both parties agree to a change.
Stripe payment links add another eligibility layer
Premium organizations with a connected Stripe account can create a hosted payment link for an invoice. The Invoice Master and Stripe payment workflow explains the processor boundary. Stripe controls which payment methods appear according to the connected account, country, currency, capabilities, settings, and transaction. A currency supported by the Invoice Master document model is not automatically a currency or payment-method combination available to every Stripe account.
When Stripe reports success, Invoice Master records the payment. Stripe controls settlement and payout conversion. Refunds and chargebacks handled later in Stripe require matching manual records in Invoice Master.
Tax and e-invoicing remain separate
Choosing a currency or interface language does not determine VAT, GST, sales tax, withholding, or place of supply. It also does not convert the PDF into a structured e-invoice. For EU VAT, the European Commission’s invoicing overview explains common requirements and national variations. Other jurisdictions have their own primary authorities.
Invoice Master can store line-item tax and custom wording. It does not validate tax identifiers, choose the legal tax treatment, or transmit Peppol or country-specific e-invoice data. The invoicing trends article separates those structured transmission changes from ordinary PDF delivery.
A support matrix
| Need | Current support |
|---|---|
| Choose a currency per invoice or quote | Yes |
| Store line items and totals in that currency | Yes |
| English, German, and Spanish interface/PDF labels | Yes |
| Automatically translate entered descriptions or notes | No |
| Live exchange rates or home-currency accounting | No |
| Automatic tax determination | No |
| Stripe-hosted invoice payment link | Premium, subject to Stripe eligibility |
| Structured government/network e-invoice transmission | No |
For the broader legal and operational sequence, use the international invoicing checklist. The honest advantage here is flexibility at the document layer—with translation, conversion, tax, and statutory transmission left explicit rather than implied.
