Changes for ERP Vendors and Service Agencies

If you use any of SEB’s integrated ERP vendors or bank integrators and deliver your services on their platforms you can easily send files for our mutual customers. No agreement with SEB is necessary since you will be considered a subcontractor. You sign an agreement of your own with your customers and your ERP vendor or bank integrator. SEB already has agreements with all the integrated ERP vendors and bank integrators.

SEB customers sign up to your chosen integrated ERP vendor or bank integrator via SEB’s digital connection service for automated accounting "Automatisk bokföringstjänst".

If you use one of SEB’s bank integrators and deliver your services on their platforms you can easily send files for mutual customers. No agreement is necessary with SEB since you’ll be considered a subcontractor to our mutual customers. You sign an agreement of your own with your customers and your bank integrator. SEB already has agreements with the integrators.

SEB customers sign up to your chosen bank integrator via SEB’s digital connection service for automated accounting, Automatisk bokföringstjänst.

Beneficiary account number is required for credit transfers, including salary payments, pensions and social benefits.
Debiting can take place from an account number or a bankgiro number.

When paying to an Alias (bankgiro number or plusgiro number), it is possible to choose what to use as a debit account. It can either be the account number or bankgiro number as debit account.

More information about what combinations are allowed can be read in our file format description, the Message Implementation Guidelines (MIG).

Yes, the customer or ERP vendor can control this in the ISO 20022 pain.001 file.

In today’s ISO offering bankgiro products is per default batch booked and there is no possibilities to choose single booking in the file, but in the future it will work as follow:

The "Batch Booking" field controls whether the payment is made as a bulk booking or if it is booked individually, so called “single booking”. There, the customer needs to enter "true" or "false". True = bulk booking and False = single bookings.

More information about what applies to each payment product can be read in our file format descriptions, the Message Implementation Guidelines (MIG).

There is a clear difference between these two types of references.

An OCR reference is always linked to a bankgiro number or plusgiro number and consists only of numbers.

An RF reference is always linked to a bank account, and always starts with the letters RF. RF reference is used today in SEPA payments but will be used for Swedish payments in future solution.

SCOR corresponds to OCR reference and is validated with check digits.
CINV is used when invoice number is not validated, instead sent in a structured way, which makes the reconciliation process easier.

This depends on how the payer initiates the payment. If it is initiated by being sent in a payment file in the PAIN format (ISO 20022), the payer himself sets the CINV parameter in the file. If the payment is initiated via one of the bank's digital channels, the parameter is set by the bank - in this case, it is not possible to assume that there will be a structured reference with the CINV parameter.

Yes, as long as each transaction has a unique reference. It is possible to send a payment to the same recipient several times with the same amount and invoice number/reference. However, the customer must always have a unique "EndToEndId" on each transaction, otherwise SEB will notify the transactions as duplicate.

During the transition to the ISO format, all reporting files will be retrieved from each bank and not from Bankgirot. Reports from SEB will be available per account and not per bankgiro number. Customer can select different types of reports in the ISO20022 format. SEB offers camt.052, camt.053 and camt.054. Bankgiro number and its related transactions have a section presented in camt reports, but the reports are based on account level. If the account has more than one BG number connected to it, it will be reported in same file.

More information about the different reporting options can be found in our file format descriptions, the Message Implementation Guidelines (MIG).

SEB offer salaries in ISO format settled via Dataclearing, which is similar to how the salary files will look like in the future. Important to note is that debit account number and debit day shall be stated in the file. More details can be found in our Message Implementation Guidelines (MIG).

If a transaction were to contain, for example, 15+ invoices/references, we will report it to the recipient. If the customer uses our online interfaces, the customer can see the total amount. The customer can expand the information to see which 15+ invoices /references are included in the transaction and the respective amount. If the customer instead has a file report in e.g. ISO 20022 (camt.052 / 053/054), we report it in a similar way.

The OCR control is not carried out at SEB but is done at Bankgirot. In today's flow, there is an opportunity to send a mix of CINV, CREN, and SCOR through a single payment. To clarify, OCR control only applies for SCOR and CINV and is not validated for CREN.

Yes, it is possible to send credit notes and multiple invoices to the same beneficiary, but it is important that the amount of invoices are higher or equal to the amount of credit notes. It is not possible to send negative amounts.

More information about what applies can be read in our file format descriptions in the Message Implementation Guidelines (MIG).

For SEB, it is a mandatory requirement that all payment files must be signed and thus approved by the end customer. SEB allows a single signatory but always recommends dual signatories.

The principle of signing depends on which integration solution you have chosen. Signing can take place either on the integrated business system supplier's (ERP) platform or at SEB's internet bank.

Some ERP platforms offer the option of signing in the ERP platform or with SEB.