I had previously made this same request. What we’ve ended up doing is using it as more of a review process. So when PTI passes the WO over we can look and find all new invoices that have WO####, we review those invoices then just delete the WO number out of the invoice field. At that point Peach can go through its normal assigning process when doing batch invoices.
Previous request regarding this:
Hi again Chris
I wanted to update you about the feature wish - that PTI places nothing in the invoice # field in the PeachTree invoice and subsequently nothing in the workorder’s Invoice# field.
It is felt that this is not a feature that could be implemented because than there would be no cross-reference between the PeachTree invoice and the AyaNova workorder. We would get so many users emailing us saying that they don’t know what workorder goes with what invoice etc - there has to be something as the invoice # field to be a reference between the two.
I know that the other wish was for PTI to figure out what the PeachTree next invoice number would be, but that is not possible at this time.
In the case of the WO text prefixing - this is used to indicate that the invoice came from an AyaNova workorder, and therefore would not conflict with an existing invoice number that may be the same number as an AyaNova workorder. We picked WO as it had to be something.
If you have another suggestion on this, I would be very happy to pass it onto development, but just wanted to give you a heads up.
Mainly what would be nice is options here. It could always be default that the WO# goes into the invoice field, but how about an option to place it in the PO field and have the Invoice NULL, or just not to put in any field at all. Again, it’s just the ability to have the choice of doing it that way. Peach has good search features at this point that the WO is already referenced in the top line and is very easy to find via search.
That’s my main wish is to have different choices, just like you have the choice to close or not close the WO upon invoicing. How about some link choices? Like allow the choice of linking client reference field to the PO field, or the WO to the PO field, etc. So basically what this is doing is allowing different options based on the different ways people are using the fields. Same request goes for the shipping address field. As I said, we changed this to be a “service address” on the Invoice. So when we bill to head office we could put the actual client address in that field and it’s easily recognizable.
If you can take what is going on with the linking of items and customers and just change it so we can link various fields in Ayanova to fields on the Peachtree invoice that would be HUGE in the way of options and choices.