UBL Transportation SC

Hello PSC and TSC, In the UBL 2.1 PRD1 documentation it says: New document types expected for PRD2 GoodsItemItinerary TransportServiceDescription CatalogueTemplate VirtualCompanyDossier And also I have email from early 2010 to the effect that CPFR wants to add PurchaseConditions Two questions. 1. Is this list of five new document types correct and exhaustive? 2. Which doctypes go under which category? Current categories of new 2.1 doctypes include: eTendering CPFR Sales reporting / VMI Intermodal Freight Management Utility billing Jon

Title: [ubl-tsc] UBL document types to be added in PRD2 Hello Jon, In answer to your questions, GII and TSD are new document types for Intermodal Freight Management. I don’t believe that are any other for transport.. Regards, Andy     From: Jon Bosak [mailto:bosak@pinax.com] Sent: Friday, January 07, 2011 2:23 PM To: ubl-psc@lists.oasis-open.org; ubl-tsc@lists.oasis-open.org Subject: [ubl-tsc] UBL document types to be added in PRD2   Hello PSC and TSC, In the UBL 2.1 PRD1 documentation it says:     New document types expected for PRD2        GoodsItemItinerary        TransportServiceDescription        CatalogueTemplate        VirtualCompanyDossier And also I have email from early 2010 to the effect that CPFR wants to add        PurchaseConditions Two questions. 1. Is this list of five new document types correct and exhaustive? 2. Which doctypes go under which category?  Current categories of     new 2.1 doctypes include:     eTendering     CPFR     Sales reporting / VMI     Intermodal Freight Management     Utility billing Jon --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1191 / Virus Database: 1435/3365 - Release Date: 01/07/11

Title: [ubl-tsc] UBL document types to be added in PRD2 Hello Jon, In answer to your questions, GII and TSD are new document types for Intermodal Freight Management. I don’t believe that are any other for transport.. Regards, Andy     From: Jon Bosak [mailto:bosak@pinax.com] Sent: Friday, January 07, 2011 2:23 PM To: ubl-psc@lists.oasis-open.org; ubl-tsc@lists.oasis-open.org Subject: [ubl-tsc] UBL document types to be added in PRD2   Hello PSC and TSC, In the UBL 2.1 PRD1 documentation it says:     New document types expected for PRD2        GoodsItemItinerary        TransportServiceDescription        CatalogueTemplate        VirtualCompanyDossier And also I have email from early 2010 to the effect that CPFR wants to add        PurchaseConditions Two questions. 1. Is this list of five new document types correct and exhaustive? 2. Which doctypes go under which category?  Current categories of     new 2.1 doctypes include:     eTendering     CPFR     Sales reporting / VMI     Intermodal Freight Management     Utility billing Jon --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1191 / Virus Database: 1435/3365 - Release Date: 01/07/11

Hi Jon, these are document types related to eTendering: CatalogueTemplate VirtualCompanyDossier PurchaseConditions is a more generic document type into eProcurement, thus it does not seem to be limited to CPFR. PurchaseConditions are often a standardized set of conditions of a Buyer that are presented to each Vendor. A Vendor is usually requested to sign such purchase conditions as part of the quotation phase or later. Hope this helps, Cheers, Roberto > Hello PSC and TSC, > > In the UBL 2.1 PRD1 documentation it says: > > New document types expected for PRD2 > > GoodsItemItinerary > TransportServiceDescription > CatalogueTemplate > VirtualCompanyDossier > > And also I have email from early 2010 to the effect that CPFR > wants to add > > PurchaseConditions > > Two questions. > > 1. Is this list of five new document types correct and exhaustive? > > 2. Which doctypes go under which category? Current categories of > new 2.1 doctypes include: > > eTendering > CPFR > Sales reporting / VMI > Intermodal Freight Management > Utility billing > > Jon > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > -- * JAVEST by Roberto Cisternino * * Document Engineering Services Ltd. - Alliance Member * UBL Italian Localization SubCommittee (ITLSC), co-Chair * UBL Online Community editorial board member (ubl.xml.org) * Italian UBL Advisor Roberto Cisternino mobile: +39 328 2148123 skype: roberto.cisternino.ubl-itlsc [UBL Technical Committee] http://www.oasis-open.org/committees/ubl [UBL Online Community] http://ubl.xml.org [UBL International Conferences] http://www.ublconference.org [UBL Italian Localization Subcommittee] http://www.oasis-open.org/committees/ubl-itlsc [Iniziativa divulgativa UBL Italia] http://www.ubl-italia.org

