Olà Pedro!
I just had a look at PEPPOLâs implementation, and they allow 0..n PaymentMeans:
https://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/tree/
Where do you see that it should be 0..1? The UBL Invoice certainly allows for 0..n PaymentMeans elements. Only the Quotation, SelfBilledInvoice and the RemittanceAdvice documents are restricted to 0..1 PaymentMeans.
The use of the Note that you describe certainly seems like bad practice. The Note is intended to contain textual information for people (not machines) to read. The reason why itâs unbounded is to allow for the same textual content expressed
in several languages.
Atenciosamente,
Kenneth
From:
Pedro Fernandes <pedro.fernandes@ADP.PT>
Date: Friday, November 22, 2019 at 1:40 PM
To: "ubl-dev@lists.oasis-open.org" <ubl-dev@lists.oasis-open.org>
Subject: [ubl-dev] Implementation of EN 16931, CIUS and UBL
Hi all!
I have been trying to implement EU norm EN 16931.
I saw that that EN 16931 changed cardinality of âcac:PaymentMeansâ from [0..*] to [0..1]
I donât understand why this was changed.
Each country has to make itâs own CIUS (Core Invoice Usage Specifications) based on EN 16931.
In Portugal there may be several âPaymentMeansâ.
Portuguese CIUS (CIUS-PT) instruct us to use several âcbc:Noteâ fields to add additional âPaymentMeansâ.
For second and next payment means are like this:
<cbc:Note>#ENTITY@ATMPAYMENT-001#12345#</cbc:Note> <!-- second payment mean -->
<cbc:Note>#REFERENCE@ATMPAYMENT-001#012345678#</cbc:Note> <!-- second payment mean -->
<cbc:Note>#AMOUNT@ATMPAYMENT-001#3264.10#</cbc:Note> <!-- second payment mean -->
<cbc:Note>#DESCRIPTION@ATMPAYMENT-001#Valor total do documento, mais valores em atraso (extrato)#</cbc:Note> <!-- second payment mean -->
This doesnât make sense to me.
I really would appreciate some light on the matter.
Best regards
Pedro Fernandes
DireÃÃo de Sistemas de InformaÃÃo
Rua Visconde de Seabra 3 | 1700-421 Lisboa | Tel: 212 469 549 (10549) | Fax: 212 469 541 | http://www.adp.pt
Tenha uma EcoAtitude. Imprima este e-mail
apenas se necessÃrio.
Esta mensagem e os ficheiros anexos podem conter informaÃÃo confidencial ou reservada. Se, por engano, receber esta mensagem, solicita-se que informe
de imediato o remetente e que elimine a mensagem e ficheiros anexos sem os reproduzir.
This message and any files herewith attached may contain confidential or privileged information. If you receive this message in error, please notify us immediately and delete this message and any files attached without copying them in any way.