[v4.6.99] Transaction collections ignores decimals

[twothreenine]

When entering transactions via finance/transactions/new_collection, the amounts are processed as integers, ignoring the decimals. Only by entering singular transactions to a specific ordergroup, it is possible to enter amounts with decimals.

[twothreenine]

I found out that it works with decimal point, just not with decimal comma.
Entering a singular transaction works both with decimal point and decimal comma.
There are more cases in which only decimal point works, like received units per group in an order:

And then there is a case where decimal point seems to work at first, but it is not processed: On the "receive" page

After submitting, the numbers are rounded to the nearest integers.

[wvengen]

Thanks for your bug report. That's quite odd, especially the receive screen-case.
The code used for allowing both comma and point is really old, it might suffer from bit-rot. Would be good to review.
The database should have a decimal for these fields.

[twothreenine]

When entering transactions via finance/transactions/new_collection, the amounts are processed as integers, ignoring the decimals. Only by entering singular transactions to a specific ordergroup, it is possible to enter amounts with decimals.

This has been resolved in #921 👍

Could we use a similar logic to fix the balancing menu case, too, or is that a different problem?