Hi Jon, these are document types related to eTendering: CatalogueTemplate VirtualCompanyDossier PurchaseConditions is a more generic document type into eProcurement, thus it does not seem to be limited to CPFR. PurchaseConditions are often a standardized set of conditions of a Buyer that are presented to each Vendor. A Vendor is usually requested to sign such purchase conditions as part of the quotation phase or later. Hope this helps, Cheers, Roberto > Hello PSC and TSC, > > In the UBL 2.1 PRD1 documentation it says: > > New document types expected for PRD2 > > GoodsItemItinerary > TransportServiceDescription > CatalogueTemplate > VirtualCompanyDossier > > And also I have email from early 2010 to the effect that CPFR > wants to add > > PurchaseConditions > > Two questions. > > 1. Is this list of five new document types correct and exhaustive? > > 2. Which doctypes go under which category? Current categories of > new 2.1 doctypes include: > > eTendering > CPFR > Sales reporting / VMI > Intermodal Freight Management > Utility billing > > Jon > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > -- * JAVEST by Roberto Cisternino * * Document Engineering Services Ltd. - Alliance Member * UBL Italian Localization SubCommittee (ITLSC), co-Chair * UBL Online Community editorial board member (ubl.xml.org) * Italian UBL Advisor Roberto Cisternino mobile: +39 328 2148123 skype: roberto.cisternino.ubl-itlsc [UBL Technical Committee] http://www.oasis-open.org/committees/ubl [UBL Online Community] http://ubl.xml.org [UBL International Conferences] http://www.ublconference.org [UBL Italian Localization Subcommittee] http://www.oasis-open.org/committees/ubl-itlsc [Iniziativa divulgativa UBL Italia] http://www.ubl-italia.org

Hi all, Regarding the VirtualCompanyDossier, there is a work on BII2 of merging the TendererQualification data model with the VirtualCompanyDossier data model. I think we should not create more confusion creating two separate XSD for the same purpose but follow-up on the conclusions of BII eTendering group and add the requirements for the VCD into the TendererQualification creating a single document model. I do not know the time frame to add changes into the TendererQualification, but I think we should try to cover all the requirements with a single document model. Regards, Oriol El 12/01/2011, a las 09:28, Roberto Cisternino escribió: > Hi Jon, > > these are document types related to eTendering: > > CatalogueTemplate > VirtualCompanyDossier > > PurchaseConditions is a more generic document type into eProcurement, thus > it does not seem to be limited to CPFR. > > PurchaseConditions are often a standardized set of conditions of a Buyer > that are presented to each Vendor. A Vendor is usually requested to sign > such purchase conditions as part of the quotation phase or later. > > Hope this helps, > > Cheers, > > Roberto > >> Hello PSC and TSC, >> >> In the UBL 2.1 PRD1 documentation it says: >> >> New document types expected for PRD2 >> >> GoodsItemItinerary >> TransportServiceDescription >> CatalogueTemplate >> VirtualCompanyDossier >> >> And also I have email from early 2010 to the effect that CPFR >> wants to add >> >> PurchaseConditions >> >> Two questions. >> >> 1. Is this list of five new document types correct and exhaustive? >> >> 2. Which doctypes go under which category? Current categories of >> new 2.1 doctypes include: >> >> eTendering >> CPFR >> Sales reporting / VMI >> Intermodal Freight Management >> Utility billing >> >> Jon >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> >> > > > -- > * JAVEST by Roberto Cisternino > * > * Document Engineering Services Ltd. - Alliance Member > * UBL Italian Localization SubCommittee (ITLSC), co-Chair > * UBL Online Community editorial board member (ubl.xml.org) > * Italian UBL Advisor > > Roberto Cisternino > > mobile: +39 328 2148123 > skype: roberto.cisternino.ubl-itlsc > > [UBL Technical Committee] > http://www.oasis-open.org/committees/ubl > > [UBL Online Community] > http://ubl.xml.org > > [UBL International Conferences] > http://www.ublconference.org > > [UBL Italian Localization Subcommittee] > http://www.oasis-open.org/committees/ubl-itlsc > > [Iniziativa divulgativa UBL Italia] > http://www.ubl-italia.org > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >

