Skip to content
DataRestro

Global

Currency, tax and time zones outside Nepal

Each restaurant has its own currency, timezone and tax settings, so one account can run a kitchen in Kathmandu and another in Dubai. Here is what is supported and what is not yet.

Try the live demoNepal first
A restaurant exterior lit at night

The same bill in six cities

Pick a city. The receipt recalculates with the same rules the API uses: inclusive tax extracted, exclusive tax added, service charge on the goods value.

Settle the same order in

Tax mode
Inclusive: VAT is inside the menu price and extracted for the return
Service charge
Off
Local time
—

Himal Kitchen

Kathmandu · Table 7 · 4 covers

  • 2 × Chicken Momo (10 pc)NPR 760.00
  • 1 × Dal Bhat ThaliNPR 450.00
  • 2 × Masala ChiyaNPR 180.00
Subtotal (incl. tax)
NPR 1,390.00
Net of tax
NPR 1,230.09
VAT 13% (included)
NPR 159.91
TotalNPR 1,390.00

Illustrative prices and rates. You enter your own

Support

What is supported today

Available
in the product, working end to end
Partial
some of it exists, limits stated
Planned
not built yet

Money

  • Currency per restaurant

    Any ISO currency code (NPR, USD, EUR, GBP, AED, SAR, INR), formatted the local way on screens and receipts.

    Available

  • Decimal arithmetic

    Money is never a floating-point number, in any currency.

    Available

  • Several currencies on one bill

    Taking USD cash in a rupee restaurant, with a rate of the day.

    Planned

Tax

  • Inclusive or exclusive tax

    Inclusive prices have tax extracted for the return; exclusive prices have it added at the till.

    Available

  • Per-item tax rate

    Override the restaurant rate for a single item.

    Available

  • Service charge

    A configurable percentage, reported separately and kept out of revenue.

    Available

  • Loyalty tax treatment

    Points redeemed as a discount (before tax) or as a tender (after). Your accountant decides.

    Available

  • Country fiscal modules

    Pluggable per-country invoicing and e-reporting. Nepal first; not built yet.

    Planned

Time & place

  • Timezone per restaurant

    Sales, tax and end-of-day reports follow the restaurant's own calendar day.

    Available

  • Restaurants in different countries

    One account, each restaurant with its own currency, timezone and tax settings.

    Available

  • Per-branch menu and prices

    Today the menu is shared across a restaurant’s branches.

    Planned

Language

  • English interface

    Staff screens, guest menus and receipts are in English today.

    Available

  • Nepali interface and receipts

    The first translation, with Devanagari receipts.

    Planned

  • Further languages, right-to-left

    Hindi, Arabic and others once the translation layer is in place.

    Planned

Reports follow your local day

Reports group sales by the restaurant's own calendar day, not the server's UTC day, so a late dinner service is counted on the right date.

Kathmandu (UTC+5:45)Server (UTC)
Dinner rush19:30Sat 26 Sep13:45Sat 26 Sep
Last table23:50Sat 26 Sep18:05Sat 26 Sep
Sunday’s first chiya05:30Sun 27 Sep23:45Sat 26 Sep
A UTC server would book Sunday's first chiya into Saturday's takings. DataRestro files it by the restaurant's timezone. Kathmandu's quarter-hour offset is a good test: plenty of systems assume offsets are whole hours.

Where your data lives

Where your data is hosted

The hosted service keeps its database in Singapore and serves the website and API through Cloudflare's network.

Some rules ask for more. Nepal's e-billing rules expect a cloud system's central server to be in the country; DataRestro can be deployed on in-country hosting, but we do not operate it there yet. Card processing stays with the acquirer you already use: DataRestro records the payment, it does not process it.

Talk to our teamSecurity