COMMERCIAL BANKING ġ J Testing your Import File in Commercial Banking Online Importing Payments in Commercial Banking Online
How to test your Import File on Commercial Banking Online 1. Complete all required changes and checks to your Import File Before importing files in Commercial Banking Online you may need to make changes to your Import File(s). Instructions on the changes required to import each payment type are available on the Move to Commercial Banking Online Support Site. Once you have completed all the required changes and checks to your Import File you will be able to run a test import of the file on Commercial Banking Online. Ó Important information Testing your Import File will help you spot and fix any errors before you go live using Commercial Banking Online 2. Import your Test File into Commercial Banking Online To import your Test File, follow the video instructions for importing payments in Commercial Banking Online. Make sure you use the correct Import Map as advised in the guidance for your Payment Type. The steps overleaf advise how to identify and resolve any errors in the Import File which cause Payments to be rejected by Commercial Banking Online. 2
3. Navigate to the Commercial Banking Online Import History screen ĩ To-do To check if any imported Payments were rejected, navigate to: Manage Payments Importing Import History 4. View the Import History for your test import In Import History you will see the Test File you imported, with a Date of Import, Type and Job ID. Click on the drop-down arrow in the Actions field for your Test File and select View. 3
5. Identify Rejected Payments The Import Summary Report screen will open. This screen provides detail of the total number of Payments submitted and of those Payments, how many were either accepted or rejected. The objective of the testing is to resolve any Rejected Payments if all Test Payments were imported successfully (i.e. accepted) then no changes are required to the Import File. If you do have any rejections you should review the errors as part of step 6. 6. Review errors causing Payment Rejections To review any errors click on the File Name of your import from the Import Summary Report. Detail on each error will be provided, including the Payment line impacted and an explanation of what caused the rejection. For example, in the screenshot below the error results because Header sequence number 29 for user is not unique. The table in step 7 below includes some of the common errors with Imported Payments to Commercial Banking Online with a suggested resolution for each. 4
7. Resolve errors causing Payment Rejections The table below contains suggested resolutions for common errors when importing to Commercial Banking Online. Note that this is not an exhaustive list and if your error is not shown the error text will provide detail on the specific error causing your Payments to be rejected. Commercial Banking Online: Error Description. 1 Header sequence number XX for user is not unique. 2 <FIELD NAME> : Invalid character set and/or field length. 3 You do not have the sufficient entitlements to create this payment, please check your account and payment access. To amend, please contact your Administrator. 4 The payment cannot be created as a valid Panel Profile Threshold Amount does not exist. 5 Invalid beneficiary bank id or beneficiary bank country code. Suggested Resolution When using the Commercial Banking Online System Import Maps the header sequence number must be unique for the user. If you had already imported a payment file with the same header sequence number you will need to change the header sequence to be unique. In Commercial Banking Online imported payments cannot contain certain special characters and must not exceed the field length as stipulated in the file specification documents. You will need to remove special character and truncate the field entry so it will not exceed the maximum length of the field. This error will occur if you do not have the required role permissions to import payments for this account OR if you have entered the debit account number in the incorrect format. To resolve, either contact your administrator to update the role permissions, or correct the debit account number or format of the debit account number (the Commercial Banking Online required format is SSSSSS-AAAAAAAA, 15 characters including the separating hyphen). This error will occur if a valid payment panel (used to establish rules for payment authorisation) is not set up for the amount of the payment in question. To resolve this error contact your administrator to adjust the payment panels assigned to your user as required. This error will occur for CHAPS and International Payments if you have entered an invalid value in beneficiary bank ID, beneficiary bank code type, beneficiary bank country code or IBAN (lower case is not accepted in the IBAN if you do not enter a SWIFT code). You should review the guidance available for importing these payment types which provides instruction on valid entries in these fields. 6 Invalid Bene Account type. This error will occur for CHAPS and International Payments if you have entered an invalid value in these fields. You should review the guidance available for importing these payment types which provides instruction on valid entries in these fields. 7 Unknown payment type. This error will occur if you have entered an invalid payment type in an XML or multipayment CSV import. You will need to use the valid Commercial Banking Online payment identifier as provided in the guidance documentation. 8 No debit found / No credit found. This error is specific to BACS payments using a BACS import. You will need to have at least one debit line for the payment and at least on credit line. Follow the guidance instructions for BACS Single to import BACS single payments on a single line. 9 Invalid Amount Entered. The value entered for the payment amount must be numeric with no special characters other than a separating decimal point you will need to remove any currency signs or commas. 5
10 Value date must be greater than or equal to today. OR Not enough forward days between transaction date and value date. OR These errors will occur if you have entered a value date that: Is in the past. Is submitted post today s cut-off time for your payment on Commercial Banking Online. Does not allow enough forward days this is specific to BACS and Basic Euro MoneyMover payment which should have a future value date to allow for the payment processing time. Invalid value date. 11 FX payments that require Get Rate are not supported for File Level Processing. If you do not enter an FX contract ID when importing EURO and International payments you will need to use the Payment Import method. All payments imported will then need to be assigned a rate using the Get Rate button in Commercial Banking Online Payment Management. 12 Invalid Charges. This error is specific to International/Euro payments. You should review the guidance available for importing these payment types which provides instruction on valid Charge codes for entry in this field. 6
Get in touch We hope you have found this Guide clear and easy to understand but remember, our Helpdesk team are always ready to answer any query you may have. You can reach them on 0808 202 1390 between 7.30am 6pm, Monday to Friday excluding bank holidays. Telephone calls may be recorded for security purposes and monitored under our quality control procedures. Bank of Scotland plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland No. SC327000. Authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority under Regulation number 169628. Eligible deposits with us are protected by the Financial Services Compensation Scheme (FSCS). We are covered by the Financial Ombudsman Service (FOS). Please note that due to FSCS and FOS eligibility criteria not all business customers will be covered. Information correct as at: January 2018. All companies are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority. BOS/I01