Does this mean, that you are suggesting to postpone the issue for the next review? /Peter -----Oprindelig meddelelse----- Fra: Oriol Bausà Peris [ mailto:oriol@invinet.org ] Sendt: 12. januar 2011 12:25 Til: roberto@javest.com Cc: Jon Bosak; ubl-psc@lists.oasis-open.org; ubl-tsc@lists.oasis-open.org Emne: [ubl-psc] Re: [ubl-tsc] Re: [ubl-psc] UBL document types to be added in PRD2 Hi all, Regarding the VirtualCompanyDossier, there is a work on BII2 of merging the TendererQualification data model with the VirtualCompanyDossier data model. I think we should not create more confusion creating two separate XSD for the same purpose but follow-up on the conclusions of BII eTendering group and add the requirements for the VCD into the TendererQualification creating a single document model. I do not know the time frame to add changes into the TendererQualification, but I think we should try to cover all the requirements with a single document model. Regards, Oriol El 12/01/2011, a las 09:28, Roberto Cisternino escribió: > Hi Jon, > > these are document types related to eTendering: > > CatalogueTemplate > VirtualCompanyDossier > > PurchaseConditions is a more generic document type into eProcurement, thus > it does not seem to be limited to CPFR. > > PurchaseConditions are often a standardized set of conditions of a Buyer > that are presented to each Vendor. A Vendor is usually requested to sign > such purchase conditions as part of the quotation phase or later. > > Hope this helps, > > Cheers, > > Roberto > >> Hello PSC and TSC, >> >> In the UBL 2.1 PRD1 documentation it says: >> >> New document types expected for PRD2 >> >> GoodsItemItinerary >> TransportServiceDescription >> CatalogueTemplate >> VirtualCompanyDossier >> >> And also I have email from early 2010 to the effect that CPFR >> wants to add >> >> PurchaseConditions >> >> Two questions. >> >> 1. Is this list of five new document types correct and exhaustive? >> >> 2. Which doctypes go under which category? Current categories of >> new 2.1 doctypes include: >> >> eTendering >> CPFR >> Sales reporting / VMI >> Intermodal Freight Management >> Utility billing >> >> Jon >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> >> > > > -- > * JAVEST by Roberto Cisternino > * > * Document Engineering Services Ltd. - Alliance Member > * UBL Italian Localization SubCommittee (ITLSC), co-Chair > * UBL Online Community editorial board member (ubl.xml.org) > * Italian UBL Advisor > > Roberto Cisternino > > mobile: +39 328 2148123 > skype: roberto.cisternino.ubl-itlsc > > [UBL Technical Committee] > http://www.oasis-open.org/committees/ubl > > [UBL Online Community] > http://ubl.xml.org > > [UBL International Conferences] > http://www.ublconference.org > > [UBL Italian Localization Subcommittee] > http://www.oasis-open.org/committees/ubl-itlsc > > [Iniziativa divulgativa UBL Italia] > http://www.ubl-italia.org > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.872 / Virus Database: 271.1.1/3372 - Release Date: 01/11/11 20:34:00

Hi all, I agree with Oriol ... furthermore, also Peppol WP2 is working on VCD. In any case, I have a question: do we have a data model for VCD? Best regards Arianna Il 12/01/2011 12:25, Oriol Bausà Peris ha scritto: > Hi all, > > Regarding the VirtualCompanyDossier, there is a work on BII2 of merging the TendererQualification data model with the VirtualCompanyDossier data model. I think we should not create more confusion creating two separate XSD for the same purpose but follow-up on the conclusions of BII eTendering group and add the requirements for the VCD into the TendererQualification creating a single document model. I do not know the time frame to add changes into the TendererQualification, but I think we should try to cover all the requirements with a single document model. > > Regards, Oriol > > El 12/01/2011, a las 09:28, Roberto Cisternino escribió: > > >> Hi Jon, >> >> these are document types related to eTendering: >> >> CatalogueTemplate >> VirtualCompanyDossier >> >> PurchaseConditions is a more generic document type into eProcurement, thus >> it does not seem to be limited to CPFR. >> >> PurchaseConditions are often a standardized set of conditions of a Buyer >> that are presented to each Vendor. A Vendor is usually requested to sign >> such purchase conditions as part of the quotation phase or later. >> >> Hope this helps, >> >> Cheers, >> >> Roberto >> >> >>> Hello PSC and TSC, >>> >>> In the UBL 2.1 PRD1 documentation it says: >>> >>> New document types expected for PRD2 >>> >>> GoodsItemItinerary >>> TransportServiceDescription >>> CatalogueTemplate >>> VirtualCompanyDossier >>> >>> And also I have email from early 2010 to the effect that CPFR >>> wants to add >>> >>> PurchaseConditions >>> >>> Two questions. >>> >>> 1. Is this list of five new document types correct and exhaustive? >>> >>> 2. Which doctypes go under which category? Current categories of >>> new 2.1 doctypes include: >>> >>> eTendering >>> CPFR >>> Sales reporting / VMI >>> Intermodal Freight Management >>> Utility billing >>> >>> Jon >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this mail list, you must leave the OASIS TC that >>> generates this mail. Follow this link to all your TCs in OASIS at: >>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >>> >>> >>> >> >> -- >> * JAVEST by Roberto Cisternino >> * >> * Document Engineering Services Ltd. - Alliance Member >> * UBL Italian Localization SubCommittee (ITLSC), co-Chair >> * UBL Online Community editorial board member (ubl.xml.org) >> * Italian UBL Advisor >> >> Roberto Cisternino >> >> mobile: +39 328 2148123 >> skype: roberto.cisternino.ubl-itlsc >> >> [UBL Technical Committee] >> http://www.oasis-open.org/committees/ubl >> >> [UBL Online Community] >> http://ubl.xml.org >> >> [UBL International Conferences] >> http://www.ublconference.org >> >> [UBL Italian Localization Subcommittee] >> http://www.oasis-open.org/committees/ubl-itlsc >> >> [Iniziativa divulgativa UBL Italia] >> http://www.ubl-italia.org >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> >> > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > >

