[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FpML-BP RE: Position Report Payment report enhancement



Hi Brian, Marc, Matt

 

Would it be worth to structure the payment information in accordance with the existing ISO20022 XML tags  for payments ?

 

pain.001.001.03 is the iso standard for initiation of a payment. Staying in synch with standard payment tags may help in the disbursement and settlement of the transaction.

 

http://www.iso20022.org/catalogue_of_unifi_messages.page

 

Thanks

 

Bart

____________________________________________________
 
Bart Cant , CTP 

Capgemini  Financial Services Global Business Unit
Practice Leader Wholesale Banking and Payments
Mobile: +1 704.737.2724 /
www.capgemini.com/financialservices  
7332 Summerlin Pl, Charlotte NC, USA

Together. Free your energies
_____________________________________________________

From: bpwg@xxxxxxxx [mailto:bpwg@xxxxxxxx] On Behalf Of Marc Gratacos
Sent: Tuesday, August 10, 2010 3:14 AM
To: bpwg@xxxxxxxx
Cc: rptwg@xxxxxxxx
Subject: FpML-BP FW: Position Report Payment report enhancement

 

See email below and attached proposal.

 


From: Brian Lynn [brian.lynn@xxxxxxxxxxxxxxxxxxx]
Sent: Thursday, July 22, 2010 6:39 PM
To: 'Simpson, Matt'; Marc Gratacos
Subject: Position Report Payment report enhancement

Matt, Marc –

 

I’ve taken a crack at modeling the CME payment enhancement to the position report that we discussed over the past few meetings.

 

I created a new model group that covers payment details, restructured the existing PaymentMatching type to use it, and created a new PositionPayment type to hold the new structure.

 

I’ve attached

- diagrams of the new types

- a zip of the schema

- a couple of examples … this first is fairly simple, the second is based on Matt’s document.

 

For your comments prior to wider distribution.  Do I need to write up a Word doc to hold all of this stuff?

 

- Brian

 


The information contained in either this email and, if applicable, the attachment, are confidential and are intended only for the recipient. The contents of either the email or the attachment may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, or distribution is prohibited and may be unlawful. If you have received this communication in error, please notify us by e-mail at isda@xxxxxxxx <mailto:isda@xxxxxxxx> then delete the e-mail and all attachments and any copies thereof. This communication is part of an ISDA process and is not intended for unauthorized use or distribution.

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.