Multi-currency Receipts
Understand how current Stareceipt code handles receipt currency, country defaults, and FX-aware features without assuming universal per-receipt exchange-rate tooling.
Last updated: 2026-06-02
Overview
Stareceipt stores a currency code on receipts, reports, and related items. Current shared code paths normalize missing or ambiguous currencies from the recognized receipt content first, then fall back to the configured default currency for the receipt country, and finally to the restricted global fallback currency when nothing better is available.
How receipt currency is resolved
When a receipt is recognized:
- If the recognition result already contains a currency code, Stareceipt keeps it.
- If the receipt currency is missing, the service falls back to the configured default currency for that country.
- If neither the receipt nor the country configuration provides a currency, the restricted global fallback currency is used.
This means the most important field to verify on foreign receipts today is the receipt currency itself.
What is surfaced today
Current shared clients and APIs prove the following currency behaviors:
- Receipts keep their own currency code.
- Report items surface per-item currency codes.
- Report summaries can expose totals grouped by currency instead of forcing every receipt into one converted base amount.
Where FX conversion exists today
Automatic FX rate fetching currently exists in the budget domain. The service can fetch and cache FX rates for budget calculations and can surface missing FX-rate gaps when a required conversion is unavailable.
What this page does not assume
The current codebase does not prove any of the following as universal receipt features:
- a receipt-level Exchange rate field,
- a guaranteed Base amount field on every receipt,
- automatic retroactive re-conversion of already saved receipts,
- a promise that analytics always flatten every receipt into one converted ledger currency.
If your deployment adds those features, document them separately for that client build.
Practical guidance
- Verify the receipt currency whenever the printed document is ambiguous.
- Keep country configuration aligned with the markets you operate in so the default currency fallback is correct.
- Expect reports to preserve original currencies and show grouped totals per currency where appropriate.