Thanks to Roberto and Oriol for the info. This raises the question of where PSC is in its work right now. We have been expecting delivery of updated data models around the end of this month; are we still on schedule for that? Will there be a meeting soon to address the issue raised by Oriol? If this is something that will take a while to resolve, we should probably try to wrap up PRD2 (in a way that does not block possibilities still on the table) and aim for a final decision in PRD3. Jon Oriol Bausà Peris wrote: > Hi all, > > Regarding the VirtualCompanyDossier, there is a work on BII2 of merging the TendererQualification data model with the VirtualCompanyDossier data model. I think we should not create more confusion creating two separate XSD for the same purpose but follow-up on the conclusions of BII eTendering group and add the requirements for the VCD into the TendererQualification creating a single document model. I do not know the time frame to add changes into the TendererQualification, but I think we should try to cover all the requirements with a single document model. > > Regards, Oriol > > El 12/01/2011, a las 09:28, Roberto Cisternino escribió: > >> Hi Jon, >> >> these are document types related to eTendering: >> >> CatalogueTemplate >> VirtualCompanyDossier >> >> PurchaseConditions is a more generic document type into eProcurement, thus >> it does not seem to be limited to CPFR. >> >> PurchaseConditions are often a standardized set of conditions of a Buyer >> that are presented to each Vendor. A Vendor is usually requested to sign >> such purchase conditions as part of the quotation phase or later. >> >> Hope this helps, >> >> Cheers, >> >> Roberto

Dear Jon I have been very buzy developing my business the past month. We had a meeting before Christmas, but only Arianna and Sven showed up. I am planning to have a skype meeting with Tim to get an overview of how to finish the last bits. Best regards Peter -----Oprindelig meddelelse----- Fra: Jon Bosak [ mailto:bosak@pinax.com ] Sendt: 12. januar 2011 15:00 Til: Oriol Bausà Peris Cc: roberto@javest.com; ubl-psc@lists.oasis-open.org Emne: [ubl-psc] PSC schedule (was: Re: [ubl-psc] Re: [ubl-tsc] Re: [ubl-psc] UBL document types to be added in PRD2) Thanks to Roberto and Oriol for the info. This raises the question of where PSC is in its work right now. We have been expecting delivery of updated data models around the end of this month; are we still on schedule for that? Will there be a meeting soon to address the issue raised by Oriol? If this is something that will take a while to resolve, we should probably try to wrap up PRD2 (in a way that does not block possibilities still on the table) and aim for a final decision in PRD3. Jon Oriol Bausà Peris wrote: > Hi all, > > Regarding the VirtualCompanyDossier, there is a work on BII2 of merging the TendererQualification data model with the VirtualCompanyDossier data model. I think we should not create more confusion creating two separate XSD for the same purpose but follow-up on the conclusions of BII eTendering group and add the requirements for the VCD into the TendererQualification creating a single document model. I do not know the time frame to add changes into the TendererQualification, but I think we should try to cover all the requirements with a single document model. > > Regards, Oriol > > El 12/01/2011, a las 09:28, Roberto Cisternino escribió: > >> Hi Jon, >> >> these are document types related to eTendering: >> >> CatalogueTemplate >> VirtualCompanyDossier >> >> PurchaseConditions is a more generic document type into eProcurement, thus >> it does not seem to be limited to CPFR. >> >> PurchaseConditions are often a standardized set of conditions of a Buyer >> that are presented to each Vendor. A Vendor is usually requested to sign >> such purchase conditions as part of the quotation phase or later. >> >> Hope this helps, >> >> Cheers, >> >> Roberto --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.872 / Virus Database: 271.1.1/3372 - Release Date: 01/11/11 20:34:00

