Skip to content

Connection setup

This section covers the setup of the connection between your peppol access provider and your Dynamics environment.

Prerequisites

  • Key vault access in Microsoft Azure

Peppol connection

First step in the setup process is to define one or multilple connections. A peppol connection is maintained on cross company level and can be used in multiple legal entitis. When creating a connection a type will have to be provided. Currently there is support for three types of connections:

  • Ibanity Peppol: used for direct connection with Ibanity (Wolters Kluwer) Flowin
  • Delawere Smartlink: user for scenario's where communication with a Peppol Acces point is handled by our Smartlink integration API's
  • Banqup: used for direct connection with Unified Post Banup API

General

  • Connection id: unique id for the connection
  • Description
  • Connector type: define the connection type as explained above

Ibanity peppol:

Ibanity API documentation

  • API URL: URL to the API.
  • Client Id: Client Id that can be retrieved in the developer portal.
  • Error retry count: Number of times the connecter retries API calls when communication error occurs *
  • Error retry seconds: Number of seconds between subsequent API calls in case of retry*
  • Azure key vault company: Company where key vault secrets are maintained in.**
  • Client certificate key vault secret: reference to a Key Vault parameter value that points to the client certificate that was obtained from the developer portal.
  • Client secret key vault secret: reference to a Key Vault parameter value that points to the client secret that was obtained from the developer portal.

When no specific need leave the default values (retry count "5"; retry seconds "1") in place * By default key vault parameters are maintained on company level. We advise to maintain all key vault secrets centralized in the "DAT" company.

  • API URL: URL to the API.
  • Authentication type: there is support for 2 authentication types when using Smartlink, OAuth2 and APIM key
    • OAuth2
      • OAuth URL: URL that will be used to fetch a bearer token, when using Azure OAUTH set url to
      • Tenant ID: Tenant ID where the SMARTLINK APIs reside in
      • OAuth Scope: scope that will be provided by integration team
      • Client ID: Client ID of the Application that will login using OAuth
      • Client secret key vault secret: Referce to Azure Key Vault secret containing the application secret
    • APIM
      • API key secret: Referce to Azure Key Vault secret containing API management key

Banqup:

Banqup API documentation

  • API URL: URL to the API.*
  • Client Id: Client Id that can be retrieved in the developer portal.
  • Azure key vault company: Company where key vault secrets are maintained in.**
  • Client secret key vault secret: reference to a Key Vault parameter value that points to the application secret for authenication.

Banqup provides separate URLs for UAT and Production environment * By default key vault parameters are maintained on company level. We advise to maintain all key vault secrets centralized in the "DAT" company.

The framework allows a connection to be defined per Legal Entity. This allows one or more legal entities to share the same connection parameters. In the supplier a unique identifier must be set that is obtained by de access provider, this is how the legal entity is identified in communication with the access provider's APIS.

delaware Peppol Parameters

This parameter section contains parameters that are not related to a specific connection. - Peppol directory search URL: URL for REST API that will be used in customer search * - eInvoice attachment: Indication whether or not an embedded document will be added to the UBL - Customer search API throttle count: max number of requests that customer search is limitid to in a given timeframe (for throttling purposes) - Customer search API throttle wait: the timeframe to wait (in milliseconds) between throttled requests