Amount fields currently parse values based on the decimal period separator (meaning, digits after a period are always treated as the fractional units). This is especially an issue when entering three digits after a period for currency notations where the period is a thousands separator, and where fractional units don't exist (i.e. ISK). Current behavior is the following, regardless of currency locale: • 100.29 (two digits after a period) = 100.29 • 100.299 (three digits after a period) = 100.30 • 100,29 (two digits after a comma) = 100.29 • 100,299 (three digits after a comma) = 100,299.00 This works for currencies that use the period as the decimal separator, and comma as the thousands separator, but when the currency locale setting is set to display with the comma as the decimal separator, and the period as the thousands separator, Lunch Money should treat entered values like this: • 100.29 (two digits after a period) = 100,29 • 100.299 (three digits after a period) = 100.299,00 • 100,29 (two digits after a comma) = 100,29 • 100,299 (three digits after a comma) = 100,30