Entity Bank Details Approvals

please ensure you have all entity bank details permissions before proceeding with using the approvals functionality you can confirm the required permissions here entity bank details installation & set up docid 6g 14xt7p3x 8vaqatfry before getting started with using the approvals feature, ensure you have all entity bank details (ebd) permissions you can confirm the required permissions here entity bank details installation & setup (netsuite) docid\ joqny3as f srherwatmv overview enabling approvals enhances security and compliance by requiring a secondary approver for every change made in the entity bank details (ebd) this approver can be anyone who has access to the approvals page, but it cannot be the person who made the initial change a change is defined as adding a new record, updating an existing record, or deleting an existing record while a change is pending, payments cannot be made to that entity, and the respective payment page will block payments for the entity until the change has been approved for example, jenna changed company x's bank account information in entity bank details jenna can access the approvals page, but she will be blocked from approving the change bibek, however, has access to the approvals page and can either approve or reject this change note entity bank details approvals works best if your netsuite environment has no customizations surrounding vendor or employee creation, deletion, or modification approval requirements for approvals, there are two additional pages and permission sets you must add these permissions to any users who require access to the settings and approvals pages suitelets entity bank details, settings (customdeploy fispan vbd settings) access to the settings page allows users to enable or disable approvals or manage the settings of approvals for imported records entity bank details, approvals ( customdeploy fispan vbd approvals) access to the approvals page allows users to approve record changes restlets entity bank details, settings restlet this restlet should come with access pre enabled for all roles granting users access to this script will allow them to access the overview page this permission, alongside the entity bank details, overview suitelet, is required to access the overview page permissions lists > employees (level view) to view the list of employee records that have pending approvals, the history of changes made to employee records, or to make changes to employee records custom record → entity bank details (fi) (level full) to approve edb changes, the role needs level full permission on the permissions tab user events no new user events required note for the settings page to work properly, you must also have access to all subsidiaries enabling approvals navigate to settings to enable approvals, navigate to setup > entity bank details > settings settings is where you can decide to enable or disable approvals enable approvals on all changes you can also enable and disable approvals for changes made via the import page to enable these settings, select the approval on all changes checkbox and click save now, all changes must be approved before you can disable approvals by enabling approvals, every change made via import on the import/export page will now require approval enable skip approval on imports in settings , you can enable the skip approvals on imports option t his setting cannot be enabled if there are pending approvals making ebd changes overview page to make a change to a vendor or employee record, navigate to setup > entity bank details > overview make changes to entity select the entity you want to change three types of changes trigger approvals update add delete make the desired changes to the entity's record and save important turn off the primary toggle if you do not want this newly created account to be a primary record if a vendor or employee does not have a primary record enabled, payments will fail confirm the change when asked to confirm the change, be aware that no payments can be made to this vendor or employee until the changes have been approved a blue banner will be displayed on vendor records indicating that changes are pending, while a red alert icon will appear on the relevant bank details record the blue banner serves as a reminder that the completion of payments is contingent upon the approval of the change the alert icon signifies that the record has changed records with pending changes should a record have a pending change, it cannot be edited again until such a change receives either approval or rejection if a vendor's record currently has a pending change, you can edit, create, or delete other records; however, the record with the pending change cannot be modified as a result, the payment page will display bills accompanied by a red alert icon, indicating that payment processing is not possible, and their associated checkboxes will be disabled making ebd changes with import/export changes to entity bank details can be made via a csv import of records, and these changes will require approval export ebd data navigate to setup > entity bank details > import/export import/export , you have the option to either download a blank template or use the generate export file option to create an existing export file update exported ebd data then, make changes or add data to the export file reimport ebd data now add the updated file to the import data box and select import the plugin will process the imported data and notify you if there are pending changes for a record payments are blocked for any entity with outstanding changes until the changes are approved or rejected approving changes to approve changes, you must have access to the approvals page, and you cannot be the user who changed the entity's record locate pending approvals navigate to setup > entity bank details > approvals the page will now display any records that have outstanding changes click view details to see the change and to begin approving or rejecting changes view changes when you click view details , a pop up appears and outlines the changes if the record you are approving is classified as a primary account, you will have the option to either confirm this designation or revoke the account's status as a primary account this option will only appear if a record's primary setting is being updated or if a new bank account is being added approve changes after reviewing the changes, you can approve or reject if unsure about a change, select the arrow beside the pop up to move to the next record and return to this change later when you approve a record, a pop up window will ask you for final confirmation after approval of the change, a confirmation window will display a checkmark, indicating that the change has been successfully approved and saved after 10 seconds, the pop up moves to the next record so you can continue reviewing changes you can also click forward using the arrow icons if there are no further changes, click close to exit the pop up window the updated entity records can be viewed on the overview page payments for this vendor or employee are no longer blocked, allowing for the processing of any outstanding payments reject changes to reject a change, select reject when prompted to provide a reason for rejection , provide an explanation up to a maximum of 250 characters after entering the reason, select yes, reject changes an x icon window indicates the change was rejected, and the vendor's record was not updated you can now successfully make payments for this vendor or employee navigate to the next record using the arrow icon or by waiting 10 seconds approvals history all approvals are logged in the entity bank details history, serving as a valuable resource for audits and reviews of approval histories locate approval history to view a history log of all changes, navigate to the history page s etup > entity bank details > history history displays a record of all changes made and approved if the approvals feature was not enabled for some historical changes, some details like reviewed by or status will be missing view approved changes select view details to see more information about a change for approved changes, a pop up confirms that it has been approved it outlines key information such as who indicated the change, who approved it, and what attributes were modified once finished looking at the pop up, click close for changes that have been approved and involve additions or updates, you have the option to access the ebd record simply click on the ebd record link located next to the corresponding record this link will take you to the record on the ebd overview page view rejected changes rejected changes will display similar information; except, it will indicate that it has been rejected and include the reason for rejection as well export approvals history to export these changes for your records, go to the history page and select export add a date range filter to limit the amount of data to include the history export will display the following data log id ebd id modified on (date and time) vendor id vendor type of change updated, added, or deleted user the user who initiated the change user id the user id of the user who initiated the change reviewed by the user who approved or rejected the change reviewed on the time when the change was approved or rejected status approved or rejected previous entry this shows the data that the record contained before the change this will be empty if the history log item is for a net new record being added proposed entry if the 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 this will be empty if the record is approved note the same columns will appear in the report regardless of whether the approvals feature is enabled or disabled faqs is there any way to disable the approvals feature after it is enabled? to disable approvals, please navigate to setup > entity bank details > settings approvals can only be disabled if there are no pending approvals can i set more than one approver set up for a change? currently, entity bank details is only able to support a single approver for a change why am i unable to pay my vendors/employees despite all pending changes being approved?