Error or Warning when uploading a payment file

Document ID: 36088
Modified: 11/07/2019

Resolution:

When uploading a payment file you get an error message, a warning or the file is uploaded as free format when it should not.

 Banking files are created by ERP or accounting software. Instead of manually correcting files you should contact your software supplier of your ERP or Accounting package and supply the error message.

 

File Format Error Fatals:

Fatal Error: File doesn't comply with ISO20022 pain.00x.001.0x.xsd

The file is badly structured.

When validating your file we notice it is not according to the specifications. Please contact your accounting or ERP software supplier for more information about a possible bug in their application. Alternatively you can search for the issue yourself.
Please read "Supported banking file formats and their corresponding specifications" for more information and how to manually validate a file according to an XSD.

Fatal Error: IBAN of creditor account is invalid

An IBAN that is used in your banking file is badly formatted or is not a registered IBAN.

Resolution

The registered IBAN's and their validation rules are available in the IBAN Registery. An IBAN must be in the IBAN registery and pass a validation check in order to be correct.

A more detailed explication and an example:
  • The length of the IBAN must be correct as stated per country. You can verify the correct length on Wikipedia.org (IBAN formats by country).
  • Move the first 4 characters of the IBAN to the end.
    Example: GB82 WEST 1234 5698 7654 32 > WEST 1234 5698 7654 32 GB82
  • Replace the letters in the IBAN to numbers (a=10, B=11, C=12, ...).
    Example: WEST 1234 5698 7654 32 GB82 > 32 14 28 29 1234 5698 7654 32 161182
  • Calculate the modulo 97 of your altered IBAN. This result must be 1 to have a valid IBAN.
    Example: mod(97) 3214282912345698765432161182 = 1

We strongly advise accounting or ERP suppliers to implement this validation to detect wrong inputs.

Fatal Error: The Belgian structured communication [StructuredMessage] is invalid. Only 12 numeric characters are allowed and the check digit must be valid.
Creditor Reference in the Remittance's Structured Information must contain the Belgian 12-digit structured communication

A structured message in your banking file is badly formatted or does not pass the modulo 97 check.

Resolution

A valid structured communication consists of only 12 didgits (no signs like *, +, \ or / are allowed). The validation is as following:

  1. The lenght of the structured communication must contain 12 digits.
  2. Take the first 10 digits and calculate the modulo 97 of those 10 digits.
    Example: 090933755493 > mod(97) 0909337554 = 93
  3. The result of this calculating must be the same as the last 2 digits of your stuctured communication. 090933755493 = 93
     Exception occurs when the result of the modulo calculation is 00, then 97 must be used. A structured message ending with 00 is therefore not possible.

In case this validation fails you have an invalid structured message. Please contact your beneficiary to request an different structured message and inform them about this validation so they can fix this at their side. Changing the structured message so it is valid is not recommended since your beneficiary will not expect this structured message.
We strongly advise ERP or accounting software suppliers to implement this validation to detect wrong inputs. Also implement the exception with a zero as result of the mod(97) since this is a common mistake.

Fatal Error: All debtor account currencies must be equal throughout the whole payment. Warning: the indicated position is approximate.

You are using an ordering account with multiple currencies.
The tag <Ccy> (Currency*) is missing. This error is because your file is badly structured. You can either manually edit your file or contact your ERP or accounting software supplier.

*Currency only to be used if one account number covers several currencies and the account to be debited is labeled in a currency other than the transfer currency.

Resolution

Add the tag <Ccy>, this is a part of the tag  <DbtrAcct> (DebtorAccount)

More information can be found in "Supported banking file formats and their corresponding specifications".

Fatal error: The amount should not have more decimals than allowed for this currency

You are using a currency that does not allow you to have this much decimals.
Depending on the used currency you are only allowed to have a certain amount of decimals (0, 2 or 3).
For most (100+) currencies 2 decimals are allowed.

Check below for the accepted number of decimals for the remaining currencies.

