How to Configure Roles and Permissions in ZoneReconcile

Identify and assign the NetSuite permissions that custom roles need to use ZoneReconcile. Configure roles correctly to avoid permission errors during statement import, reconciliation, and deletion.

Note: Clicking on the images within this guide will enlarge them for better viewing.

Identify needed permissions

ZoneReconcile installs an example user role, ZoneReconcile - Comparison Role, that you can use to identify the minimum permissions a custom role needs to use ZoneReconcile to its full extent. NetSuite lets you compare your custom role with this default role.

1. Navigate to Setup > Users/Roles > Show Role Differences.
2. Select ZoneReconcile - Comparison Role as the base role.
3. Select the custom role that needs to use ZoneReconcile as the role to compare.
4. Click Show to display the list of differences.

Set each permission on your custom role to the same level as, or a higher level than, the ZoneReconcile - Comparison Role. For example, if the list shows that the Bank Account Configuration custom record permission is None on your custom role, change it to Full at minimum. After all permissions are equal or higher, proceed to the next sections.

Additional custom permissions

Add these permissions only if your company uses the Electronic payments module. The ZoneReconcile - Comparison Role cannot include them by default.

• Company Bank Details
• Bill EFT Details
• Bill EFT Payment Information
• Payment File Administration

Subsidiary permissions

Grant the custom role access to every subsidiary for which users import and reconcile statements. Configure this access in the Subsidiary Restrictions section of the custom role record.

Reconciliation report permissions

Edit a script deployment to give roles access to the Reconciliation Report.

1. Navigate to Customization > Scripting > Scripts.
2. Click View next to BS SL Reconciliation Report.
3. Select the Deployment subtab.
4. Edit the deployment and add the necessary roles to the audience.

Unlock statements permission

The unlock option lets users unlock statements that are stuck in the Processing status.

Important: Confirm that the statement is stuck before you unlock it. Wait at least 1 hour before you trigger any unlock. Provide this option to Administrators only.

To give additional roles or users access to the Unlock Bank Statement section, edit the script deployment:

1. Navigate to Customization > Scripting > Scripts.
2. Locate and open the BS SL Unlock Statements script.
3. Select the Deployments subtab.
4. Click the BS SL Unlock Statements deployment link.
5. Click Edit.
6. Add the additional roles or users to the Audience subtab.
7. Click Save.

The added roles and users can now access the Unlock Bank Statement section.

Multi-book accounting permission

When you reconcile a bank statement with a custom role, the following error can appear on save:

{"type":"error.SuiteScriptError","name":"SSS_SEARCH_ERROR_OCCURRED","message":"Search error occurred: Record 'accountingBook' was not found.\nError","id":null,"stack":["Error"],"cause":{"name":"SSS_SEARCH_ERROR_OCCURRED","message":"Search error occurred: Record 'accountingBook' was not found.\nError","notifyOff":true},"notifyOff":true,"userFacing":true}

To resolve this error, ask your Administrator to add the Accounting Book permission to your custom role. View level is sufficient.

ZR LMS license permission

When you reconcile a bank statement with a custom role, the following error can appear on save:

Search error occurred: Record 'customrecord_zr_ffm_license' was not found

This error indicates a missing permission for the license record. To resolve it, ask your Administrator to add the ZR LMS License permission to your custom role. View level is sufficient.

Delete transactions permission

To delete created transactions, the custom role must have the Full permission level for the transaction types being deleted. This applies to both deletion methods:

• The Delete Payment Transactions button (statement line level)
• The Delete button (statement level)

To delete transactions with the Delete Payment Transactions button, the custom role also needs the SuiteScript and SuiteScript Scheduling permissions.

Override the permission requirement

To let users delete transactions without Full permission, change Execute As Role from Current Role to a role with higher permissions in the relevant deployment:

• Delete Payment Transactions (statement line level)
• Delete (statement level)

Important: This change applies to all users. Use it with caution.