Electronic Bank Payments Error Codes

Company Bank Details
Electronic Payments Preferences
Entity Bank Details
Instant Electronic Bank Payment File
Payment File Administration Processing
Payment Batches
Payment File Formats

Company Bank Details

Error Code	Error Message	Description / Recommended Action
EP_00039	You must complete the approval routing setup process for this bank record. To do so, follow the instructions at Payments > Setup > Bank Details.	If Approval Routing is enabled for Electronic Bank Payments, this error occurs when Approval Routing is not properly set up in the bank details record. You need to properly set up the approval routing process by going to Payments > Setup > Bank Details.
EP_00047	Error encountered while adding field with id: {FIELD_ID} to the form.	This error is due to a missing id, label, incorrect field value, etc. This is an internal error. Contact Customer Support and provide details such as the error code and the error message found in the script execution log.
custrecord_8858_process_user	You entered an invalid field value 108 for the following field: custrecord_8858_process_user	This error occurs, when a user does not have access to the subsidiary of the company bank account and still submits the bank file for generation.

Error Code

Error Message

Description / Recommended Action

EP_00039

You must complete the approval routing setup process for this bank record. To do so, follow the instructions at Payments > Setup > Bank Details.

If Approval Routing is enabled for Electronic Bank Payments, this error occurs when Approval Routing is not properly set up in the bank details record.

You need to properly set up the approval routing process by going to Payments > Setup > Bank Details.

EP_00047

Error encountered while adding field with id: {FIELD_ID} to the form.

This error is due to a missing id, label, incorrect field value, etc.

This is an internal error. Contact Customer Support and provide details such as the error code and the error message found in the script execution log.

custrecord_8858_process_user

You entered an invalid field value 108 for the following field:

custrecord_8858_process_user

This error occurs, when a user does not have access to the subsidiary of the company bank account and still submits the bank file for generation.

Electronic Payments Encryption Suitelet

Error Message

Description Or Recommended Action

EP_ENCRYPTION_MISSING_PARAMETER

This error is displayed when the required parameters are missing for the request.

Missing iv

This error is displayed when the cipherText provided for decryption does not contain initialization space vector (v).

No GUID

This error is displayed when the GUID value is missing.

AN_ERROR_OCCURRED_WHILE_DECRYPT_PASSWORDGUID

This error is displayed when the script using the GUID is not mentioned in the restricted script IDs.

EP_ENCRYPTION_ERROR

This error is displayed when the request is processed.

Electronic Payments Preferences

