Subject: Re: [ubl] Approach to reporting scemantic errors on an invoice. Anyadvice?
I agree with Steve Capell - the requirement is not completely clear. But if we were to assume that what you need is another UBL document type and not a messaging protocol signal then there is currently a proposal to introduce several additional document types for UBL 1.1 Billing process. The European Government Agency's UBL collaboration group has had a long discussion about the value of an Invoice Response document type. They currently recommended not introducing this document because of the commercial complexities (and taxation issues) that may result. I guess it is not as simple as the Order-Order Response pattern. Rather they recommend using a Debit Note sent from the Buyer to the Seller, stating that Buyer has deducted amounts from a Sellers Invoice. In situations where a Buyer and Seller have agreed to the use of a Debit Note, a Debit Note obviates the need for the Seller to create a Credit Note. My interpretation of this is that the Debit Note forms a kind of business-level negative acknowledgement. It is used to communicate variance between what was Invoiced and what the payee intends to pay. Its key advantage is that is a recognized VAT document. However, I am only an observer of this debate so others may have more to add. The UBL 1.1 process model also introduces a Statement document type which could provide further reconciliation if necessary. For the complete model see the notes attached to... http://lists.oasis-open.org/archives/ubl/200503/msg00038.html The models for these new document types are being rationalized over the next few weeks so it would be useful to get you input into their suitability for your requirement. Hope that helps. Mikkel Hippe Brun wrote: >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: firstname.lastname@example.org > >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 >email@example.com > >--------------------------------------------------------------------- >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 > > > -- regards tim mcgrath phone: +618 93352228 postal: po box 1289 fremantle western australia 6160 DOCUMENT ENGINEERING: Analyzing and Designing Documents for Business Informatics and Web Services (coming soon from MIT Press) http://mitpress.mit.edu/catalog/item/default.asp?sid=632C40AB-4E94-4930-A94E-22FF8CA5641F&ttype=2&tid=10476