Skip to content

Profile Nemhandel

Philip Helger edited this page Oct 21, 2026 · 1 revision

Underlying specifications: https://rep.erst.dk/git/openebusiness/common/-/tree/master/guidelines/specification (Danish Business Authority, Erhvervsstyrelsen). A copy of the versions used is stored in the docs folder of the submodule phase4-profile-nemhandel.

This profile is available since v4.8.2. See #408.

AS4 Profiles

This submodule comes with one profile only:

  • ID nemhandel

Relation to Peppol

Nemhandel eDelivery is based on the Peppol AS4 profile 2.0.2 (plus Peppol SML 1.2.0, SMP 1.3.0, SBDH 2.0.1 and the Peppol policies for identifiers and transport security). The Nemhandel specifications do not define any AS4 or PMode level deviation. Therefore this submodule has no logic of its own:

  • NemhandelPMode.createNemhandelPMode delegates to PeppolPMode.createPeppolPMode
  • NemhandelCompatibilityValidator extends PeppolCompatibilityValidator without any change
  • The profile is registered via SPI (AS4NemhandelProfileRegistarSPI) with the ID nemhandel, the name Nemhandel and the dynamic PMode ID provider

For all AS4 details (one-way push, signing, encryption, compression, ...) see Profile Peppol.

Maven Coordinates

    <dependency>
      <groupId>com.helger.phase4</groupId>
      <artifactId>phase4-profile-nemhandel</artifactId>
      <version>x.y.z</version>
    </dependency>

The module depends on phase4-lib and phase4-profile-peppol.

Constants

The class CNemhandel contains the Nemhandel specific values, taken from the Nemhandel eDelivery Network Specification 1.2.0:

Constant Value Meaning
TRANSPORT_PROFILE_ID_NEMHANDEL_AS4_V2 nemhandel-transport-as4-v2_0 SMP transport profile (Peppol uses peppol-transport-as4-v2_0)
SML_URL https://sml.erst.dk/nemhandel-sml/ URL of the Nemhandel SML (SML DK)
SBDH_SCOPE_TYPE_SIGNATURE NEMHANDEL_EDELIVERY_SIGNATURE SBDH business scope type that carries the XAdES document signature
SBDH_SCOPE_IDENTIFIER_SIGNATURE nemhandel-edelivery-1.2 SBDH business scope identifier that accompanies the signature

Sending and receiving

There is no Nemhandel specific client or servlet submodule. Use the Peppol ones:

Because Nemhandel Access Points do not have a Peppol seat ID, the Peppol seat ID pattern P[A-Z]{2}[0-9]{6} must be switched off:

  • Incoming: set the configuration property phase4.peppol.inbound.check-seat-id=false (default true). The pattern is then no longer enforced for PartyInfo/From/PartyId and PartyInfo/To/PartyId.
  • Outgoing: call performSeatIDCheck (false) on the Phase4PeppolSender builder.

What is not covered (yet)

Topic Nemhandel Status in phase4
AP certificates MitID system certificates (FOCES3) with the CVR number in the subject; no Peppol seat ID Not checked by this module. Make sure that the trust configuration of your sender and servlet matches your Nemhandel environment
Payload signature Detached XAdES-BASELINE-B in StandardBusinessDocumentHeader/BusinessScope/Scope of type NEMHANDEL_EDELIVERY_SIGNATURE Not supported; only the constants exist
Validation XSD error: synchronous rejection; Schematron error: asynchronous MLR/AR Asynchronous responses are not supported
Error codes E-APR21xxx list (Error Code List 1.1.0) Not supported
Logging, uptime, payload size 5 years, 99.65 %, 100 MB Operational requirements, not enforced

Open points in the Nemhandel sources themselves: the Network specification requires error code list 1.2.0, but only 1.1.0 is published, and that version still refers to ASiC-E / transfer delegation, which the Network specification no longer uses.

Further information

Clone this wiki locally