Currencies allowing NO decimals or 0 decimals
  • BIF
  • BYR
  • CLF
  • CLP
  • DJF
  • GNF
  • JPY
  • KMF
  • KRW
  • MGA
  • PYG
  • RWF
  • VUV
  • XAF
  • XOF
  • XPF
Currencies allowing up to 3 decimals
  • BHD
  • IQD
  • JOD
  • KWD
  • LYD
  • OMR
  • TND
Fatal Error: The file does not comply with the expected format

3 bytes are added to the file lenght when saving this file (for example in Notepad) with UTF8 encoding. This file is not a real UTF8 file any more.
Please contact your ERP or accounting software supplier to resolve this issue.

Fatal Error: Creditor Scheme Private Identification 'Other Identification' is not a valid identifier

This error is because your file is badly structured at the level of Creditor Scheme Identification <CdtrSchmeId>

Resolution

You should check the following tag: Identification <Id>
You can either manually edit your file or contact your ERP or accounting software supplier.
More information can be found in "Supported banking file formats and their corresponding specifications".

A file is uploaded as a free format file when it should be uploaded in a different file format

The Isabel 6 program checks the payment file to determine the type of bankingfile it is. When the payment file or the type of file is not correct, the payment file may be uploaded as a free format type. As a result, this files will not be executed by your bank.

Please contact your ERP software vendor to check the file and verify "supported banking file formats and their corresponding specifications".

Fatal error: VR.BF.V.CT3.ISO.130 - Control sum of message is invalid (/Document/CstmrCdtTrfInitn/GrpHdr/CtrlSum).

This error appears when you have uploaded a SEPA Direct Debit with an incorrect control sum in the group header or payment level of the file. When the tag <CtrlSum> is present in the upload file, its content needs to be correct. Please correct or delete this tag.

Fatal error: VR.BF.V.CT3.ISO.133 - Number of payment transactions is invalid (/Document/CstmrCdtTrfInitn/PmtInf/NbOfTxs).

This error appears when you have uploaded a SEPA Direct Debit with an incorrect number of payment transactions in the group header or payment level of the file. When the tag <NbOfTxs> is present in the upload file, its content needs to be correct. Please correct or delete this tag.

Fatal error: The bank .......... does not allow the upload of the format XML-CT pain.001.003.03

This file format is only supported by ING

Fatal error: Payment type information must be absent on transaction level when this information is present on payment level

PaymentTypeInformation <PmtTpInf> is mandatory and may be present at CreditTransferTransactionInformation level and at Payment level. However it may not be present on both levels simultaniously.

When the tag is present at Payment level, it applies to all transactions in the file.
If the tag is present at transaction level, it must be determined separately for each transaction.

If you receive this error message, you should remove the full tag on one level.

 

File Format Warnings

How to accept warnings: "Accept or refuse extra conditions"

You can accept the warning in the details of the uploaded transaction. Go to Transactions and open your uploaded transaction. In the Actions menu at the left side the option "Accept or refuse extra conditions" will be available.

Or you can accept a warning during the upload process in the column Action. The dropdown menu will be selectable seconds after the upload finished.

 Once you have accepted or refused the conditions you cannot change it.

Warning: Double; this file has already loaded on xx/xx/xx x:xx:xx, with reference uploaded payment file: xxxx

Double: this file has already loaded on [Timestamp], with reference : [FilenameOrDescription]

You (or someone else in your contract) uploaded the same file in the past 7 days, within the same ebanking contract or having the same hash code.

You can still accept this message, but there is a risk that you upload the same file twice.

Remark: You will receive this message even if the previous uploaded file is already removed or sent. If you understand the risk you can still accept the warning.

Warning: File has an execution date in the past [YourExecutionDate], today=[DateOfToday]

The execution date in your file is in the past.

You can still accept this message, but the file might still be rejected by the bank.

To be sure your payment will be executed by the bank it's recommended that the execution date is today or set in the future. In case you ignore this warning the bank might reject your banking file (this is bank specific).

