What is the difference between Financial/Transactions/Batch and a Sales/Transactions/Invoicing Batches other than the Financial batch allowing a number of "Frequency" recursion options other than "Single Use" (of which is the only Frequency option available to an Invoicing Batch)?
The reason I ask is I am able to manually create a new Sales/Transactions/Invoicing Batch and modify it within the Financial/Transactions/Batch entry editor, and visa versa assuming I type in the Batch ID rather than selecting it from a list using the search magnifying glass. The only visual difference I can see is the "Origin:" value is displayed/saved differently depending on whcih entry editor is used to view/save the entry and, of course, the "Frequency:" value is always "Single Use" when the batch is viewed in the Invoice Batch entry editor (see below). I have to presume the "Origin:" value is used for contextual entry filtering during magnifyingglass based searches.
I have been asked to write software of which will manage recurring Inovices in the hopes of reducing manual work-load and data entry errors. Ultimately, I will be creating recurring Invoices progammatically and I would like to programmatically handle recurring invoices via these batches allowing GP to handle the Invoice process schedule. Not all programmatically submitted invoices will be recurring. Some will be handled via Single Use batches. And, not all invoices will be created programmatically. Quite often, there will be manual batch and invoice entry.
My concern is this: "If" I am able to create the recurring batch as shown above on the left and programmatically stuff it with Invoices such that those invoices "join" the recurring schedule and are handled by GP, would this cause any "weirdness" in GP (Reporting wise, General Ledger wise, Manual Data Entry wise, etc..)? I do understand if I create the Invoicing Batch on the left and manually edit and save it using the Sales/Invoicing Batch entry editor I will loose my Recursion and Origin attributes.
*This post is locked for comments