Is there a workaround or third-party solution for the limitation with AP system-generated payment batches being limited to only one at a time?
Is there a workaround or third-party solution for the limitation with AP system-generated payment batches being limited to only one at a time?
The only workaround for the standard sage is to export the AP Payment batch that is system generated, then delete it and reimport. IT then has imported status rather than System Generated.
So you could build a macro that would change the APBTA.BATCHTYPE field 4 to 1 or 2.
Hope this helps in some way
Stacey
The only workaround for the standard sage is to export the AP Payment batch that is system generated, then delete it and reimport. IT then has imported status rather than System Generated.
So you could build a macro that would change the APBTA.BATCHTYPE field 4 to 1 or 2.
Hope this helps in some way
Stacey
Simple yet brilliant
*Community Hub is the new name for Sage City