Formpipe uses cookies to improve how the website works for you as a visitor. To change your settings or for more information about cookies, click on 'Settings'.
Formpipe uses cookies to improve how the website works for you as a visitor. Here you can change and see information about what cookies are used. Turn on and off categories and save your choice. To learn more click 'Cookie policy'.
These cookies are essential for the website to operate correctly and cannot be disabled without ruining the usability of the website. We delete these cookies when you leave the website, where possible.
Name | Retention period | Information about the cookie | Disclosure of information to third party |
ASP.NET_SessionId | Used to maintain an anonymised user session by the server. | 1 session | No. |
cookie-consent-settings | Used to determine if the user has accepted the cookie consent, contains consent choises | 30 days | No. |
lidc | To promote data center selection | 1 day | Yes, LinkedIn |
li_mc | Used as a temporary cache to avoid database lookups for a member's consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side | 2 years | Yes, LinkedIn |
BIGipServer~EPWS~EPWSWEB103_HTTP_Pool | Determine pool | 1 session | Yes, EPiServer |
These cookies are used to track our visitors across our website. They can be used to build up a profile of search and/or browsing history for every visitor, or to better understand how the user uses the website so that we can improve it. Identifiable or unique data may be collected. Anonymized data may be shared with third parties.
Name | Information about the cookie | Retention period | Disclosure of information to third party |
_fbp | Used by Facebook | 90 days | Yes, Facebook |
AnalyticsSyncHistory | Used by LinkedIn | 30 days | Yes, LinkedIn |
bcookie | browser identification | 2 years | Yes, LinkedIn |
lang | Language preference | 1 session | Yes, LinkedIn |
li_gc | Used to store guests' consent to the use of cookies for non-essential purposes | 2 Years | Yes, linkedIn |
lms_analytics | Used to identify LinkedIn Members in the Designated Countries for analytics | 30 days | Yes, LinkedIn |
_guid | Used to identify a LinkedIn Member for advertising through Google Ads | 30 days | Yes, LinkedIn |
_ga | Used by Google Analytics to identify a visit. | 2 years | Yes, Google gains access to the information collected by the cookie. |
_gid | Used by Google Analytics to identify a visit. | 24 hours | Yes, Google gains access to the information collected by the cookie. |
_gat_gtag_[Property-ID] | Used by Google Analytics to identify if a visitor (web browser) is new or recurrent. | 1 minute | Yes, Google gains access to the information collected by the cookie. |
These cookies are used by third party to track and collect data to be used in advertisment. They can be used to build up a search and/or browsing history for every visitor. Identifiable or unique data may be collected.
Name | Information about the cookie | Retention period | Disclosure of information to third party |
ajn | Used by adnxs for marketing | 90 days | Yes, adnxs |
uuid2 | Used by adnxs for marketing | 90 days | Yes, adnxs |
IDE | Used by Google doubelclick | 2 years | Yes, doubleclick |
_gcl_au | Google adsense | 30 days | Yes, Google |
msd365mkttr | Dynamics marketing | 2 years | Yes, Microsoft |
NID | Google ads optimization | 6 months | Yes, Google |
__Secure-3PAPISID | Builds a profile of website visitor interests | 2 years | Yes, Google |
__Secure-3PAPISID | Builds a profile of website visitor interests | 2 years | Yes, Google |
__Secure-3PAPISID | Builds a profile of website visitor interests | 1 year | Yes, Google |
UserMatchHistory | Sync LinkedIn Ads ID | 30 days | Yes, LinkedIn |
lms_ads | Used to identify LinkedIn Members off LinkedIn in the Designated Countries for advertising | 30 days | Yes, LinkedIn |
Support
Whether you're looking for some
assistance or further information
regarding your solution, we're here
to help. Yes, take me there!
Sweden
Headquarters, Stockholm
Formpipe Software AB
Sveavägen 168, Stockholm
Box 231 31, 104 35 Stockholm
SE – Sverige
Tel: +46 8 555 290 60
Email
Linköping
Gasverksgränd 2, 582 22 Linköping
Tel: +46 8 500 072 25
Email
Västerås
Metallverksgatan 6, 721 30 Västerås
Örebro
Engelbrektsgatan 6, 702 12 Örebro
Denmark
Lautrupvang 1
2750 Ballerup
Tel: +45 3325 6555
Email
Germany
Formpipe Lasernet GmbH
THE SQUAIRE 12
Am Flughafen
60549 Frankfurt am Main
Email
UK, Cambridge
First Floor, Block A, Harston Mill,
Cambridge – CB22 7GG
Tel: +44 1223 872747
Email
UK, Nottingham
Unit 1, Isaac Newton Centre
Nottingham Science Park
Nottingham – NG7 2RH
Tel: +44 115 924 8475
Email
USA
Formpipe, inc.
1200 US Highway 22 E Suite 2000
Bridgewater, NJ 08807
Tel : +1 908 200 7937
Email
Accelerating Change through Banking Digitisation
Banks are entering an era of transformation and evolution. Now more than ever, customers want a quick and easy customer experience, and banks are faced with a challenging decision. Do they upgrade and move away from the comfort of complacency or do they embrace the era of the digital age and accelerate change through the digitisation of their core banking systems?
Ben Saxton, head of Customer Success at Formpipe, recently sat down with Patricia Moore of the financial services arm of DXC Technology on the latest episode of Beyond The Document. The pair discussed the challenges, overheads and opportunities banks face when they approach the digitisation of their core banking systems and how they can harness that to accelerate change.
Below is a full summary of the conversation between Ben and Patricia. Alternatively, if you would like to listen to the podcast, follow the link.
What are the challenges banks face when upgrading and digitising core systems?
Some banks have well established and trusted operational systems which can sometimes date back to the 1990s and early 2000s so they’re trusted, proven and working but they can hold back the modernisation of a bank. Upgrading from these systems can be a true challenge for banks and will often be why many banks are reluctant to digitise their core banking systems.
The first major challenge is taking that initial leap of faith into the digital world because banks have previously never been in such a competitive world. Banks are competing now more than ever against challenger banks, but also in a climate where digital payments are transitioning and becoming quicker.
Another challenge that has started to emerge in the last five to ten years is that banks need to actually build around their core systems. Some smaller tier two or tier three banks have already taken that leap of faith and replaced those core systems. But it's still very difficult for a tier one bank to move because there's so much invested in their core banking system. These systems are often online 365 days a year, 24/7, and if you have a 99.9% uprate, then it's very difficult to move to something that might only have a 97% uprate.
Additionally, the cost of introducing a new digitised system, or moving to one that may not have been used operationally previously, is another challenge banks face. You're potentially concerned that the applications or solutions you want to integrate into your core banking system are delivered by new vendors and you need to vet them… what's their referenceability like? What's it going to be like going forward? Are they going to be bought and therefore the software may stagnate? However, we have seen companies such as Oracle, SAP, and IBM who have been around for 50/60 years. It's a long time for any bank to have worked with these vendors and their systems are proven and reliable.
What potentially can be done for a bank is to highlight that a lot can be upgraded without the need to rip and replace - working with the bank to migrate to their new system slowly, thereby causing little downtime or disruption. An awful lot can be done to core systems to make them even more functional and digitised. For example, creating a ‘single view’ for the customer and delivering a better customer experience with those with accounts, mortgages or loans with that particular bank.
What are the digitisation opportunities for banks and the cloud?
If you go back just over five years, many established banks such as Barclays and HSBC were slightly reticent moving into the cloud until the introduction of ‘born in the cloud’ applications that were essential for banks. Part of this transition was driven by Microsoft with its Dynamics platform, but also with their competitor Salesforce.
With many solution providers becoming cloud born. Banks that wanted a specific application or solution would have to transition into the cloud and then make the decision of how it wanted to host that solution, whether hosted on-premise, with a managed service or through a hybrid of the two.
A lot of the drivers for banks is whether the business solution is cloud based or not. If it is only cloud based, banks have no choice but to migrate into the cloud if that's the business solution they want. Banks have to go for it if that's going to improve their business. If it's one of the more legacy solutions, banks probably still have a choice.
Many core banking systems are starting to move to the cloud, for example, a loan or an e-savings solution. They are things that are now running on the cloud and you build them into your banking processes to fit your requirements.
What are the overheads when banks consider digitisation?
The overheads associated with banking digitisation projects are a challenge. Tools like DevOps in Azure are available for improvement programs making it much easier and less daunting to deliver.
The nature of application development has massively changed partially due to ‘platformification’, which began in 2010. A lot of these companies designed a platform to provide agile development and allowed you to go to a customer, sit in front of them and virtually design their solution. You could look at the business processes and literally drag and drop those processes to build an application seamlessly.
That process is being handled by the core vendors because these were previously the new vendors that were born in the cloud. It is becoming the standard where you can create minimal viable products very quickly, completing a project in stages and in each stage show the business benefits and the user acceptance training.
Banking has moved away from actually engaging with the users when developing products, previously all testing and development was accomplished alongside a user group who then fed back exactly what they thought about the product banks were delivering. But this process is coming back in the 2020s.
Now that there's this massive shift back to completing a project in three to six months and delivering something quickly to the business that is viable, offers the business returns and is accepted by the end users, there is an importance of getting close to the clients. Whether that be a multinational bank or a small mutual in one part of the UK, getting close to the clients and designing the solution that adheres to their needs as well as operating optimally for their end users is becoming an important part of the process. Creating and maintaining that business relationship is essential.