Customers using 2020.3 REST Version and above
What are we doing about it?
We have logged a ticket with ConnectWise advising the issue.
You may request updates to this ticket and advise if you are affected by this issue:
ConnectWise Ticket: #14465878
Date Reported: 24th of February 2021
|24 Feb 2021|
Submitted a ticket with ConnectWiseTicket#14465878
|25 Feb 2021||Connectwise has confirmed that this has been escalated to their Development Team|
The underlying issue is that the PO and PackingSlip ID when defaulted will allow records that have already posted to post. This is as a result of the data being provided in the export again, even though the export has previously been completed for some items on the purchase order. Simply, the export contains data that it should not.
How do we know it's an issue?
When the Packing Slip ID is set to the default, PO# in ConnectWise will send through all items for that PO / SLIP combination, regardless if the items had been previously posted. There is NO GL Batch details in the above purchase details, or an indication if an item has been previously batched which results to have received two items, both will be posted into the accounting system (duplicating the already posted item).
See example below: One item has been received with Packing Slip: PO297, and posts through correctly.
When the next items are received (after the above has been batched), but with the same packing slip information. There are NO GL Batch details in the above purchase details, or an indication if an item has been previously batched. As we now have received two items, both will be posted into the accounting system (duplicating the already posted item).
The current workaround is to ensure that the Supplier-Invoice Process is being followed.