Payment Method Approvals (NetSuite)

the payment method approvals feature provides a robust and secure method for managing changes to payee 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 payee's banking data enable payment method approvals login to an erp administrator or erp consultant must first access the by logging in at sys fispan live https //sys fispan live/login enable payment method approvals click on the payment method approvals tile a summary pop up will appear click enable & configure to complete the setup once enabled, you will be prompted to begin creating your workflows creating a workflow to create your payment method approvals workflow for your erp utilizing the plugin, please follow these steps go to payment method approvals from the , click on the payment method approvals tile you'll then be prompted to start creating your workflows create a workflow once you are on the payment method 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 payee record address bank accounts applies to bank accounts added via the payment methods page or changes made to the native erp payee record bank account email groups applies to email groups added via the payment methods page or changes made to the native erp payee record emails note payment method approvals captures all payee changes by default—both changes made in the payment methods page and automated updates synced from your netsuite environment for the configured entities to exclude erp synced changes and only require approval for updates made in the plugin, contact 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 payees keep this in mind if a single user frequently acts as both the payee 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 to view payment method approvals, outlined in the required permissions section of this page save workflow once you have configured your workflow, click save new workflow your workflow is now active all changes made to payees through the will now follow this approval process editing a workflow you can edit or delete a workflow, but only if there are no payee record changes pending approval for that workflow this prevents any confusion or errors with changes currently going through the approval process in the event you need to edit a workflow with associated open payee record changes, process or cancel any outstanding changes 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 netsuite required permissions to get access to the payment method approvals page, please have your erp administrator navigate to the role to customization → scripting → script deployment use the following filters on the type dropdown, select suitelet on the api version dropdown, select 2 1 edit the pymt method approvals suitelet script and, under the audience tab, add roles that require access to payment method approvals accessing pending approvals navigate to the payment method approvals page within the erp plugin by default, you'll see all pending approval requests for your organization the approvals page table provides a comprehensive overview of each payment request, with the following key details request date the precise date when the payment was initiated within the plugin payee the name of the payee that had their record modified entity the type of data changed it will be either 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 which provides context to 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 whether it's an update to existing details, a new payee bank detail, or a deletion of a payee bank detail requested date the date and time the change was submitted requester the user who initiated the change detailed breakdown a comprehensive view of the proposed changes, addition, or deletion to the payee's bank details approval process to approve a request click approve to authorize the proposed changes the request will either progress to the next level in the approval workflow (if multiple tiers are configured) or, if you are the final approver, the payee's bank details will be updated accordingly in the payment methods page to reject a request 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 you will be required to provide a rejection reason since rejections are terminal, the request will not be routed to any other approvers and the proposed changes will be reverted erp synced changes rejection disabled for changes that originate from your erp system (erp synced changes), the "reject" button will be disabled rationale this restriction is in place to prevent accidental overwrites or conflicts with the data in your erp maintaining consistency between the plugin and your erp is crucial resolution if an erp synced change needs to be reversed or modified, the initiating user must make the necessary adjustments directly within the erp system note if you would like erp synced changes to not be eligible for approval, please reach out to the support team impact on workflows when an approval request is created by modifying a payee's payment information, the following updates happen within your plugin payments/expense reimbursements page when a payee has a pending change, payments cannot be processed for this payee this is to ensure that the payee has the most up to date information before payments are processed a warning icon and greyed out checkbox will prevent these payees from being paid payment methods page on the payment methods page, the payee will have an icon identifying that there are pending changes if you click on the payee, you will see that the record that has been changed is highlighted furthermore, if you open the record, you will see that all fields are greyed out and cannot be edited approvals history the approvals history page maintains a comprehensive log of all approval requests, including both those that were approved and those that were rejected to view more details about a request, you can click view and see the following 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 export file includes modified on date the change was made payee payee name type of change updated, added, deleted user email user who initiated the change reviewed by user emails who approved or rejected the change approval/rejection time time when the final approving user reviewed the change or rejection was sent status approved or rejected previous entry what the entry looked like before it was changed this would be empty if the history log item is for a new record being created proposed entry what the entry looks like after a change was initiated or rejected if entry was rejected, this is the change that was proposed if the entry was approved, this is the change that was accepted reason for rejection the rejection reason 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 faq can i reject erp synced changes? no, rejection is disabled for erp synced changes to prevent data inconsistencies 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 will need to resubmit the request