Nets Share

Get started
Step 1
Step 2
Step 3
Overview
Request demo access
Request production access
Implementation guide
Service description
Functional description
XML format
Implementation plan
e-Boks channel
Print channel
Operation pattern and deadlines
Advanced features
Example Package & XSD's
Contact us

Step 1

 

In step one you will learn how Nets Share works along with the most common files you can expect to receive.


 

How Nets Share works

Nets Share is a distribution service where the customer gets access to an Inbound and Outbound SFTP folder with the aim of sending documents to their customers via e-Boks or Print.

In the inbound folder the customer places a Zip file with the name netsshare_*.zip which contains the pdf files for distribution, along with one shipment.xml which describes how Nets Share is to process the pdf files.

In the Outbound folder, the customer receives  five types of files. These types are explained in the text below.

In the image below is a receipt flowchart of Nets Share to help understand the relation between the different files. Please refer to this when in doubt of when a file is to be expected or the more detail​​ed flo​wchart in the Overview section.

   Receipt_flow_Process2.png 

  • «Receipt Flowchart of Nets Share which senders are required to automatically read – a more detailed flowchart of Nets Share is viewable in the Overview​ section»


 

Output file examples and explanations: 

Shipment receipts - Receipts when placing a shipment (the zip file containing PDF's and the shipment.xml) can be received with either a code 200 for success or a code 400 for rejection.

Success example –

File name:

tTEST_DK12345678_XXXXXXX_shipmentfilename​.zip.receipt

Content:

<receipt>
  <status>200</status>
  <messages/>
</receipt>

​​

Reject example –

                File name:

tTEST_DK12345678_XXXXXXX_shipmentfilename.zip.receipt

Content:

<receipt>
  <status>400</status>
  <messages>
    <message>This shipment has already been received before</message>
  </messages>
</receipt>

​​

Shipment realtime.receipts - Realtime.Receipts are placed within a minut of the shipment being processed by Nets Share, telling the sender if e-Boks has accepted or rejected the messages within the shipment that was sent in realtime. Messages delivery status from the given shipment sent with realtime=false will not be shown in the realtime.receipt but only in the daily distributionreport. Delivery status for messages sent with realtime=true will both be stated immidiately after dispatch in the realtime.receipt and also in the daily distributionreport which covers all messages.

The realtime.receipt can include both messages that have been delivered successfully and been rejceted and will list all messages from a given shipment with had realtime=true. If no message in a shipment was set to realtime=true, no realtime.receipt will be presented post processing by Nets Share.

Success & Reject example –

File name:

tTEST_DK12345678_XXXXXXX_shipmentfilename.zip.realtime.receipt

Content:

 

<receipt>
  <messages>
    <message id="1">
      <rejectReasons>
        <reason>400 The material is not linked to the system</reason>
      </rejectReasons>
      <channel>EBOKS</channel>
    </message>
    <message id="2">
      <channel>EBOKS</channel>
    </message>
  </messages>
</receipt>

  

 

Distribution report – a distribution report covering the previous days 24 hrs of messages (the individual messages from each shipment) which has been confirmed, or rejected by the final distribution channel. (The report is generated every day shortly after midnight and is available in the Outbound folder between 0100hrs and 0200hrs.

 

Example –

                File name:

12345678_distributionreport_2017-08-13.xml

                Content:

 

<?xml version="1.0" encoding="UTF-8"?>
<distributionReport>
    <summary>
        <distributed channel="EBOKS">1</distributed>
        <distributed channel="PRINT">0</distributed>
        <distributed channel="PRINT_NORDIC">0</distributed>
        <distributed channel="EMAIL">0</distributed>
        <distributed channel="RETURN">2</distributed>
        <rejected>2</rejected>
    </summary>
    <messages>
        <message>
            <shipmentId>aaaaaa</shipmentId>
            <messageId>XXX</messageId>
            <messageSenderId>11111111</messageSenderId>
            <processedDate>2016-03-01</processedDate>
            <channel>EBOKS</channel>
        </message>
        <message>
            <shipmentId>bbbbbb</shipmentId>
            <messageId>YYY</messageId>
            <messageSenderId>11111111</messageSenderId>
            <processedDate>2016-03-01</processedDate>
            <channel>RETUR</channel>
        </message>
        <message>
            <shipmentId>bbbbbb</shipmentId>
            <messageId>YYY</messageId>
            <messageSenderId>11111111</messageSenderId>
            <processedDate>2016-03-01</processedDate>
            <rejectReason>returkode: 7, returtekst: Abonnementsforholdet findes ikke</rejectReason>
        </message>
        <message>
            <shipmentId>cccccc</shipmentId>
            <messageId>ZZZ</messageId>
            <messageSenderId>11111111</messageSenderId>
            <processedDate>2016-03-01</processedDate>
            <channel>RETUR</channel>
        </message>
        <message>
            <shipmentId>cccccc</shipmentId>
            <messageId>ZZZ</messageId>
            <messageSenderId>11111111</messageSenderId>
            <processedDate>2016-03-01</processedDate>
            <rejectReason>returkode: 70, returtekst: Afvist pga. fejl vedrørende signeringsbart dokument</rejectReason>
        </message>
    </messages>
</distributionReport>

​​ 

Return files – a return file is generated if a message has been rejected or was unable to be delivered in the selected distribution channels and ended up in the final channel which is the "Return channel". This is meant as a virtual "returned to sender", and is available immediately after the message has been rejected by the last channel, and is hence a fast way of being informed of something being wrong, instead of waiting for the distribution report being generated past midnight.

 

Example -

                Filename:

tTEST_12345678_shipmentname_1.return

                Content:

 

<?xml version="1.0" encoding="UTF-8"?>
<return xmlns="http://www.nets.eu/nets-share/1.2/return"><shipmentInfo xmlns="http://www.nets.eu/nets-share/1.6">
    <shipmentId>shipmentname</shipmentId>
    <sender>
  <corporateIdentityNumber>12345678</corporateIdentityNumber>
      <country>DK</country>
    </sender>
  </shipmentInfo><message xmlns="http://www.nets.eu/nets-share/1.6" id="1">
      <sender>
        <print-nordic:returnAddress xmlns:print-nordic="http://www.nets.eu/nets-share/1.6/print-nordic">
          <print-nordic:name>Joe Jensen</print-nordic:name>
          <print-nordic:addressline1>Strandvejen 10</print-nordic:addressline1>
          <print-nordic:addressline2>Fyn</print-nordic:addressline2>
          <print-nordic:postalCode>1234</print-nordic:postalCode>
          <print-nordic:city>Copenhagen</print-nordic:city>
          <print-nordic:country>DK</print-nordic:country>
        </print-nordic:returnAddress>
      </sender>
      <print-nordic:receiver xmlns:print-nordic="http://www.nets.eu/nets-share/1.6/print-nordic">
        <print-nordic:name>Hans Hansen</print-nordic:name>
        <print-nordic:addressline1>Hansensvej 001</print-nordic:addressline1>
        <print-nordic:postalCode>8001</print-nordic:postalCode>
        <print-nordic:city>Buller By</print-nordic:city>
        <print-nordic:country>DK</print-nordic:country>
      </print-nordic:receiver>
      <document>
        <filepath>document2.pdf</filepath>
      </document>
    </message></return>

​ 

Subscription lists – [only applicable if using voluntary subscription in e-Boks] the list contains the e-Boks ID and Material ID's with a social security number for each receiver who has subscribed for digital post from the sender via e-Boks. (The subscription file is generated and placed in the Outbound folder every day close to 1400hrs). The subscription list can be used to in advance know to whom it is possible to send documents via e-Boks. Alternatively, if you send a shipments where all recipients contain both postal and e-Boks information Nets Share will automatically deliver all to e-Boks where possible and Print the rest. Most customers prefer to know who has e-Boks and who is missing, since it is more economical to distribute to e-Boks than Print.

 

Example -

                Filename:

12345678_eboks_subscribers_2017-07-24_15723_DK_2.zip

                Content:

<?xml version="1.0" encoding="UTF-8"?>
<eboksSubscriptions xmlns="http://www.nets.eu/nets-share/2.0/eboks/subscriptionlist">
  <header>
    <senderEboksId>11111</senderEboksId>
    <generated>2017-08-11</generated>
  </header>
  <subscriptions country="DK">
    <subscription receiver="0123456789" receiverType="P">
      <materialType>111111</materialType>
      <materialType>111112</materialType>
    </subscription>
    <subscription receiver="1234567890" receiverType="P">
      <materialType>111111</materialType>
      <materialType>111112</materialType>
    </subscription>
    <subscription receiver="12345678" receiverType="V">
      <materialType>111111</materialType>
      <materialType>111112</materialType>
    </subscription>
  </subscriptions>
</eboksSubscriptions>
​

Signed Document – [only applicable when a document has been signed in demo which the Nets Share Support team can help with, upon request] when a document has been signed a Zip file containing an SDO and an xml describing which sent file it relates to. *Its also possible to receive a PAdES file in addition to the SDO, but only the SDO is considered legal proof of the document being signed.

 

Example -

                Filename:
signed_documents_20210714_44a12412-cf14-44ba-9e86-65c62b344471_229359665.zip

                Content:

EBOKSsignatur.sdo AND/OR signed_documents.xml


 When a user has signed a document the first file received back is a zip with a signed_documents.xml stating that cpr or cvr 123456 has signed but more signers might missing. If only one signer is required, shortly after the below files will turn up. In some cases the below files will come before this mentioned file, and it might not be sent by eboks at all. An example of this file is in the example package:
Example package XSD v1.62.zip\Signing\signed_documents_20190521_2d524cfc-78ee-445f-a67c-afdfabe159d3_7173439 (signed).zip 

The sdo file is encrypted and can be validated at: https://www.sign.nets.eu/validator/index.html​  (IP whitelist required request whitelisting HE​RE​ fill out the contact information and write N/A in the rest, and write in the notes field in the bottom that you need access to the above site and add your public IP)

 

Successful signing: 

<?xml version="1.0" encoding="UTF-8"?>
 
<signedDocuments xmlns="http://www.nets.eu/nets-share/1.0/eboks/signed-documents">
  <header>
    <mailbox>tTEST</mailbox>
    <created>2017-07-31</created>
  </header>
  <signedDocument>
    <shipmentReference>
      <shipmentId>shipment1</shipmentId>
      <messageId>001</messageId>
      <messageSenderId>12345678</messageSenderId>
    </shipmentReference>
    <responseDate>2017-07-31 07:27:41</responseDate>
    <signed>
      <sdo>EBOKSsignatur.sdo</sdo>
    </signed>
  </signedDocument>
</signedDocuments>

If the receiver did not sign the document and it was allowed to expire the below message will be received:

<?xml version="1.0" encoding="UTF-8"?>
 
<signedDocuments xmlns="http://www.nets.eu/nets-share/1.0/eboks/signed-documents">
  <header>
    <mailbox>tTEST</mailbox>
    <created>2017-07-31</created>
  </header>
  <signedDocument>
    <shipmentReference>
      <shipmentId>shipment2</shipmentId>
      <messageId>001</messageId>
      <messageSenderId>12345678</messageSenderId>
    </shipmentReference>
    <responseDate>2017-07-31 01:32:27</responseDate>
    <rejected reason="PASSED_DEADLINE">
      <reasonText></reasonText>
    </rejected>
  </signedDocument>
</signedDocuments>

​​Rejected signing (with optional custom text from the user <reasontext>):

<?xml version="1.0" encoding="UTF-8"?>
 
<signedDocuments xmlns="http://www.nets.eu/nets-share/1.0/eboks/signed-documents">
  <header>
    <mailbox>tTEST</mailbox>
    <created>2017-07-28</created>
  </header>
  <signedDocument>
    <shipmentReference>
      <shipmentId>shipment3</shipmentId>
      <messageId>1</messageId>
      <messageSenderId>12345678</messageSenderId>
    </shipmentReference>
    <responseDate>2017-07-28 11:39:56</responseDate>
    <rejected reason="REJECTED_BY_SIGNER">
      <reasonText>Test afvisning test rejection test</reasonText>
    </rejected>
  </signedDocument>
</signedDocuments>

​​What's next?

Now that you are familiarized with the different files you can expect to receive in Nets Share, the next step is – How to create your own shipment.

 Nets Share Step 2 - Click here