-
Hallo,
eine XRechnung (2.0) mit dem Validator zu validieren funktioniert. XML wird nicht "beanstandet".
Eine PDF/A3 mit einer einbetteten XRechnung (2.0) zu validieren, endet mit folgender Excepti…
-
data values correct but still errors:?
53.45
281.30
53.45
S
19
VAT
…
-
Impacted versions: 16.x
Steps to reproduce: create UBL Invoice (German XRechnung) and validate it against current standard e.g. here https://erechnungsvalidator.service-bw.de
Current behavior: A…
-
Gemäß der Spezifikation hat BT-17 die Kardinalität 0..1, jedoch wird dies nicht vom Validator geprüft.
[invoice_cefact_2.3.xml.txt](https://github.com/itplr-kosit/validator-configuration-xrechnung/fi…
tzcsx updated
11 months ago
-
After upgrading from Mustang 2.5.1 to 2.7.1 our XRechnung invoices got rejected by the recipient, because XRechnung version 2.3 is already used, even though it's not valid until 2023-08-01. I solved t…
-
### Description
Input files document containing a working text layer (as in pdftotext and a number of GUI tools can access it) are nevertheless sent to ocrmypdf (and failing due to other circumstance…
-
### Objective
In version 2.0.0 these codes were still accepted, in 2.0.1 they are no longer. Ms Ditze can gladly provide details
### Challenges
Considering that such a change can have unexpectedl…
-
Hi there 👋
First of all - fantastic work. Thank you for building this!
Currently, this library is not up to date with new releases of the specification.
The specs for `xrechnung_2.3` and `xrechn…
-
Hello, I have a question,
When I use the UBL Marshaller, the XML is not generated completely; it always gets cut off at line 74. Does anyone know where my mistake is? Here is the code snippet:
```…
-
The visualization files contain a single page-sequence, which contains all content.
This however can lead to very high >2GB memory consumption for large documents with, e.g. many line trade items.
A…