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
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:
- the working semantic libraries for this subcommittee:
Google sheets are located in the ALSC google drive
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