The bank integration is currently available for the following banks:

Sweden:

• Handelsbanken (only File pay ISO)

• Nordea

• SEB

• Swedbank

Norway:

• DNB

• Nordea (only Open Banking)

• Sparebank1 (only Open Banking)

Finland:

• Nordea (only Open Banking)

Nordea Corporate Netbank is not currently supported. A complete feature overview can be found here.

To get started with Bank integration you first need to contact our sales department. Once the option has been added, you need to onboarding with your bank and configure settings in Monitor ERP. You can read more information here.

Discover how Bank integration can help you and see a feature overview for different banks here.

Read more about Open Banking here.

Read more about Global Pay here.

Read more about File pay ISO here.

Normally, Monitor ERP loads bank transactions from the bank between 07:00-09:00. This is the case for all banks except Swedbank (08:00-09:00) and Handelsbanken (07:15-09:00). Prior to the transactions being loaded, the system checks whether the payment details have been filled out. If the information is missing (due to a delay from the bank’s side), the system will wait and try to download the transactions again an hour later. This is repeated on an hourly basis until the transactions are ready to be downloaded. When the download is delayed, a notification is sent to the users entered under Notify when error occurs explaining why there aren’t any records to confirm. It is therefore important that you have entered users under the Notify when error occurs button under the Bank integration tab, in the Bank settings procedure so that they receive these notifications.

This means that you may not be able to confirm payments early in the morning as the transactions may not have been loaded yet.

When onboarding, the bank accounts are automatically activated and “matched” to the accounts that are registered in the Bank accounts tab.

If it states that a bank account is missing in Monitor ERP despite it having been registered, this may be due to the bank account not being registered with the correct Swift/BIC under the Bank accounts tab.

To access this tab you need to activate Bank integration for your user. Only users that have registered consent with their bank can access the tab. You also need to have access to the bank account via the bank in order to be able see this in Monitor ERP. You activate your user in the Bank settings procedure.

To access the desktop component you need to activate Bank integration for your user. Only users that have registered consent with their bank can access the tab. You also need to have access to the bank account via the bank in order to be able see this in Monitor ERP. You activate your user in the Bank settings procedure.

1. Check that your consent is still valid. Newly given consent can be activated in the Bank integration tab in the Bank settings procedure.

2. Use the Download transactions manually button in the Bank integration tab in the Bank settings procedure.

If the above does not help, please contact the Monitor Support.

This depends on your bank. If you bank with SEB (Sweden) or Nordea (Sweden) and pay via Open Banking, you cancel payments in Monitor ERP and the payment is then automatically canceled by the bank. Otherwise, you need to cancel the payment manually both via the bank and in Monitor ERP. Payments are canceled in Monitor ERP via the Cancel outgoing payments list type in the Outgoing payments procedure.

This is determined by your permission settings in the bank.

In Bank integration there is no limit to the number of credit invoices per supplier and payment dates like there are with traditional ISO files. Regardless of whether you use File pay (ISO) or Open Banking, payment orders are sent at net value. The net value must however be positive.

However, please note that there is a limitation regarding the number of characters used for payment reference. The maximum character limit for total number of characters for the payment reference is 70 characters in connection to batch payment of debit invoices containing deductions for credit invoices to the same supplier and with the same payment day. The limit applies to the total number of characters in the payment reference for all supplier invoices in the same batch.

For File pay (ISO) payments, the bank file is uploaded to the bank via API and signing is done through the bank.

For Open Banking payments, signing is done through Monitor ERP. If you use countersigning, the first signing is done in Monitor ERP, and the second via the bank. Please note that SEB and Nordea do not currently support countersigning via Open Banking.

If the payment has a green tick under Status, it means that the payment has gone to the bank. If there is a yellow warning or a red cross, it means that something has gone wrong and the payment has not gone to the bank. This can occur for individual payments or for an entire signing session. Under the Message button for the payment record, you can see what is stopping the payment from being sent to bank. If the error is for the entire signing session, you will see an error message in the Message column on the main row (the row at the very top) instead.

If a signing error occurs, the payment must be canceled. If the signing error is for the entire signing session, you will need to cancel the whole transaction list. If it is only individual payments, you only need to cancel the payments in question as the others have been sent to the bank. The issue needs to be resolved before you can resend the payment.

Below is a list of the most common error messages and what you need to do in order to resolve them:

When using this payment method, you (the sender) are the one paying the bank charges. It is not your regular bank's fees/charges that apply, but a fee charged by Open Payments. This fee is often lower than what the banks usually charge. There will be no fee at all for the receiver since it is regarded as a domestic transaction.

You can also see the bank charge that will be charged for international payments via Global Pay in advance, before you send the payment. You can see this in the payment suggestion via the Load provided exchange rate and bank charge button. The fee will then be displayed in the list, in the Provided exchange rate column. The fee is recorded in connection with the payment confirmation in the Manage bank transactions procedure.

With this payment method, the outgoing payment is always sent with the bank charge code SHAR, which means that the sender and recipient pay for their own bank's costs.