One of our customers in AR somehow lost the information in "Average days to pay" on the statistics tab. It says 0 even though they have a lot of activity on their account and the accurate number should be much larger. Also "Total days to pay" is at 0. The only editable field I see is the "Total days to pay" so I looked at a backup of our data and it said that the "total days to pay" was at 61090 and the "average days to pay" was 43.14 for this customer. I tried to manually edit the "Total days to pay" and put it back to 61090 but it gave me this restriction.

"Value must be between 0 and 32,767".

So, if I enter 32,767 and save it and go back in, it puts the amount to 0. If I enter 32,766 it saves the number successfully but the average days to pay calculates to only 23.11 instead of 43.14.

Why am I limited to the 32,766? Is this what caused the customers stats to go to 0?

I notice the same problem on other large accounts. "Total days to pay" is being reset to 0, perhaps after the number exceeds 32,766? We are therefore not able to see the "Average days to pay" on our large accounts.

Hi Susan,

The Total Days to Pay field is stored in the database as an integer value, which indeed means that there is a maximum value of 32,766, which is 2 to the power of 15, minus 2. If the maximum value is exceeded, indeed that could result in getting set to zero. As would the average days to pay, which is calculated from the total days to pay divided by the total paid invoice count. This calculation is why when you put in the maximum 32,766 for Total Days, the 'new' average days is about half of what you were expecting, because the 'real' total days is close to double the maximum.

These field values get reset when Year End Processing is performed. So for customers that have a high volume of invoices that aren't paid promptly in a given year, it is possible to blow the maximum. For example, having 1000 invoices in a year and taking on average 33 days to pay. Or perhaps Year End Processing is not run, in which case these statistics values would never get reset.

It would take a database change to the customer records to increase this maximum. I will forward your comments to R&D.