Billing UoM - not matching Sales Order

Few settings to check:

• Decimal precision in “Companies” screen
• “Divisible” setting on the stock item for the UOM

Have a screenshot of the examples of the differences between the stock item conversions and the billing?

Hello ​@sahbixby ,

Acumatica does fully support fractional (decimal) quantities for converted Units of Measure (UOMs), provided that the Divisible Unit check box is selected for the items in question.
By default, you can configure UOMs for items so that they can be measured only in integer quantities, which is often used to prevent fractional errors in inventory, sales, and purchase documents
If the system is forcing your UoM to act as an integer value with no decimals, it means this setting is currently turned off.
To resolve this issue and allow fractional quantities, you need to update the item's settings:

• Navigate to the Stock Items (IN202500) or Non-Stock Items (IN202000) form (depending on the item type).
• On the General tab, locate the Unit of Measure section
• Next to the Base Unit, Sales Unit, and Purchase Unit boxes, you will find the Divisible Unit check box
• Select the Divisible Unit check box for the relevant UOMs. When this check box is cleared, the system operates using only integer quantities for that item in transactions and documents Selecting it will allow you to use decimals.

Note: If you want this to apply to all new items created within a specific class, you can also select the Divisible Unit check box in the Unit of Measure section on the Item Classes (IN201000) form
The UOM settings specified at the item class level are automatically copied to new items created within that class.
 

Regards,

Vard

​@travislawson ​@Vard86 -

I can confirm:

1. We have decimal precision to 4 digits turned on
2. The UoM is defined in the stock item with conversions
3. Stock items have divisible unit checked

I have received feedback from Acumatica confirming that Acumatica will not convert the invoice document if it results in non-integer (decimals), and will use the base/shipping unit on the original document.  

I have provided feedback to their development team as it seems to deviate from the purpose of having a unit of measure conversion if it limits it to only integers and from my perspective is a limitation of system based on design