Working Group meeting
Date: 30/05/2024
Participants: Dragos Stoica, Edmund Gray, Giovanni Paolo Selitto
Model editor: Andreea Pasăre
Note editor: Andreea Pasăre
Discussion
-
The invoicing diagram was presented.
-
Replaced epo-inv:hasPaymentTermsDescription with epo-ord:PaymentTerm
-
epo-ord:AccountingCost should be the same in the Order and Invoice; but we can have an Invoice without an Order.
-
The invoice period could start 30 days after the delivery date, depending on the contractual terms.
In the Order data model the Order validity period Business Group represents the Invoicing period Business Group. Are they the same thing, though? To ask Pietro.
Added epo:hasValidityPeriod predicate:
-
Actual delivery date is the date when the supply of goods was made or the supply of services was completed.
Deliver to party name can be a warehouse. We can use locn:locatorName fromd locn:Address
-
LegalRepresentative deals with administrative tasks, and the TaxRepresentative communicates and exchanges info with the fiscal authorities. These are two different roles.
-
The epo:Invoicer role is not required for the eInvoicing core data model. It might be included in an extension of the eInvoicing data model in the future. Maybe it will be used in the Ordering data model.
-
We added SellerTaxRepresentative and Payee roles as specialisations of epo:Offering party.
-
Direct debit Business Group model:
-
Banking identifier is for Seller/Payee.
-
Debited account identifier is for the Buyer.
-
epo-inv:hasInvoicedObjectIdentifier is supplier specific and customised for the Buyer. It is not a CPV code.
-
epo-ord:hasCustomerReference is modelled as a boolean in eOrdering. Ask Pietro if this shouldn’t be a text. It looks like in eOrdering this term was removed from the data model.
-
-
epo-ord:hasCustomerReference is the same as Buyer Reference. Reused this at the level of the Invoice, but not as a boolean.
-
Presenting the diagram:
-
Presenting the diagram for the Invoice totals:
-
VAT Breakdown
-
Summarises what we have in the Invoice Line per each VAT category
-
To be implemented at the level of the Invoice.
-