Error Code	Error Message	Description / Recommended Action
EP_00037	Email Template Folder missing EP_START_TIME_NULL	No email template folder was found for Electronic Bank Payments SuiteApp. This is an internal error. Contact Customer Support and provide details such as the error code and the error message found in the script execution log.
EP_00038	Duplicate email template folders exist.	Multiple email template folders exist in your File Cabinet for Electronic Bank Payments SuiteApp. 1. Check which folder needs to hold your email templates. This is usually the folder where your custom email templates are stored. 2. Delete or rename the duplicate folders.
EP_00048	Email notification was not sent. Please go to Payments > Setup > Electronic Payments Preferences and check your email template settings.	Sending email notification failed due to an error in the email template used. Check your email template for any errors. For reference, see Help topic Sending Payment Notifications.
EP_00049	Email notification was sent but not all items were successfully processed.	Go through the failed transactions and check for points of failure, for example: Invalid email, no subject, incorrect template.
EP_00057	Priority can only be changed during Queued status.	Editing the priority other than queued status. You must wait for the queued status before changing its priority.
EP_00061	You may not disable EFT Payment Batch Approval Routing preference because you have at least one payment batch in Pending Approval status. Please approve or reject all payment batches if you would like to disable this preference.	You need to process any pending payment batches before disabling the EFT Payment Batch Approval Routing preference.
EP_00062	Deployments in the current queue setting are currently in progress. Please wait for them to finish before saving an update:	You must wait for the current deployment to finish processing before updating a record.
EP_00063	Subsidiary for default setting may not be set.	The Default queue management setting is used in case no setting record matches a specific subsidiary filter. Assigning the default setting to a subsidiary is not allowed.
EP_00064	Parent deployment {value} is invalid.	Enter a valid script deployment record.
EP_00065	Parent Deployment {value} is selected more than once.	You must select another deployment value, if there is none, create a new deployment record.
EP_00066	Parent Deployment {value} is reserved for the default setting.	You must select another deployment value, if there is none, create a new deployment record.
EP_00067	Parent Deployment may not be blank.	Parent Deployment value is missing.
EP_00068	Payment creator deployment {value} is invalid.	Payment creator deployment is assigned to the incorrect column.
EP_00069	Payment Creator Deployment {value} is selected more than once.	Using a Payment Creator Deployment that is already assigned.
EP_00070	Payment Creator Deployment {value} is reserved for the default setting.	Currently selected Payment Creator deployment value cannot be used.
EP_00071	Payment Creator Deployment may not be blank.	Payment Creator deployment value is missing.
EP_00073	Deployments setup on lines {value} are using the same queue {value2}. You may need to update your script deployments.	This error occurs when you are adding a new deployment line on the same queue that is already use by a different line. You must assign the new deployment line to a different queue. If the account is provisioned only for one queue, contact your Account Manager to inquire about Multiple Queues feature.
EP_00075	Inline editing of Payment File Format record is not allowed.	Direct List Editing (DLE) of Payment File Format record is not allowed.
EP_00076	Unable to create data object without request parameters.	This is an internal error. Contact Customer Support and provide details such as the error code and the error message found in the script execution log.
EP_00077	Unable to create data object without entities.	This is an internal error. Contact Customer Support and provide details such as the error code and the error message found in the script execution log.
EP_00078	Unable to create data object without start time.	This is an internal error. Contact Customer Support and provide details such as the error code and the error message found in the script execution log.
EP_00079	Please enter value(s) for: Priority Queue	Priority Queue value is missing. You need to enter a value for Priority Queue.
EP_00080	No Advanced Template found.	There were no templates found during CSV import. Make sure to add a value for Advanced Template when importing.
EP_00081	deployment {value} is invalid.	Deployment is either not existing or not a valid value. You must select another deployment value.
EP_00082	Deployment {value} is selected more than once.	Deployment can only be used once per line.
EP_00083	Deployment {value} is reserved for the default setting.	Currently selected deployment value cannot be used. Deployment can only be used once per line.
EP_00084	Deployment may not be blank.	You must enter a Deployment value.
EP_00085	Deployment {value} should be on queue {value2}.	Incorrect deployment assignment. You must transfer the deployment to the correct queue.
EP_00086	You do not have permission to Edit this Payment Batch.	Permission error. Contact your account administrator.
EP_00087	Copying or creating new Electronic Payments Preference record is not allowed.	Multiple Electronic Payments Preference record is not allowed.
EP_00088	This record cannot be deleted because it has dependent records.	You need to delete the dependent or child records first.
EP_00089	Cannot retrieve/recreate EP preferences.	Uninstall and reinstall the bundle. If the problem persists, contact Customer Support.
EP_00092	Unable to start payment processing after Rollback.	Unable to start the Rollback process due to specific errors. You need to check the error logs to find out what caused the failure and fix it.
EP_00128	Creating and customizing payment file templates require an active license and the NetSuite SuiteApps License Client SuiteApp installed in your account. If you would like to purchase the license, please contact your NetSuite account manager.	You don’t have the Electronic Bank Payments license, or it is already expired. Contact your NetSuite Account Manager to purchase or renew your license.
INSUFFICIENT_PERMISSION	Permission Violation: You need the Lists >Documents and Files permission to access this page.	For script deployment customdeploy_8858_translation_service_su, Execute As Role field must be set to Administrator.

Entity Bank Details

Error Code	Error Message	Description / Recommended Action
EP_00018	Entity record creation have issues. See error logs for more details.	This error occurs during the building of the payment file and the entity (vendor, employee, or customer) does not have a corresponding entity bank. Create an entity bank record where the error occurred.
EP_00020	Retrieving bank details failed for the entities for the following entities: {MISSING_ENTITIES}	This error occurs when you try to build the payment files and the entity is inactive (vendor, employee, or customer) does not have the corresponding entity bank details.
EP_00093	Create new Entity Bank Details from the {value} version of this record. Vendor ID: {value2}	This error occurs when you are trying to create Entity Bank Details from a vendor record when there is partner record. Disable the partner record first before creating an entity bank record for the vendor.
EP_00094	The International Bank Account Number (IBAN) you entered is not valid. Please enter a valid IBAN for Italy.	Enter a correct IBAN value.
EP_00095	BIC is invalid.	Enter the correct BIC value.
EP_00096	IBAN code is invalid.	Enter thecorrect IBAN code.
EP_00097	Routing number is invalid.	Enter the correct Routing Number.
EP_00098	BBAN code is invalid.	Enter the correct BBAN code.
EP_00099	Payment Description is invalid.	Enter the correct Payment Description.
EP_00100	Account Number is invalid.	Enter the correct Account Number.
EP_00101	Payment Reference is invalid.	Enter the correct Payment Reference.
EP_00102	Payment Code is invalid.	Enter the correct Payment Code.
EP_00103	BIC is missing.	Provide the BIC value.
EP_00104	IBAN code is missing.	Provide the IBAN code value.
EP_00105	Account Number is missing.	Provide the Account Number.
EP_00106	Bank code is missing.	Provide the Bank Code value.
EP_00107	Branch number is missing.	Provide the Branch Number.
EP_00108	Bank name is missing.	Provide the Bank Name.
EP_00136	Access to this log record is restricted. You must have access permission to edit or delete the log record.	This error occurs when you click the Edit button on the Bank Details Logs record. The Edit button is provided by default and cannot be removed. The access is restricted to prevent any modifications or changes to the log records.

Instant Electronic Bank Payment File

Error Code	Error Message	Description / Recommended Action
EP_00001	Verify that the saved search Transaction filter has been set to Bill/Customer Payment only. Click the Edit Search link if you want to review the filtering criteria.	This error occurs when the transaction saved search does not match with the record's search type when generating instant payment files via Payments > Bank File Generation. Make sure that the selected Transaction Saved Search is of Type = Bill Payment for EFT and Type = Payment for Direct Debit
EP_00002	Click the Edit Search link if you want to review the filtering criteria or you may select another saved search.	When an error is encountered while loading the Transaction saved search record via its ID. Edit the selected transaction saved search and add the necessary filters to return expected results. Please refer to Help topic Defining Transaction Saved Searches for Electronic Bank Payment for guidance in customizing your saved search.
EP_00003	There are no transactions retrieved using this saved search. Click the Edit Search link if you want to review the filtering criteria. You may also select another saved search or verify that transactions have been tagged for electronic payment.	This error occurs when the selected transaction saved search when generating instant payment files returns zero result. Edit the selected transaction saved search and add the necessary filters to return expected results. Please refer to Help topic Defining Transaction Saved Searches for Electronic Bank Payment for guidance in customizing your saved search.
EP_00004	There are missing or incorrect filters in this saved search. Click the Edit Search link if you want to review the filtering criteria. For more information, see the Defining Transaction Saved Searches for Electronic Payment topic in the Help Center.	This usually happens when the default Bill or Customer Payment Transaction for EP saved search selected under Payments > Bank File Generation > Generate Bill Payment / Customer Payment File has missing requirements. There are some required search criteria that needs to be validated before processing; see Defining Transaction Saved Searches for Electronic Bank Payment topic in Help Center to identify which criteria needs to be added.
EP_00005	You must select the company bank account first before selecting the transaction saved search.	This usually happens when the company bank record is deleted while loading the Payment File Generation suitelet. Refresh the Suitelet to resolve the problem.
EP_00009	There are no transactions retrieved using the saved search.	May occur if the saved search selected by the user returns no result. Edit the selected transaction saved search and add the necessary filters to return expected results. Please refer to Help topic Defining Transaction Saved Searches for Electronic Bank Payment for guidance in customizing your saved search.

Payment File Administration Processing

