Internationalization Quality: Currency Amount Formatting Toolkit
Scale currency consistency across a global product suite
I led a currency formatting standard for a worldwide employee-facing system—turning fragmented patterns into a practical toolkit (rules + examples + components) that teams could ship consistently across products and surfaces.
Problem
Currency UI was inconsistent across products (format, symbol/ISO usage, abbreviation, hierarchy), creating design churn, review friction, and avoidable implementation rework.
Solution
A flexible currency toolkit that teams could apply consistently across products:
- 3 display formats: Short / Standard / Explicit
- Decision rules: when to use each format + accepted exceptions
- Code-backed components: estimates/abbreviations, conversion, currency selector, amount input
- Design QA: a lightweight Figma QA plugin to catch common i18n issues earlier
Impact
Adopted by 10+ design teams and scaled across 20+ product lines, with code-backed components shipped and added to the central design system library.
Currency formatting was inconsistent—and expensive to maintain
As our products scaled globally, currency amounts showed up everywhere—travel, procurement, contracts, finance. But teams used different formats and precision, leading to inconsistent UI and slow, repetitive reviews.
Key Currency Formatting Inconsistencies
- Inconsistent ISO code placement (e.g., USD 1,000 vs 1,000 USD)
- Mixed currency format（$ / USD / US$）
- Unclear large-number formatting (K / M / B)
- Inconsistent currency picker options
- Define visual hierarchy rules for totals
One standard, global by default
Define a global-by-default currency standard that works across:
- Products (travel / procurement / finance)
- Surface (card / table / form)
- Intent (scan / compare / verify)
Step 1: Audit current patterns and tag issues
🎯 Objective
Create a complete picture of today's currency formats and pinpoint the inconsistencies.
💪 Action
Audited key products/surfaces and tagged recurring formatting problems.
Formatting Problems Collection
Step 2: Synthesize from 50+ industry references
🎯 Objective
Extract scalable patterns that work under real UI constraints.
💪 Action
Reviewed 50+ references and summarized durable currency display conventions.
References from different industries
✅ Output
A draft 3-format framework, synthesized from internal audit + 50+ benchmarks, to validate with business lines.
Format framework (initial framework—not final rules)
Step 3: Validate the 3-format model with multiple design teams
✅ Output
Aligned on a draft guideline that teams can apply consistently—covering edge cases, cross–business line needs, and rollout expectations.
- Decision rules (Short vs Standard vs Explicit)
- Edge-case alignment
- Examples by surface + adoption agreement across business lines
Deliver a toolkit, not just formatting rules
A 3-format framework + decision rules + reusable components—so teams can display and implement money consistently by default.
Part 1: Format rules teams can implement
Locked the "how to format" rules (ISO, spacing, separators) into a single source of truth.
❇️ What teams get
- Exact formatting rules (ISO and number placement, spacing, separators)
- Correct vs incorrect examples for quick QA
- Implementation-ready for design + engineering
Format rules for Short and Standard formats (USD)
Part 2: Decision guidance for choosing formats
Defined decision rules so teams can pick Short / Standard / Explicit consistently across scenarios.
❇️ What teams get
- Decision rules: how to choose Short vs Standard vs Explicit
- Accepted exceptions: when variations are allowed
- Surface examples: table / card / form / detail
Decision guidance for Standard formats
Part 3: Components & patterns for money workflows
Turned the standard into reusable components—so teams ship money workflows consistently, not just format text.
❇️ What teams get
- Large-number shorthand (estimate + full value)
- Patterns for conversion (original vs converted)
- Currency selector + amount input (defaults, validation, formatting states)
❇️ Read the full guideline
If you're interested in the full specification (format rules, scenario examples, and component usage), you can view the document here: Currency Amount Formatting Guidelines.pdf
Bonus: Figma QA plugin to reduce i18n review churn
Designers can't realistically memorize every i18n rule (currency, date/time, English copy). To catch issues earlier, I built a lightweight Figma QA plugin (Cursor + GPT) that brings i18n checks into the design workflow.
❇️ What teams get
- Scans frames and flags non-compliant patterns
- Gives clear, fixable guidance (what's wrong + what to change)
- Enables one-click apply for safe fixes
Partner with engineering on adoption and migration.
New work (default by design):
Use the latest currency component and guideline for all new features and surfaces.
Existing inconsistency (incremental migration):
Migrate legacy screens during feature iterations.
Shipped and standardized: Added currency components and guidelines to the central design system library, with code-backed components implemented in production.
Adopted at scale: Used by 10+ design teams and reused across 20+ product lines.
Reduced rework: A lightweight Figma QA plugin helped catch common i18n issues earlier and lowered avoidable iterations.
I realized a global format fails when it's too strict—teams will resist or work around it. A toolkit approach worked better: a clear default, lightweight guidance on when to use each format, and documented exceptions that keep flexibility without losing consistency.