Summary history 1972
1973 1977
1984
SAP is established by five former IBM employees. SAP completes its first financial accounting system – RF.
Headquarters are moved from Weinheim to nearby Walldorf. SAP’s first non-German customers are also gained, in Austria.
SAP (International) AG is founded in Biel, Switzerland as the starting point for SAP’s efforts in markets abroad. Numerous international subsidiaries follow over the next few years.
1987 Work begins on the development of R/3. 1988 1992
SAP transforms from a private, limited-liability company into the publicly traded SAP AG. SAP R/3 is launched.
2004 Launch of the NetWeaver integration platform. 2005 2008 2008 2010 2011 2012 2012
SAP makes a series of acquisitions including that of retail provider, Khimetrics. The acquisition of business intelligence specialist, Business Objects, is completed by SAP. There is the belated go-live of the SAP Payment Engine at Postbank for domestic payments. SAP acquires Sybase for $5.8 billion.
The Sybase-derived In-memory, high-performance HANA platform is launched. SAP acquires buyer-seller network, Ariba.
SAP announces the Financial Services Network (FSN) for bank-to-corporate connectivity.
2013 FSN seems to have moved more slowly than planned but Volante is now a partner for data translation; there are a number of important large cut-overs for SAP’s core banking and payment systems.
2014 A major release in April, Payment Engine 8.0, reflects the strategic nature of this sector for SAP and brings a wide range of enhancements.
2016 Launched new B2B payments system in partnership with First Data Product suite
Given its roots, the payments solution is clearly designed for high-end processing. It was benchmarked for more than ten million payments per hour, while at Postbank a peak volume of about 19 million transactions was going through the system per day not long after go-live. It is a platform-independent offering, leveraging SAP NetWeaver and supporting all major hardware and database options, albeit now with a HANA-enabled version (see below). SAP based the development of its payments engine on
three criteria set by banks. First, all rules and validations within the system should be centred on a single data model and should support multiple channels, such as Swift and national ACHs. Second, it should be multi-bank and multi-entity, so that it could constitute a utility, fitting within a payment hub business model. This meant it should be able to support group-wide reengineering of payments as was likely to occur within institutions in the light of SEPA. And third, the system needed to be highly scalable to support insourcing scenarios and rapidly growing payment volumes. Also, the intention was to make it modular so that users could take appropriate components, for distinct areas such as liquidity management. It was expected that partners would offer complementary
solutions around the payment system, for areas such as anti- money laundering. The rules-based nature of the solution is intended to allow users to support mass processing as well as conform to service level agreements (SLAs), so they will be able to dictate routing based on different criteria. It
is meant to span retail and corporate payment
processing, with full domestic, SEPA and international payments support and real-time, online, 24/7 processing. There are rules-based configuration tools, data warehouse/ reporting and an integration broker, plus support for parallel account management.
On the technical side, it runs on all platforms supported
by SAP NetWeaver, e.g. Unix (IBM AIX and HP-UX), z/OS, with DB2 or Oracle, plus HANA. First Data and SAP joined forces in 2016 to create a new B2B payments system that aims to make transactions smoother. The resulting AribaPay solution looks to make the procure- to-pay process faster using a cloud-based model across a business network. Delivered through the Ariba Network, the solution will be available across Europe and Latin America. Users will be able to exchange purchase orders, invoices and payments with lower processing costs and better remittance advice, according to the two firms. Clients will also be able to track transactions and have decreased reconciliation and dispute resolution times.
Payment Systems & Suppliers Report |
www.ibsintelligence.com 249
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 |
Page 193 |
Page 194 |
Page 195 |
Page 196 |
Page 197 |
Page 198 |
Page 199 |
Page 200 |
Page 201 |
Page 202 |
Page 203 |
Page 204 |
Page 205 |
Page 206 |
Page 207 |
Page 208 |
Page 209 |
Page 210 |
Page 211 |
Page 212 |
Page 213 |
Page 214 |
Page 215 |
Page 216 |
Page 217 |
Page 218 |
Page 219 |
Page 220 |
Page 221 |
Page 222 |
Page 223 |
Page 224 |
Page 225 |
Page 226 |
Page 227 |
Page 228 |
Page 229 |
Page 230 |
Page 231 |
Page 232 |
Page 233 |
Page 234 |
Page 235 |
Page 236 |
Page 237 |
Page 238 |
Page 239 |
Page 240 |
Page 241 |
Page 242 |
Page 243 |
Page 244 |
Page 245 |
Page 246 |
Page 247 |
Page 248 |
Page 249 |
Page 250 |
Page 251 |
Page 252 |
Page 253 |
Page 254 |
Page 255 |
Page 256 |
Page 257 |
Page 258 |
Page 259 |
Page 260 |
Page 261 |
Page 262 |
Page 263 |
Page 264 |
Page 265 |
Page 266 |
Page 267 |
Page 268 |
Page 269 |
Page 270 |
Page 271 |
Page 272 |
Page 273 |
Page 274 |
Page 275 |
Page 276 |
Page 277 |
Page 278 |
Page 279 |
Page 280 |
Page 281 |
Page 282 |
Page 283 |
Page 284 |
Page 285 |
Page 286 |
Page 287 |
Page 288 |
Page 289 |
Page 290 |
Page 291 |
Page 292 |
Page 293