Note: This warning only applies to pain.001.001.02 and SEPA Direct Debit

Warning: Unknown BIC (BIC) for creditor agent

The BIC of one of your counterparties is not known.

Isabel uses a list of all known Swift connected banks and verifies these with the BIC's used in your file. In case a BIC is not known, it does not mean that the BIC is incorrect. Verify if a BIC is known at Swift. Isabel updates it's known BIC's once a month.

Note: If you use a valid BIC but it is not from this account, you will also receive this notification.

Here you can look up which BIC code your account needs.

Warning: The country of the creditor account (account number) does not match with the country of the creditor agent BIC (BIC).

The country code of your counterparty BIC is not the same as the country code of the account number.

Make sure you are using the correct BIC for your counterparty.

You can still accept this message, but the file might still be rejected by the bank

Warning: The address of the debtor is mandatory because the country of the debtor account or the creditor account is located in a non-EEA SEPA country or territory.

Any Sepa Direct Debit requires the debtor address when debtor or creditor account is located in a non-EEA SEPA country. Please check for <Dbtr> <PstlAdr>, the info contained under this second tag needs to be filled in correctly: street and number need to be present on the first line, postal code and city on the second line. 

If the tags are not provided, only a warning will be displayed. You are able to ignore this but the bank can still refuse your file. It is highly encouraged to provide this data, more specific information can be found in the relevant "Supported banking file formats and their corresponding specifications".

 

Bankcontract related right issues with allowed File Formats, QTT's, ordering accounts:

Error: The bank service does not support this file format
  • The encoding of your banking file is not UTF-8 or ANSI.
  • Your bank does not support this type of banking file format3.
  • You are not subscribed to the module Upload of cheques & various files.

Resolution

To verify if your bank supports your banking file:

  1. Verify if your file is supported by Isabel 6.
  2. If your file is one of the supported filetypes, contact your bank to verify if the bank supports this filetype.
  3. If your file is not one of the supported filetypes. With Isabel you can send unknown filetypes. If you are trying to send an unknown filetype make sure that your bank supports this and that you are subscribed to the Upload of cheques & various files module.
Error: The ordering account number xxx in your file is not known in the contract(s) or out of the supported ranges

You are using an ordering account which is not known or not yet configured in your Isabel contract.

Make sure the ordering account used is yours and is configured in your Isabel contract. You can test this by trying to create a new transaction with your ordering account.

 It is only required that the ordering account is listed in the mentioned wizard, not that the representation has to be the same.

  • If you are uploading a (non)-SEPA payment you must be able to use the ordering account as in your upload file when creating a  Payment in the Isabel payment wizards.
  • If your account is not listed in the mentioned wizard, your account is not yet configured. Contact your bank to add your ordering account.
Error: You are not authorized to upload this file format

You are not allowed to upload this type of banking file.

In case you are trying to upload a Sepa Direct Debit, make sure you are subscribed to the module Direct Debit.

Error: Bank service: xxx does not allow production files with qualified transaction type code: xxx

You are not allowed to upload this type of file.

Please contact your bank to request the option to upload files with the mentioned qualified transaction type (QTT)

Or if possible use one of your ordering account (of another bank) that allows this mentioned QTT.

[WARNING:] Select your contract bank
[WARNING:] Select your subtype
[WARNING:] Enter your subtype parameter

The banking file you are uploading is not a known file type.

  • If you are aware that you are uploading a file that is not a known file type and your bank will accept this file, you will need to select your contract bank and a subtype or subtype parameter (you can choose a subtype for your file, but the file might still be rejected by the bank).
  • In case your file is a known file type and you get these options, your file is badly structured since the detection of the file type failed. Contact your ERP or accounting software supplier to verify if the file is valid.
Fatal Error: Import process failed

This error will be generated if there's an advanced mandates profile active for your user account, which is restricting uploads. Please contact your bank to adjust the advanced mandates profile.

