Setting Up Primary Bank for Customer and Vendor Accounts with Multiple Subsidiaries

For customer and vendor accounts that use multiple subsidiaries, you can assign one subsidiary to each entity bank. Also, you can assign only one Primary bank to each entity. With this feature, you can also perform the following actions:

• Create multiple bank records per entity based on the account’s base country of operation.

• Use the Subsidiary list to assign a subsidiary to a bank.

• Process transactions assigned to a different subsidiary.

  Note:

  You can process transactions assigned to a different subsidiary only if it meets the following criteria:

  • The transaction’s company and entity bank templates must match the subsidiary

  • The entity bank is set to primary.

• Process transactions related to all the subsidiaries of an entity that match the criteria if the Subsidiary field of the entity bank is blank. If the Subsidiary field is not blank, then transactions related only to that subsidiary are processed in the entity records.

Important:

Loading transactions in the processing pages is restricted if their respective entity bank is inactive. However, this condition applies only when the entity bank is set to inactive directly from Bank Details page and not from the List page on the Bank Details page.

To set the bank type and update the subsidiaries:

1. Go to Lists > Relationships > Customer or Vendor.

2. Next to any customer or vendor record, click Edit.

3. On the Bank Payment Details subtab, next to any bank record, click Edit.

4. From the Type list, select either Primary or Secondary as required.

5. In the Subsidiary field, change the selection as required.

6. Click Save.

You must set the bank type and update the subsidiaries before processing any transactions. For more information, refer to the help topics based on the country of operation.

When you remove entity bank Details from the Bank Payment Details subtab on a customer or vendor record, you cannot edit that entity bank details again.

As a part of SuiteScript 2.0 implementation, the following UI elements are not hidden on the Bank Details page. NetSuite does not recommend using the following UI elements to attach entity bank details as it can change the parent entity and can cause errors. By default, you cannot attach an entity bank detail from the Bank Details page to prevent changes in the payment processes. However, an error is logged in the script logs with detailed notes. For more information about bank detail records, see Setting Up Bank Records.

• Bank Details field

• Attach button

• Customize View button

The following Electronic Bank Payment pages retrieve transactions based on subsidiary, template, and primary bank combination:

• Bill Payment Processing

• Invoice Payment Processing

• Instant Bank File

• Customer Refund Processing

• Auto-Batch Processing

• EP-API Custom Suitelet

Note:

There is no impact on saved searches used for Instant Bank File and Batch Processing pages.

Creation of Bill Payment and Customer Payment is not restricted by the subsidiary selected in Bank Details page. Hence, the transaction is displayed on the Generate Bill Payment File and Generate Customer Payment File pages. But, you can process a PFA successfully when the subsidiary of an entity bank is blank or matches with the subsidiary of a company bank. The PFA is not processed and displays an error when the subsidiary of the entity bank is not blank or is not matching with the subsidiary of the company bank. For more information on the error codes, see the topic Electronic Bank Payments Error Codes.

Note:

Electronic Bank Payments SuiteApp supports approximately 200 entity banks for an entity. The number of entity banks depend on the data available in the account. If the number of entity banks is more than 200 for an entity, processing of payments is still allowed. However, when you edit the Bill Payments Processing page, you can get the Script Execution Usage Limit Exceeded error. Alternatively, you can update payment record using CSV import or mass update option. You can also clear the EFT Bill Payment box on vendor record. After you edit the Bill Payment Processing page, you can check the EFT Bill Payment box at vendor record again.

Guidelines on Primary Bank Setup for OneWorld Accounts with Multiple Subsidiaries

• If you have any customizations on the Bank Details page, you must revisit them based on the required Subsidiary field.

• If you are using any web services to create an entity bank, then you must add the Subsidiary field in the web service request.

• For mapping the Subsidiary field, refer to the SuiteAnswers support article CSV Import to Add Entity Bank Details for Vendors, ID 27012.

• Refer to the following sample syntax for generating the Subsidiary field when creating bank details using a script.

  o rec.setFieldValues('custrecord_9572_subsidiary', [1]); //Subsidiary Internal Id

• During the SuiteApp update, a Map Reduce (MR) script labeled Global Entity Migration Script MR runs automatically. This MR script updates the File Format field on your existing Bank Details page. You cannot run the MR script manually. You can view the script status by going to Customizations >Scripting > Map/Reduce Script Status.

  When you trigger the MR script, it behaves as following:

  • EFT, DD and CR file formats along with subsidiary attached to entity banks are updated in the custom fields for the respective templates of each entity.

  • The MR Script runs independently of the SuiteApp update. For example, when the SuiteApp update is complete, the MR script still runs in the background until all the records are updated.

  • For accounts that are not One World, only the file format of each entity bank is stored in the custom fields for EFT, DD and CR templates. These values are used to populate the transactions to increase the performance of the entity records.

  • In One World accounts, file formats along with subsidiary attached to entity bank will be updated in the custom fields for the respective templates of each entity. These Values are used to retrieve the transactions in the Suitelets.

  Important:

  You must check the status of the MR script before submitting any PFA or Batch for processing. If the script status has an error, then you must trigger the script manually. Once you trigger the script manually and the script completes the execution successfully, then you can process the PFA. This is applicable only when the SuiteApp is updated from 2020.2 release to 2021.1 release.

  To Trigger the scripts manually:

  1. Go to Customizations >Scripting > Script Deployment.

  2. Click Edit beside the Script ID customdeploy_9572_migration_script_mr.

  3. On the Script Deployment page, click Save and Execute to run the MR.

  4. Click Ok.

  To check the successful execution and completion of MR script:

  1. Go to Customizations >Scripting > Map/Reduce Script Status.

  2. Click Details on the Details column for the global entity migration MR script.

     Check if all the stages of the MR script are in complete status.

General Notices