This document covers the proceedings of the work group meeting.

Next online meeting: Wednesday, September 12, 14:00 to 16:00 CEST

Roll Call of Attendees

P=present, E=excused

Agenda

Agenda

1. Approval of agenda and roll call.
2. Planing schedule
3. Schematrons, status, work.
4. Quantity vs price UoM in view of approach taken in EN invoice.
5. Further alignment of allowance/charge classes.
   
6. AOB.

• Decision Log

  DECISIONS TAKEN IN THIS MEETING. Please see minutes for Decisions. Log of all decisions
  

  Issue and Action Log

  Following tasks were raised in this meeting. For overview of tasks go to Task report - All 

Meeting notes

1. Approval of agenda and roll call

Agenda approved and attendance noted in attendance table.

2. Time schedules

The schedule of the project has been modified so that it aligns with the schedule of the 2018 Fall release. The two projects will continue as separate projects but we will seek to align the work. Key dates are the following:

2018-09-24 — Initiate Peppol Review.

2018-10-22 — Review period ends.

2018-11-12 — Comment resolution and testing completed.

2018-11-15 — Publishing.

3. Schematrons

The schematrons will be developed by using a generation tool provided by DIFI. The tool has been setup for the Order transaction.

Schematrons for transactions will be restructured so that the following schematron sets are used for validating each transaction. Each set has its own id sequence.

• Common rules, this is a shared schematron rule set used by all transactions for testing rules that are common to them all.
• Basic rules, automatic. A set of transaction specific schematron rules that have been automatically generated from the data model. Mainly concerning cardinalities and code lists.
• Basic rules, manual. A set of transaction specific schematron rules that have been manually written. Mainly concern conditional values and calculations.

Although the sets are managed as separate sets they may be distributed as a single file.

• Write a guide describing schematron generation Siw Midtgård Meckelborg (Unlicensed)
• Write a common section into the BIS documents describing the structuring of the rule sets. Siw Midtgård Meckelborg (Unlicensed)

The development of schematrons for each transaction requires the following steps

1. Activating auto generation and generating rules.
2. Identifying rules that do not autogenerate.
3. Evaluate if ungenerated rules should be skipped, identify new rules for a complete list of rules that need to be manually written.
4. Write schematron for manual rules.

The above needs to carried out for each transaction. Only steps one and two have been carried out for Order.

This work has not yet been resourced. Peppol authorities can contribute either by providing a resource or by funding resource. Following was noted by participants for:

• SE may be able to provide a resource.
• NO, Siw can work no schematrons but requires funding. Funding not known.
• DK, Resources are available but require funding. Funding not known.
• BE, Resources not available. Funding not known.
• IT, Resources may be available at later time. Funding needs to be investigated.

• Follow up on resources for schematron development Georg Birgisson

4. Quantity vs price UoM

Peppol BIS2 specification allow different unit of measure for orderable quantity and price. This supports ordering and catalogues where the orderable unit is e.g. pieces but the measurement of each piece (weight, volume etc.) varies and the item is priced by that measure. An example is that food items are often ordered in pieces but priced by weight. The EN invoice does not allow these units to be different and that is adopted in the BIS3 Billing.

It was agreed that the use case for different UoM is valid in Order, Order Agreement and Catalogue so Peppol will continue to allow those to be different. A note will be added into relevant sections that when ordering parties should be aware that the invoice will use the price UoM for both price and quantity.

5. Alignment of allowance and charge classes.

• The BIS3 billing adds allowance/charge code and percentage/base into document level. Agreed to add this to Order and Order Agreement.
• BIS3 Billing has allowance/charge classes on line level. Agreed to add to Order and Order Agreement.
• BIS3 Billing supports allowance on price on line level to support price discounts. Also supported in Order. Agreed to add to Order Agreement.

6. Alignment of codes.

Since the meeting was flowing well it was agreed to continue into alignment of codes even though that was not on the initial agenda.

• The EN requires that item classification codes are identified by UNECE 7143 which does not support UNSPSC. Agreed to:
  • Temporarily use code MP "Product/service identification number" to identify UNSPSC.
  • Apply this agreement to BIS3 Billing as well.
  • Submit RFC for addition of a new code to identify UNSPSC specifically and update through a maintenance release once available.
    • Initiate a RFC for UNSPSC id code. Georg Birgisson
• EN/BIS3 require that standard item ID schema used must be stated by using ICD list but most values in list are not relevant. Agreed to restrict the list for Standard Item identifiers in all transaction. Allowed values will be 0160 "Global Trade Item Number" only as that is the only currently recognized need. Other item id schemes can be added if requested either after review or in later maintenance releases.
  
• EN/BIS3 are more restrictive on allowed mime codes for attachments. Agreed not to apply same restriction to other transactions. Review what values should be allowed.
  • List allowed mime codes for transactions other than invoice, get input from Philip Helger. Siw Midtgård Meckelborg (Unlicensed)
• Discussion on alignment of action codes postponed to next meeting. Issue requires preparation.
  • Describe misalignment of action codes and propose resolution Siw Midtgård Meckelborg (Unlicensed)

AOB

• Alignment of VAT sub category classes raised as an issue. Discussion postponed to next meeting.
  

Meeting closed at 16:00 CEST.