In Logistiqo, electronic invoice settings can be maintained for each customer.
These settings define whether invoices for a customer should be created as regular invoices or as electronic invoices, and which e-invoice format should be used.
The general e-invoice setup is usually defined in the domain settings. On the customer record, you can either use this general setting or define a customer-specific setting if the customer requires a different format.
Once the correct setting is maintained on the customer, users usually do not have to select the e-invoice format manually each time. When an invoice is created or sent by email from Logistiqo, the invoice is generated according to the e-invoice settings stored for that customer.
Opening the E-Invoice Settings
Go to Contacts > Debtor Company.
Select the customer for whom you want to maintain the e-invoice settings.
Open the Interfaces tab.
The e-invoice settings are shown in the E-Invoice section.
eInvoice Format
The field eInvoice format defines which electronic invoice format should be used for this customer.
The available options can include:
- Domain default
- No eInvoice
- XRechnung (UBL)
- Peppol BIS Billing (UBL)
- ZUGFeRD / Factur-X
Choose the option that matches the customer’s invoice requirements.
Domain Default
Select Domain default if the customer should use the general e-invoice setting of your Logistiqo domain.
This is usually the correct option if no customer-specific e-invoice format is required.
The domain default can be changed by an administrator in the Administration menu. This means the general e-invoice behavior is controlled centrally, while individual customers can still have their own specific setting if required.
Use Domain default when:
- the customer should follow your general invoice setup
- no special e-invoice format was requested by the customer
- e-invoice settings are managed centrally in your domain configuration
- the customer should automatically follow the default setting defined by the administrator
No eInvoice
Select No eInvoice if invoices for this customer should not be created as electronic invoices.
Use this option when the customer receives regular PDF invoices or does not require an electronic invoice format.
XRechnung (UBL)
Select XRechnung (UBL) if the customer requires invoices in XRechnung format.
XRechnung is a structured electronic invoice format. It is mainly used when the recipient requires machine-readable invoice data, for example in public-sector or specific business processes.
With XRechnung, the invoice data is created as structured XML data. Depending on the sending process, this XML file may be sent as a separate attachment or transferred through the configured electronic channel.
Depending on the recipient, additional information such as Default buyer reference / Leitweg-ID may be required.
Peppol BIS Billing (UBL)
Select Peppol BIS Billing (UBL) if the customer requires invoices in Peppol BIS Billing format.
This option is relevant when invoices are exchanged through a Peppol-based process or when the customer explicitly requests this format.
Peppol BIS Billing is also based on structured invoice data. Depending on the configuration and transmission process, the invoice data may be sent as an XML file or transferred through the connected electronic invoice channel.
For this format, the eInvoice endpoint ID and Endpoint scheme may be required so that the recipient can be identified correctly.
ZUGFeRD / Factur-X
Select ZUGFeRD / Factur-X if the customer requires this invoice format.
ZUGFeRD / Factur-X is a hybrid invoice format. This means that the invoice is still a readable PDF document, but the structured electronic invoice data is embedded inside the PDF.
In practice, the recipient receives a PDF invoice. The PDF can be opened and read normally, but it also contains machine-readable XML invoice data for electronic processing.
This format is useful when the customer wants a readable PDF invoice and structured invoice data in one file.
Additional E-Invoice Fields
Depending on the selected format, additional fields may be required.
eInvoice endpoint ID
The eInvoice endpoint ID identifies the electronic invoice recipient.
This field is especially relevant for formats or transmission methods where the recipient must be addressed through a specific electronic identifier.
Endpoint scheme
The Endpoint scheme defines what type of identifier is used for the endpoint.
The endpoint ID and endpoint scheme usually belong together. If the customer provides e-invoice receiver information, both values should be entered exactly as provided.
Default buyer reference / Leitweg-ID
The Default buyer reference / Leitweg-ID is a buyer reference that can be required by the invoice recipient.
If the customer provides a Leitweg-ID or buyer reference, enter it in this field.
This is especially important if the recipient requires the reference for invoice routing or approval.
Sending E-Invoices from Logistiqo
After the e-invoice settings have been saved on the customer, Logistiqo uses these settings automatically when invoices are created or sent.
This means that users normally do not have to remember the required e-invoice format each time they send an invoice.
When the invoice is sent by email from Logistiqo, the invoice is generated according to the customer’s stored e-invoice format.
For example:
- If the customer uses No eInvoice, the invoice is sent as a regular invoice according to the normal invoice process.
- If the customer uses XRechnung (UBL), the invoice data is generated in the XRechnung format.
- If the customer uses Peppol BIS Billing (UBL), the invoice data is generated in the Peppol BIS Billing format.
- If the customer uses ZUGFeRD / Factur-X, the structured invoice data is embedded in the PDF invoice.
Depending on the selected format and the configured sending process, the electronic invoice data may be included inside the PDF, attached as a separate XML file, or transferred through the configured electronic invoice channel.
Saving the Settings
After selecting the e-invoice format and entering the required additional information, click Save.
The selected e-invoice settings will then be used when invoices are created for this customer.
What to Check Before Creating an Invoice
Before creating an invoice for a customer with e-invoice requirements, check the following:
- Is the correct customer selected?
- Is the correct eInvoice format selected?
- Is Domain default correct, or does the customer need a specific format?
- Is the eInvoice endpoint ID required and filled in?
- Is the Endpoint scheme required and filled in?
- Is the Default buyer reference / Leitweg-ID required and filled in?
- Are the customer’s address and company data complete?
- Are the invoice and accounting settings maintained correctly?
Missing or incorrect e-invoice data can cause the invoice to be rejected or created in the wrong format.
Common Issues
If an e-invoice cannot be created or is not accepted, check the customer’s Interfaces tab first.
Common causes are:
- wrong e-invoice format selected
- customer should not use Domain default
- missing endpoint ID
- missing endpoint scheme
- missing Leitweg-ID or buyer reference
- incorrect customer master data
- incomplete invoice data
- required invoice fields are missing
If the customer has provided exact e-invoice information, compare the values in Logistiqo with the customer’s instructions.
Important Notes
Only change customer-specific e-invoice settings if the customer requires a specific format or provides specific e-invoice receiver data.
If the general domain setting should apply, keep Domain default selected.
E-invoice requirements can vary by customer. Always use the format and receiver data provided by the invoice recipient.
Summary
Customer-specific e-invoice settings are maintained under:
Contacts > Debtor Company > Interfaces
The most important field is eInvoice format.
Use Domain default for the general system setup. Select a specific format such as XRechnung (UBL), Peppol BIS Billing (UBL), or ZUGFeRD / Factur-X only if the customer requires it.
Once the setting is saved on the customer, Logistiqo uses it automatically when invoices are created or sent by email from Logistiqo.
With ZUGFeRD / Factur-X, the structured electronic invoice data is embedded in the PDF invoice. With XML-based formats such as XRechnung (UBL) or Peppol BIS Billing (UBL), the electronic invoice data is created as structured invoice data and may be sent or transferred according to the configured process.
If required, also maintain eInvoice endpoint ID, Endpoint scheme, and Default buyer reference / Leitweg-ID.