If your financial software doesn't have a built-in e-in e-invoicing functionality, but does support exporting to or importing from a local folder, we offer the ability to connect to a local folder.

In this instruction page we discuss the design of theClient Connectortool. This is a commandline program that receives and sends new documents based on a folder structure by company and document type. This keeps the exchange with the eConnect platform optimally secure.

Watch out!To set up the ClientConnector requires extensive knowledge of IT.

What are the minimum requirements for the ClientConnector?

• It must run on a Windows machine - there are no versions for other operating systems
• .NET framework 4.6.1 or higher must be present
• Connection must be possible toGate 443towards the eConnect endpoint (listed in the subscription key)
• Make sure that the software can be started/exetutable andReading and writing rightshas in the workbook
• For the tool itself, 1 MBDisk spacerequired plus space for downloading the files (variably based on number of documents to be processed, including any PDF)
• There areNo further system requirementsIn terms of processor, memory etc., it is a very light app and the system load is almost nil.

Step 1 - Create the work environment

• If you have an subscriptionKey, the latest version can be used
  EConnectCommandLine_1_0_10_1(See Annex).Please contact ussales@econnect.euto apply for a subscription key.

Step 2 - Generate the security keys

FollowThis linkand the instructions in step 1

Step 3 - Select Organization ID

In the organization it isExternal IDfind what you need when setting up the config asCompanyID.

Step 4 - Set the configuration

Enter the values in the application settings and check them. Use the security keys from step 2. The values can be overruled by giving them as an argument.
The following values must be adjusted for use.

1. Fill in the security details from Step 2ConsumerKey, Consumer Secret and RequesterId.
   
2. Enter Organization ID from Step 3CompanyId.
   
3. Fill in the location for the documents that must be picked up or where the documents come from before shipment atWorking directorory.This directory should be created for use. For example: {{ComapnyId}}\{{DocumentType}} or XCAb123456\Inbox (This location is relative to the current directory.)
   
4. WithDocument typeIndicates which documents to download (Inbox or Outbox) or that documents should be sent (Send)
   
5. Give withPDFDownloadwhether the document should also be retrieved as a .pdf file.
   
6. Default values (adjust in consultation only): MasterTemplateId, ConversionPartnerGroupId, ConversionFileExtensions, ConversionPartner, TransformXSLT, AddExternalId, CleanXML, Action

ExampleConfiguration file (Watch out: the configuration on your system may vary, check the environmental variables):

1. xml version="1.0" encoding="utf-8"?
2. Release
3. Econnection Command Line Tool
4. 
   
5. ## Usage info:
6. "'"
7. EConnectCommandLine.exe -help
8. "'"
9. 
   
10. ##How to:
11. Download invoice from inbox and oubox or send documents for a single company
12. 
    
13. 1. Get access keys from https://platform.everbinding.nl
14. 2. Setup this config file (EConnectCommandLine.exe.config)
15. Set endpoint at the end of this config with the endpoint supplied with subscriptionKey
16. 3. Create working directory to store or read files from.
17. The application must have write rights in this directory
19. In my case I created: C:/EConnect/Inbox/XCNL10019/ and C:/EConnect/Outbox/XCNL10019/
20. And for sending: C:/EConnect/Send/XCNL10019/
21. 4. Run application to:
22. 
    
23. Download inbox documents:
24. "'"
25. EConnectCommandLine.exe -w C:/EConnect/XCNL10019/Inbox/ -t inbox -c XCNL10019 -d 2016-03-01
26. "'"
27. Download outbox documents:
28. "'"
29. EConnectCommandLine.exe -w C:/EConnect/[CompanyId]/[DocumentType]/ -t outbox -c XCNL10019 -d 2016-03-01
30. "'"
31. - send documents:
32. "'"
33. EConnectCommandLine.exe -w C:/EConnect/XCNL10019/Send/ -t send -c XCNL10019
34. "'"
35. - upload documents (conversion task):
36. "'"
37. EConnectCommandLine.exe -w C:/EConnect/[CompanyId]/[DocumentType]/[Action]/ -t inbox -c XCNL10019 -a Upload - -template=GLDT9223370606989915978RA0000006DTP2000109 -partnerid=XGC4144005987345172
38. "'"
39. ## Notes:
41. - The application creates a .econnect file to store the created date of the most recently downloaded
42. file Contents of the file can be modified to get document with an earlier date.
43. 
    
