Skip to main content

How to connect to Mijn Data, Mijn Business?

Support medewerker
  • Updated

Introduction

Software partners have various options for connecting to the SBR Nexus infrastructure via My Data, My Business. This document outlines the steps to help software partners prepare to make the connection as simple as possible. 
We distinguish two steps that must be taken for this: XBRL creation and XBRL sending. 

 

1. Application for an eHerkenning tool

You need an eHerkenning tool to log in to My Data My Business as a user. The eHerkenning tool is issued at organizational level. The eHerkenning tool is issued by a recognized eHerkenning supplier.  More information can be found here. To test your software, you can request a test tool from SBR Nexus to gain access to the acceptance environment.

 

2. Use MDMB 

MDMB supports both manual and system-to-system communication. As soon as you have a valid eHerkenning tool, you can log in to MDMB. Via the user interface you are able to send an SBR report manually (in XBRL format) to the correct receiving party. To do this, click on the 'SBR Annual Accounts' tile. 

Would you prefer to deliver system-to-system in SBR? Then you must have an API token with which you can deliver software to the receiving party. You can read more about the MDMB API here. 

 

3. Generate API token

To send SBR messages you need a one-time API token. You can easily generate this in the MDMB portal. You can then use this in your software to communicate with the MDMB API. 

Would you prefer to exchange tokens automatically via API? Then follow this link to our OAuth link documentation.

 

4. Create an XBRL file

The data from a software package must be converted to the XBRL format, as this is the only format that can be sent to the receiving parties via the SBR Nexus infrastructure. The XBRL specifications are applied internationally in numerous sectors and are therefore not specific to SBR Nexus, the specifications are published at https://www.xbrl.org/.

The options for xbrl creation are:

Do you have a file format other than XBRL? Then you may be able to use the converter. Easily convert your current file format such as XML to the correct XBRL format. You can use the converter (API) for this.

Support of Financing Taxonomy or Real Estate Taxonomy

A software package must support a current version of the Financing Taxonomy or Real Estate Taxonomy. The current version of the taxonomies and associated documentation can be found here.

Complying with the Banking Quality Framework for the SBR Annual Accounts (Credit Reports)

The Banking Quality Framework for Credit Reports sets out the quality norms and standards for the SBR Annual Accounts (Credit Reports).

SBR Nexus offer: Support with XBRL creation and/or sending by Accept

SBR Nexus offers software partners the opportunity to use Accept's services for XBRL creation under the following conditions:

  • The Accept tooling is used
  • SBR Nexus will cover the one-off costs for connection support
  • SBR Nexus covers the usage costs
    • Limited to 1 year or 500 documents
  • The contract for these Accept services is concluded directly between Accept and the software partner

SBR Nexus test policy XBRL

SBR Nexus publishes various data standards in the form of data products for business use in the Netherlands. New versions of these products are published every year.

This document describes the policy for the chain test (end to end test) of these products in the supply chain. Testing is central to this policy, because careful testing is crucial for guaranteeing data quality throughout the entire chain.

 

5. Send the XBRL report to the bank

The options for sending an XBRL file to the receiving parties are:

  • Connect to the REST API of My Data, My Business by developing a connection yourself.
  •  Manual upload of an XBRL file on My Data, My Business (Acceptance environment)


6. Status and error codes 

MDMB sends the XBRL file to the BIV. The BIV is the Banking Infrastructure Facility of SBR Nexus and is responsible for validating the messages and routing to the correct recipient. If the message does not meet the requirements, the BIV will reject it. 

In the BIV technical documentation you will find the error and status messages that can be returned by the BIV to parties that use the BIV services (also via MDMB). These can be found in the Appendix "A. Status and fault codes".

When new services and new processing processes are created within these interfaces, new error and status messages can be defined. The technical documentation contains these messages for the BIV interface: WUS 2.0 for Companies version 1.2.

Each error code has a three-letter prefix. This prefix indicates for which service the error occurred.

The following prefixes are used (in brackets the service generating the error):

  • ALS (Supply Service): errors during the delivery of the information
  • AFS (Delivery Service): errors during the delivery of the information

A delivery via MDMB follows the process below, in which the following calls can be distinguished:

  • Call #1: Software calls API converter (/api/converter) --> Software receives the xbrl file in the response
  • Call #2: retrieve available recipients / messagetypes (/api/messagetypes)
  • Call #3: Send xbrl file to MDMB (/api/reports)
  • Call #4: Update Chamber of Commerce Number in the report (/api/reports/{GUID}
  • Call #5: send xbrl message to the bank (api/filings)
  • Call #6: retrieve status of the delivery (api/filing)

MDMB_API_flow.png

 

7. Testing for MDMB Acceptance 

Logging into the MDMB Production environment is done using: eRecognition, however, in the MDMB Acceptance environment this is done by means of username and password. After logging in, it is possible to create a link code (API token) here

  • To create a username and password we need the following information, which can be sent to support@mijndatamijnbusiness.nl:

    • First name + last name
    • E-mail address
    • Company Name
    • Chamber of Commerce number

The test parameters

  • Environment:                        BTBA (Acceptance)
  • Message type:                     Rental list (or other message types i.e. annual accounts, KYC etc.)
                                             see example below from the message types service API)

1.png

  • Entry point:                         VT15 Rental information (see example below from the message types service API)

2.png

  • Requesting party:         For test deliveries that must be assessed by SBR Nexus: “SBR Nexus” (Recipient ID: 00000003111111190000, see the example below from the message types service API)

3.png

For test deliveries that do not need to be assessed by SBR Nexus (SBR Nexus cannot view these): “Test bank” (recipient ID: 00000000123456780000)

 

The test scenarios

To determine whether the XBRL meets the quality standards, it is advisable to test different scenarios. This prevents messages from being unwantedly rejected when it is in use. You can use the MDMB acceptance environment for testing work. The heading below 'XBRL transmission' explains in more detail how this XBRL can be sent.  

After submitting the test scenario, we would like to receive the following by email:

  • The BIV characteristic per scenario (for example, it looks like this: BTA-220805-0000007)

This can be emailed to laurens.klomp@sbrnexus.nl 

 

Was this article helpful?
0 out of 0 found this helpful