Go to search feature Go to content

You need to use a different browser. To be able to use our internet services, you can instead use one of these browsers: Apple Safari, Google Chrome, Microsoft Edge or Mozilla Firefox.

Read more about recommended browsers

Changes to ERP vendors and service agencies regarding payments in Swedish kronor

The restructuring of the Swedish payment market has now begun, and the next generation of payments will be handled by the banks and P27, which is the Nordic clearing house. The change will continue for several years and the development will take place in different phases. The first phase concerns the migration of payments in Swedish kronor, which means that payments to the bankgiro system will gradually be replaced by the new joint payment platform P27, where the ISO 20022 file format is mandatory.


The Transformation Committee within the Swedish Bankers' Association (with the aim of leading the Swedish banking transformation) has drawn up a timetable for the transition to the payment platform P27, to which all banks relate. SEB recommends customers, as well as ERP vendors and service agencies, to switch to the new ISO 20022 file format in good time, but no later than in 2022, as a first step in the transformation to the new P27 payment platform.

Frequently asked questions and answers: ERP vendors and service agencies

If your file communication has been directly with Bankgirot, for example via bankgiro link, you need to ensure that your future files can be sent to each customer's bank. See SEB's Message Implementation Guidelines for file format descriptions. Also check that the ERPs you and/or your customers use can handle the new file format for ISO 20022. You can also choose to work with one of our integrated partners, who are all ready for the new format ISO 20022.

Today, there are two alternatives for you as an ERP vendor to be able to serve existing customers in SEB when bankgiro products are shut down.

Direct integration

A technical integration between you and SEB is required. Direct integration over the Internet is based on secure communication protocols. Here, SEB supports both SFTP and AS2 (encrypted communication protocols). A direct integration requires an integration agreement with SEB and will be based on a mutual business-based decision. Both a KYC assessment and a reputational risk assessment is required. Through this option you will leverage on the SEB brand in marketing and market communication. You will also be published as an integrated ERP on SEB home page. Anyone who is directly integrated with SEB should be directly integrated with all major banks to be able to support all customers.

Indirect integration

Indirect integration is the model for ERP vendors that do not want to invest in technical integration with all the leading banks in the market. Instead, you rather want to outsource the technical bank integration to one of SEB’s bank integration partners. Existing SEB bank integrators are listed on SEB home pages. SEB is striving to increase the number of integrated bank integrators.

To become an indirect integrated ERP to SEB, there are two different options:

SEB agreement - indirect integration model: Together we will analyze the business case for entering this kind of partnership before signing the integration agreement. Besides signing the integration agreement, a KYC assessment and reputational risk assessment are required. Through this option, you will be able to leverage the SEB brand in marketing and market communication.

SEB non-agreement - indirect integration model: In case SEB or you decide not to go for the indirect integration agreement model there is another option. You can choose to perform the technical integration via one of our bank integration partners. Through this option you will reach your customers and get the technical integration to SEB and other leading banks. You will be able to offer your customers the same services as if you were agreement-based, but you are not allowed to use the SEB brand in your marketing or market communication. You will not be listed as an integrated ERP on SEB web pages. In this model, you don’t need to be a customer of SEB.

Today, there is one alternative for you as a service agency to be able to automate your processes when serving existing customers in SEB.

The service agency model via one of SEB’s integrated ERP vendor

If you as a Service Agency use an already integrated ERP vendor to SEB, whose platform is used to deliver your services, you can easily send payment files for existing customers in SEB. You do not sign an agreement with SEB because in this model you are considered a subcontractor to our joint end customers. You sign an agreement with your end customer and the ERP vendor. SEB already has an agreement with the ERP vendor and only signs an agreement with each end-customer. Existing integrated ERP vendors to SEB are listed on SEB home pages.

SEB currently offers Salary via Supplier Payments to Bankgirot in ISO format, where a bankgiro number must be specified and debited. From Q2 2022, SEB will also offer salary payments in ISO format, which will not be settled via Bankgirot. It will resemble how the payroll files are to be designed when we switch to P27 in the future, and in the file the account number for debiting and debiting date must be stated. Detailed information about the design of the files can be found in our file format descriptions "Message Implementation Guideline (MIG)".

Format

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 descriptions "Message Implementation Guideline (MIG)".

The payee's name needs to be stated and we will check that the payee's name is as correct as possible.

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 when we move to P27 products 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 "Message Implementation Guideline (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 an account, and always starts with the letters RF. RF reference is used today in SEPA payments but will be used for Swedish payments in the future P27 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 "Message Implementation Guideline (MIG)".

Multiple invoices / references to the same recipient

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 "Message Implementation Guideline (MIG)".

Signing

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.

Upcoming offers

No, not all payments will be real-time payments with P27. There will be two different payment infrastructures: Real-time payments made 24/7, 365 days a year, and cyclically made payments that are collected and sent during banking days. For payments in SEK, these cyclical payments will be made up to 9 times a day. These payments will primarily replace today's bankgiro payments. This means that all types of payments, i.e. bankgiro payments, plusgiro payments and account transfers, will be able to be sent and reach the recipient in one and the same day, provided that they arrive at the bank before the closing time. Salaries are an exception and must be sent to the bank the day before the payment date.

Today's Autogiro will be phased out. In the future payment infrastructure, a new service is planned that will replace both the current E-invoice Internet Bank and Autogiro. The idea is to improve and simplify the way to pay bills and invoices, but with retained functionality. Planning is ongoing and we will update regularly when new information is in place.

Extended Remittance Information (ERI), a so-called aggregated payment, makes it possible to have up to 999 references. If a transaction were to contain, for example, 50 invoices/references, we will report it to the recipient. If the customer is inside our online interface, the customer can see a total amount, where the customer can expand the information to see which 50 invoices/references are included in the transaction. If the customer instead has a file report in ISO 20022 (camt.052 / 053/054), we report it in a similar way.

The OCR control will be performed if the SCOR qualifier is used in the file. Credit Invoices (CREN) will not have any OCR control. There is an option to send a mix of CINV, CREN, and SCOR within an ERI payment. The total amount of the payment must exceed 0.  

Through Extended Remittance Information (ERI), a so-called aggregated payment, it is possible to send credit notes and/or several invoices to the same recipient. ERI is a term used for a payment sent to one recipient and contains several invoices/references with amounts specifically per invoice. These extended invoices / payment references provide the opportunity to use credit invoices in connection with an invoice payment. The total amount of the payment must exceed 0.

SEB's collaborations with ERP vendors and bank integrators

We work continuously to expand our network. Examples of collaborations are:
ERP: Björn Lundén, Fortnox, Hogia, PE Accounting, Procountor, Visma eEkonomi, Visma Autopay, Wint, Xledger och 24SevenOffice to name a few.
Bank integrators: Pagero, ZData och Zwapgrid
Salary-related services: Zalaris

Test your files and file format descriptions (ISO 20022 format)

SEB Test Bench is an online tool for SEB's customers and business partners. The test helps you ensure correct implementation, based on SEB ISO 20022 file format descriptions "Message Implementation Guidelines (MIG)". Here you will also find support documents, such as file format descriptions for account transfers.

SEB Test Bench & MIG

SEB's offer for payments in ISO format

Read more about SEB's offers for payments in ISO 20022 format, for our mutual customers.

Payments through XML | SEB (in Swedish)
Automate your accounting | SEB (in Swedish)
File Integration Partners | SEB

Information from the Swedish Bankers' Association

Contact us

If you have further questions or need help.