Intacct Approval Processes (Informational)

this page is for informational purposes only and should not be used as a guide to make changes to the configuration of your sage intacct environment for support with your sage intacct native approval flows, please reach out to sage or your intacct implementation partner directly sage intacct has two known base approval processes bill approval , and payment approval generally speaking, out of the box configurations for bill approvals are supported by fispan, while payment approvals are not supported by fispan and will result in weird behavior for processing of payments viewing your configuration you must have sufficient permissions in sage intacct to view if you have approvals enabled go to accounts payable → setup → configuration scroll down in the page to find two sections “bill approval settings” and “payment approval settings ” bill approval ( supported ) the out of the box bill approval process is generally supported by the fispan sage intacct integration bills created are required to be approved prior to being available for payment in the plugin, bills that are created, but not approved, are not be shown as available for payment once a bill has been approved and is in the ‘posted’ status, it will be available for payment in the plugin this workflow is generally supported by fispan and does not interfere with the fispan payment flow payment approval ( not supported ) this approval process is not supported by fispan and will result in weird behaviour for processing of payments this payment approval flow requires someone to approve each payment, based on some rules set up in intacct why? without a payment approval flow, two things happen behind the scenes when a payment is submitted the payment request is sent from sage intacct to the bank for processing a bill payment is created, marking the bill as closed custom fields on the bill are updated with the latest payment status information however, with payment approval is set up, there is no mechanism to delay the sending of the payment to the bank until approval the payment is sent to the bank immediately, regardless of if the payment is approved or rejected inside of sage intacct this brings a considerable risk of duplicate payments a bill payment rejected in sage intacct returns the bill to a “posted” state (ready for payment), but does not recall the payment already submitted to the bank as a result, intacct will show an unpaid bill, despite the fact that the payment was already transmitted to the bank fispan requires that users disable the sage intacct payment approval flow before proceeding forward with production payments failure to do so will result in adverse impacts on payments that are rejected within the native intacct approval flow