OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-requirements message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: Auto-reconciliation - the killer app - go for it!


Thanks very much for the comment and the background.   It seems that you feel we
have not captured an important requirement.  It will help us to make sure it is
captured if you would please submit wording to be added to a specific section or
paragraph.  For guidance, the first and second paragraphs of your note are
probably more detailed and implementation oriented than we want to be in the
requirements document.   Something more like your final statement "third party
assurance of
non-repudiation" is more at the level we need.  You might want to elaborate a
bit more than that, but I hope this gives you the idea.



Andrew Chilcott wrote:

> Mike
> The situation that Todd Boyle describes is already in use in the UK
> securities market and I will try to explain the business model in generic
> terms as I believe that it could well be included under the General Business
> Requirements as a model for secure transactions between members of an
> electronic community with a central record archive and a trusted third-party
> to provide assurance for non-repudiation of contracts.
> A central industry hub (CREST) provides a service whereby industry
> participants (who can be securely identified by the hub) are able to submit
> a message detailing a transaction they claim to have undertaken with another
> participant. The messages submitted by each party to the transaction are
> matched on the basis of mandatory fields. The hub provides status update
> messages to the transaction participants. As soon as matching occurs the
> trade is available for settlement on the due date (one of the mandatory
> fields). The hub has real-time access to a record of the resources being
> exchanged in the transaction (cash and securities). When the due date is
> reached the hub checks to see that each party has sufficient resources to
> complete the transaction and, if so, issues messages to the custodians of
> the resources (cash and securities) instructing settlement to take place.
> The central hub holds messages, copies of which can be downloaded by the
> participants and imported into accounting systems, of all aspects of the
> transaction. Each participant is therefore using an identical record to
> update their internal systems and no reconciliation is required. The central
> message is archived after 60 days but can be recovered by the hub (as a
> trusted third-party) to prove that a contract existed between the parties
> and the terms of the contract.
> In B2B transactions I think that the third party assurance of
> non-repudiation is critical to the global roll-out of eCommerce.
> andrew.chilcott@stpsolutions.com
> 19-21 Great Tower Street, London EC3R 5AR
> Tel:    +44 207 929 7600
> Fax:    +44 207 929 7601
> Mobile: 07775 564166
> http://www.stpsolutions.com

Michael C. Rawlins, Rawlins EDI Consulting

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC