RE: [ubl-dev] Collection Invoice

["Pim van der Eijk" <lists@sonnenglanz.net>]

I agree with Roberto, the logical exchange (between partners
in an e-business collaboration) is best done at the level of
individual documents,  but it is still possible, and often
desirable, to optimize exchange of large amounts of
documents in a messaging protocol.  

In ebMS 3.0, Part 2, we defined new functionality called
"bundling", which allows a sender to send a collection of
"logical" messages (where a "logical" message includes the
payload or payloads, like a UBL document and message
metadata) as a single "physical" message.  Submission and
delivery is still at the document level, so there are no
changes there.  The protocol uses agreement parameters that
control what can be bundled together, size/timing
parameters, how ordering and error handling work, and
control delivery policies. 

The main benefit of bundling is to optimize exchange of
large amounts of relatively small messages. You avoid the
overhead of many small messages, each of which needs a
separate TCP/IP connections to be set up, SSL sessions to be
negotiated or resumed, reliable messaging and WS-Security
processing etc.  

The benefits are even better when you combine bundling and
message compression, which is also in the new ebMS 3.0 Part
2, and you can send large amounts of documents in a single
SOAP message with compressed content.  As UBL invoices use
elements from the same schema and same UBL library, they
compress extremely well.  I did some experiments with three
XML document sets (13 UBL 2.0, 23 GS1 GDSN,  11 GS1 eCom 2.6
documents) and the message size of message bundles
(documents and metadata) is, in the worst case, just 8% of
the combined size of unbundled message. The best case was
the GDSN set with bz2 compression, at just 4% of size of the
uncompressed, unbundled messages.  

Pim van der Eijk


 


-----Original Message-----
From: Roberto Cisternino [mailto:roberto@javest.com] 
Sent: 03 December 2010 13:21
To: Roland Hommes
Cc: ubl-dev@lists.oasis-open.org
Subject: Re: [ubl-dev] Collection Invoice

Hello,

I am not sure I understood your requirement so I provide you
a question and an answer:

Question: Do you intend the following CollectiveInvoice case
?

in which any number of single invoices addressed to the same
payer are listed.
Each collective invoice has a unique collective invoice
number. The system transfers this collective invoice number
into the billing and accounting documents that belong to the
collective invoice. In this way, the single invoices are
assigned to the collective invoice.
A billing or accounting document is not created for the
collective invoice itself. (source: SAP)

Answer:

From the above description it appears the CollectiveInvoice
has a number but it is not an Invoice itself, thus is not an
accounting document but just a binder.

The fact that the Payer is the same for a CollectiveInvoice
binder I think do not simplify so much the document exchange
because the receiver is usually the Debtor/Customer/Payer.

UBL documents are designed to promote a collaborative
document exchange between partners within a business process
and even in the whole Financial Supply Chain.

It means the Invoice document is required to be reconciled
with purchase orders and payments.

Collecting invoices into a single file is more an enveloping
task, but from the business point of view it is better to
deal with single business documents in a document-centric
system.

These days, with the automation of Business processes it is
preferred to deal with single documents.

Moreover by handling a single document partners are enabled
to provide simpler aknowledges.
---

By the way UBL 2.1 has introduced the "CollaborationID" that
can be used to correlate the document with its process, so
you could use the same CollaborationID for your pool of
invoices.

This is my opinion and I hope it helps.

Roberto

> Hi,
>
>
>
> Is it possible to create another level into the Invoice
(2.0) in which 
> a 'collection' of invoices are communicated with the
current ABIE/ASBIE's?
>
> At this moment all I can see are Invoice/InvoiceLine
levels. Can the 
> "CollectiveInvoice" only be added as a custom extension or
has this 
> problem already been solved in a different way?
>
>
>
> Thanks,
>
> Roland Hommes
>
> Logius-NL
>
>


--
* JAVEST by Roberto Cisternino
*
* Document Engineering Services Ltd. - Alliance Member
* UBL Italian Localization SubCommittee (ITLSC), co-Chair
* UBL Online Community editorial board member (ubl.xml.org)
* Italian UBL Advisor

  Roberto Cisternino

  mobile: +39 328 2148123
begin_of_the_skype_highlighting              +39
328 2148123      end_of_the_skype_highlighting
  skype:  roberto.cisternino.ubl-itlsc

[UBL Technical Committee]
    http://www.oasis-open.org/committees/ubl

[UBL Online Community]
    http://ubl.xml.org

[UBL International Conferences]
    http://www.ublconference.org

[UBL Italian Localization Subcommittee]
    http://www.oasis-open.org/committees/ubl-itlsc

[Iniziativa divulgativa UBL Italia]
    http://www.ubl-italia.org



------------------------------------------------------------
---------
To unsubscribe, e-mail:
ubl-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail:
ubl-dev-help@lists.oasis-open.org