-
Hi guys,
I heard that validation artefacts are close to ready. I would like to add them on peppol.helger.com as well, so any release would be appreciated :)
// Philip
-
Due to a previous remark on alternatives for ChargeIndicator – true/false and 1/0 respectively – a change was made in favour of true/false to be the only option. This may be fine, but I have one conse…
-
With the SI UBL 2.0 RC1 schematron we get alot of errors due to rule BR-NL-2:
```
[BR-NL-2] For suppliers in the Netherlands, the invoice MUST contain either the buyer reference (cbc:BuyerReference)…
-
`01.15a-INVOICE_uncefact.xml` beinaltet:
```xml
DE123456789
```
das führt beim validieren zu Fehlern:
Referenz: 01.15a-INVOICE_uncef…
-
Lenke til Behov:
https://github.com/Informasjonsforvaltning/behov/issues/124
As: a system user (another system used in the PoCs)
I wish: to create an business transaction entry based on eInvoices…
-
- [x] investigate whether there is a content type we can use
- [x] is it a purchase or a sales invoice?
- [x] create mapping from document type to documents
- [x] create tests
-
We've seen some issues with the calculations made in invoice lines, by softwarevendors that generate UBL invoices.
Here's an interesting fragment, that is OK according to the current schematron val…
-
-
The binding of EN to UBL carries over too few of the rules in the norm, regarding the naming principles. This applies also to the distinction between the seller’s and the tax representative’s respecti…
-
A lot of the UBL syntax rules (examples: UBL-CR-001, UBL-SR-01, UBL-SR-47) only have the ubl:Invoice as context, most of these should be valid for credit note as well I assume?