Vendor Approvals

the vendor approvals feature provides a robust and secure method for managing changes to vendor bank account information within your erp this approval process ensures data accuracy, minimizes the risk of errors, and enhances security by requiring authorization for changes to your vendor's banking data creating a workflow to create your vendor approvals workflow for your erp utilizing the plugin, please follow these steps enable vendor record approvals an erp administrator or consultant must first access the fispan portal by logging in at sys fispan live once logged in, select the vendor record approvals tile you'll then be prompted to start creating your workflows create a workflow once you are on the vendor record approvals page, click let's get started start by giving your workflow a clear, descriptive name for easy identification later next, select the entities you want the approval workflow to apply to addresses applies to addresses added via the payment methods page or changes made to the native erp vendor record address bank accounts applies to bank accounts added via the payment methods page or changes made to the native erp vendor record bank account email groups applies to email groups added via the payment methods page or changes made to the native erp vendor record emails note to exclude changes synced from the erp from this approval process, please contact the support team add approvers to workflow next, you need to define the approvers for your workflow in the first level, enter the approver's email address exactly as it appears on their user record in the erp system add another level for approval and additional approvers, if needed you can set up to three levels of approval at each level, you can add up to five potential approvers you can also decide how many individual approvals are required per level (e g level 1 requires 2 approvals, level 2 requires 3 approvals, level 3 requires 1 approval) note important considerations no self approval you cannot approve your own payments keep this in mind if a single user frequently acts as both the payment creator and an approver best practice for approvers to avoid delays, we suggest avoid having a single approver in a level adding more approvers than the required approvals (e g , include 4 approvers in a level that requires 2 approvals) this ensures the process can continue even if someone is unavailable important to approve changes, users in the workflow must have both an erp license and the necessary plugin permissions save workflow once you have configured your workflow, click save new workflow your workflow is now active all changes made to vendors through the {{productname}} will now follow this approval process editing a workflow you can edit or delete a workflow, but only if there are no pending approvals for that workflow this prevents any confusion or errors with payments currently going through the approval process in the event you need to edit a workflow with associated open payments, process or cancel any outstanding payments associated with the workflow select workflow you can edit existing workflows to adjust them click on the workflow you would like to modify edit workflow make your desired modifications, and click save changes editing restrictions modifying the entities associated with a workflow will disable any other workflows that were previously applied to those entities similar to making edits to workflows, all future requests for these entities will go through the new workflow; existing requests will remain unaffected deleting a workflow workflows with pending approvals cannot be deleted until those approvals are resolved deleting an active workflow can be done following these simple steps select workflow select the workflow to delete then, click delete workflow confirm deletion a pop up will appear confirm deletion by clicking yes, delete workflow disabling a workflow to disable a workflow, toggle enable flow then click save changes intacct required permissions if you are unable to access the vendor approvals page, you may be missing permissions your erp administrator will need to navigate to the role associated with your bank's plugin and add permissions for vendor approvals (new) accessing pending approvals navigate to the vendor approvals page within the intacct plugin by default, you will see all pending approval requests for your organization the approvals page table provides a comprehensive overview of every payment request, including the following key details request date the exact date when the payment was initiated within the plugin vendor the name of the vendor whose record was modified entity the type of data that has been changed it will be either an address, bank account, or email group user/requested by the name of the user who submitted the payment request source where the change was made it will be either plugin ui or erp approval progress a tracker that provides context for where a payment is within the approval process to view only the requests assigned to you, click the show assigned to me only filter to review a specific request, click view this will display key information such as type of change this indicates whether it is an update to existing details, a new vendor bank detail, or the deletion of a vendor bank detail requested date the date and time the change was submitted requester the user who initiated the change detailed breakdown a comprehensive overview of the proposed changes, additions, or deletions to the vendor's bank details approve a request approve request after accessing your pending approvals, click into the request you would like to approve click approve to authorize the proposed changes complete approval the request will either advance to the next level in the approval workflow (if multiple tiers are configured) or, if you are the final approver, the vendor's bank details will be updated accordingly on the payment methods page reject a request reject request after accessing your pending approvals, click into the request you would like to approve click reject to deny the proposed changes important rejection is a terminal action if a change is rejected in error, the initiating user will need to resubmit the request provide rejection reason you will be required to provide a rejection reason since rejections are final, the request will not be routed to any other approvers, and the proposed changes will be reverted erp synced changes for changes originating directly from your erp system (erp synced changes), the system restricts action to ensure data integrity by disabling the "reject" button this restriction prevents accidental overwrites or conflicts with your core erp data if an erp synced change needs reversal or modification, the initiating user must make the necessary adjustments directly within the erp system impact of pending approvals when an approval request is created by modifying a vendor's bank details, your plugin updates its interface as follows pay bills page when a vendor has a pending change, payments cannot be processed for that vendor this restriction ensures you have the most up to date information before any payment is initiated a warning icon and a greyed out checkbox prevent these vendors from being selected for payment payment methods page on the payment methods page, the vendor entry will display an icon identifying the pending changes if you click on the vendor, the specific record that has been changed is highlighted if you open the record, you'll find all fields are greyed out and cannot be edited while the approval is pending approvals history the approvals history page maintains a comprehensive log of all approval requests, including both those that have been approved and those that have been rejected to view more details about a request, you can click view and see the following fields date and time when the approval or rejection occurred user the individual who approved or rejected the request reason any comments or explanations provided for the decision source the origin of the change request (e g , manual update, import) approvals history export you can export the approvals history for record keeping or analysis the exported file includes the following columns modified on the date the change was made vendor vendor name type of change updated, added, deleted user email the user who initiated the change reviewed by user emails who have approved or rejected the change approval/rejection time the time when the final approving user reviewed the change or when the rejection was sent status approved or rejected previous entry this entry reflects its state before it was changed it will be empty if the history log item pertains to the creation of a new record proposed entry this entry reflects the adjustments made after a change was initiated or rejected if the entry was rejected, it reflects the proposed change if the entry was approved, it represents the accepted change reason for rejection the reason for rejection provided by the rejecting user this will be empty if the record is an approved item to generate this export, click the export button on the approvals history page faqs can i reject erp synced changes? no, rejection is disabled for erp synced changes to prevent data inconsistencies please contact the user who initiated the change to resolve any issues what if i accidentally reject a valid change? rejection is a terminal action if a change is rejected in error, the initiating user must resubmit the request