Dear Oasis,
There has been increasing demand from the Finnish state that invoices should include a so called security code which indicates if a certain piece of the invoice should be classified. The Finnish national e-invoicing formats include this information, but as
Peppol uses UBL it is not possible to have this information in a dedicated field in Peppol invoices. Right now the only logical place for this code is in the header level note or invoice line note fields. For future proofing I suggest that UBL 2.5 would include
a dedicated fields for the security code as it is quite important to be able to distinguish this piece of data.
The need comes from a national public procurement data repository that Finland is currently building. It will contain the information from all public sector invoices (
National
Public Procurement Data Repository - Valtiovarainministeriö). As there are some invoices that should not be published fully, we need a way of saying that on the invoice itself. It is foreseen that similar needs will arise from other countries as well.
The demand for a security code in the future is wider than only the invoice. I suggest that you also consider adding the new fields at least to catalogues, orders, despatch advices, waybills and other logistics documents. And the responses to those documents.
They will most likely have a wider usage in the future and not just for government use.
Some examples for different codes:
Data on the invoice xml and the explanation that will not be part of the XML after the -:
SC970050 - Salassa pidettävä, toimittajatieto RU: Sekretessbelagd, leverantör
ENG: Secret, supplier
SC970060
- Salassa pidettävä, toimintayksikkö RU: Sekretessbelagd, verksamhetsenhet
ENG: Secret, operational unit
SC970061 - Salassa pidettävä, sisäisen laskennan seurantakohteet RU: Sekretessbelagd, uppföljningsobjekt i internredovisningen
ENG: Secret, monitoring objects in management accounting
SC97 - Salassa pidettävä, kaikki otsikko- ja tiliöintirivitiedot RU: Sekretessbelagd, alla rubrik- och konteringsradsuppgifter
ENG: Secret, all header and posting line data
SC97E - Salassa pidettävä, HankintatietovarantoL 5 § 2 mom. RU: Sekretessbelagd, Lag om informationsresursen för upphandling 5 § 2 mom.
ENG: Secret, HankintatietovarantoL 5 § 2 mom.
SC98 - TLIV, KÄYTTÖ RAJOITETTU RU: TLIV, BEGRÄNSAD TILLGÅNG
ENG: SC IV, RESTRICTED
SC98E - TLIV, KÄYTTÖ RAJOITETTU, ei hankintatietovarantoon RU: TLIV, BEGRÄNSAD TILLGÅNG, inte till informationsresursen för upp-handling
ENG: SC IV, RESTRICTED, not to the Procurement Data Repository
To conclude:
I suggest that UBL 2.5 would include fields for a security code at least to the invoice header level and on the invoice line level. And also consider adding it to other business and logistics documents and their responses.
It should be a free text field that allows both letters and numbers to accommodate all possible security code systems. Perhaps it would be a good idea to add @schemeID as well.
I am happy to provide any additional information if you want to discuss the suggestion further.
Best regards,
