A finance lead in Gurgaon exports a GST report on the first of the month and finds three invoices dated a day earlier than the payment confirmation she received. Nothing crashed. A server in Singapore wrote the timestamps in UTC, a browser in IST rendered them, and nobody had decided which one the invoice date should follow. That is the shape most global-application bugs take in the first ninety days: quiet disagreements between systems about what day it is and what a number means. It hits finance and operations teams first, well before it hits the roadmap.
What breaks first when an app goes global?
Dates, money and locale formatting break first, and they break in that order. Translation and layout get the attention in planning because they are visible, but a second timezone or a second currency creates bugs on its own — usually within two or three sprints of the first non-Indian customer signing up. The failure is rarely a crash. It is a report that does not tie to a bank statement, an invoice dated a day early, or a total that is off by a paise on screen and off in the other direction in the CSV export. These are expensive because they destroy trust in the numbers, and finance notices before engineering does.
Should every timestamp be stored in UTC?
Yes — store every instant in UTC and convert only at the edges, but keep the user's IANA timezone in its own column. In Postgres that means timestamptz rather than timestamp, and a text column holding values like Asia/Kolkata, never a fixed offset like +05:30, because offsets change for reasons your code will not predict. The harder distinction is between an instant and a calendar date. An invoice date, a payroll cut-off and a subscription renewal on the 1st are dates, not moments. A renewal on 1 March in IST fires at 18:30 UTC on 28 February; if you derive the billing date from the server clock each time, a slice of your customers lands in the wrong month and the reconciliation never quite closes. Retrofitting this into a live schema is the expensive version — a system architecture review before the migration is usually cheaper than doing it twice.
Why should money be stored as an integer?
Store amounts as integers in minor units with an explicit currency code, never as a float. Binary floating point cannot represent 0.1 exactly, so errors accumulate once you start summing line items and applying tax. Use a bigint of paise (or cents) or a numeric column with fixed scale, and treat the currency code as part of the value. Not every currency has two decimals — JPY has none, KWD has three — so rounding must follow the currency, not a global constant.
Take a ₹1,499 monthly plan at 18% GST. The line tax is ₹269.82 and the invoice total ₹1,768.82. Compute that in floating point, round the line and the total independently, and you can drift by a paise per invoice — invisible in testing, a reconciliation problem across 40,000 invoices a year. For cross-border billing, record the exchange rate and its source on the invoice itself; export invoices under an LUT are typically converted at the RBI reference rate on the invoice date. Confirm the exact treatment with your CA.
Is locale the same thing as language?
No — a locale is a bundle of formatting and behavioural conventions, and language is only one item in it. A Hindi-speaking user in Gurgaon and an English-speaking user in Cardiff may share a language and still expect different date orders, number grouping and a different first day of the week. Locale typically controls:
- number grouping and decimal separators (1,00,000 in India, 100,000 in the UK, 1.234,56 in parts of Europe)
- date order and month names (12/03/2025 is 12 March in India and 3 December in the US)
- currency symbol placement and how negatives are written
- week start day and weekend days, which matters for every calendar and SLA timer
- address field order, phone grouping and name order
Use the platform's built-in formatters (Intl.NumberFormat, Intl.DateTimeFormat) instead of hand-rolled string concatenation, and put them behind one module. Formatting scattered across templates drifts within weeks; consolidating it is the part of a web platform build that pays back longest.
What changes for an India-first product?
GST invoicing, the April–March financial year and lakh/crore grouping are the three that most often force schema or template changes. Invoice numbering has to run sequentially within a financial-year series with no gaps, which is awkward if your ID generator is distributed and invoices can be voided. Indian operations dashboards want 1,00,000 rather than 100,000, and often 12 Mar 2025 rather than 2025-03-12. Consent records under the DPDP Act need a timestamp plus the timezone in which consent was captured. And UPI settlement reports carry a settlement date that is not the transaction date — reconcile on the field your finance team actually books against, or the daily mismatch reports will never go quiet.
Where to start
Do it in this order: audit every date column and convert to timestamptz with a separate zone column, then move money to integer minor units with a currency column, then consolidate all formatting into one module, then touch invoice templates and FX capture. In our experience the first three are two to four weeks of work on a mid-sized codebase; the invoice layer takes longer because finance has to sign off on rounding rules before anyone writes code. Maysan Labs builds web platforms, dashboards and B2B portals for teams going through exactly this, and a second pair of eyes on the migration plan before it starts is a short conversation.
Buying software or a website?
Twelve questions to ask any vendor before you sign: price, your data, fit for an Indian business and support.
Get the free checklistWritten by Maysan Engineering Team at Maysan Labs, a software studio in Gurgaon, India. Follow us on LinkedIn