TBG1 - UBL Convergence Project Core Group Progress Report New Delhi - October 2006

TBG1 – UBL core group Basis documents  UBL 2.0 trade messages  Approved TBG1 Business Requirements Specifications (BRS) and the existing BRS documents in production TBG1 - UBL core group  TBG1 (Pat Toufar, Anders Grangard, Freddy De Vos) - UBL (Mark Leitch, Martin Forsberg, Peter Borresen)  Draft a convergence document dealing with mission, deliverables, work plan  Gap analysis for the messages having a UBL and a TBG1 version, based on an Gap analysis evaluation how to integrate  Set up of a joint project for the UBL messages not yet in development in TBG1 (Despatch advice, Receipt advice)  Common production of updated or new BRS documents

Organisation  Set-up of the core group for the Gap analysis and integration planning  Define work plan of the projects for the integration of the UBL messages for which there are not yet TBG1 developments  Should report at the next UN/CEFACT forum on their work plan and progress  Incorporation of the UBL Procurement group into TBG1  Should be finalised at the next UN/CEFACT forum meeting (October 2006)  Assimilation of the UBL procurement members as full TBG1 members  Should be finalised by the end of 2007 TBG1 – UBL core group

Present situation  Two meetings of 3 days (July, September)  Gap analysis of the invoice (including credit note and debit note)  Gap analysis of the remittance advice Next steps  Present the Gap analysis to TBG1 and OASIS UBL TC  Distribute full report (gap analysis and proposed amendments) for approval  Draft of updated version of the BRS documents  Present the BRS documents for approval to UN/CEFACT  Work plan (start July 2006 – planned end September 2007)  November 2006 meeting – Gap analysis Order  December 2006 meeting – Gap analysis Order response, Order change, Order cancellation  January 2007 meeting – Gap analysis Despatch advice, Packing list, Receipt advice  March 2007 meeting – Gap analysis Catalogue messages  July 2007 meeting – Gap analysis Self-billing TBG1 – UBL core group

Gap analysis of the Invoice (incl. Credit Note – Debit Note)  High degree of match between TBG1 and UBL  e.g. document header, totals etc.  Some gaps in other areas  e.g. Item/Product, Party etc.  Proposed additions in Invoice Header (examples)  Subset and Profile IDs (may be part of a new SBDH)  Receipt, Originator and Additional Document References  Prepaid amount  Payable Rounding Amount  Review the structure of pre-payments and split payments  Structure Financial Account within Payment Means (used by Sweden)  Open issues in Invoice Header (examples)  Version ID  Signature  Naming of Party Roles (Invoice Issuer / Invoicee - Accounting Supplier Party / Accounting Customer Party)  Only a few UBL identified elements were not accepted  Evaluated by the UBL core members as not relevant  Will be presented to OASIS UBL TBG1 – UBL core group

Gap analysis of the Invoice (Credit Note / Debit Note)  Proposed additions to Invoice Line (examples)  UUID  “Free of Charge” indicator  Receipt and Billing Document cross referencing using existing ABIE Reference_ Documents  Allowance charge independent of the Price  Delivery terms  Latest delivery date  Delivery address and location  Discrepancy response (credit note, debit note)  Open issues in Invoice Line (examples)  Pricing reference  Delivery  Product and Product unit (Item and Item instance) incl. Lot ID  Only a few UBL identified elements were not accepted  Evaluated by the UBL core members as not relevant  Will be presented to OASIS UBL TBG1 – UBL core group

Gap analysis of the Invoice (Credit Note – Debit Note)  Proposed additions to existing classes (ABIEs)  Reason information in Allowance charge  Calculated amount in Allowance charge  Tax information in Allowance charge  Note (free text) in Contact  Other Communication in Contact  Effective date, Document type, Attachment in Referenced documents  Exchange market identifier, Exchange Contract in Currency Exchange  Care Of, Attention Of, Logo, Website, Physical Location in Party  Party Legal Entity, Party Tax Scheme to Party  Payment Channel, Instruction and Financial Account to Payment Means  Information regarding penalties for Late Payments  Tax Per Unit information in Tax TBG1 – UBL core group

Gap analysis of the Invoice (Credit Note – Debit Note)  Open issues in existing classes  Loss risk information in Delivery Terms  Currency in Financial Account  Address of the Financial Institution – to be discussed with TBG5  Tax Evidence Indicator to Tax Totals Difference between UBL Invoice (Credit Note – Debit Note)  Same content with addition of  Discrepancy Response in Header  Discrepancy Response in Line  Billing Document Reference in Line  Sender / Receiver roles are reversed for Debit Note  Supplier side sends Invoice and Credit Note  Customer side sends Debit Note (to obviate Credit Note)  To be decided  One document covering Invoice, Credit Note and Debit Note or  Three distinct documents TBG1 – UBL core group