44. Have two copies for the executable and config file, if you can pass the arguments
45. to the executeable.
47. Application will not detect if it runs multiple times.
48. 
    
49. - A log file is created in the same directory of this executable by default.
50. This can be changed in the log4net section.
51. See https://logging.apache.org for config examples.
52. 
    
53. - Only *.xml files are fetched for sending and uploading in the working directory.
54. The filename will be appended after sending with ".done" or when sending fails to ".error".
55. 
    
56. The following special features are available
57. AddExternalId If set to true will add the eVerbinding ExternalId in the document.
58. This is only needed when the receiving software can use this
59. CleanXML If set to true will remove the namespace statement by element.
60. This is only needed when the receiving software has problems with this use of namespaces.
61. - TransformXSLT will do a transformation base on XSLT file.
63. 
    
64. -->
65. <configuration>
66. <configSections>
67. <section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler, log4net" requirePermission="false"/>
68. <sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
69. <section name="EConnectCommandLine.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false"/>
70. <section name="EConnectApi.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false"/>
71. </sectionGroup>
72. </configSections>
73. <applicationSettings>
74. <EConnectCommandLine.Properties.Settings>
75. <setting name="MasterTemplateId" serializeAs="String">
76. Gldt9223370666504283001ra0000006dtp2000001
77. </setting>
78. <setting name="CompanyId" serializeAs="String">
79. {{CompanyId like XCNL10019}}
80. </setting>
81. <setting name="ConversionPartnerGroupId" serializeAs="String">
82. Xgc4144005987345172
83. </setting>
84. <setting name="ConversionFileExtensions" serializeAs="String">
85. pdf,png,jpg,jpeg,tiff
86. </setting>
87. <setting name="RequesterId" serializeAs="String">
88. {{email address}}
89. </setting>
90. <setting name="ConversionPartner" serializeAs="String">
91. Conversion partner
92. </setting>
93. <setting name="ConsumerKey" serializeAs="String">
94. {{ConsumerKey}}
95. </setting>
96. <setting name="ConsumerSecret" serializeAs="String">
97. {{ConsumerSecret}}
98. </setting>
99. <setting name="WorkingDirectory" serializeAs="String">
100. {{ComapnyId}}\{{DocumentType}}
101. </setting>
102. <setting name="Action" serializeAs="String">
103. Download
104. </setting>
105. <setting name="DocumentType" serializeAs="String">
106. DocumentType Inbox or Outbox or Send}
107. </setting>
108. <setting name="PDFDownload" serializeAs="String">
109. True
110. </setting>
111. <setting name="TransformXSLT" serializeAs="String">
112. <value />
113. </setting>
114. <setting name="AddExternalId" serializeAs="String">
115. False
116. </setting>
117. <setting name="CleanXML" serializeAs="String">
118. False
119. </setting>
120. <setting name="ExtractSenderIdFromPayload" serializeAs="String">
121. True
122. </setting>
123. </EConnectCommandLine.Properties.Settings>
124. </applicationSettings>
125. <log4net>
126. <appender name="TraceAppender" type="log4net.Appender.TraceAppender">
127. <layout type="log4net.Layout.PatternLayout">
128. <conversionPattern value="[%property{company}] %-5level %logger{1} - %message%newline"/>
129. </layout>
130. </appender>
131. <appender name="ConsoleAppender" type="log4net.Appender.ConsoleAppender">
132. <layout type="log4net.Layout.PatternLayout">
133. <conversionPattern value="[%property{company}] %message%newline"/>
134. </layout>
135. </appender>
136. <appender name="FileAppender" type="log4net.Appender.FileAppender">
137. <file value="log-file.txt" />
138. <appendToFile value="true" />
139. <layout type="log4net.Layout.PatternLayout">
140. <conversionPattern value="%date [%thread] %-5level %logger [%property{NDC}] - %message%newline" />
141. </layout>
142. </appender>
143. Uncomment when needed. The Appender must be uncommented.
144. Maybe it needs to be run as administrator for the first time
145. <!--    
146. <appender name="EventLogAppender" type="log4net.Appender.EventLogAppender" >
147. <applicationName value="EConnectCommandLine" />
148. <layout type="log4net.Layout.PatternLayout">
149. <conversionPattern value="%date [%thread] %-5level %logger [%property{NDC}] - %message%newline" />
150. </layout>
151. </appender>
152. -->    
153. <root>
154. <level value="DEBUG"/>
155. <appender-ref ref="ConsoleAppender"/>
156. <appender-ref ref="TraceAppender"/>
157. <appender-ref ref="FileAppender"/>
158. Uncomment when needed. The Appender must be uncommented.
159. Maybe it needs to be run as administrator for the first time
160. http://logging.apache.org/log4net/release/faq.html#trouble-EventLog
161. <!--
162. <appender-ref ref="EventLogAppender"/>
163. -->      
164. </root>
165. </log4net>
166. <startup>
167. <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6.1"/>
168. </startup>
169. <system.serviceModel>
170. <bindings>
171. <basicHttpBinding>
172. <binding name="EConnectServiceSoap" maxBufferSize="2147483647" maxBufferPoolSize="524288" maxReceivedMessageSize="2147483647">
173. <security mode="Transport" />
174. </binding>
175. <binding name="EConnectServiceSoap1" />
176. </basicHttpBinding>
177. </bindings>
178. <client>
179. <endpoint address="https://api.everbinding.nl/soap/v3.1/?subscriptionKey={{{{subscriptionKey}}"
180. binding="basicHttpBinding" bindingConfiguration="EConnectServiceSoap"
181. contract="EConnectService.EConnectServiceSoap" name="EConnectServiceSoap" />
182. </client>
183. </system.serviceModel>
184. </configuration>

