Multi-Currency by Default: Global Compliance Without the Complexity
We're built different. Because your business shouldn't break when a guest pays in a different currency.
Global operators don't think in one currency. Their software shouldn't either.
Most platforms bolt on multi-currency as an afterthought. A locale setting here, a conversion table there. The result: rounding errors, mismatched reports, compliance gaps, and revenue leakage across borders. Calisto treats currency as a first-class entity woven into every product, every transaction, every report from the architecture up.
Native Currency Storage
Every transaction stores both the local currency and the reporting currency. No post-hoc conversions. No rounding drift. The source amount is always preserved alongside the converted value.
Per-Property Configuration
Each property operates in its own currency with its own tax rules. A hotel in Lisbon charges EUR, your resort in Cancún charges MXN, your lodge in Cape Town charges ZAR. One dashboard, correct everywhere.
Compliance Built In
Tax calculations, invoice formatting, decimal precision, and currency symbols follow regional rules automatically. Brazilian Real uses comma decimals. Kuwaiti Dinar uses three decimal places. Calisto knows.
Currency is an entity, not a setting. That changes everything.
From property configuration through POS checkout to consolidated reporting, currency flows through the entire architecture without manual intervention.
1. Property-Level Currency
Each property declares its operating currency during setup. All pricing, invoicing, tax calculation, and POS transactions use this currency natively. No global override. No locale hacks.
2. formatCurrency Everywhere
A single shared formatting function handles symbol placement, decimal precision, grouping separators, and locale rules for every currency. Every product uses the same function. Consistency is architectural.
3. Dual-Amount Transactions
Every financial record stores the original amount in local currency plus the converted amount in reporting currency, with the exchange rate and timestamp locked at transaction time. Auditable. Immutable.
4. Regional Tax Engines
Tax rules vary by jurisdiction: VAT in Europe, GST in Australia, CFDI in Mexico, ISS in Brazil. Calisto applies the correct tax engine per property, per transaction type. Not a tax table. A tax architecture.
5. Channel-Aware Pricing
Pulse publishes rates in the property's currency. OTA channels receive prices in their expected currency. Conversion happens at the channel layer, not at the property. Rate integrity preserved.
6. Consolidated Reporting
Portfolio-level reports roll up revenue across currencies into a single reporting currency. Exchange rates captured at transaction time, not report time. Historical accuracy maintained. No reconciliation surprises.
How native multi-currency transforms global operations
Same architecture, different currencies. Every vertical benefits from built-in global compliance.
Multi-Property Hotel Groups
Properties in five countries, five currencies, five tax regimes. Each property operates natively in its local currency. Owners see consolidated P&L in their reporting currency. POS charges in local currency. Folios convert automatically.
Result: Eliminate manual FX reconciliation
Vacation Rental Portfolios
Listings across Airbnb, Booking.com, VRBO in multiple countries. Guests book in their currency, property earns in local currency, manager reports in home currency. OTA payouts reconcile automatically against bookings.
Result: Zero revenue leakage from FX gaps
International Event Venues
Proposals sent in client's preferred currency. Deposits collected in venue currency. Vendor payments in supplier currency. Event P&L consolidated accurately with locked exchange rates. No spreadsheet gymnastics.
Result: Accurate cross-border event costing
Real Estate Developers
International buyers purchasing units in USD, EUR, or local currency. Milestone payments tracked per-unit in buyer's currency. Development costs in local currency. Investor reports in reporting currency with full FX audit trail.
Result: Compliant cross-border sales tracking
Multi-currency requires architectural commitment, not a settings page
Adding currency support after the fact means every product, every report, every tax calculation needs retrofitting. That never fully works.
Locale-Based Approach
Set a locale, get a currency symbol. Formatting inconsistent across modules. Tax rules hardcoded per region. Reports only in one currency. Cross-property consolidation requires export and manual conversion.
Plugin or Add-On
Third-party currency plugin bolted onto existing system. Conversion at display time, not transaction time. Historical rates lost. Tax compliance separate. POS and booking system may not share the same conversion logic.
Calisto Native
Currency is an entity on every transaction. Dual-amount storage with locked exchange rates. Shared formatting across all 27 products. Regional tax engines per property. Consolidated reporting with full audit trail. Built in, not bolted on.
Every region has rules. Calisto follows them automatically.
Currency formatting is just the surface. Real global compliance means tax invoicing, decimal precision, regulatory reporting, and data residency handled per jurisdiction.
Americas
USD, BRL, MXN, COP, ARS, CLP. CFDI electronic invoicing for Mexico. Nota Fiscal for Brazil. IRS-compatible reporting for US properties. Comma vs period decimal handling automatic.
Europe & Middle East
EUR, GBP, CHF, AED, SAR, KWD. VAT-compliant invoicing with reverse charge support. Three-decimal currencies (KWD, BHD, OMR) handled natively. GDPR-compliant financial records.
Africa & Asia-Pacific
ZAR, AUD, NZD, THB, IDR, JPY. Zero-decimal currencies (JPY, KRW) handled correctly. GST for Australia and New Zealand. Region-specific invoice templates. Right-to-left currency display where required.