UBL Australian Localisation SC

  • 1.  [ubl-australia] updates to google sheets

    Posted 08-15-2018 04:17
    The ALSC Models Google sheets 1) Library elements 2) DBC Business Rules Have been updated, ready for ALSC members to review before next call. thanks Levine


  • 2.  Re: [ubl-australia] updates to google sheets

    Posted 08-15-2018 12:18
    For the public record, these spreadsheets can be found at: https://drive.google.com/drive/u/0/folders/16YIef092Y7xBqeiLqevUglAxKxa5QjKG . . . . . ALSC Secretary At 2018-08-15 04:17 +0000, Levine Naidoo wrote: The ALSC Models Google sheets 1) Library elements 2) DBC Business Rules Have been updated, ready for ALSC members to review before next call. thanks Levine -- Contact info, blog, articles, etc. http://www.CraneSoftwrights.com/o/ Check our site for free XML, XSLT, XSL-FO and UBL developer resources Streaming hands-on XSLT/XPath 2 training class @ US$45 (5 hours free)


  • 3.  Re: [ubl-australia] updates to google sheets

    Posted 08-21-2018 00:53
    Hi All, I've reviewed the sheets and have the following feedback and additional recommendations. - Feedback on ALSC Invoice (cardinality references relate to ALSC subset column): - We should re-introduce the StatementDocumentReference that was previously excluded.   - My conversations with several large corporates indicate common business usage of the Statement.  Including Large supplier to Small/Medium Buyer relationships.  - TaxTotal - Has a mandatory child element TaxAmount which is OK - Has an optional child element TaxSubtotal which I believe should be 1 or many. - TaxSubtotal.TaxCategory  - The semantic element name is GST Category.  I think this is too limiting.   - Suppliers may wish to seperate GST and WET at a TaxSubtotal level.   - As such, this should remain as TaxCategory. - TaxSubtotal - Should Percent be 0 or 1 to provide a smooth path towards a single trans-tasman localisation and single window trade?  eg. 10% AU and 15% NZ? - TaxScheme.Name - should we make this 0..1 too? - BuyerCustomerParty currently cardinality of 0.   - I note that the AccountingCustomerParty is mandatory, but these parties will often not be the same party.   - Inside the AccountingCustomerParty we have set the AccountingContact to 0 and the BuyerContact to 1.   - I think we need further consistency around these elements.   - My suggestion is to keep BuyerCustomerParty = 0, but to set all the xContact elements of AccountingCustomerParty to 0..1. - CustomerParty.SupplierAssignedAccountID and CustomerAssignedAccountID.   - I have had requests to populate these fields from Australian companies.  These should be 0..1. - PaymentTerms - currently cardinality 0 - suggest we reconsider this. - PrepaidPayment - currently cardinality 0 - suggest we reconsider this. Thanks, Matt Lewis From: ubl-australia@lists.oasis-open.org <ubl-australia@lists.oasis-open.org> on behalf of Levine Naidoo <levine@lxndigital.com> Sent: 15 August 2018 14:17 To: ubl-australia@lists.oasis-open.org Subject: [ubl-australia] updates to google sheets   The ALSC Models Google sheets 1) Library elements 2) DBC Business Rules Have been updated, ready for ALSC members to review before next call. thanks Levine