1. 1 © VimpelCom Ltd 2012 Selection and implementation of a TMS Noordwijk, 9 November 2012 Joan Schutte Assistant Treasurer

2. 2 © VimpelCom Ltd 2012 Introduction Who??

3. 3 © VimpelCom Ltd 2012 Multiple telecoms operators providing voice and data services Headquartered in Amsterdam since summer 2010 following combination of businesses by 2 main shareholders under new holding company; a Bermuda Ltd Listed on the New York Stock Exchange under the ticker VIP Operations in 18 countries; Russia, CIS, SE Asia, South Asia, Africa, Italy, Canada 2011 revenue: $23.5 billion from 205 mln subscribers 2011 EBITDA: $9.3 billion 2011 debt: $27.0 billion 5 business units covering regions Operationally independent HQ acts as Strategic Controller VimpelCom – some key facts

4. 4 © VimpelCom Ltd 2012 Treasury challenges Spring 2011 - the key issues: 1.100+ people in the New VIP doing Treasury in 19 countries 2.Many different cultures (country and corporate) and back grounds 3.Widely varying practices, processes and policies (or lack of them) 4.No treasury management systems – access to information 5.No (Treasury) staff in Amsterdam – need to cooperate/delegate The immediate first step: Bring key Treasury people together and get aligned on 1. VMV and organization 2. Burning issues – fix the important and urgent first 3. Align on the end-state for all key elements of the function 4. Agree on a road map from as-is to end-state

5. 5 © VimpelCom Ltd 2012 Treasury at VimpelCom - Organization

6. 6 © VimpelCom Ltd 2012 TMS – Selection process 1.Key urgency issue: get detailed visibility on cash, debt, derivatives, bank accounts, etc. (June 2011) 2.Start monthly reporting in excel on cash and debt (July 2011) 3.Investigate what TMSs are used and how (July – Oct 2011) 4.Formulate TMS requirements and weights in light of the defined end state, local needs and decentralized organization (Dec 2011) 5.Ask 2 Treasury consultancy firms to rank available systems in the market based on the defined requirements and weights (Jan 2012) 6.Based on feedback consultants (same recommendation), invite vendor to demonstrate – webex meetings with RTCs (Jan 2012) 7.Develop detailed & tailored test script with one of the consultants and do extensive test demo based on these scripts (Feb 2012) 8.Additional demos for RTC teams and testing based on demo version 9.Agree on final conclusion and recommendation to select – sign-off 10. Start implementation – kick off March 2012

7. 7 © VimpelCom Ltd 2012 TMS requirements & weights TMS criterion groupTMS scoring criterionWeight Score Weighed score Score Weighed score Score Weighed score Score Weighed score Score Weighed score Score Weighed score FunctionalityCash/debt visibility 10%000000 import/reconciliation bank statements position monitoring FunctionalityInstrument coverage 8%000000 straight forward debt instruments plain vanilla derivatives trade finance I/C loans FunctionalityCash forecasting 10%000000 FunctionalityExposure/risk management 6%000000 FX and IR exposure, incl. scenario analysis Credit risk MtM calculation Functionality Settlement 5%000000 Treasury Payments FunctionalityAccounting 0%000000 FunctionalityHedge accounting 0%000000 FunctionalityReporting 5%000000 IntegrationInterfacing 8%000000 Banks Dealing platform(s) Market data vendor(s) ERP / General Ledger (Oracle,C1) IntegrationGlobal system access 10%000000 FunctionalityMulti-language 5%000000 FeasibilitySegregation of duties 5%000000 FeasibilityAudit Trail 5%000000 FeasibilitySystem security 5%000000 FeasibilityImplementation time 10%000000 CostPricing (TCO) 8% 0 0 0 0 0 0 Overall Weight / Scoring 100% - - - - - -

8. 8 © VimpelCom Ltd 2012 TMS – Implementation process (1/2) 1.Global kick-off meeting March 2012 – jointly with BELLIN – paint the bigger picture / policy in which the TMS fits – not a stand alone project 2.Create clear (local) ownership and responsibility – GT / RTCs / OpCos / IT 3.RTC relationship managers at GT level, key users in RTCs, single point of contact with BELLIN (top-down approach) 4.Step-wise implementation – cash and debt first, the rest later 5.Staff-up for initial phase of (centralized) static data entry - interns 6.Add all bank accounts in tm5 – 1,300 accounts globally – replace excel based reporting with tm5 based reporting 7.Ongoing training of key users in RTCs and some key OpCos through webex 8.Progress reporting to all teams on the project in general, motivate the laggards

9. 9 © VimpelCom Ltd 2012 TMS – Implementation process (2/2) 9.Make processes and instruments fit the system – not v.v. 10.Keep pushing on simplification of underlying structures – cut back on complexity (# bank accounts, banks, manual processes)

10. 10 © VimpelCom Ltd 2012 TMS – Implementation process

11. 11 © VimpelCom Ltd 2012 Treasury Management System - Lessons 1.Keep it simple - ease of use & access is key for TMS to work for VIP 2.Align (with IT early), involve and communicate 3.Consultants do add value in speeding up the selection process; implementation can (and should) be done yourself 4.Know what you want, focus on what you need; nice-to-haves add complexity; will come later when people are familiar with the basics 5.Celebrate successes and recognize role model behavior – create we 6.Demonstrate solutions for those that present issues 7.Creating customized user manual is time consuming but essential Key statistics after 6 months: 1,300 bank accounts and all Treasury deals in tm5 180 users in 18 countries 500 entities / counterparties Global consolidated Treasury reporting from tm5