Working Group Meeting
Date: 08/05/2025
Participants: Natalie Muric, Pietro Palermo
Model editor: Andreea Passare
Note editor: Achilles Dougalis
Discussion
-
The remittance advice and remittance advice amount diagrams were discussed. Both diagrams were based on UBL’s Remittance Advice. Looking at the UBL-RemittanceAdvice-2.4 model, the following assumptions were made for the ePO model:
-
The Accounting Customer is the Buyer.
-
The Accounting Supplier is the Seller.
-
The Payee is the supplier.
-
It was noted that Payee was already modeled for ePO in the eInvoicing module.
-
-
PayerReference: An internal reference to the payer’s order for payment. It was decided that this can be represented as a datatype property at the level of Class epo-pay:RemittanceAdvice:
-
epo-pay:hasPayerReference rdf:Plainliteral [0..1] was added.
-
-
PaymentOrderReference - An internal reference to the order for payment from the payer to the payer’s bank. It was decided that this can be represented as a datatype property at the level of Class epo-pay:RemittanceAdvice:
-
epo-pay:hasPaymentOrderReference rdf:Plainliteral was added.
-
-
InvoicingPartyReference - *An internal reference to the order for payment by the invoicing party. This may have been requested of the payer by the payee to accompany the payer’s remittance. We can drop this since we do not have modeled the Invoicing party on the eInvoicing module. (We just have the buyer and the seller)
-
-
It was mentioned Invoice Period is 0..n in UBL because it may refer to many lines.
-
Billing Reference: A billing document is similar to an invoice. We can use the epo:hasAccountingCost datatype property (on the level of the epo-pay:RemittanceAdvice) for this.
-
It was mentioned that the RemittanceAdvice is a specialization of epo-cat:PostAwardDocument.
-
Predicate epo:isSupportedByForTender linking epo-sub:ESPD to epo:Tender was deleted, because Tender exists in ePO core, and ESPD in eSubmission. In its place, predicate epo-sub:isContainedinTender was created linking epo-sub:ESPD to epo:Tender
-
Class PaymentExecutor was removed from eInvoicing since it was not necessairy.
-
It was noted that the following UBL concepts are not currently needed for ePO:
-
paymentChannelCode
-
InstructionID and InstructionNote
-
PaymentMandate
-
TradeFinancing
-
Tax information
-
-
PaymentID is useful. We need to create this Identifier:
-
Class epo-pay:PaymentInformation was created
-
Predicate epo-pay:hasPaymentIdentifier[0..1] linking to adms:Identifier
-
Attribute epo-pay:hasPaymentDate rdf:PlainLiteral[0..1].
-
A hasPaymentInformation [0..1] predicate was added from RemittanceAdvice to PaymentInformation
-
Predicate epo-pay:hasPaymentMeansInformation was added linking epo-pay:PaymentInformation to epo-inv:PaymentInstructionInformation.
-
-
ServiceLevelCode this is the same as these we have in the eEnvoicing module.
-
It was noted that the RemittanceDocumentDistribution concept is the contact point of the remitance Advice Receiver.
In the end of the WGM the remittance advice CM looked as follows:
In the end of the WGM the remittance advice CM looked as follows:
