Next WG Meeting: 18 August 2009, 1000-1100EST (London Time: 3-4pm)

Dial-in details:

US: + 1 (888) 481 - 3032

Intl: + 1 (617) 801- 9600

UK: 0800 904-7961

Participant Code: 28413758

Agenda

- Review updated trade structures.

- Review cancel/modify structures.

- Review feedback from WG members.

Regards,

Bhavik Katira

CEO

TenDelta™

Fresh insight. Pure logic.

www.tendelta.com

+1.917.582.4574 new york

+44.(0).7780.808732 london

TenDelta™ provides business process consulting, technology design/implementation & education services, specializing in the Syndicated Loan Market. Entrusted with engineering innovative & logical solutions, we endeavor to deliver timely, robust, cutting-edge solutions.

TenDelta™ Limited is a company registered in England & Wales. The Company registered number is 06285903. The registered office is 3 Francis Road, Harrow, Middlesex, HA1 2QZ, United Kingdom.

From: loanwg@xxxxxxxx [mailto:loanwg@xxxxxxxx] On Behalf Of Bhavik Katira
Sent: Tuesday, August 04, 2009 11:43 AM
To: loanwg@xxxxxxxx; Rosalind.Greener2@xxxxxxxxxxxxxxxxxxx
Subject: RE: Loan WG Meeting: 4 August 2009, 1000-1100EST (London Time: 3-4pm)

Minutes from 4 August 2009 Meeting:

- Scope & priority

o Updated to include modification/cancellation messages earlier. Next steps: discuss the requirements within the business working group and understand what modifications can be performed with respect to each of the notification messages that have already been defined. Document the specific requirements (if any) within the business requirements document.

o Cash flow messages. The concept here was to include a generic structure which basically defines the overall cash flow which is taking place on any business event. This was mentioned as something that participants are “unable” to go-live without.
The point of FpML having free-form fields was mentioned – this should allow participants to still communicate any details which might not have been fully specified as yet.

- Review of the updates to the requirements document (v1.39).

o Trade structure presented:

§ Deal Trade

§ AllocatedMultiFacilityTrade

§ MultiFacilityTrade

§ FacilityTrade

§ LoanContractTrade

§ LcTrade

§ DelayedCompensation

o We should potentially look to trying to integrate the loan trade structure more closely with the FpML OTC derivatives generic trade structure.

o Within the interest accrual and fee accrual sections of the trade structure we should have a delayed compensation amount for each accrual. These amounts will correspond to the overall delayed compensation associated with the facility being traded.

- Usage of Identifiers for all message types.

o We should publish a document which outlines the usage of the various identifiers within the current message structures e.g. Message Id, Event Id, Conversation Id.

o An additional option was to include a version identifier within a message to enable better tracking of modifications/cancellations in the future.