Currency type fields are changing unexpectedly. It may appear that they are being rounded off at first glance, but a better description is that they are being approximated imprecisely. This is a feature of all floating point values.
For example: if you enter the value as 8092384905, Marketo will truncate it to 8092390000.
This is an expected behavior. Currency type fields are stored as single precision float values which have 6-7 digits of significance. Since standard fields type cannot be changed, we suggest that you create a new custom field to hold the currency value.
Often the easiest work-around for larger currency values is to use a field of type "String". String fields are adequate for storing a value, but do not offer the capability to compare (between, greater than, less than, at least, at most) values.
To preserve comparison capability, store the value as an integer which can take on values from -2147483647 to 2147483647. For US Dollars, this integer can represent the number of cents (pennies) and therefore currency values from ($21,474,836.47) to $21,474,836.47. Using this technique, the operators between, greater than, less than, at least, and at most will work, just remember you're what you're comparing: cents in this example.
If even larger values are required, two integer fields (large and small) can be used to represent currencies (again, assuming cents) from ($46,116,860,141,324,206.00) to $46,116,860,141,324,206.00. To break up a currency value into two fields, divide the number of cents by 2147483647 and store in the large value field, then store the remainder (modulus) in the small value field. To compare a compound (two fields) value, compare the large values first and if they are equal, then compare the small values. Since compound fields will be hard for a human to read, it may be prudent to also store the value as a string depending on your requirements.
Is this article helpful ?