You have just tried to upload a payment file and received a message that something went wrong. It is important to look at the type of the message:
Select the warning message that you have received to read the instructions:
You (or someone else in your contract) uploaded the same file in the past 7 days, within the same ebanking contract.
You can still accept this message, but there is a risk that you upload the same file twice.
Note: The previously uploaded file may be in the list of Transactions (if not sent) or Sent transactions (if sent). You may also get this message if you (or a colleague) deleted the file.
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.
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
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.
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.
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.
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.
If you don't change the country code and accept the conditions anyway, note that the transaction could still be rejected by the bank.
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.
Any Sepa Direct Debit requires the debtor address when debtor or creditor account is located in a non-EEA SEPA country. 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 recommended to provide this data, more specific information can be found in the relevant "Supported banking file formats and their corresponding specifications".
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.
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.
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.
If your software supplier cannot help you, send an email to customercare@isabel.eu with the following information:
The first number after FATAL(4) points to the line number the error is, the second is the number of characters
example: Fatal(4) - (540,32)
Look in the payment file on line 540, character 32.
Some accounting software create files on 1 single line, in that case the error will be something like this:
example: Fatal(4) - (1,3248)
Look in the payment file on position 3248.