BII eTendering group is going to discuss this issue during this month. I would suggest not including the VirtualCompanyDossier and wait to publish a final release in PRD3 with a data model taking into account requirements from BII as a whole (Qualification + VCD). Best regards, Oriol El 12/01/2011, a las 14:59, Jon Bosak escribió: > Thanks to Roberto and Oriol for the info. > > This raises the question of where PSC is in its work right now. > We have been expecting delivery of updated data models around the > end of this month; are we still on schedule for that? > > Will there be a meeting soon to address the issue raised by Oriol? > If this is something that will take a while to resolve, we should > probably try to wrap up PRD2 (in a way that does not block > possibilities still on the table) and aim for a final decision in > PRD3. > > Jon > > Oriol Bausà Peris wrote: >> Hi all, >> Regarding the VirtualCompanyDossier, there is a work on BII2 of merging the TendererQualification data model with the VirtualCompanyDossier data model. I think we should not create more confusion creating two separate XSD for the same purpose but follow-up on the conclusions of BII eTendering group and add the requirements for the VCD into the TendererQualification creating a single document model. I do not know the time frame to add changes into the TendererQualification, but I think we should try to cover all the requirements with a single document model. >> Regards, Oriol >> El 12/01/2011, a las 09:28, Roberto Cisternino escribió: >>> Hi Jon, >>> >>> these are document types related to eTendering: >>> >>> CatalogueTemplate >>> VirtualCompanyDossier >>> >>> PurchaseConditions is a more generic document type into eProcurement, thus >>> it does not seem to be limited to CPFR. >>> >>> PurchaseConditions are often a standardized set of conditions of a Buyer >>> that are presented to each Vendor. A Vendor is usually requested to sign >>> such purchase conditions as part of the quotation phase or later. >>> >>> Hope this helps, >>> >>> Cheers, >>> >>> Roberto

OK, folks, here's my current understanding of where we are with additions for PRD2. New transportation doctypes: GoodsItemItinerary TransportServiceDescription New etendering doctypes: CatalogueTemplate Originally raised by CPFR but (according to Roberto) usable in a number of eprocurement contexts: PurchaseConditions That makes four additional schemas for a total of 64 in PRD2. The list originally included VirtualCompanyDossier, but regarding this, Oriol said: Regarding the VirtualCompanyDossier, there is a work on BII2 of merging the TendererQualification data model with the VirtualCompanyDossier data model. I think we should not create more confusion creating two separate XSD for the same purpose but follow-up on the conclusions of BII eTendering group and add the requirements for the VCD into the TendererQualification creating a single document model. I do not know the time frame to add changes into the TendererQualification, but I think we should try to cover all the requirements with a single document model. To which Arianna replied: I agree with Oriol ... furthermore, also Peppol WP2 is working on VCD. In any case, I have a question: do we have a data model for VCD? And Oriol remarked: BII eTendering group is going to discuss this issue during this month. I would suggest not including the VirtualCompanyDossier and wait to publish a final release in PRD3 with a data model taking into account requirements from BII as a whole (Qualification + VCD). Unless someone has an objection, I am going to take this as our plan for the moment. We will revisit this in PRD3 to see whether a separate VCD document type is needed. Jon

OK, folks, here's my current understanding of where we are with additions for PRD2. New transportation doctypes: GoodsItemItinerary TransportServiceDescription New etendering doctypes: CatalogueTemplate Originally raised by CPFR but (according to Roberto) usable in a number of eprocurement contexts: PurchaseConditions That makes four additional schemas for a total of 64 in PRD2. The list originally included VirtualCompanyDossier, but regarding this, Oriol said: Regarding the VirtualCompanyDossier, there is a work on BII2 of merging the TendererQualification data model with the VirtualCompanyDossier data model. I think we should not create more confusion creating two separate XSD for the same purpose but follow-up on the conclusions of BII eTendering group and add the requirements for the VCD into the TendererQualification creating a single document model. I do not know the time frame to add changes into the TendererQualification, but I think we should try to cover all the requirements with a single document model. To which Arianna replied: I agree with Oriol ... furthermore, also Peppol WP2 is working on VCD. In any case, I have a question: do we have a data model for VCD? And Oriol remarked: BII eTendering group is going to discuss this issue during this month. I would suggest not including the VirtualCompanyDossier and wait to publish a final release in PRD3 with a data model taking into account requirements from BII as a whole (Qualification + VCD). Unless someone has an objection, I am going to take this as our plan for the moment. We will revisit this in PRD3 to see whether a separate VCD document type is needed. Jon

