I suspect the receiver number got converted to zeroes. So you can probably locate it in invoicing using this receiver number of zero.

As far as making back-end changes, I cannot generally recommend that one do this. An example of this is that you may not get all the places the TranNo exists. For example, depending upon your posting detail level, the TranNo may also exist in tglTransaction.TranNo. This is only an example, and the may be more places.

Unless the receiver number is crucial, you will be safest in using the zeroes TranNo and just live with the one receipt with the issue. The issue should not occur again as if someone enters one that rounds down to less than one, it will complain about it being a duplicate.

If you feel that you must have changes made in the back-end, realize that you may generate data that is incorrect and unsupported by Sage. If you must do this and you are an end-user, please contact a partner for assistance. If you are a partner, proceed at your own risk (and that of your customer's).

Thanks for the answer. You are correct that it wants to convert the number to zeros when we select it. When we enter a receiver number of 0 (or 10 0s) directly, it does not work. It would appear we will need partner assistance.

In case you have not already done this, ensure that the receiver has not already been invoiced. Both 7.4 and the upcoming release will allow you to invoice a receiver of zero. However, once it is invoiced, the lookup will no longer allow it to be selected. You can use the Explore Stock Receipts for this, making sure the display includes the Voucher Nbr column. I am sure there are other ways to do this lookup.

If you have already done this, then argh! If you haven't, then maybe it will save you a call.

Good luck either way.