Gap analysis of the Remittance Advice  Matches between TBG1 and UBL  Very high level of commonality  UBL Remittance Advice based largely on work of TBG1  Proposed additions in Remittance Advice Header  Subset and Profile IDs (may be part of a new SBDH)  UUID  Line Count  Invoice Period [covered] rather than specific Invoice reference  Open issues in Remittance Advice Header  Version ID  Signature  Total Credit and Debit Amounts (in addition to Balance)  Tax Totals per Tax Rate TBG1 – UBL core group

Gap analysis of the Remittance Advice  Difference in structure  TBG1; 1 Line is equal to one invoice  UBL; 1 line can be equal to one Invoice plus all Credit Notes and Debit Notes related to the Invoice  Proposed additions in Remittance Advice Line  UUID Open issues in Remittance Advice Line  Total Credit and Debit Amounts  Buyer and Seller  Naming of Party Roles (Invoice Issuer / Invoicee - Accounting Supplier Party / Accounting Customer Party)  Invoice Period [covered] rather than specific Invoice reference  Billing Reference TBG1 – UBL core group

Work plan Ref.Document (s)MeetingCompletion Target 1.1Invoice (including Credit Note and Debit Note)3 day workshop 26 th to 28 th July 2006 CEN Offices, Brussels November Credit Note, Debit note and Remittance Advice3 day workshop September 2006 November Order3 day workshop November 2006 March Order response. Order response simple, Order change, Order cancellation 3 day workshop December 2006 March Despatch Advice, Packing list and Receipt Advice3 day workshop January 2007 May Cataloguing Messages2 x 3 day workshop March 2007 April 2007 September Self Billing (incl. Self Billed Credit Note), Application Response and Accounting Token 3 day workshop July 2007 October Request for Quotation and QuotationSet up project team at the UN/CEFACT forum meeting of October 2006 November ReminderSet up project team at the UN/CEFACT forum meeting of October 2006 November StatementSet up project team at the UN/CEFACT forum meeting of October 2006 November 2007

Core group is working well and according to planned schedule  highly pragmatic approach Level of shared requirements is high Common understanding of goals  to take the best of UBL’s work and the best of TBG1’s work and create a converged, unified standard suite of business documents  to propose new candidate core components where deemed necessary OASIS UBL Perspective

Work on the fiscal documents to date has highlighted two main issues:  UBL’s approach to message assembly is different to that of TBG1  the core group has identified potential problems with core components such as Party (and Product) The core group’s issues are predominantly ‘mechanical’  business issues are more in line OASIS UBL Perspective

Future work  continue convergence of the business documents as per the schedule November - Order December - Order Response, Order Change & Order Cancellation Hold the results in abeyance  wait for UN/CEFACT advice regarding: the agreed method of message assembly the use of core components e.g. when a transaction moves from the Tendering phase to the Purchasing phase to the Shipment phase etc. UN/CEFACT advice required urgently OASIS UBL Perspective

Differences in modelling approach  UBL has a high degree of reusable components  CII uses core components in a more specific way In UBL  when an ABIE is associated from e.g. Invoice Line, all BBIEs and ASBIEs within the ABIE are ”imported” In CII  only the BBIEs required are ”picked” Modelling Approach

Document context specific content in ABIEs UBL always imports the entire ABIE from the library, even though only parts of it are needed (as in EDIFACT, where all qualifiers are available to a segment without regard to the message where it is used) Profiling or subsetting required to make the documents more specific This makes the GAP analysis more difficult but we have a great deal of help from NES (Northern European Subset of UBL) where the profiling is already done Example from CII

UBL CII Structured Unstructured Post box Example from CII

UBL CII Reused in order and other documents Example from CII

UBL 2.0 NES Subset Stand Alone Order Stand Alone Invoice Basic Procurement REFINEMENT UBL Approach

EDIFACT EANCOM Profile 1Profile 2Profile 3 REFINEMENT EDIFACT Approach

UBL Common LibraryUBL Documents UBL Level Subset Level NES Common LibraryNES Generic Documents Order Order Response Invoice NES Context Specific Documents Order Related InvoiceOrder (with Invoice)Order (with Response) Stand Alone InvoiceStand Alone Orderetc. Profile Level NES MEMBER BUSINESS REQUIREMENTS UBL NES Approach

CC06B – BIE Library (Supply Chain Context) Cross Industry Invoice Assembled in Containers (Message specific “BIEs”) CC06B – Core Components Qualify, restrict and extend Results in CII approach

UBL REFINEMENT NES Stand Alone Invoice Stand Alone Order Basic Procurement UBL Component Re-use & Restriction

UBL REFINEMENT NES Stand Alone Invoice Stand Alone Order Basic Procurement UBL Component Re-use & Restriction

UBL REFINEMENT NES Stand Alone Invoice Stand Alone Order Basic Procurement UBL Component Re-use & Restriction

UBL REFINEMENT NES Stand Alone Invoice Stand Alone Order Basic Procurement UBL Component Re-use & Restriction