Hello PSC, I recently discussed with Oriol Bausà the need to revive an old issue about the "Withholding Tax" because we found this use case is not well supported by UBL 2.1 as we initially believed. The "Withholding Tax" information has a different behaviour and meaning from goods/service and VAT taxes. It is a tax related to the personal income of the invoicer (usually a soleproprietorship or freelance) that is calculated in percentage on the taxable amounts (for such kind of tax), but is paid to the Government by the Invoicee (Customer). The Withholding Tax is applied just to certain line items (usually expenses like transport, hotel are excluded) As the Withholding Tax is not always applicable to the whole Invoice taxable amounts, it "could" be useful to present a separated taxable amount for it, but this information can be calculated. From the VAT point of view (the main Invoice purpose) the "Total Due Amount" of an invoice (aka. Payable Amount) is NOT including any "Withholding Tax". The "Withholding Tax" is however a component of the Invoice Total just like "Prepaid Amount", but is not payable to the Invoicer/Supplier (as explained before). On paper invoices the "Withholding Tax" total is also provided separately from other totals, as this amount is important to be presented to the Invoicee (Customer) who is requested by the Government to pay on behalf of the Invoicer. The full Withholding Tax concept is available here: http://en.wikipedia.org/wiki/Withholding_tax Finally I provide a set of improvements required to support this case: 1) Add a new ABIE named "WithholdingTaxTotal" after the "TaxTotal" 2) Add the new "WithholdingTaxTotal" ABIE under the cac:InvoiceLine after the "TaxTotal" (this will be used to identify those line items subject to withholding tax) The proposed definition for WithholdingTaxTotal is: "An association to Withholding Tax Total." For the purpose of evaluating and understanding this important requirement I attach a real invoice where the withholding tax is applied, but not VAT. The sample is also useful to see how the withholding tax data is presented separately from VAT amounts. The invoice is provided either in English and italian. Best regards Roberto -- * JAVEST CEO * * Document Engineering Services Ltd. - Alliance Member * UBL Italian Localization SubCommittee (ITLSC), co-Chair * UBL Online Community editorial board member (ubl.xml.org) * Italian UBL Advisor Roberto Cisternino mobile: +39 328 2148123 skype: roberto.cisternino.ubl-itlsc [UBL Technical Committee] http://www.oasis-open.org/committees/ubl [UBL Online Community] http://ubl.xml.org [UBL International Conferences] http://www.ublconference.org [UBL Italian Localization Subcommittee] http://www.oasis-open.org/committees/ubl-itlsc [Iniziativa divulgativa UBL Italia] http://www.ubl-italia.org Invoice-WithholdingTax.JPG

on first impression I think this is not the way to go.  the principle of UBL tax structures is that they are not based on specific types of taxes. we recognize consumption taxes (such as VAT) and sales taxes (used in US, etc.) but  need to keep the models  independent. So is it that we need to specify a payable total that does not include certain taxes? On 4/03/2011 10:37 PM, Roberto Cisternino wrote: 49570.62.110.96.182.1299249473.squirrel@mail.javest.com type= cite > Hello PSC, I recently discussed with Oriol Bausà the need to revive an old issue about the Withholding Tax because we found this use case is not well supported by UBL 2.1 as we initially believed. The Withholding Tax information has a different behaviour and meaning from goods/service and VAT taxes. It is a tax related to the personal income of the invoicer (usually a soleproprietorship or freelance) that is calculated in percentage on the taxable amounts (for such kind of tax), but is paid to the Government by the Invoicee (Customer). The Withholding Tax is applied just to certain line items (usually expenses like transport, hotel are excluded) As the Withholding Tax is not always applicable to the whole Invoice taxable amounts, it could be useful to present a separated taxable amount for it, but this information can be calculated. >From the VAT point of view (the main Invoice purpose) the Total Due Amount of an invoice (aka. Payable Amount) is NOT including any Withholding Tax . The Withholding Tax is however a component of the Invoice Total just like Prepaid Amount , but is not payable to the Invoicer/Supplier (as explained before). On paper invoices the Withholding Tax total is also provided separately from other totals, as this amount is important to be presented to the Invoicee (Customer) who is requested by the Government to pay on behalf of the Invoicer. The full Withholding Tax concept is available here: http://en.wikipedia.org/wiki/Withholding_tax Finally I provide a set of improvements required to support this case: 1) Add a new ABIE named WithholdingTaxTotal after the TaxTotal 2) Add the new WithholdingTaxTotal ABIE under the cac:InvoiceLine after the TaxTotal (this will be used to identify those line items subject to withholding tax) The proposed definition for WithholdingTaxTotal is: An association to Withholding Tax Total. For the purpose of evaluating and understanding this important requirement I attach a real invoice where the withholding tax is applied, but not VAT. The sample is also useful to see how the withholding tax data is presented separately from VAT amounts. The invoice is provided either in English and italian. Best regards Roberto --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php begin:vcard fn:Tim McGrath n:McGrath;Tim org:Document Engineering Services Ltd. email;internet:tim.mcgrath@documentengineeringservices.com title:Managing Director tel;work:+45 36 95 33 58 tel;cell:+61 438 352228 url:www.documentengineeringservices.com version:2.1 end:vcard

