When there is a PNV workflow template to export XUT files to an external system there are now two scenarios that can happen when using BravoTran:
Likely your PNV workflow template is set up to only handle scenario 1.
To support both manual processing of invoices in CargoWise and posting invoices through BravoTran, existing triggers will need to be updated to only export payables transactions, and two triggers will need to be added, one for auto-posting payables transactions, and one to export the XUT to the external system, similar to scenario 1 above.
What your existing trigger to export the invoice to the external system likely looks like, but with the REF = AP|INV|Posted condition added.
The trigger to automatically post the BravoTran invoice with a delay to a trigger that will export the BravoTran invoice to the external system. REF is set to PA|IPA|Created to make sure it only fires if the transaction is in the transactions pending allocation queue.
The trigger that fires after a minute to export the BravoTran invoice to the external system. This should be the same as the first trigger, but without a REF condition.
The one ADD trigger to export to the external system has fired.
The ADD to export to the external system hasn’t fired, but the one that auto-posts the transaction and start a delay has fired.
The DLY to export to the external system after the invoice from BravoTran has been posted has fired.
There is a race condition when there is both an ATP completion action and an XUT completion action to export the invoice from CargoWise. The XUT will actually be an XML file for a pending allocation, not a payables transaction.
Pending Allocation XUT (bad):