The email PDF invoice sending has been expanded to include digital invoices (ZUGFeRD EN16931).

Configuration

The following settings must be made for sending digital invoices:

In the program settings / Miscellaneous tab

To ensure correct data transfer to the XML file, the input mask for general company data has been expanded to include new fields.

Until now, your own address data was entered completely into one address field and was mainly used for transferring to text templates.

However, digital invoices require this data in a split form.

The following individual address fields have been added to the program settings:

Miscellaneous program settings

In the program settings / selection lists

An e-invoice contains various data in the form of standardized codes, e.g. ISO country codes and codes for article units.

This data is maintained in the ingenious software as individual selection lists.

To ensure that the correct codes are transferred in the e-invoice, an export mapping column has been added to the tables.

For  contacts/country, either the country names or the ISO country codes or other alternative forms are stored.

The previous values ​​can still be retained, but the ISO country codes must be assigned to the individual countries.

If ISO country codes are already stored, they do not need to be mapped separately.

Mapping of the country codes

Product Catalog / Price Per Unit SP:

Similar to the country codes, a mapping has also been added which maps the existing units to selected codes according to the UN-ECE Recommendations (No. 20).

These are:

Mapping of article units

Contacts / Payment method:

A mapping has been added that maps the existing payment methods to selected codes from the code list 4461 (Payment means code) of the United Trade Data Interchange Directory (UNTDID).

A valid code must be assigned to each of the payment methods stored in the selection list.

These are:

Mapping of payment types

In the program settings / Projects tab / Invoices section

Settings for outgoing invoices

Customizing contact records

If an invoice recipient wants a different format than the standard configured in the program settings, a different format can be stored for this contact in the financial data.

Possible selection:

• PDF simple (simple PDF without XML – no e-invoice)
• ZUGFeRD (PDF with integrated XML)
• XRechnung (XML)

Invoice format settings for contact

Sending digital invoices

Sending an invoice can be started from the detail view or from the list view using the button “Send as PDF” or “Send as PDF and attach”.

The invoice will be attached to the email in the selected format.

If invoices are sent automatically via a scheduler script in a company, this script may need to be adapted.

Our developers will support you.

transfer of individual data

The XML files of the digital invoices are filled with the data of predefined fields.

Not all companies use the same ingenious fields for printing on invoices.

In particular, position texts in the documents are often created from different sources and placeholders.

In order to be able to design the e-invoice individually, the script DigitalInvoiceBeforeExport was created, with which the single nodes of the XML can be filled differently.

The XML node is selected via the node identifier.

The else condition must always return the default value.

public override string DigitalInvoiceBeforeExport(DataRow row, string nodepath, string defaultvalue)
{
    if (fieldname == “Name“)
    {
        return “Max Mustermann“;
    }
    else if (fieldname == “Chargeamount“)
    {
        return row[“sales_price“].ToString();
}
    else
    {
        return defaultvalue;
    }
}

All nodes of the ZUGFeRD EN16931 format can be addressed in the script.

However, it is not intended to add additional nodes via script, e.g. any number of IncludedNote nodes.

For the IncludedNote at document level, a node is filled with the company’s “REG” data, which should not be overwritten.

A second IncludedNote node has been added for individual comments, which can be filled as desired.

The documentation of the nodes and assigned ingenious fields can be requested from Ingenious.

Notes:

The current ingenious version takes the ZUGFeRD EN16931 format into account.

At this level of detail,

• Payment terms are mainly transferred as text
  In particular, discount periods cannot be exported clearly
• Collective invoices are not supported
  The e-invoices cannot be structured cleanly (no headings, no subtotals, no different information on the delivery/service date).

The creation of digital invoices is gradually being supplemented by the extended format and the XRechnung format.