Hi Tim Withholding tax is not a tax in the sense we have all the other taxes in an invoice. It is something like a payment means. You are giving instructions to the receiver of the invoice: Pay this taxes for me to the Tax Authority, I do not know whether this must be a tax total or another structure more close to Allowance and charges but we need it separate as the business rules governing it are quite different from the ones governing other types of taxes. regards Oriol El 05/03/2011, a las 02:23, Tim McGrath escribió: on first impression I think this is not the way to go.  the principle of UBL tax structures is that they are not based on specific types of taxes. we recognize consumption taxes (such as VAT) and sales taxes (used in US, etc.) but  need to keep the models  independent. So is it that we need to specify a payable total that does not include certain taxes? On 4/03/2011 10:37 PM, Roberto Cisternino wrote: 49570.62.110.96.182.1299249473.squirrel@mail.javest.com type= cite > Hello PSC, I recently discussed with Oriol Bausà the need to revive an old issue about the Withholding Tax because we found this use case is not well supported by UBL 2.1 as we initially believed. The Withholding Tax information has a different behaviour and meaning from goods/service and VAT taxes. It is a tax related to the personal income of the invoicer (usually a soleproprietorship or freelance) that is calculated in percentage on the taxable amounts (for such kind of tax), but is paid to the Government by the Invoicee (Customer). The Withholding Tax is applied just to certain line items (usually expenses like transport, hotel are excluded) As the Withholding Tax is not always applicable to the whole Invoice taxable amounts, it could be useful to present a separated taxable amount for it, but this information can be calculated. >From the VAT point of view (the main Invoice purpose) the Total Due Amount of an invoice (aka. Payable Amount) is NOT including any Withholding Tax . The Withholding Tax is however a component of the Invoice Total just like Prepaid Amount , but is not payable to the Invoicer/Supplier (as explained before). On paper invoices the Withholding Tax total is also provided separately from other totals, as this amount is important to be presented to the Invoicee (Customer) who is requested by the Government to pay on behalf of the Invoicer. The full Withholding Tax concept is available here: http://en.wikipedia.org/wiki/Withholding_tax Finally I provide a set of improvements required to support this case: 1) Add a new ABIE named WithholdingTaxTotal after the TaxTotal 2) Add the new WithholdingTaxTotal ABIE under the cac:InvoiceLine after the TaxTotal (this will be used to identify those line items subject to withholding tax) The proposed definition for WithholdingTaxTotal is: An association to Withholding Tax Total. For the purpose of evaluating and understanding this important requirement I attach a real invoice where the withholding tax is applied, but not VAT. The sample is also useful to see how the withholding tax data is presented separately from VAT amounts. The invoice is provided either in English and italian. Best regards Roberto --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php <tim_mcgrath.vcf> --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

