Overview

The Nuclet enables the generation of electronic invoices in XML or PDF format, their official validation and their presentation in an HTML file.

The following format is supported: XRechnung in version 3.0.2 (20.06.2024) in the XML syntax Universal Business Language (UBL) of OASIS in version 2.1 and the XML syntax Cross Industry Invoice (CII) of UN/CEFACT in version D16B.
Furthermore, the specification ZUGFeRD in version 2.3.3 (07.05.2025) is covered.

The following options are available for generating the files:

1. The rule org.nuclet.xrechnung.ErzeugeERechnung, which can be embedded in a suitable layout and, as before (version 1), creates an XRechnung (UBL).
2. Your own rule that calls and processes org.nuclet.xrechnung.ErzeugeERechnung#erzeugeERechnung(org.nuclet.xrechnung.Rechnungen, boolean, org.nuclos.api.common.NuclosFile) with suitable parameters (see further below).
3. Your own rule that calls and processes org.nuclet.xrechnung.ErzeugeERechnung#erzeugeERechnung(org.nuclet.xrechnung.XRechnung, boolean, org.nuclos.api.common.NuclosFile) with a suitable object (see further below).

Depending on the respective configuration, the following files are generated, returned and stored in a suitable subform.

• XML file according to the XRechnung standard or PDF file according to the ZUGFeRD standard (depending on the method call)
• HTML file as a preview of the generated data
• HTML file with the results of the XML validation
• If the validation of the PDF file was not successful: TXT file with the results of the PDF validation
• LOG file with the results of the invoice generation

Optionally, a validation of the Leitweg-ID is also included in the Nuclet.

Example

An example is available in the attached Beispiel-Nuclet .

Further examples for adapting the data sources, e.g. for the Basisnuclet für Handelsunternehmen, are available on request.

Notes

Notes on the method public static List<XRechnung.XRechnungFile> erzeugeERechnung(Rechnungen rechnungen, boolean formatUbl, NuclosFile pdfFile):

• rechnungen: the respective invoice as org.nuclet.xrechnung.Rechnungen (integration point); must have an ID and an invoice number

• formatUbl: controls the XML syntax (if false: CII)

• pdfFile: pre-generated PDF file in PDF-A1 format into which the XML file is to be embedded - if specified, the CII format must be chosen

• Return value: list of the generated files including validation results

Notes on the method public static List<XRechnung.XRechnungFile> erzeugeERechnung(XRechnung xRechnung, boolean formatUbl, NuclosFile pdfFile):

• xRechnung: Java object that specifies the corresponding configuration (see table) for creating the electronic invoice

• formatUbl: as above

• pdfFile: as above

• Return value: as above

Nuclet structure

Two Nuclets are required:

• org.nuclet.xrechnung: main Nuclet for generating electronic invoices
• org.nuclet.xrechnung.datenquellen: Nuclet for defining the data sources, which should be adapted per project. This Nuclet is required by the former and should be imported once as a template.
  
  

PDF generation via a form for ZUGFeRD

The JasperReports integrated in Nuclos enables the generation of PDF files in PDF-A1 format. For this, the following settings must be made in the template - font and ICC profile are already included in the main Nuclet.

	<property name="net.sf.jasperreports.export.pdfa.conformance" value="pdfa1a" />
	<property name="net.sf.jasperreports.export.pdfa.icc.profile.path" value="org/xre/icc/sRGB2014.icc" />
	<style name="default" isDefault="true" fontName="xreLibSans"/>

Integration

The integration after a successful Nuclet import (see Nuclet import) is to be carried out as follows.

Step	Description	Screenshot
1	After importing both (nuclet-import, nuclet-datenquellen) Nuclets, the server instance must be restarted, as the main Nuclet contains its own extensions.
2a	Three business objects are required, which can be embedded under Configuration → Integrationspunkt . Invoice Invoice document [optional] Invoice recipient (Customer) [optional] Documents (generalsearchdocument) [optional]
2b	Example configuration for Documents (generalsearchdocument)
3	In addition, there must be a business object for the invoice items , but this is not required for the integration points.
4	The second Nuclet also contains four data sources (Configuration → Data sources → Report & form), which still have to be adapted to the respective circumstances. Ausgangsrechnung XRechnung Ausgangsrechnung XRechnung Positionen Ausgangsrechnung XRechnung Kommentare Outgoing invoice XRechnung VAT breakdown (optional from 2.1.2) Outgoing invoice XRechnung allowances and charges (optional from 2.1.3) These supply the actual data for generating the electronic invoice, see also the implementation in the Beispiel. The assignment of the data fields to the contents of the electronic invoice takes place according to the XRechnung standard, but only some of the available fields are supported (see data sources or Testfallgruppe_01.xlsx).
5	After that, the rule ErzeugeERechnung or your own implementation (here: ErzeugeBeispielERechnung) can be linked to the corresponding business object (Configuration → Server rule manager) and embedded via a button in the layout (Configuration → Layout). The rules for validating the Leitweg-ID are automatically linked to the business object Invoice recipient .
6	In the case of valid data, the four files described above are generated via the button and the result is presented in a message.

Releases