PROBIS-ZUGFeRD 19.0.4

dotnet add package PROBIS-ZUGFeRD --version 19.0.4
                    
NuGet\Install-Package PROBIS-ZUGFeRD -Version 19.0.4
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="PROBIS-ZUGFeRD" Version="19.0.4" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="PROBIS-ZUGFeRD" Version="19.0.4" />
                    
Directory.Packages.props
<PackageReference Include="PROBIS-ZUGFeRD" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add PROBIS-ZUGFeRD --version 19.0.4
                    
#r "nuget: PROBIS-ZUGFeRD, 19.0.4"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package PROBIS-ZUGFeRD@19.0.4
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=PROBIS-ZUGFeRD&version=19.0.4
                    
Install as a Cake Addin
#tool nuget:?package=PROBIS-ZUGFeRD&version=19.0.4
                    
Install as a Cake Tool

PROBIS fork of ZUGFeRD-csharp

NuGet NuGet NuGet

Attribution and license

This repository is a modified fork of ZUGFeRD-csharp by Stephan Stapel / STwo Industries GmbH, licensed under the Apache License, Version 2.0. The fork starts at upstream commit 58f530e ("Prepare 18.0.1 deprecation release", 2026-10-09). All later changes were made by PROBIS Software GmbH and are tracked in this repository's history. This fork is maintained independently and is not affiliated with or endorsed by the original author, STwo Industries GmbH or FeRD. See NOTICE.txt and LICENSE.txt.

The packages are published on nuget.org as PROBIS-ZUGFeRD, PROBIS-ZUGFeRD.PDF and PROBIS-ZUGFeRD.CDAR. Source code: https://codeberg.org/probis/Probis.ZUGFeRD


In case you need consulting or commercial support for implementing ZUGFeRD/ XRechnung/ Factur-X in your company, please contact us at PROBIS Software GmbH


Introduction

The ZUGFeRD library allows to create XML files as required by German electronic invoice initiative ZUGFeRD as well invoices in the successor Factur-X. One special profile of Factur-X is the German XRechnung format. The library is meant to be as simple as possible, however it is not straight forward to use as the resulting XML file contains a complete invoice in XML format. Please take a look at the ZUGFeRD-Test project to find sample creation code. This code creates the same XML file as shipped with the ZUGFeRD information package.

