I added the CODE option to your original post, now we can see how your numbers are not lining up. I see what you mean now.
I suggest painting a field in your model template that ensures you will capture the column of numbers you want without worrying (yet) if you capture supefluous numbers. Specify this field as a CHARACTER field (not numeric). Let's call this field: Original_Field.
Then, in your Monarch table, try a calculated field (numeric) to cleanse the original field and show the correct number:
Here is the same formula with annotations:
/Above checks to see if a negative sign exists/
/If a negative sign exists, the field is split into two parts based on the negative sign, then converts to a value, making sure the value is negative/
/If no negative sign exists, just convert the original field contents from a character field to a numeric field. The leading space is ignored./
Let me know if this helps you. If you also trap superfluous numbers when no negative sign exists, we can modify the above formula to handle that.
I always recommend creating one long field in the model template and then cleaning up the results in the Monarch table view using string functions like INSTR and LSPLIT. You can always convert the results back to a numeric value using VAL function.
An excellent resource for Monarch functions is the Monarch functions guide, available on our website-definitely worth reviewing:
(Large PDF-75 pages-but very helpful. Monarch V8 new functions to be added)