Launch the ClientConnector via the commandline or shortcut as follows: EConnectCommandLine.exe -help

• Example: download inbox documents
  EConnectCommandLine.exe -w C:/EConnect/XCNL10019/Inbox/ -t inbox -c XCNL10019 -d 2016-03-01
• Example: download outbox documents
  EConnectCommandLine.exe -w C:/EConnect/[CompanyId]/[DocumentType]/ -t outbox -c XCNL10019 -d 2016-03-01
• Example: Send documents
  EConnectCommandLine.exe -w C:/EConnect/XCNL10019/Send/ -t send -c XCNL10019

Some comments on the use

• The ClientConnector will create a .econnect file that tracks what the last minute of updating has been. The contents of this file can be adjusted to retrieve documents with an earlier date and time.
• After downloading and saving the XML invoice, a PDF invoice is also created with the same name but with the .PDF extension in the same folder. If the PDF is present in the XML as a 'primary file', it is used for this purpose and in other cases the PDF is generated based on the information in the XML. This can be turned off by means of the option "-p false" or set the value when PDFDownload to "false" in the config file.
• The ClientConnector can be started several times and run as parallel processes. There is no control from the app itself.
• All applicationSettings from the config file can also be given as an option. UsageEConnectCommandLine -?to display all possible options.
• A log file is created in the folder where the program files are located. This can be adjusted in the config in the log4net section. See alsohttps://logging.apache.orgfor more examples. To do this, see in the //log4net part in the config file. In this part you can also choose to have the logs in the Windows Event logs via EventLogAppender.
• Only *.xml files are covered when sending in the workbook.
• The filename is renamed after sending by an addition, '.done' if successful, or '.error' if something has gone wrong.

Important shipping fields in the SI-UBL

The data for the recipient are included (order of importance):

//cac: AccountingCustomerParty/cac:Party/cbc: EndpointID

//cac: AccountingCustomerParty/cac:PartyLegalEntity/cbc:CompanyID

//cac: AccountingCustomerParty/cac:Party/cac: PartyTaxScheme/cbc:CompanyID

Email address:

//cac: AccountingCustomerParty/cac:Party/cac:Contact/cbc: ElectronicMail

//cac: AccountingCustomerParty/cac: AccountingContact

//cac: AccountingCustomerParty/cac:BuyerContact

At least 1 ID and 1 e-mail address must be entered. The E-mail address is optional but may lead to an error message during sending if the document cannot be delivered based on the ID. To maintain good control over the routing of the document, it is recommended to use cbc:EndpointID. This gives the possibility to send based on VAT (VAT) number and also to have filled in the Chamber of Commerce number. Without cbc: EndpointID, it will be sent on Chamber of Commerce number if it is present.

Since version 1_0_4_2It is also possible to send NLCIUS with numbers as identifiers. Such as 0106: for the NL:KVK: and the 0190: for the NL:OIN:.