Error Code	Error Message	Description / Recommended Action
EP_00007	Another process is queued for the same GL bank account and payment file format. Try again after the first process has been completed.	Payment File Administration (PFA) can only process records with same GL bank account and file format one at a time. Allow the current queue process to finish first, then try again.
EP_00017	An error has occurred during payment file creation.	Check the following: 1. If exceeds time limit, try to generate with a smaller number. 2. Check the template for any errors. 3. Check for errors in any scripts attached to the entity, transactions, company, bank, and PFA.
EP_00023	An error occurred while creating the Payment File Administration record.	This happens when an error occurred during the creation of payment record for a transaction. Check individual payments and see why the creation of the payment file failed.
EP_00046	Error in retrieving the entities {ENTITIES_ID}. Verify that the following entity records are active and set up for electronic payment.	Error in the Payment File creation due to an invalid bank entity record. Check the entity of the transactions created if they are existing and active.
EP_00059	Unable to call parent process to recreate payment file. Scheduled script status:	Retrieving data. Wait a few seconds and try to cut or copy again. Wait for the ongoing process to finish before starting a new one.
EP_00109	An error occurred when reversing payments. See logs for more details.	You must make sure that the discount accounts are set to the following default values when reversing a payment file administration with discount payments: Purchase Discount Account – Purchase Discounts Sales Discount Account – Sales Discounts

Payment Batches

Error Code	Error Message	Description / Recommended Action
EP_00015	Failed to create payment transactions for all records in the Unprocessed Transactions list. See logs for more details.	Check the execution log of the script deployment EP Payment Processor to identify what caused the payment creation failure. Go to Customization > Scripting > Script Deployments > EP Payment Processor > Execution Log subtab.
EP_00016	View the list of unprocessed transactions.	This error occurs when selecting an invalid Aggregation type when processing Bill or Invoice payments. You must check the individual unprocessed transactions to identify what caused the error.
EP_00019	Aggregation method not found on the payment transactions: Internal ID <transactioncolumn>	This error occurs when selecting an invalid Aggregation type when processing Bill or Invoice payments. Go to Payments > Setup > Payment Aggregation and edit the Aggregation type. Make sure the Transaction Field ID value can be found on the vendor bill and expense report form.
EP_00028	Error occurred during marking payments for processing. See logs for more details.	This error occurs when the PFA information is incomplete, for example: missing payment list, or if the payment type is not supported or missing. Check the batch transactions if they all have the information needed to be processed.
EP_00029	Not all transactions were paid. Number of unprocessed transactions: {NUMBER_OF_TXNS}	This error occurs during bulk payment processing. Check each unprocessed transactions to identify the cause of the error.
EP_00052	Payment Batch is being updated.	Modifying a batch process while the current batch is still updating. You must wait for the batch to finish its current process before processing or editing a new one.
EP_00058	Permission Violation: You need a higher permission for Payment Batch record to access this page.	Trying to access the Payment Batch record without the appropriate permission. Contact your administrator for the appropriate permission.

Payment File Formats

Error Code	Error Message	Description / Recommended Action
EP_00012	The FreeMarker length exceeds the maximum allowed length {value} characters	This error occurs when the FreeMarker template is too long. Go to Payments > Setup > Payment File Templates > edit the template in use and review the Advanced Template field.
EP_00013	FreeMarker errors were found in the custom payment file template. See error details here. For information, see the Working with Advanced Templates topic in the Help Center	This issue occurs if the Payment File Template contains FreeMarker syntax errors that needs to be corrected. Go to Payments > Setup > Payment File Templates > edit the template in use and review the Advanced Template field. Check if you are using valid FreeMarker syntax, see the Working with Advanced Templates topic in the Help Center for guidance.
EP_00024	The payment file template of this batch cannot be used because the Electronic Bank Payments license is expired. Contact your NetSuite account manager to renew your license.	This error occurs when your Electronic Bank Payments license has expired. You must have the Electronic Bank Payments license or renew if it is already expired. The NetSuite SuiteApps License Client SuiteApp is also required to validate your license.
EP_00031	A FreeMarker Template Library file with the same name already exists. Every library file must have a unique name.	This error occurs when you are attempting to save a FreeMarker Template file name that already exist. You must enter a unique file name for every new FreeMarker template created.
EP_00054	A Payment File Format with the same name already exists. You must enter a unique name for each record you create.	Renaming or creating a file format where name is already used by another Payment File Format. You must enter a unique name for each file format record.
EP_00055	Editing a native Payment File Format is not allowed. You need to save this format with a different name.	You must rename the Payment File Format record to other than its default name.
EP_00056	Setting the Payment File Format as native is not allowed.	This error occurs when you enable the Native Format checkbox when editing a payment file format record. You must uncheck the field before saving.