Consistency in decimal recognition
DS should make use of the standard method of decimal identification and apply that to all numbers within a document.
i.e. 8,930.15: ","is a thousand separator while "." is a decimal separator. If this is the standard for all numbers in a document, then a number presented as 45.118 should be read with "." as a decimal separator (not a thousand separator).
AdminJustin
(Admin, DataSnipper)
shared this idea
-
Anonymous
commented
Account Numbers or Codes being recognized with periods included, not as numbers in the thousands
-
Anonymous
commented
This is a crucial item for our firm as several of our key ideas for DataSnipper integration are not the "standard" dual decimal format (as noted by previous comments)
-
Anonymous
commented
I have noticed this issue when snipping Tonnes sold on Grain tickets for agricultural clients, which typically have 3 decimal places (i.e, 123.456 Tonnes will snip as 123,456.00 Tonnes).
-
AdminJustin
(Admin, DataSnipper)
commented
This is particularly relevant for investment statements where rounding to the nearest 3rd or even 4th decimal place is common.
Very small differences can easily become material errors when extrapolated. Having DataSnipper correctly read the numbers where rounding is therefore crucial.
-
Kayla Williams
commented
Periods are being recognized as commas and vice versa. A number such as $8,088.83 is being imported as 8,088,83 and as such not being recognized as a number.