This kind of tax is in connection with micro businesses (soleproprietorship) that may have *special* tax regimes, and the "Withholding tax" is applied to the proprietorship personal income. For such kind of micro businesses the tax authority is applying similar rules that are applied to employees where the employer takes from their salaries a percentage in advance for personal income taxation. The invoice payable amount is still the amount to be paid by the customer to the supplier. The withholding tax amount is to be paid by the customer to the tax authority on behalf of the supplier. So in simple words, the supplier proprietorship is pre-taxed (in Italy is 20%) on each invoice issued. At the end of the year the proprietorship will have to present a tax return to the authority to pay the remaining taxes. Usually micro businesses subject to Withholding tax are not allowed to apply VAT on their invoices, but they are subject to VAT however (on invoice receival) This is a separate thing that cannot be mixed with other taxes. Hope this clarify the issue Cheers, Roberto > Hi Tim > > Withholding tax is not a tax in the sense we have all the other taxes in > an invoice. It is something like a payment means. You are giving > instructions to the receiver of the invoice: Pay this taxes for me to the > Tax Authority, > > I do not know whether this must be a tax total or another structure more > close to Allowance and charges but we need it separate as the business > rules governing it are quite different from the ones governing other types > of taxes. > > regards > Oriol > > El 05/03/2011, a las 02:23, Tim McGrath escribió: > >> on first impression I think this is not the way to go. the principle of >> UBL tax structures is that they are not based on specific types of >> taxes. >> >> we recognize consumption taxes (such as VAT) and sales taxes (used in >> US, etc.) but need to keep the models independent. >> >> So is it that we need to specify a payable total that does not include >> certain taxes? >> >> >> >> On 4/03/2011 10:37 PM, Roberto Cisternino wrote: >>> >>> Hello PSC, >>> I recently discussed with Oriol Bausà the need to revive an old issue >>> about the "Withholding Tax" because we found this use case is not well >>> supported by UBL 2.1 as we initially believed. >>> >>> The "Withholding Tax" information has a different behaviour and meaning >>> from goods/service and VAT taxes. >>> It is a tax related to the personal income of the invoicer (usually a >>> soleproprietorship or freelance) that is calculated in percentage on >>> the >>> taxable amounts (for such kind of tax), but is paid to the Government >>> by >>> the Invoicee (Customer). >>> >>> The Withholding Tax is applied just to certain line items (usually >>> expenses like transport, hotel are excluded) >>> >>> As the Withholding Tax is not always applicable to the whole Invoice >>> taxable amounts, it "could" be useful to present a separated taxable >>> amount for it, but this information can be calculated. >>> >>> >From the VAT point of view (the main Invoice purpose) the "Total Due >>> Amount" of an invoice (aka. Payable Amount) is NOT including any >>> "Withholding Tax". >>> >>> The "Withholding Tax" is however a component of the Invoice Total just >>> like "Prepaid Amount", but is not payable to the Invoicer/Supplier (as >>> explained before). >>> >>> On paper invoices the "Withholding Tax" total is also provided >>> separately >>> from other totals, as this amount is important to be presented to the >>> Invoicee (Customer) who is requested by the Government to pay on behalf >>> of >>> the Invoicer. >>> >>> The full Withholding Tax concept is available here: >>> http://en.wikipedia.org/wiki/Withholding_tax >>> >>> Finally I provide a set of improvements required to support this case: >>> >>> 1) Add a new ABIE named "WithholdingTaxTotal" after the "TaxTotal" >>> >>> 2) Add the new "WithholdingTaxTotal" ABIE under the cac:InvoiceLine >>> after >>> the "TaxTotal" (this will be used to identify those line items subject >>> to >>> withholding tax) >>> >>> The proposed definition for WithholdingTaxTotal is: >>> >>> "An association to Withholding Tax Total." >>> >>> >>> For the purpose of evaluating and understanding this important >>> requirement >>> I attach a real invoice where the withholding tax is applied, but not >>> VAT. >>> The sample is also useful to see how the withholding tax data is >>> presented >>> separately from VAT amounts. >>> The invoice is provided either in English and italian. >>> >>> >>> Best regards >>> >>> Roberto >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this mail list, you must leave the OASIS TC that >>> generates this mail. Follow this link to all your TCs in OASIS at: >>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> <tim_mcgrath.vcf>--------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > -- * JAVEST by Roberto Cisternino * * Document Engineering Services Ltd. - Alliance Member * UBL Italian Localization SubCommittee (ITLSC), co-Chair * UBL Online Community editorial board member (ubl.xml.org) * Italian UBL Advisor Roberto Cisternino mobile: +39 328 2148123 skype: roberto.cisternino.ubl-itlsc [UBL Technical Committee] http://www.oasis-open.org/committees/ubl [UBL Online Community] http://ubl.xml.org [UBL International Conferences] http://www.ublconference.org [UBL Italian Localization Subcommittee] http://www.oasis-open.org/committees/ubl-itlsc [Iniziativa divulgativa UBL Italia] http://www.ubl-italia.org