When to Use
Use Currency fields for:- Prices and costs
- Revenue and income
- Claim amounts
- Loan amounts
- Insurance premiums
- Fees and charges
- Any monetary value
- Use Number for non-monetary numeric values (quantities, scores, measurements)
- Use Text for formatted financial references (invoice numbers, account IDs)
Configuration Options
Examples
Basic Currency Amount
Collect a monetary value:Annual Revenue
Collect revenue with prefix:Insurance Premium
Collect premium amount:Validation
Currency fields enforce monetary validation automatically:Type Validation
- Only numeric values accepted
- Maximum two decimal places (cents precision)
- Non-numeric input rejected
Range Validation
min- Minimum allowed value (inclusive)max- Maximum allowed value (inclusive)- User cannot enter values outside range
Currency fields always enforce a maximum of 2 decimal places, ensuring
consistent monetary precision.
Best Practices
Always use Currency for monetary data:- Don’t use Number for financial amounts
- Currency enforces two-decimal precision automatically
- Ensures consistent formatting across the platform
- Add
prefix: "EUR"orsuffix: "EUR"to indicate the currency - Helps users understand the expected currency
- Be consistent across all currency fields in a case
- Use
min: 0to prevent negative amounts (when appropriate) - Set realistic max values based on business context
- Catches data entry errors early
- Include currency in the name when relevant: “Amount (EUR)”
- Distinguish between gross and net amounts
- Clarify the time period: “Annual Revenue” vs “Monthly Revenue”
Related Field Types
Number
Use for non-monetary numeric values
Text
Use for financial reference numbers and IDs
Data Schema Overview
Back to Data Schema overview