Setting up the Vendor Whitelisting
Table of Contents
Poland Localization Settings
To set up the Poland Localization Settings for vendor whitelisting:
Global search: “Poland Localization Settings”
Click Edit next to the subsidiary.
Go to the Vendor Whitelisting tab.
Vendor Search for Whitelisting - Select the saved search that includes all vendors eligible for vendor whitelisting. This field should contain a vendor-type saved search. The default value is [STA] PL Loc Vendor Whitelist Search.
Transaction Search for Whitelisting - Select the saved search that includes all transactions eligible for vendor whitelisting. This field should contain a transaction-type saved search. The default value is PL Default Transaction Whitelisting Search.
Vendor Whitelisting PDF Folder ID - Enter the internal ID of the file cabinet folder where PDF Files are stored.
Overwrite Vendor Data - Check this preference if you want to overwrite the data on the vendor record with data retrieved from the Polish government. If cleared, only the Whitelist Status, Date Verified, and Electronic Key will be overwritten.
Hold Payment When the Bank Account is Invalid - Check this preference if you want to automatically check the Payment Hold checkbox in the Transaction if the Vendor Bank Account selected is invalid.
Split Payment When the Bank Account is Invalid - Check this preference if you want to automatically check the Split Payment checkbox in the Transaction if the Vendor Bank Account selected is invalid.
Click the Save button.
Important: The following fields will be overwritten with data from the official VAT database if the OVERWRITE VENDOR DATA preference is checked:
REGON
Whitelist Name
Residence Address
Working Address
Representatives
Authorized Clerks
Partners
Date of VAT Registration
Basis of Registration Denial
Date of VAT Re-registration
Date of VAT Registration Removal
Has Virtual Accounts
Pesel
KRS
Vendor Entry Forms
The Poland Localization tab should be displayed in the vendor entry form, including the following fields:
[STA] PL REGON
[STA] PL BANK ACCOUNT NUMBER
[STA] PL WHITELIST STATUS
[STA] PL WL DATE VERIFIED
[STA] PL ELECTRONIC KEY
[STA] WHITELIST REPORT PDF
[STA] PL ERROR MESSAGE
[STA] PL WHITELIST NAME
[STA] PL RESIDENCE ADDRESS
[STA] PL WORKING ADDRESS
[STA] PL REPRESENTATIVES
[STA] PL AUTHORIZED CLERKS
[STA] PL PARTNERS
[STA] PL DATE OF VAT REGISTRATION
[STA] PL BASIS OF REGISTRATION DENIAL
[STA] PL DATE OF VAT REGISTRATION DENIAL
[STA] PL BASIS OF VAT RE-REGISTRATION
[STA] PL DATE OF VAT RE-REGISTRATION
[STA] PL BASIS OF VAT REGISTRATION REMOVAL
[STA] PL DATE OF VAT REGISTRATION REMOVAL
[STA] PL HAS VIRTUAL ACCOUNTS
[STA] PL PESEL
[STA] PL KRS
Transaction Entry Form
The following fields must be displayed in the vendor bill transaction form:
[STA] PL SPLIT PAYMENT APPLIED (id: custbody_sta_pl_apply_split_payment)
[STA] PL BANK ACCOUNT NUMBER (id: custbody_sta_pl_ban)
Vendor Bank Account (id: custbody_sta_pl_vendor_bank_acct)
Default Roles
The Vendor Whitelisting feature deals with sensitive banking and company information. Due to this, it is suggested that any changes and deletions for this information sourced from the official VAT database must be regulated. To facilitate this, the following default roles are highly encouraged to be used when dealing with Vendor Whitelisting:
Role | Create Vendor Bank Account | View Vendor Bank Account | Edit Vendor Bank Account | Delete Vendor Bank Account | Perform Whitelisting | Schedule Whitelisting |
---|---|---|---|---|---|---|
Administrator | Yes | Yes | Yes | Yes | Yes | Yes |
[STA-PL] Admin Role | Yes | Yes | Yes | Yes | Yes | Yes |
Controller | Yes | Yes | Yes | No | Yes | No |
A/P Clerk | Yes | Yes | No | No | Yes | No |
Permission List
The below table shows the permissions required to run the vendor whitelisting feature. In cases where businesses already have established custom roles, it is best to check each to see if they have the minimum permission level for each entry on the list below. Make sure that the permission level corresponds to the desired task that a role can perform.
Subtab | Permission | Administrator (Minimum Level) | [STA-PL] Admin Role (Minimum Level) | Controller (Minimum Level) | A/P Clerk (Minimum Level) |
---|---|---|---|---|---|
Transactions | Find Transaction | View | View | View | View |
Transactions | Bills | Full | Full | Full | Create |
Transactions | Enter Vendor Credits | Full | Full | Full | Create |
Transactions | Purchase Order | Full | Full | Full | Create |
Lists | Custom Record Entries | Full | Full | Full | View |
Lists | Vendors | Full | Full | Full | Create |
Setup | SuiteScript | Full | Full | View | View |
Setup | SuiteScript Scheduling | Full | Full | None | None |
Custom Record | Poland Localization Setting | Full | Full | View | View |
Custom Record | Vendor Bank Account | Full | Full | Edit | Create |
Script Deployment
Upon installation, the scripts for the on-demand and scheduled whitelisting must be properly deployed to ensure that the feature works as expected. Below are the steps administrators need to take to deploy the vendor whitelisting feature fully:
Deploy/Undeploy On-Demand Whitelisting on Vendor
To deploy the On-Demand Whitelisting on the Vendor Record:
Go to Customization > Scripting > Scripts.
Search for a script named [STA] UE PL Vendor Whitelisting (id: customscript_ue_sta_vendorwhitelisting)
Click the View link next to the script.
Navigate to the Deployment subtab and view the deployment for the Vendor record.
Edit the deployment record and make the necessary adjustments:
Deployed - Check the box to deploy the script.
Status - Select the Released status as default.
Execute As Role - Select the [STA-PL] Admin Role as default.
Roles - Check the Select All box.
Employees - Check the Select All box.
Click the Save button.
Go to Customization > Scripting > Scripts.
Search for a script named [STA] SL PL Vendor Whitelisting (id: customscript_sl_pl_vendorwhitelisting)
Click the View link next to the script.
Navigate to the Deployment subtab and view the deployment record.
Edit the deployment record and make the necessary adjustments:
Deployed - Check the box to deploy the script.
Status - Select the Released status as default.
Execute As Role - Select the [STA-PL] Admin Role as default.
Roles - Check the Select All box.
Employees - Check the Select All box.
Click the Save button.
Deploy/Undeploy On-Demand Whitelisting on Transaction
To deploy the Scheduled Whitelisting on the vendor record:
Go to Customization > Scripting > Scripts.
Search for a script named [STA] UE PL Vendor Whitelisting (id: customscript_ue_sta_vendorwhitelisting)
Click the View link next to the script.
Navigate to the Deployment subtab and view the deployment for the Vendor Bill record.
Edit the deployment record and make the necessary adjustments:
Deployed - Check the box to deploy the script.
Status - Select the Released status as default.
Execute As Role - Select the [STA-PL] Admin Role as default.
Roles - Check the Select All box.
Employees - Check the Select All box.
Click the Save button.
Repeat Steps 1-6 for each of the following transaction records:
Purchase Order
Vendor Credit
Go to Customization > Scripting > Scripts.
Search for a script named [STA] SL PL Vendor Whitelisting (id: customscript_sl_pl_vendorwhitelisting)
Click the View link next to the script.
Navigate to the Deployment subtab and view the deployment record.
Edit the deployment record and make the necessary adjustments:
Deployed - Check the box to deploy the script.
Status - Select the Released status as default.
Execute As Role - Select the [STA-PL] Admin Role as default.
Roles - Check the Select All box.
Employees - Check the Select All box.
Click the Save button.
Deploy/Undeploy Scheduled Whitelisting on Vendor
To deploy the scheduled whitelisting on the vendor record:
Go to Customization > Scripting > Scripts.
Search for a script named [STA] MR PL Vendor Whitelisting (ID: customscript_mr_sta_pl_vendorwhitelist).
Click the View link next to the script
Navigate to the Deployment subtab and view the deployment record.
Edit the deployment record and make the necessary adjustments:
Set Status to Scheduled
Define the desired recurrence schedule:
Select Daily Event
Repeat Every is set to 1 by default, but you may change this to any other value if you do not wish to run the script daily.
Enter the Start Date and Start Time
Define whether the schedule will end on a certain date by entering an End By date value,
Or having the schedule run indefinitely by checking the No End Date field.
Optionally, configure any of the following fields:
Priority - Available options are High, Standard, and Low. The default option is Standard. This field determines the urgency of the script processing. The higher the priority of the script run, the higher up the queue it will be included.
Concurrency Limit - Determines the number of job queues that can be used to process runs of this script. The default option is 1. Depending on your licensing agreement with NetSuite, you may have other values available. You should only increase this value if regular vendor whitelisting is at the top of your priority list and several thousands of vendors are eligible for regular checks. Otherwise, please keep this value to 1.
Yield After Minutes - This is a soft time limit on how long a script can run before yielding. The default value is 60 minutes. You can enter any value from 3-60. It is highly suggested that this is kept at 60. Only reduce the value if necessary.
Buffer Size - This value determines how many records can be processed in parallel before information about the job’s progress is saved to the database. A low Buffer Size minimizes the risk of any records being processed twice. The default value is 1. It is generally suggested to leave this value to 1 unless special circumstances dictate otherwise.
Click the Save button.
Deploy/Undeploy Scheduled Whitelisting on Transactions
To deploy the scheduled whitelisting on transaction records:
Go to Customization > Scripting > Scripts.
Search for a script named [STA] MR PL Vendor Whitelisting By Trxn (ID: customdeploy_mr_sta_pl_vw_by_trxn)
Click the View link next to the script
Navigate to the Deployment subtab and view the deployment record.
Edit the deployment record and make the necessary adjustments:
Set Status to Scheduled
Define the desired recurrence schedule:
Select Daily Event
Repeat Every is set to 1 by default, but you may change this to any other value if you do not wish to run the script daily.
Enter the Start Date and Start Time
Define whether the schedule will end on a certain date by entering an End By date value,
Or having the schedule run indefinitely by checking the No End Date field.
Optionally, configure any of the following fields:
Priority - Available options are High, Standard, and Low. The default option is Standard. This field determines the urgency of the script processing. The higher the priority of the script run, the higher up the queue it will be included.
Concurrency Limit - Determines the number of job queues that can be used to process runs of this script. The default option is 1. Depending on your licensing agreement with NetSuite, you may have other values available. You should only increase this value if regular vendor whitelisting is at the top of your priority list and several thousands of vendors are eligible for regular checks. Otherwise, please keep this value to 1.
Yield After Minutes - This is a soft time limit on how long a script can run before yielding. The default value is 60 minutes. You can enter any value from 3-60. It is highly suggested that this is kept at 60. Only reduce the value if necessary.
Buffer Size - This value determines how many records can be processed in parallel before information about the job’s progress is saved to the database. A low Buffer Size minimizes the risk of any records being processed twice. The default value is 1. It is generally suggested to leave this value to 1 unless special circumstances dictate otherwise.
Click the Save button.
Send an email to support@staria.com for questions or concerns regarding this topic.
Related content
©2024 Staria. All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher.