search.noResults

search.searching

note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
solutions prior to the acquisition by Wolters Kluwer. In 2008, FRSGlobal gained a foothold in the Russian


market through a deal with BNP Paribas Corporate and Investment Banking (CIB) group. The supplier was to tailor FinancialAnalytics to cover reporting to the Central Bank of Russia (CBR) and the global reporting functionality at Moscow-based BNP Paribas ZAO. According to Rebecca Bond, at this time global director of marketing at FRSGlobal, the bank’s four-month evaluation included a number of Russian providers. FRS Global already had its eyes on the Russian market. ‘The work started many months before, with a series of workshops to measure the complexity of the Russian regulatory reporting,’ she said. A local partner was identified to help with the push. With this signing, Russia became the tenth BNP country


operation to take FinancialAnalytics after Belgium, Germany, Hungary, Ireland, Poland, Portugal and the Netherlands, where the system was already up and running, and Greece and Spain, where it would be rolled out in 2009 and 2010. Other entities of the group also used reporting software from FRSGlobal, including BNP Paribas Private Banking and BNP Paribas Securities Services.


Another notable signing came in early 2009 from


Skandinavisk Data Centre (SDC), a Denmark-based IT provider to over 130 banks in the Nordic region, which was to implement the stress testing component of RiskPro in all of its member banks. During the course of six months, FRSGlobal held three workshops with SDC and its major customers. The first workshop was a general one, followed by an ALM themed session. The closing workshop was prepared by FRSGlobal, but executed by SDC itself, and was focused on stress testing and liquidity risk. All sessions were based on ‘the real data supplied by one of the SDC’s banks’, said Kris Luyten, account manager at FRSGlobal. ‘It wasn’t just an academic exercise. The participants could really see what RiskPro could produce based on actual data.


‘Our main competition was an in-house development,’ he continued. ‘A number of SDC’s customers have already been producing stress testing reports by themselves for a year or so, mainly Excel-based. Some of the bigger banks also had front office systems with such capabilities.’ In his view, the main reason for choosing FRSGlobal’s offering was that it enabled the banks to integrate risk and regulatory reporting, as SDC and its member banks had been using RiskPro for credit and market risk capital adequacy (CAD) reporting since 2004. In 2009, Zurich-based EFG International began the implementation of RegPro across all of its international locations. The group had been using Fire in Hong Kong, Singapore, Monaco and Luxembourg. In the Asia Pacific sites, the new solution was to be implemented ‘to update regulatory reporting in line with latest requirements’, said Mark Bagnall, head of IT at EFG. Luxembourg and Monaco upgraded to RegPro the previous year due to the Basel II requirements. RegPro was also to be deployed at one of the group’s start-ups,


in France. It is clear from just these three examples that, broadly speaking, FRSGlobal had a diverse customer base which provided repeat business. However, the vendor did not have everything its own way and its fiercest competitor was probably Financial Architects. There were also regional competitors. For instance, Bank of India, which used FRSGlobal worldwide, opted to replace it in the US with a more local solution, Sofgen’s REG-Reporter.


Financial Studio (FinStudio)


Founded in Belgium in 1997, Finnacial Architects (FinArch) achieved


considerable success with Financial Studio


(FinStudio), its comprehensive financial management suite. It was set up by Dirk de Beule (ex-FRS) and Chris Puype (ex-ABN Amro). ABN Amro was the first customer and FinArch swiftly came to compete with FRS, among others. It remained a private company for a long while and established offices across the globe, with its success based on a single Microsoft-based platform that was extended to meet regulatory, accounting and business reporting requirements over its 15+ years. Marketed as a fully integrated finance resource planning (FRP) solution for banks and other financial institutions, FinStudio was intended to provide the tools needed to manage, measure, and report all financial activities, including IAS/IFRS and multi-GAAP accounting, Basel II and Basel III, management and central bank reporting (for the latter, it now supports 20+ countries), risk and liquidity management, and others forms of compliance. It was claimed that the solution’s modular approach provided flexibility, scalability, and the power to connect to all existing data sources. FinStudio spanned both compliance and accounting, and could constitute a full sub-ledger in the latter domain. Moves within some banks to bring together these disciplines had played to its strengths. A suite of generic modules underpinning the FinStudio FRP


solution comprised an industry standard data model; multi- dimensional reporting hierarchies; archiving tools; full audit trail and historical information management; and rules-based engines. FinArch claimed that the single platform approach meant it was a small step for users that had FinStudio for Basel II to support Basel III, with 95 per cent of the data the same, in contrast to the position faced by users of some competitor products. It had ridden the wave of heightened regulation, as well as the demand for better internal reporting and management, particularly around liquidity. The product’s features were deliverable via web


technology, where an intranet portal solution enabled the distribution and exchange of financial information across the enterprise. Financial reports were delivered through standard web browsers, and could be distributed in various formats. The solution was thin client-based, had an SQL relational database, was based on open standards, and utilised OLAP


Risk Management Systems & Suppliers Report | www.ibsintelligence.com 155


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164  |  Page 165  |  Page 166  |  Page 167  |  Page 168  |  Page 169  |  Page 170  |  Page 171  |  Page 172  |  Page 173  |  Page 174  |  Page 175  |  Page 176  |  Page 177  |  Page 178  |  Page 179  |  Page 180  |  Page 181  |  Page 182  |  Page 183  |  Page 184  |  Page 185  |  Page 186  |  Page 187  |  Page 188  |  Page 189  |  Page 190  |  Page 191  |  Page 192