- SDK members
- FillZUGFeRD_Structure() ValidateInvoicePDF() ValidationReport
- Business terms
- BT-29 Seller identifier BT-46 Buyer identifier BT-157 Item standard identifier BT-24 Specification identifier BT-120 VAT exemption reason text BT-121 VAT exemption reason code
- Code samples
- VB.NET
- Published
Many companies have introduced e-invoicing: the normal invoice with 19 % VAT is created as ZUGFeRD or XRechnung and passes validation. The project is then often considered finished. The work, however, sits in the cases next to it – and those are still handled by hand.
In short: The standard case is rarely the problem. Manual work arises in special cases: a customer requires fields the ERP does not write, a recipient accepts only one format, VAT exemptions trigger warnings, final invoices and corrections do not fit the pattern, and incoming invoices are typed in instead of read. Each of these cases can be automated with the Aloaha ZUGFeRD SDK – without replacing the ERP.
The standard case is not the problem
One VAT rate, no discount, a domestic customer: almost every system can do that today. If you test only this case, you get a green tick and a wrong picture. The questions our support receives show where things get stuck in daily work – almost never in the standard case.
Where the manual work really is
| Special case | What often happens today | How to automate it |
|---|---|---|
| A customer requires additional fields: GLN, GTIN, order number | Accounting opens every invoice and adds the values. | Read the finished ERP invoice, add the fields, validate, merge again: adding GLN and GTIN (German) |
| A recipient accepts only XRechnung or only EN 16931 | The invoice is rejected and created again by hand. | Define the format per recipient: XRechnung or ZUGFeRD? and EN 16931 despite EXTENDED fields (German) |
| Reverse charge, intra-community supply, export | The validator warns and someone searches for the error. | Put exemption reason and code in the right place: exemption reason on line level (German) |
| Partial and final invoices | Final invoices are sent as a PDF without valid data. | Final invoice with partial invoices (German) |
| Corrections and credit notes | The correction is treated like a new invoice; the reference is missing. | Corrected invoice and credit note (German) |
| Incoming invoices | The XML data is there, yet the invoice is typed in from the screen. | Validate and read on receipt: validating e-invoices with the SDK |
| Invoice from a new sender | Nobody checks sender and bank details before paying. | Compare the data with your master data: genuine or phishing? (German) |
Five questions for a self-check
- How many outgoing invoices does someone still touch after the ERP, before they are sent?
- How many invoices come back from the recipient because format or fields do not fit?
- Is every outgoing invoice validated automatically before sending – or only by the customer?
- How many incoming invoices are typed in although they arrive as e-invoices?
- Which invoice types are not e-invoices at all yet: final invoices, credit notes, invoices from side systems?
If you do not know these numbers, you do not know your automation rate. A one-week tally is usually enough to find the three most expensive special cases.
What automation looks like
The SDK is a library for .NET and COM. It runs locally next to your ERP, also as a service on a server, and takes over the steps someone otherwise does by hand:
- Incoming: validate every e-invoice, read the data and pass it to accounting. Deviations in VAT ID or IBAN show up immediately.
- Outgoing: add customer fields to ERP invoices without changing the ERP.
- Validation before sending: check every invoice against EN 16931 or XRechnung. Only valid invoices go out.
- Special types: create partial, final and corrected invoices with the same calls as the standard invoice.
' VB.NET – validate and read an incoming invoice
Dim key As String = "YOUR-LICENCE-KEY"
Dim alo As New Aloaha_ZUGFeRD.XML(key)
If alo.ValidateInvoicePDF("C:\Inbox\INV-4711.pdf") = False Then
' rejected: store the report, send the invoice to clarification
System.IO.File.WriteAllText("C:\Clarify\INV-4711.txt", alo.ValidationReport)
ElseIf alo.FillZUGFeRD_Structure("C:\Inbox\INV-4711.pdf", key) Then
' valid: the data is available and goes to accounting without retyping
End If
Validation runs locally; the invoice data does not leave your premises.
Why it pays off now
From 1 January 2027, German companies with a prior-year turnover above EUR 800,000 must issue their domestic B2B invoices as e-invoices, from 2028 all companies. After that there is no way around the special cases via paper or a plain PDF.
Then comes reporting to the tax authorities. According to the current timetable, the EU introduces digital reporting of cross-border B2B transactions on 1 July 2030 (ViDA). A national reporting system for domestic transactions is planned in Germany but not yet decided. One thing is certain: reporting will be fed from invoice data. What is corrected by hand today will have to be right by itself.
And the two or three cases a month?
Not every special case is worth automating. For a few invoices a month there is the Aloaha ZUGFeRD GUI: load the invoice, add fields, validate, merge with the PDF. As soon as the same step is needed every week, the SDK is the better way. A free trial licence is available from info@aloaha.com; prices are listed under licences & prices.
Frequently asked questions
We already create e-invoices. Why is the topic not finished?
Because usually only the standard case is automated. Special cases such as customer fields, VAT exemptions, final invoices, corrections and incoming checks are often still handled by hand.
Do we have to replace our ERP to automate the special cases?
No. The Aloaha ZUGFeRD SDK reads the finished ERP invoice, adds to it or validates it and writes it out again. It runs next to the ERP, also as a service on a server.
How do I measure my automation rate?
Count for one week how many outgoing invoices are still touched after the ERP, how many come back from recipients and how many incoming invoices are typed in.
From when must all German companies issue e-invoices?
From 1 January 2027 companies with a prior-year turnover above EUR 800,000, from 1 January 2028 all domestic companies for domestic B2B transactions. Everyone has had to be able to receive them since 2025.
Will Germany get a reporting system for invoice data?
It is planned but not yet decided. The EU starts digital reporting of cross-border B2B transactions on 1 July 2030 according to the current timetable.
Is the SDK worth it for only a few special cases?
For two or three invoices a month the Aloaha ZUGFeRD GUI is enough. For recurring cases the SDK saves the manual work and avoids typing errors.
Business terms in this article: BT-29 BT-46 BT-157 BT-24 BT-120 BT-121