Cost Management - Cost payment applications - don't allow manual entry of decimals that exceed the project rounding settings

[danylleu]

Example: If the Project Rounding Settings have an Accuracy of 1 - I don't want end users to enter extended accuracy values greater than the allowed rounding setting. 

I'm being told The API always returns the same accurate value that was saved on the database side. 

This is problematic when extended accuracy values could exceed the allowed schedule of value amount on the Cost payment applications 

But the rounding setting doesn't flag this as an overbilling.