Error: The address of the debtor is mandatory because the country of the debtor account or the creditor account is located in a non-EEA SEPA country or territory.

This error can appear when you are trying to upload a new SEPA Direct Debit, with a non-EEA SEPA debtor OR creditor account, without providing an debtor address. As of september 24 2017, all new SEPA Direct Debits or new mandates added to existing SEPA Direct Debits, must contain this address in these cases. Please adapt the file and enter the required address, and reupload it.

Fatal error: VR.BF.V.CT3.ISO.130 - Fatal(4) - (1,220) - Control sum of message (101) is invalid (/Document/CstmrCdtTrfInitn/GrpHdr/CtrlSum).

This error will appear when the control sum in the group header of file and the payment level is invalid, please correct the file and reupload it.

Fatal error: VR.BF.V.CT3.ISO.133 - Fatal(4) - (1,416) - Number of payment transactions (2) is invalid (/Document/CstmrCdtTrfInitn/PmtInf/NbOfTxs).

This error will appear when the number of payments in the group header of file and the payment level is invalid, please correct the file and reupload it.

 

Failed upload (your file has not been uploaded to Isabel); these are client-server secure communication issues ex. activeX, tar file, CIS:

 

Uploaded file validation:

The upload file validation process

When uploading bank files to your bank via Isabel 6, Isabel will validate the structure and content to any known banking file type. This validation process will give you more security since you will get real-time feedback about your files. This validation may fail if the structure or content is not what is described in "Supported banking file formats and their corresponding specifications" (*). We have 3 types of messages that could occur.

 (*) These specifications (or implementation guidelines) are not maintained by Isabel, only implemented.

  • Warning: a warning will inform you about a possible issue with the file or alert you about an additional step the file will pass through. When you receive a warning you can decide for yourself if you can accept or decline this warning. Although they can be accepted by Isabel the file itself might still be rejected by the bank.
  • Error Fatal: a fatal error is shown when your file cannot be accepted because it is badly structured. You cannot send this file to the bank.
  • Failed upload: the upload fails and your transaction is not visible when returning to transaction overview.
It's not possible to change an uploaded transaction file

Make the changes in your ERP or Accounting package and upload the file again.
Because you cannot modify the contents of an uploaded file in Isabel, you best delete the incorrect file in Isabel 6.

The upload error/warning message explained

In case you receive a warning or a fatal during the upload processes you can click on the magnifying glass to view the error or warning that corresponds to your upload file or you can view the error message by returning to Transactions overview and view the details of your uploaded file. A warning or fatal error will be structured as following:

SEPA.CT.V3_ISO20022.1 - Fatal(4) - (25,32) - File doesn’t comply with ISO20022 pain.001.001.03.xsd

SEPA.CT.V3_ISO20022.1 The technical ID used at Isabel for the validation rule that caused this error
Fatal(4) Could be either Fatal (4)= Error or Warning.
(25,32) Line number and position on that line where the error occurred. Note that this position is approximate. In some occasions this location is not filled in.
File doesn’t comply with ISO20022 pain.001.001.03.xsd The technical error message in text.
Other warnings or fatal error messages

Contact your ERP or accounting software supplier and provide the received error mesage.
Or you could manually edit your file using the received error message information.

 Manually correcting banking files is at your own risk.

Manually correcting files

 Banking files are created by ERP or accounting software. Instead of manually correcting files you can also contact your software supplier and supply the error message.

 Manually correcting banking files is at your own risk.

In case you are manually correcting files you can open your banking file using a more advanced text editor like XML Copy Editor (this editor can display line numbers and validating XML files with the corresponding XSD).

In some cases when using banking file in XML all data might on 1 single line. This is done by your ERP or accounting software to reduce the file size, but is not user friendly to manually edit files. If you are using XML Copy Editor you can format your file by going to menu XML > Pretty-print.

You can correct the file using the line number, position and warning that is displayed in the error message you received from Isabel.

Error or Warning when uploading a payment file
36088
11/07/2019