← Prev in month ← Prev in thread
Next in thread → Next in month →

[ubl-australia] Minutes of ALSC Call 8 August 2018 10:00 AEST

From
Levine Naidoo <>
Date
2018-08-08T08:01:25+00:00
ID
Thread
[ubl-australia] Minutes of ALSC Call 8 August 2018 10:00 AEST
Minutes of ALSC Call 8 August 2018 10:00 AEST

ATTENDANCE

Todd Albers

Ken Holman

Matt Lewis

Andrew Mitchell

Levine Naidoo (convenor)

Matt Vickers

APOLOGIES

None

REFERENCING THE SPECIFICATION

the following should be used as a specific citation:

        OASIS Universal Business Language (UBL) v2.2

the canonical 2.2 documents are available in the OASIS repository:

        http://docs.oasis-open.org/ubl/os-UBL-2.2/

the working semantic libraries for this subcommittee:

	Google sheets are located in the ALSC google drive 

https://drive.google.com/drive/folders/16YIef092Y7xBqeiLqevUglAxKxa5QjKG?usp=sharing

STANDING ITEMS

Review of minutes

	Minutes of 25/7/18 have been approved

Review of DBC semantic model

Model issues:

Single-child ABIEs should not have an optional child:  There are 5 of these elements:
"Commodity Classification"
"Country"
"External Reference"
"Status"
"Tax Scheme"

Accounting Supplier and Customer Party are mandatory but all their child elements are optional

For completeness the delivery structure not described in semantic document or einvoicing implementation guide  - other structures are documented. 	There is also duplication of delivery address as a semantic element

Purchase order/sales order numbers are excluded at the invoice line level

There are some elements excluded from the model that make sense to put back in such as line references, party contact - but they should only be put back if we find evidence of use (existing trading networks)

Guidance Issues:

Guidance is required for Party taxscheme being used to indicate branch.

In the semantic model Company ID is labeled ABN whereas it should be ABN Branch ID 

Can an invoice be issued by more than one branch?;

and can it be issued to more than one branch? - need explicit examples

Insufficient guidance on payment  means and various options available in Australia

GST category codes are needed - makes sense to collaborate with the ATO

No guidance on invoice as receipt

Current examples are either insufficient or demonstrate incorrect scenarios or usage

Rules:

Guidance on free /exempt GST is required, i.e .GST amounts can be zero

Need to review the business rules spreadsheet

Schematron for code lists have been provided but not for business rules

UBL specs consists of additional document constraints where no element can be empty - there should be a schematron rule to catch all

Testing the model - as with all things modelling the best way to test a model is to put some data in it. Should we also look at multiple industry scenarios such as agriculture, construction etc to expand the sample set, provided that there is sufficient variety

Proposed approach for review and creation of ALSC artefacts with coaching from Ken

	- cnd01dw01 as working draft for artefacts

	- cnd01dw01 be reviewed under public consultation

	- Templates are available from OASIS

	- ALSC Artefacts should be:

	- document (xml via docbook or word document)

	- spreadsheets

	- schemas

	- schematron

Actions:

Levine to capture above issues in the ASLC model spreadsheets with comments

Levine to reach out to ABSIA to socialise the ALSC work

Discussion of short term P2P scope

Explore alignment with ISO20022, so that information set is available in UBL  -  this will be ongoing and to do this work under payments and finance subcommittee and then subset it

Remittance Advice

Documents to support the purchase order process - to be expanded in later meetings

Explore supplemental documents to the invoice - to be expanded in later meetings

JIRA tickets

Summary - https://issues.oasis-open.org/issues/?jql=project%20%3D%20UBL%20AND%20component%20%3D%20%22Australia%20SC%22

When creating tickets for the SC, remember to use âAustralia SCâ to distinguish between the following components by how they are described to be used as categories:

https://issues.oasis-open.org/browse/UBL/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel

if you leave the "Component/s" field empty, the ticket will not show up in the SC summary filter

status and resolution values:

NEW - the issue has been created but not yet agreed to be in consideration or not for the development distribution

in order for the issue to become active work for the committee the new ticket must be changed to OPEN or it will not be seen in the "to do" filter

the other option on a new ticket is to change it to DEFERRED

please remember to look at the open filter to ensure visibility:

https://issues.oasis-open.org/issues/?jql=project%20%3D%20UBL%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20%22Australia%20SC%22

OPEN - the issue is in consideration for the development distribution

keep the issue OPEN when assigning to Ken for incorporation

please remember to add a comment regarding expectations whenever you assign an OPEN ticket to another person for any action

RESOLVED + Applied - the issue is incorporated in test but not released

RESOLVED + Fixed - the issue is incorporated in a working draft version

RESOLVED + Later - the issue is still up for discussion for a future minor revision but not the current development

RESOLVED + No Action - considered as no action for any distribution

RESOLVED + Cannot Reproduce - considered as no action for distribution

APPLIED + Fixed - the issue is included in a public review (record the availability of the disposition once review opened)

DEFERRED - the issue is not in consideration for any minor revision

please remember to use this when creating new tickets for backwards-incompatible changes

see also the discussion on the status workflows here:

https://lists.oasis-open.org/archives/ubl/201709/msg00000.html

members please note to discuss ticket issues as comments to the ticket so that we can audit the discussion when making decisions about the ticket, without having to find the discussion on the main mail list

FACE TO FACE MEETING

Should we plan a face to face - to be discussed at next meeting

CONFERENCE CALL SCHEDULE

22 August 10am AEST

5 September 10am AEST

19 September 10am AEST

SC Calendar - https://www.oasis-open.org/apps/org/workgroup/ubl-australia/calendar.php

SC Calendar subscription link - webcal://www.oasis-open.org/apps/org/workgroup_feeds/ical/my_vcalendar.ics?token=f352ce7037f9b5ccc709d6085becd4e0&workgroup_id=559

OTHER BUSINESS

None

Thanks
Levine
← Prev in month ← Prev in thread
Next in thread → Next in month →