[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ubl] Approach to reporting scemantic errors on an invoice. Any advice?
Depends whether you want: 1 A process independent acknowledgement signal that is non-repudiable. Or 2 An acknowledgement that contains business information specific to the process in addition to the fact that the invoice was received and understood. For the first case, you need a transaction protocol signal such as a signed receipt acknowledgement and acceptance acknowledgement as defined in the ebXML BPSS specification. For the second case you need a specific "invoice response document". To my mind, and invoice falls into what might be called a "notification" transaction pattern where there is NO response business document BUT there IS a requirement for non-repudiable confirmation of receipt. That means option 1. So you should be looking to something like the BPSS specification and planning implementation of a compliant "Business Service Interface". Regards, Steve Capell Red Wahoo www.redwahoo.com p: + 61 2 9438 3700 m:+ 61 410 437854 f: + 61 2 9439 2738 This email message and any accompanying attachments may contain information that is confidential and is subject to legal privilege. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately, and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of Red Wahoo Pty. Ltd. Before opening any attachments, please check them for viruses and defects. We do not accept any liability for loss or damage which may arise from your receipt of this e-mail. -----Original Message----- From: Mikkel Hippe Brun [mailto:mhb@itst.dk] Sent: Wednesday, 13 April 2005 5:13 PM To: 'ubl@lists.oasis-open.org' Subject: [ubl] Approach to reporting scemantic errors on an invoice. Any advice? Dear TC, As you may know - we have implemented the UBL invoice based on 0p7 in the public sector. More than one million invoices has been exchanged since February 1th. The technical infrastructure is based on a VANS-network (5 operators). The addressing mechanism is using EAN-location numbers. The VANS network operates with a primitive "Acknowledgment Message". It is similar to the functionality of ebMS "AckRequested" and "Acknowledgment" between message handlers. We will now implement most of ebMS in the VANS network. My problem is that we lack a mechanism to report scemantic errors and other kinds of rejects to the invoice. It seems like ebMS is not suitable and should not be used for "business-level acknowledgments". We need an InvoiceResponse type message. Any advice to what path we should follow? Best regards Mikkel Hippe Brun Chief Consultant, M.Sc. Phone: +45 3337 9220 Cell: +45 2567 4252 E-mail: mhb@itst.dk National IT and Telecom Agency Office of IT Strategy Holsteinsgade 63 DK-2100 Copenhagen Ø Denmark Phone: +45 3545 0000 Fax: +45 3545 0010 www.itst.dk itst@itst.dk --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]