Relationship between the different standards

  • ZUGFeRD was developed by the German initiative FeRD as a hybrid standard for electronic invoices (PDF/A-3 with embedded XML) (https://www.ferd-net.de/).
  • Since ZUGFeRD 2.1 (2020) every release is published jointly with the French Factur-X and both are technically identical, only the version numbers differ (e.g. ZUGFeRD 2.1 = Factur-X 1.0.05, ZUGFeRD 2.3 = Factur-X 1.0.07) (https://www.ferd-net.de/en/standards/zugferd/factur-x).
  • The European norm EN 16931 defines a syntax-neutral semantic data model for invoices with two official XML syntaxes: UN/CEFACT 'Cross Industry Invoice' (CII) and OASIS UBL.
  • ZUGFeRD/ Factur-X uses the CII syntax. The profiles BASIC, EN 16931 and EXTENDED are conform with EN 16931, the profiles MINIMUM and BASIC WL are not (they are no full invoices).
  • XRechnung is the German standard for invoices to public authorities. It is a restriction (CIUS) of EN 16931, allows CII as well as UBL, and is maintained by KoSIT (https://www.xoev.de/) with its own validation rules (https://xeinkauf.de/dokumente/).
  • Both ZUGFeRD/ Factur-X and XRechnung are conform with EN 16931. This does not automatically mean that an invoice in one format is also valid in the other.
  • To bridge this gap, ZUGFeRD 2.1.1 introduced the reference profile XRECHNUNG: a ZUGFeRD invoice whose embedded XML follows the current XRechnung specification.

Installation

Use nuget and install PROBIS-ZUGFeRD and, as needed, PROBIS-ZUGFeRD.PDF (PDF container) and PROBIS-ZUGFeRD.CDAR (invoice response / lifecycle messages):

dotnet add package PROBIS-ZUGFeRD
dotnet add package PROBIS-ZUGFeRD.PDF
dotnet add package PROBIS-ZUGFeRD.CDAR

Any new release covers each individual package. Make sure all package references within a .net project target the same package version.

Building on your own

Prerequisites:

  • .net10
  • IDE of your choice (optional)

Build the solution..

dotnet build Probis.ZUGFeRD.sln -c Release

..or the libraries individually

dotnet build Probis.ZUGFeRD/Probis.ZUGFeRD.csproj -c Release
dotnet build Probis.ZUGFeRD.PDF/Probis.ZUGFeRD.PDF.csproj -c Release
...

Step-by-step guide for creating invoices

Central class for users is InvoiceDescriptor. This class does not only allow to read and set all ZUGFeRD attributes and structures but also allows to load and save ZUGFeRD files.

However, the standard has become quite large during the recent years. So it is worthwhile to go through the creation process step by step.

Creating an invoice

InvoiceDescriptor desc = InvoiceDescriptor.CreateInvoice("471102", new DateTime(2013, 6, 5), CurrencyCodes.EUR, "GE2020211-471102");
desc.Name = "WARENRECHNUNG";
desc.ReferenceOrderNo = "AB-312";
desc.AddNote("Rechnung gemäß Bestellung Nr. 2013-471331 vom 01.03.2013.");
desc.AddNote("Es bestehen Rabatt- und Bonusvereinbarungen.", SubjectCodes.AAK);
desc.SetBuyer("Kunden Mitte AG", "69876", "Frankfurt", "Kundenstraße 15", CountryCodes.DE, "88", new GlobalID(GlobalIDSchemeIdentifiers.GLN, "4000001123452"));
desc.AddBuyerTaxRegistration("DE234567890", TaxRegistrationSchemeID.VA);
desc.SetBuyerContact("Hans Muster");
desc.SetSeller("Lieferant GmbH", "80333", "München", "Lieferantenstraße 20", CountryCodes.DE, "88", new GlobalID(GlobalIDSchemeIdentifiers.GLN, "4000001123452"));
desc.AddSellerTaxRegistration("201/113/40209", TaxRegistrationSchemeID.FC);
desc.AddSellerTaxRegistration("DE123456789", TaxRegistrationSchemeID.VA);
desc.SetBuyerOrderReferenceDocument("2013-471331", new DateTime(2013, 03, 01));
desc.SetDeliveryNoteReferenceDocument("2013-51111", new DateTime(2013, 6, 3));
desc.ActualDeliveryDate = new DateTime(2013, 6, 3);
desc.SetTotals(202.76m, 5.80m, 14.73m, 193.83m, 21.31m, 215.14m, 50.0m, 165.14m);
desc.AddApplicableTradeTax(129.37m, 7m, TaxTypes.VAT, TaxCategoryCodes.S);
desc.AddApplicableTradeTax(64.46m, 19m, TaxTypes.VAT, TaxCategoryCodes.S);
desc.AddLogisticsServiceCharge(5.80m, "Versandkosten", TaxTypes.VAT, TaxCategoryCodes.S, 7m);
desc.AddTradePaymentTerms("Zahlbar innerhalb 30 Tagen netto bis 04.04.2018", new DateTime(2018, 4, 4));
desc.AddTradePaymentTerms("3% Skonto innerhalb 10 Tagen bis 15.03.2018", new DateTime(2018, 3, 15), PaymentTermsType.Skonto, 30, 3m);

Optionally, to support Peppol, an electronic address can be passed:

desc.SetSellerElectronicAddress("DE123456789", ElectronicAddressSchemeIdentifiers.GermanyVatNumber);
desc.SetBuyerElectronicAddress("LU987654321", ElectronicAddressSchemeIdentifiers.LuxemburgVatNumber);

The fields are only necessary if you want to send the XRechnung via the Peppol network. A description of the fields can be found in the following documents:

https://docs.peppol.eu/edelivery/policies/PEPPOL-EDN-Policy-for-use-of-identifiers-4.3.0-2024-10-03.pdf

In Luxembourg, it has been mandatory since this year to process all invoices via Peppol:

https://gouvernement.lu/de/dossiers.gouv_digitalisation%2Bde%2Bdossiers%2B2021%2Bfacturation-electronique.html

In Germany, this has so far only been necessary for invoices in the course of a public contract from the federal government:

https://www.e-rechnung-bund.de/ubertragungskanale/peppol/

Adding line items

Handling of line ids

The library allows to operate in two modes: you can either let the library generate the line ids automatically or you can alternatively pass distinct line ids. This is helpful if you want to convert existing invoices, e.g. from ERP systems, to ZUGFeRD/ Factur-X.

To let the library create line ids, you can use:

InvoiceDescriptor desc = InvoiceDescriptor.CreateInvoice("471102", new DateTime(2013, 6, 5), CurrencyCodes.EUR, "GE2020211-471102");
desc.AddTradeLineItem("Item name", 23.99m, QuantityCodes.H87, "Detail description", ....);

This will generate an invoice with trade line item numbered as '1'.

To pass pre-defined line ids, this is the way to go:

InvoiceDescriptor desc = InvoiceDescriptor.CreateInvoice("471102", new DateTime(2013, 6, 5), CurrencyCodes.EUR, "GE2020211-471102");
desc.AddTradeLineItem(lineID: "0001", 23.99m, QuantityCodes.H87, "Item name", "Detail description", ....);
desc.AddTradeLineItem(lineID: "0002", 49.99m, QuantityCodes.H87, "Item name", "Detail description", ....);

which will generate an invoice with two trade line items, with the first one as number '0001' and the second one as number '0002'.

Working with product characteristics

Product characteristics are used to add information for the specified trade product in the 'ApplicableProductCharacteristic' section. One trade product can have one or more product characteristics, which can contain description, value, typecode and value measurand elements.

// you can optionally add product characteristics:
desc.TradeLineItems.Add(new TradeLineItem("0003")
{
   ApplicableProductCharacteristics = new List<ApplicableProductCharacteristic>
   {
       new ApplicableProductCharacteristic()
       {
           Description = "Description",
           Value = "Value"
       }
   }
});

Document references

The library allows to add special references to an invoice which are pretty rare but nevertheless supported:

// you can optionally add a reference to a procuring project:
desc.SpecifiedProcuringProject = new SpecifiedProcuringProject {Name = "Projekt AB-312", ID = "AB-312"};

// you can optionally reference a contract:
desc.ContractReferencedDocument = new ContractReferencedDocument {ID = "AB-312-1", IssueDateTime = new DateTime(2013,1,1)};

Invoice Line Status

The library supports setting a status code and a reason for each line item. This feature helps clarifying whether a line item contributes to the invoice total or is for information only. It can be useful for marking items as informational, subtotal lines, or fully processed items, adding context to each invoiced item.

// Example: Adding a trade line item with a specific status and reason
TradeLineItem tradeLineItem3 = desc.AddTradeLineItem(
    name: "Abschlagsrechnung vom 01.01.2024",
    netUnitPrice: 500,
    unitCode: QuantityCodes.H87,
    billedQuantity: -1m,
    categoryCode: TaxCategoryCodes.S,
    taxPercent: 19.0m,
    taxType: TaxTypes.VAT
);

// Set a line status code and reason code to indicate that this line is for documentation only
tradeLineItem3.SetLineStatus(LineStatusCodes.DocumentationClaim, LineStatusReasonCodes.INFORMATION);

Storing the invoice

FileStream stream = new FileStream(filename, FileMode.Create, FileAccess.Write);
desc.Save(stream, ZUGFeRDVersion.Version23, Profile.XRechnung);
stream.Flush();
stream.Close();    

Support for ZUGFeRD 1.x, ZUGFeRD 2.x

In order to load ZUGFeRD files, you call InvoiceDescriptor.Load(), passing a file path like this:

InvoiceDescriptor descriptor = InvoiceDescriptor.Load("zugferd.xml");

alternatively, you can pass an open stream object:

Stream stream = new FileStream("zugferd.xml", FileMode.Open, FileAccess.Read);
InvoiceDescriptor descriptor = InvoiceDescriptor.Load(stream);

The library will automatically detect the ZUGFeRD version of the file and parse accordingly. It will automatically be chosen which XRechnung version to use depending on the current date. The lifecycle of the stream is not influenced by the ZUGFeRD library, i.e. the library expects an open stream and will not close if after reading from it.

For saving ZUGFeRD files, use InvoiceDescriptor.Save(). Here, you can also pass a stream object:

InvoiceDescriptor descriptor = InvoiceDescriptor.CreateInvoice(......);

// fill attributes and structures

FileStream stream = new FileStream(filename, FileMode.Create, FileAccess.Write);
descriptor.Save(stream, ZUGFeRDVersion.Version1, Profile.Basic);
stream.Flush();
stream.Close();            

As you see, the library does not influence the lifecycle of the stream, i.e. it is not automatically closed by the library. Just as opening the stream, flushing and closing is the duty of the calling function.

Alternatively, you can pass a file path:

InvoiceDescriptor descriptor = InvoiceDescriptor.CreateInvoice(......);

// fill attributes and structures

descriptor.Save("zugferd.xml", ZUGFeRDVersion.Version1, Profile.Basic);          

Optionally, you can pass the ZUGFeRD version to use. Currently, the default version is 1.x, e.g.:

InvoiceDescriptor descriptor = InvoiceDescriptor.CreateInvoice(......);

// fill attributes and structures


descriptor.Save("zugferd-v1.xml", ZUGFeRDVersion.Version1, Profile.Basic); // save as version 1.x
descriptor.Save("zugferd-v20.xml", ZUGFeRDVersion.Version20, Profile.Basic); // save as version 2.0
descriptor.Save("zugferd-v23.xml", ZUGFeRDVersion.Version23, Profile.Basic); // save as version 2.3

For reading and writing XRechnung invoices, please see below.

Support for XRechnung

In general, creating XRechnung files is straight forward and just like creating any other ZUGFeRD version and profile:

descriptor.Save("xrechnung.xml", ZUGFeRDVersion.Version23, Profile.XRechnung);

This will save the invoice as XRechnung 3.0.1 as valid from 2024/02/01.

Make sure to also add a business process which is required starting with XRechnung 3.0.1:

desc.BusinessProcess = "urn:fdc:peppol.eu:2017:poacc:billing:01:1.0";

Furthermore, XRechnung comes with some special features. One of these features is the ability to embed binary files as attachments to the xrechnung.xml document:

InvoiceDescriptor desc = _createInvoice();
byte[] data = System.IO.File.ReadAllBytes("my-calculation.xlsx");
desc.AddAdditionalReferencedDocument(
    id: "calculation-sheet",
    typeCode: AdditionalReferencedDocumentTypeCode.ReferenceDocument,
    name: "Calculation as the basis for the invoice",
    attachmentBinaryObject: data,
    filename: "my-calculation.xlsx");

desc.Save("xrechnung.xml", ZUGFeRDVersion.Version23, Profile.XRechnung);            

The resulting xrechnung.xml file will then contain the calculation file content. As this is not standardized, the decision was to encode the attachments in base64. Please note that there are only few mime-types supported by the XRechnung standard. The supported mime-types are defined in BG-24 and BT-125. At the time of writing this tutorial, those are also listed in the discussion you find over here: https://projekte.kosit.org/xrechnung/xrechnung/-/issues/59

  • application/pdf
  • image/png
  • image/jpeg
  • text/csv
  • application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
  • application/vnd.oasis.opendocument.spreadsheet
  • application/xml

Support for E-Reporting

For french companies, a dedicated profile exists called E-Reporting. This profile is implemented on top of XRechnung/ Factur-X. It is used when transactions are done to customers who don't make use of VAT. One example are private customers (in B2C scenarios). The other example is when selling to entities beyond France. More information can be found here: https://www.impots.gouv.fr/e-reporting-la-transmission-de-donnees-de-transaction-ladministration (French) And here: https://www.roedl.de/themen/frankreich-e-invoice-reporting-umsatzsteuer-digital (german)

Thanks to @Athilla, this profile is also supported by PROBIS-ZUGFeRD.

The information that is written into the invoice descriptor is identical to standard XRechnung/ Factur-X invoices, you just need to adjust the profile:

descriptor.Save("factur-x.xml", ZUGFeRDVersion.Version23, Profile.EReporting);

This information needs to be sent to the tax authorities. Different due dates apply for implementation for different sizes of companies.

Support for profiles

The library contains support for all profiles that are supported by the ZUGFeRD formats:

Profile Version1 Version20 Version23
MINIMUM X X
BASIC WL X X
BASIC X X X
COMFORT/EN16391 X X X
XRECHNUNG X
EXTENDED X X X

Please note that version 1 implementation of the library is not strict, i.e. it will output all information available into the invoice xml, regardless of the profiles that is used. Reading various files with different profiles will generate the correct output.

If you want to write the invoice xml with a certain ZUGFeRD version and a certain profile, make sure to use the parameters of the Save method:

descriptor.Save("zugferd-v1.xml", ZUGFeRDVersion.Version1, Profile.Basic); // save as version 1.x, profile Basic
descriptor.Save("zugferd-v20.xml", ZUGFeRDVersion.Version20, Profile.Basic); // save as version 2.0, profile Basic
descriptor.Save("zugferd-v23.xml", ZUGFeRDVersion.Version23, Profile.Basic); // save as version 2.3, profile Basic
descriptor.Save("zugferd-v23-xrechnung.xml", ZUGFeRDVersion.Version23, Profile.XRechnung); // save as version 2.3, profile XRechnung

Configuration

In order to make the xml more readable for humans, you can optionally add comments to the xml file (currently available only in German). If you like to enable these comments, you can use the options builder and pass the resulting options to the Save() command:

InvoiceFormatOptions options = InvoiceOptionsBuilder
.Create()
.EnableXmlComments(true)
.Build();
desc.Save(ms, version, profile, format, options);

This will work with all ZUGFeRD versions and also with XRechnung UBL files.

Another new feature in version 18.0.0 of the library is cleaning of invalid xml characters or throwing an exception when invalid xml characters are found. Can you enable automatic cleaning of xml files using:

InvoiceFormatOptions options = InvoiceOptionsBuilder
.Create()
.AutomaticallyCleanInvalidCharacters()
.Build();
desc.Save(ms, version, profile, format, options);

Otherweise, an exception will be thrown once an invalid character is written to the xml file.

Working with ZUGFeRD PDF files

The PROBIS-ZUGFeRD component has a sister component, PROBIS-ZUGFeRD.PDF, which relies on PDFSharp to read and write PDF files.

Download the package here:

NuGet

The component makes loading the invoice from a pdf as easy as this:

InvoiceDescriptor desc = await InvoicePdfProcessor.LoadFromPdfAsync("invoice.pdf");

// alternatively, you can invoke the function in synchronous manner:
InvoiceDescriptor desc = InvoicePdfProcessor.LoadFromPdf("invoice.pdf");

Converting a PDF file to a ZUGFeRD PDF/A is almost as simple:

InvoiceDescriptor descriptor = InvoiceDescriptor.CreateInvoice("471102", new DateTime(2018, 03, 05), CurrencyCodes.EUR);
// ... fill the descriptor

await InvoicePdfProcessor.SaveToPdfAsync("zugferd-invoice.pdf", ZUGFeRDVersion.Version23, Profile.Comfort, ZUGFeRDFormats.CII, "input-invoice.pdf", descriptor);

// alternatively, you can invoke the function in synchronous manner:
InvoicePdfProcessor.SaveToPdf("zugferd-invoice.pdf", ZUGFeRDVersion.Version23, Profile.Comfort, ZUGFeRDFormats.CII, "input-invoice.pdf", descriptor);

Support for CDAR invoice responses (French "cycle de vie")

The package PROBIS-ZUGFeRD.CDAR reads and writes UN/CEFACT Cross Domain Acknowledgement and Response (CDAR) messages, schema version D22B: the CII-syntax invoice response that the French e-invoicing reform (AFNOR XP Z12-012) uses as lifecycle status message ("cycle de vie", CDV) between platforms, buyers and sellers. Neither ZUGFeRD nor XRechnung define a CDAR profile; the model is schema-complete and the French rules are one profile (CdarProfile.FranceCdvInvoice, or FranceCdvEInvoicingF2 for messages addressed only to the public platform PPF). CdarDescriptor mirrors InvoiceDescriptor: Load, GetVersion, Save, CreateResponse, AddNote, SetSender, AddRecipient, AddAcknowledgement and the same exception types.

Creating a lifecycle message for an invoice

CdarDescriptor.FromInvoice derives everything that is deterministic from the invoice and the status: identification of sender, issuer and recipients, the acknowledgement type (305 transmission phase for 200/201/202/203/213/221, 23 processing phase otherwise), the referenced invoice (number, type, date, seller SIREN), the UNTDID 1373 document status and the French label. Statuses that must be reported to the PPF (200, 210, 212, 213) get the PPF recipient automatically. Reasons, requested actions and amounts are business decisions and are added by the caller:

InvoiceDescriptor invoice = InvoiceDescriptor.Load("F202500003.xml");

// the buyer refuses the invoice
CdarDescriptor cdar = CdarDescriptor.FromInvoice(invoice, InvoiceStatusCodes.Refused, CdarResponder.Buyer,
                                                 issueDateTime: DateTime.Now, documentNo: "F202500003_210_20250702100500");

CdarReferencedDocument doc = cdar.GetPrimaryReferencedDocument();
doc.AddStatusDetail(CdvReasonCodes.TX_TVA_ERR, "Taux de TVA erroné",
                    RequestedActionCodes.NIN, "Créer une facture rectificative");

// the file overload validates the French rules (BR-FR-CDV) first and throws
// MissingDataException / UnsupportedException; Save(Stream) writes without validating
cdar.Save("F202500003_210.xml");

A seller reporting the invoice as collected (212) adds the amount and VAT rate; a platform uses CdarResponder.Platform for the transmission-phase statuses:

CdarDescriptor collected = CdarDescriptor.FromInvoice(invoice, InvoiceStatusCodes.Collected, CdarResponder.Seller);
collected.GetPrimaryReferencedDocument().AddStatusDetail()
         .AddAmountCharacteristic(DocumentCharacteristicTypeCodes.MEN, 12000m, CurrencyCodes.EUR, percent: 20m);

CdarDescriptor deposited = CdarDescriptor.FromInvoice(invoice, InvoiceStatusCodes.Deposited, CdarResponder.Platform,
                                                      receiptDateTime: DateTime.Now);

Recipients take their electronic address from SellerElectronicAddress / BuyerElectronicAddress; a recipient without one does not pass validation (BR-FR-CDV-08). ValidationResult result = CdarValidator.Validate(cdar); lists every violation and warning, with the rule id and the French rule it implements.

Loading a CDAR message

CdarDescriptor cdar = CdarDescriptor.Load("UC2_F202500004_02-CDV-213_Rejetee.xml");
CdarReferencedDocument doc = cdar.GetPrimaryReferencedDocument();
Console.WriteLine($"{doc.ID}: {doc.Status} ({doc.StatusLabels.FirstOrDefault()}), issued by {cdar.Issuer?.RoleCode}");
foreach (CdarDocumentStatus detail in doc.StatusDetails)
{
    Console.WriteLine($"  {detail.ReasonCode}: {string.Join(" ", detail.Reasons)}");
}

Detection is structural: an invoice passed to CdarDescriptor.Load and a CDAR passed to InvoiceDescriptor.Load both throw an UnsupportedException naming the right entry point. A message with a guideline the library has no rules for loads with CdarProfile.Generic. Codes outside the library's enums (statuses agreed bilaterally, roles, scheme identifiers, characteristic types, note subject codes such as AHN) are kept in Raw… properties and round-trip unchanged. Save defaults to CdarProfile.AsLoaded, so loading and saving a message never changes its guideline identifier.

You can find more information about ZUGFeRD here: https://www.ferd-net.de/

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.
  • net10.0

    • No dependencies.

NuGet packages (2)

Showing the top 2 NuGet packages that depend on PROBIS-ZUGFeRD:

Package Downloads
PROBIS-ZUGFeRD.PDF

PROBIS fork of ZUGFeRD-csharp: .NET library for reading and creating ZUGFeRD, Factur-X and XRechnung documents. Derived from ZUGFeRD-csharp by Stephan Stapel / STwo Industries GmbH (Apache-2.0), maintained independently by PROBIS Software GmbH. See NOTICE.txt.

PROBIS-ZUGFeRD.CDAR

PROBIS-ZUGFeRD.CDAR: .NET library for reading and writing UN/CEFACT Cross Domain Acknowledgement and Response (CDAR) messages, the CII invoice response / lifecycle status message used by the French e-invoicing reform (cycle de vie, XP Z12-012). Creates CDAR messages from a PROBIS-ZUGFeRD InvoiceDescriptor. Maintained by PROBIS Software GmbH. See NOTICE.txt.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
19.0.4 86 11/17/2026
19.0.3 120 11/13/2026
19.0.2 96 11/10/2026

19.0.4
New package PROBIS-ZUGFeRD.CDAR: reads and writes UN/CEFACT CDAR (French cycle de vie) invoice response messages and creates them from an InvoiceDescriptor. Core: date formats 203/204, CDAR document detection. See CHANGELOG.md for details