[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (UBL-138) bringing UBL "billing" documents in sync
Kees Duvekot created UBL-138: -------------------------------- Summary: bringing UBL "billing" documents in sync Key: UBL-138 URL: https://issues.oasis-open.org/browse/UBL-138 Project: OASIS Universal Business Language (UBL) TC Issue Type: Improvement Reporter: Kees Duvekot Assignee: Ken Holman All, As part of the analysis of tickets UBL-44, UBL-60 and UBL-137 I have looked at all the billing documents in UBL and see where they are “not in sync” with each other. I have looked at the following billing documents: Invoice CreditNote SelfBilledInvoice SelfBilledCreditNote FreightInvoice I have done a comparison of the various UBL elements that are in these documents on “header level”. This is the result: cbc:DueDate This is only available in Invoice, and not in the other documents. As part of bringing all billing documents in sync I would propose to add this the the 4 other billing documents (preferably at the same “position” as invoice) cbc:InvoiceTypeCode / cbc:CreditNoteTypeCode In all documents except SelfBilledCreditNote there is a “TypeCode” element. I would propose to add the cbc:CreditNoteTypeCode to the SelfBilledCreditNote to bring it in line with the normal CreditNote Document. cbc:BuyerReference This element is available in Invoice and CreditNote, but not in the SelfBilled equivalents. I would propose to add this to both SelfBilledInvoice and SelfBilledCreditNote I would NOT include It in the FreightInvoice to avoid confusion about “Buyer” in the FreightInvoice context. cac:DiscrepancyResponse This element is available in both the CreditNote and SelfBilledCreditNote, not in the other documents I would propose to leave this .. because this is a specific element that is only relevant in the CreditNote context as far as I can tell. cac:Shipment This element is only available in the FreightInvoice, and is the only real element that is different with a “normal” invoice. I would NOT add this to the other documents to keep the separate status of FreightInvoice. cac:StatementDocumentReference This element is missing from the FreightInvoice. As far as I can tell the statements can not be used for “Freight” purpuses .. so not having this on the FreightInvoice makes sense cac:ProjectReference This element is only available in the Invoice, not in the other 4 billing documents. I would propose to add this element also to all the other billing documents. cac:BuyerCustomerParty / cac:SellerSupplierParty These two element are not available in the FreightInvoice It makes sense that they are NOT in the freightInvoice, but what would be the equivalants for Freight? Based on TransportExecutionPlan(Request)Type I would think TransportUserParty / TransportServiceProviderParty but I would leave that discussion for 2.3 cac:Delivery / cac:DeliveryTerms These elements are not available in the FreighInvoice I would NOT add them to FreightInvoice, as that they are really “Ordering” related cac:PrepaidPayment This element is not available in the CreditNote and SelfBilledCreditNote But it makes sense that it is NOT there, because prepaying your credit … that does not make sense at all cac:WithholdingTaxTotal This element is only available in the Invoice not in the other documents I would propose that we also add this to all the other elements to bring the WithHoldingTax handling on all documents in line with each other. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]