Record Locking & Resubmission Thresholds
Abstract
Administrators can configure record locking rules and resubmission thresholds in NetSuite to enforce control over vendor bill changes during the approval process. These settings help prevent unauthorized edits and ensure that any meaningful change to a transaction — such as a price increase — goes through a new round of review. For example, if a user increases a bill total after approval, the system can automatically lock the record or trigger resubmission to protect financial accuracy.
This article covers configuring the Record Locking and Approval Resubmission tabs in the Approval Workflow Automation (AWA) Settings.
Configuring the Record Locking Settings
The Record Locking allows you to restrict editing access to records while they are pending approval or after they have been fully approved. This ensures that changes cannot be made without explicit permission from approved user roles.
Follow these steps to configure Record Locking settings:
From the AWA Approval Record Type Settings, locate and select the Record Locking tab:
Then, to prevent users from editing records during the approval process, check the LOCK RECORDS PENDING APPROVAL box. When enabled, users (except for the roles defined below) will be unable to press the Edit button on a record while it’s pending approval:
To allow certain roles to edit pending records, select a role from the EDIT LOCKED SUBMITTED RECORDS ROLES field:
Note: It’s recommended that this be set up for the Administrator role.
Next, to prevent edits after a record has been fully approved, check the LOCK RECORDS APPROVED box:
Note: When enabled, users (except for the roles defined below) will be unable to press the Edit button on a record once it has been fully approved.
To permit post-approval edits for specific roles, select those roles in the EDIT LOCKED APPROVED RECORDS ROLES field:
Note: It’s recommended that this be set up for the Administrator role.
Configuring Approval Resubmission Settings
The Approval Resubmission allows you to define thresholds that determine when edits to a vendor bill should trigger reapproval. These controls ensure that important changes — such as price increases or edits to key data — are reviewed again before payment processing. Approval resubmission only applies to records that include a total field, such as vendor bills and other transaction records.
Follow the steps below to configure Approval Resubmission settings:
From the AWA Approval Record Type Settings, locate and select the Approval Resubmission tab:
Then, to trigger resubmission based on a percentage change in the total amount, enter a value in the TOTAL PERCENT THRESHOLD field. For instance, entering 5 means the record will require reapproval if the total increases by more than 5%:
Enter an amount in the TOTAL AMOUNT THRESHOLD field to enforce reapproval when a specific dollar value is exceeded. This helps catch significant but low-percentage increases:
Next, select the appropriate value from the TOTAL AMOUNT CURRENCY dropdown to define the currency for the dollar-based threshold. If the record uses a different currency, the system will convert it using current exchange rates before applying the threshold:
Then, to require that both the percent and amount thresholds must be exceeded before resubmission is triggered, check the box for MUST BE WITHIN BOTH THRESHOLDS:
Note: When this setting is not enabled, exceeding either threshold will trigger reapproval, which allows this setting to change that behavior and requires both conditions to be met.
Enable the DECREASES MUST BE WITHIN THRESHOLD field to include decreases in the resubmission logic. This ensures reductions in total are also evaluated:
Next, select the AUTO RESUBMIT option to allow the bill to automatically re-enter the approval flow when thresholds are exceeded:
Then, enable ANY CHANGE REQUIRES RESUBMISSION to trigger reapproval for any modification, not just financial edits. This includes changes to text fields or other non-monetary data:
To allow admins to make necessary adjustments without triggering resubmission, select the EXCLUDE ADMINISTRATORS FROM RESUBMISSION LOGIC to prevent administrator actions from restarting the approval process:
This concludes the process of configuring Record Locking and Approval Resubmission thresholds for vendor bill approvals.
Last updated
Was this helpful?