Skip to main content
P
Patti MC
May 22, 2020
Solved

Extra decimal points in the cost column of invoices and estimates

  • May 22, 2020
  • 1 reply
  • 0 views

We use QB for estimating as well as invoicing for our interior design business.  We do not use set prices in QB as everything is indivual to each client's estimate so we enter each price at the time the estimate is prepared.  Randomly, after a cost is entered in the cost column (say a price of 34.55), when the estimate or invoice is saved or printed QB will add an additional 4 decimal points (so the price shows up when printed as 34.556723).  If there are say 10 line items in the estimate this will occur with only one and it looks very unsightly.  I cannot figure out why it is doing this.  If you go in and change the price to get rid of the extra decimals when you save the estimate they magically appear again.  Any ideas as to how to prevent/get rid of this?

Best answer by GeorgiaC

Hi Patti, 

 

Thanks for your post and welcome to the Community 🙂

 

The number format should always be set to 2 decimal points so this is unusual to hear.

 

Can I check when you are referring to the cost column, does this relate to the 'amount' column on the invoice/estimate?

 

Do you use one of the default product/service in the product/service column (e.g. Sales) or is this a custom product/service? 

 

It may be worth checking this isn't relate to a cache issue by clearing the cache on the browser you are using here. 

 

Thanks

1 reply

G
GeorgiaCAnswer
May 22, 2020

Hi Patti, 

 

Thanks for your post and welcome to the Community 🙂

 

The number format should always be set to 2 decimal points so this is unusual to hear.

 

Can I check when you are referring to the cost column, does this relate to the 'amount' column on the invoice/estimate?

 

Do you use one of the default product/service in the product/service column (e.g. Sales) or is this a custom product/service? 

 

It may be worth checking this isn't relate to a cache issue by clearing the cache on the browser you are using here. 

 

Thanks

Terms & ConditionsAccessibility statement