In the New processing step xSuite eDNA Helix receives a new document for dispatch. Incoming documents from a source system must always be transferred via the SendV2 endpoint of the REST API .

When handing over the document to xSuite eDNA Helix, the sender must provide the following information:

xSuite eDNA Helix automatically checks the incoming document for syntactic correctness of the data model. If the document is incorrect, xSuite eDNA Helix rejects the document. The source system must retrieve the error message via the REST API. This error message is displayed in the outbound monitor.

If the document does not contain any errors, it is converted to the internal xSuite eDNA Helix format. xSuite eDNA Helix generates a work item. The generated work item is displayed as a new entry in the outbound monitor.

In processing step Validate, an outgoing document is checked for compliance with European standard EN 16931 by xSuite eDNA Helix. The validation report is saved in the work item.

If the check fails, the document is set to Error status. In this case, the document must be corrected and then sent to xSuite eDNA Helix again. If the same document (work item with the same tracking ID) is sent again, xSuite eDNA Helix processes the data again and transfers the work item to the next processing step.

In the Transform processing step, xSuite eDNA Helix converts the document data into the required format. xSuite eDNA Helix saves the result of the conversion in a work item.

The required format depends on the connector:

xSuite eDNA Helix internal data processing is complete in the processing step Send document. The document is sent via the specified connector.

The target system checks whether the data can be processed technically. Depending on the type of connector, the target system also checks format conformity.

If the checks in the target system fail, an error message from the target system is displayed in the outbound monitor for the respective work item. If there is a compliance error, the document must be corrected in the source system. The work item with the same tracking ID must be sent again.

Once the document has been successfully transmitted, the work item is transferred to the next processing step.

In the Wait for send approval processing step, xSuite eDNA Helix retrieves the acknowledgments and saves them in the work item. The acknowledgments are only retrieved if the target system (e.g., Peppol) provides for this.

Depending on the target system, the documents remain in this queue for a longer period of time. In the Peppol network, for example, this queue is set to 6 hours.

During the Post processing step, xSuite eDNA Helix performs technical rework in the background.

The processing step Sent is the final step in the process. The document has been sent successfully and can now be archived by the source system.