Hey! Found it — and you were right on the money, the decimal point and comma were tripping over each other. Here's what was happening in plain English: because budgets can use either format (1,234.56 or 1.234,56), the input field has some logic to figure out which character you meant as the decimal point. Normally that helps people out — if you type a comma when your format expects a dot, it'll auto-correct it for you, since typing the "wrong" separator doesn't really make sense for anything else. But that auto-correct was too eager. When you pasted 140,915.77, it grabbed the first comma it saw and went "ah, that's the decimal!" — locked it in, took the next two digits as cents (91), and then dropped everything after that. So 140,915.77 became 140.91. Whatever came after the first separator got thrown away. Same thing was quietly breaking pastes on the dot-thousands format too (1.234,56 was becoming 1,23). Fix is in — now it scans the whole number first before deciding which separator is the decimal. The last separator wins, and anything before it is treated as thousand grouping and stripped out. Pastes from spreadsheets, bank statements, anywhere — should all just work now, regardless of which format your budget is set to. It's out now :) Try again and let me know.
I wonder what is going on here? I have just tried creating a transaction for 140,915.77 (both as inflow or outflow) and the number input has formatted perfectly. My test is on Web using the Brave browser and also on iPhone BUT AS YOU SAY, if I try copying and pastingthe number in than this error appears!! I had never thought of pasting before.
I understand your explanation and appreciate your breaking it down for me. I will have an opportunity to check it out tomorrow and will let you know…Thanks again!
Paul, I use copy/paste since it prevents typos because I sometimes I’m switching between multiple browser tabs when messing around in the budget.
Thank you! And it’s good that all use cases are now covered.
Ran into this copy/paste issue again while copying "241,538" into a Balance Adjustment window. The result of the paste was "241.53". I will post again when and if I run into this anomaly.