To main content

Production Access Point validation

The NPa Peppol Test Tool will, by default, only send documents to access points configured with PEPPOL Test certificates. The reason for this is that otherwise, the test tool could be abused to send false documents to production servers and the accounting softare behind those.

However, there is a way to use your production access point with the test tool, should you wish to do so.

First, add your access point like you would a test access point in the Access Point overview. If the access point uses production certificates, the access point type will be shown as ‘PROD’.

The access point details page has a fourth tab, called ‘Production Validation’.

To send documents to this access point, or to receive documents from this access point, you must validate one or more ISO 6523-identifiers on this tab.

The process to do so is similar to the sender extended tests:

  1. On the tab ‘production validation’, click on the button ‘create test code’
  2. The system will generate and show a random code
  3. Go to your access point or ERP software, and create a document in any of the formats supported by the system (such as SI-UBL). This document must contain the generated code in either the document-level note (cbc:Note), or any of the invoice lines (cbc:Name or cbc:Description).
  4. Send this document to the test tool. Do NOT use the identifier at the top of the page for this, but send the document to the address ‘0190:00000099003214345003’ (9954: if it is an SI-UBL 1.2 document).
  5. If the document is accepted, and the code is correct, the identifier that was used to send the document is added to the list of validated identifiers.
  6. Click ‘refresh’ to see whether the list has been updated.

Validated identifiers can be used to send documents to the test tool through the identifier ‘0190:00000099003214345003’, and to send documents from the test tool to this access point.

If you wish to add additional identifiers, repeat the above steps. You will need to create a new code for each identifier you wish to add.

NPa Peppol Test Tool documentation

Production Access Point validation

The NPa Peppol Test Tool will, by default, only send documents to access points configured with PEPPOL Test certificates. The reason for this is that otherwise, the test tool could be abused to send false documents to production servers and the accounting softare behind those.

However, there is a way to use your production access point with the test tool, should you wish to do so.

First, add your access point like you would a test access point in the Access Point overview. If the access point uses production certificates, the access point type will be shown as ‘PROD’.

The access point details page has a fourth tab, called ‘Production Validation’.

To send documents to this access point, or to receive documents from this access point, you must validate one or more ISO 6523-identifiers on this tab.

The process to do so is similar to the sender extended tests:

  1. On the tab ‘production validation’, click on the button ‘create test code’
  2. The system will generate and show a random code
  3. Go to your access point or ERP software, and create a document in any of the formats supported by the system (such as SI-UBL). This document must contain the generated code in either the document-level note (cbc:Note), or any of the invoice lines (cbc:Name or cbc:Description).
  4. Send this document to the test tool. Do NOT use the identifier at the top of the page for this, but send the document to the address ‘0190:00000099003214345003’ (9954: if it is an SI-UBL 1.2 document).
  5. If the document is accepted, and the code is correct, the identifier that was used to send the document is added to the list of validated identifiers.
  6. Click ‘refresh’ to see whether the list has been updated.

Validated identifiers can be used to send documents to the test tool through the identifier ‘0190:00000099003214345003’, and to send documents from the test tool to this access point.

If you wish to add additional identifiers, repeat the above steps. You will need to create a new code for each identifier you wish to add.