Bank Automation News

No products in the cart.

Subscribe
  • News
  • Data
  • Transactions
  • Events
    • Bank Automation Summit
    • Apply to Speak
    • Apply to Demo
  • Podcast
  • WEBINARS
    • On-Demand Webinar: Emerging fintechs: New technologies you need to know now
    • Webinar Library
Log In
No Result
View All Result
  • AI
  • Business Banking
  • Core
  • Cloud
  • Payments
  • Retail Banking
  • Risk & Security
Bank Automation News
  • News
  • Data
  • Transactions
  • Events
    • Bank Automation Summit
    • Apply to Speak
    • Apply to Demo
  • Podcast
  • WEBINARS
    • On-Demand Webinar: Emerging fintechs: New technologies you need to know now
    • Webinar Library
BAN PLUS
Log In
No Result
View All Result
Bank Automation News
No Result
View All Result

Realtime Banking

Daily FintechbyDaily Fintech
August 7, 2016
in Archive
Reading Time: 6 mins read
0
Share on Facebook

Unstoppable

What happens when an unstoppable force meets an immovable object? The unstoppable force is customer expectation of real time, which we get from using email, text and social media.  We are instant gratification junkies, like Veruca in Willy Wonka “I want it and I want it now”. The immovable force is the batch legacy that derived from IT 1.0 moving from paper systems to computers about half a century ago.

Expect a loud noise! 

Personally I am betting on the unstoppable force. You don’t go far wrong by serving customer needs. If Veruca wants it now, find a way to sell it to her!

First we look at the 5 batch hangovers from paper. Then we look at the responses of different players in the ecosystem.

The 5 batch hangovers from paper

  • LIBOR & other “Fixes”.
  • Quarterly Financial Reporting
  • Daily Accounts Close
  • T+2/3 Securities Settlement
  • Regulatory Reporting

 

LIBOR & other “Fixes”.

Quick word association – LIBOR = scandal (if you want to understand the LIBOR FX scandal, go to this BBC explainer). Another batch “fix” (when a price is fixed for the day in a process dating back pre computers) is for Gold (and other precious metals). The gold fix used to happen in the physical offices of Rothschild and then, in a classic bandaid move, became updated by moving to a teleconference system (this Wikipedia article explains the history). The point is simply that when 21st century real time global trading in FX and precious metals meets a Victorian batch hangover from paper, there is a lot of room for collusion and other illegal activity. The regulatory response so far has been to layer more processes on the banks so that their compliance people can catch the bad traders while they are colluding via phone, email or trading terminal messaging system. Lets apply more bandaid! Bandaid vendors vote for this response.

A more radical response would be to replace the fix with a computed “daily price”. This is technically simple. There are multiple methods (eg. trade weighted average) and banks that need a daily closing price (eg to value a portfolio or an index) can choose which algo they use (all of them would be open source). If one algo gets gamed too much, they can switch to a different one (which will reduce the value of gaming the system). Our trading systems will cope with this quite easily. The problem is which regulator in which country can make this change? This is difficult because it will affect banks and traders in every country.

Quarterly Financial Reporting

Our systems record transactions as they happen. It would be technically simply to apply a filtering process in order to issue an abstract of that data (not so much that it gave away trade secrets) to investors in real time. Instead we have layers of processes to produce a report for investors and regulators on a quarterly basis. Plus we have a whole industry of analysts and media whose job it is to guess the numbers and to manage investors expectation of those numbers.

Core Banking Daily Accounts Close

Little known fact – CORE stands for “centralized online real-time exchange”. What we think of as those old-fashioned legacy systems were disruptive in the 1970s when we moved from paper in bank branches to branches that were connected via a network to a head office where all the accounts were processed by a computer. This allowed branches to exchange account data in real time. The paper systems had been processed quarterly (try doing it any quicker with paper). Core banking systems speeded that up massively by going to daily close. It is still batch – just much faster batch.

In an era when we debate the value of branches vs mobile phone banking, this automation of accounting between branches seems rather quaint.

T+2/3 Securities Settlement

This is where the Ferrari meets the Donkey. We measure trading in fractions of a second. That is the Ferrari. Then we move to Settlement which takes 2 or 3 days (T+2/3 Securities Settlement). This is starting to change, enabled by Blockchain technology (for an analysis of three projects in this area read this post).

Regulatory Reporting

Regulators demand data from banks and traders. In order to not be too intrusive, they only ask for that data in predefined periods – days, weeks, months, quarters, years depending on the data. Banks have to reconcile what they send with what goes to investors and internal management. Any mistake and the fines come pouring in. Pity the poor compliance officer.

What if all the data was streamed in real time (after a suitable filter to protect customer confidentiality and trade secrets)?  Regulators, investors and internal management could all parse the feed to get what they need for their decision support systems.

Responses from different players in the ecosystem

The reason change takes so long is that no single entity can make a decision in isolation. There are too many moving parts and as any deal-maker knows, when there are too many moving parts, nothing happens. Each of these players in the ecosystem have a different response to the unstoppable force of real time.

  • Incumbent Financial Institutions
  • StartUp Neobanks
  • IT Vendors

(Regulators also need to respond but mainly to get rid of the vestiges of Victorian days via daily fixes as described above).

The Incumbent Financial Institution Response

When banks study their legacy systems, which they are maintaining at huge cost, they discover massive overlap with many systems serving exactly the same need. The sensible reaction, to get rid of the overlap, gets crushed by a business group telling IT that their business is utterly reliant on that legacy system and suggesting that any glitch in the conversion would be career suicide for the project manager.  In one case, a system had only one user!

This has to change. The question is how. There are two corporate responses:

  • Lets do a total core system revamp, move everything to real time. It will take years and cost millions but the effect on our agility and sustainable competitive advantage will be a game-changer.
  • Lets bypass the old legacy systems (let IT move them to “end of life maintenance” when the time comes) and simply buy the startups when they get to reasonable scale or partner with startups or other Banks by using Open APIs on top of utility platforms.

The Response of StartUp Banks

StartUp Banks (aka as “challenger banks” or “full stack startup banks” or “neobanks”) are fully regulated Financial Institutions that don’t have any legacy. Its that simple. They can meet Veruca’s demand for real time, because everything they do is in real time. They still need some batch jobs that are designed to serve the needs of investors and regulators, but those batch jobs are simple after the fact reporting; the cart does not drive the horse.

As these StartUp Bank start to get actual market share, it will impact the Incumbent Financial Institution Response (decisions where they assumed they had plenty of time now become a lot more urgent).

IT Vendors

Traditional Fintech is a huge business (see this report, its a few years old but this is not an area of rapid change). It may not be “exciting” but today it is bigger than Emergent Fintech and, done right, it is hugely profitable.

There are three responses:

  • the Banks are locked into our legacy systems and its a massive cash cow, lets milk it for everything it is worth. Private Equity loves this approach as it can service big debt loads.
  • lets be the vendor of choice when the Banks need a transformational move to real time. This is only possible for a few very big vendors. There are not that many deals like this but they are huge.
  • forget about the legacy systems, we are about new systems that “sit on top”. That has been the de facto response for decades. The problem now is that we are reaching the limits of what we can do on top. If we offer a real time response to the customer but the transactional processing is batch, there is room for a lot of error and liability.

Most IT Vendors have a mix of these three responses, but the emphasis and mix varies a lot.

Expect this subject to be debated vigorously in a few weeks time in Geneva when 8,000 bankers and their vendors arrive for the annual gathering of the tribes known as SIBOS. See y’all there.

Daily Fintech Advisers provides strategic consulting to organizations with business and investment interests in Fintech & operates the Fintech Genome P2P Knowledge Network. Bernard Lunn is a Fintech thought-leader.

Tags: Strategic Viewpoint
Previous Post

Blockchain Technology and Smart Contracts for Reinsurance

Next Post

Disney Adds Messaging Service for Kids with Games (and Payments?)

Related Posts

Image by CanStock
Archive

Blend Labs integrates acquisition’s mortgage automation process

August 20, 2021
Photo by CanStock
Archive

Chilean fintech looks for slice of giant money transfers market

August 5, 2021
Image by CanStock
Risk & Security

Listen: How banks can protect themselves against cybersecurity risks

August 3, 2021
Next Post

Disney Adds Messaging Service for Kids with Games (and Payments?)

Please login to join discussion

Stay Informed with Our Newsletters

EMERGING FINTECH DIRECTORY

Emerging Fintech Directory

The Buzz Podcast

RETAIL BANKING

Huntington Bank’s new branch in Spartanburg

Huntington Bank resolves outage

May 7, 2025
bank

Barclays, Banco Santander, Lloyds plan product expansion

May 5, 2025
satisfactiin

Online banks lead FIs in customer satisfaction

May 2, 2025

SPONSORED

Just Released! 2025 Strategy Benchmark

May 1, 2025

Leverage Treasury Management to Turn Fraud Prevention Into a Strategic, Revenue-Generating Opportunity

April 1, 2025

A growth mindset in banking requires AI

March 27, 2025
  • About Us
  • Help Center
  • Contact Us
  • Privacy Terms
  • ADA Compliance
  • Advertise

 Manage Cookie Consent

Connect

twitter linkedin podcast podcast podcast
© 2025 Royal Media
No Result
View All Result
  • NEWS
    • All News
    • AI
    • Business Banking
    • Core
    • Cloud
    • Payments
    • Retail Banking
    • Risk & Security
  • DATA
  • TRANSACTIONS
  • EVENTS
    • Bank Automation Summit
  • PODCAST
  • WEBINARS
    • Upcoming Webinar
    • Webinar Library
  • SUBSCRIBE
  • Log In / Account

Welcome Back!

Login to your account below

Forgotten Password?

Retrieve your password

Please enter your username or email address to reset your password.

Log In
No Result
View All Result
  • NEWS
    • All News
    • AI
    • Business Banking
    • Core
    • Cloud
    • Payments
    • Retail Banking
    • Risk & Security
  • DATA
  • TRANSACTIONS
  • EVENTS
    • Bank Automation Summit
  • PODCAST
  • WEBINARS
    • Upcoming Webinar
    • Webinar Library
  • SUBSCRIBE
  • Log In / Account

THIS WEBSITE USES COOKIES

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “I CONSENT”, you consent to the use of ALL the cookies.

Cookie settingsI CONSENT

Review our Cookie Policies
.
Manage Cookie Consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
__cfruidsessionCloudflare sets this cookie to identify trusted web traffic.
__RequestVerificationTokensessionThis cookie is set by web application built in ASP.NET MVC Technologies. This is an anti-forgery cookie used for preventing cross site request forgery attacks.
_abck1 yearThis cookie is used to detect and defend when a client attempt to replay a cookie.This cookie manages the interaction with online bots and takes the appropriate actions.
34f6831605sessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
a64cedc0bfsessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
ak_bmsc2 hoursThis cookie is used by Akamai to optimize site security by distinguishing between humans and bots
ARRAffinitysessionARRAffinity cookie is set by Azure app service, and allows the service to choose the right instance established by a user to deliver subsequent requests made by that user.
ARRAffinitySameSitesessionThis cookie is set by Windows Azure cloud, and is used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session.
AWSELBsessionAssociated with Amazon Web Services and created by Elastic Load Balancing, AWSELB cookie is used to manage sticky sessions across production servers.
bm_sz4 hoursThis cookie is set by the provider Akamai Bot Manager. This cookie is used to manage the interaction with the online bots. It also helps in fraud preventions
cf_ob_infopastThe cf_ob_info cookie is set by Cloudflare to provide information on HTTP Status Code returned by the origin web server, the Ray ID of the original failed request and the data center serving the traffic.
cf_use_obpastCloudflare sets this cookie to improve page load times and to disallow any security restrictions based on the visitor's IP address.
CONCRETE5sessionThis cookie is set by the provider Concrete5 web content management system. This is a necessary cookie used for maintaining the user session between pages.
connect.sid1 monthThis cookie is used for authentication and for secure log-in. It registers the log-in information.
cookielawinfo-checkbox-advertisement1 yearSet by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
cookiesession11 yearThis cookie is set by the Fortinet firewall. This cookie is used for protecting the website from abuse.
crmcsrsessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
ep20130 minutesThis cookie is set by Wufoo for load balancing, site traffic and preventing site abuse.
JSESSIONIDsessionThe JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application.
LS_CSRF_TOKENsessionCloudflare sets this cookie to track users’ activities across multiple websites. It expires once the browser is closed.
PHPSESSIDsessionThis cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed.
sxa_sitesessionThis cookie is used to identify the webiste visitor's session state across page requests on server.
ts3 yearsPayPal sets this cookie to enable secure transactions through PayPal.
ts_c3 yearsPayPal sets this cookie to make safe payments through PayPal.
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
wordpress_test_cookiesessionThis cookie is used to check if the cookies are enabled on the users' browser.
Functional
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
CookieDurationDescription
__cf_bm30 minutesThis cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_zcsr_tmpsessionZoho sets this cookie for the login function on the website.
663a60c55dsessionThis cookie is related to Zoho (Customer Service) Chatbox
bcookie2 yearsLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID.
bscookie2 yearsLinkedIn sets this cookie to store performed actions on the website.
e188bc05fesessionThis cookie is set in relation to Zoho Campaigns
geosessionThis cookie is used for identifying the geographical location by country of the user.
iamcsrsessionZoho (Customer Support) sets this cookie and is used for tracking visitors (for performance purposes)
langsessionLinkedIn sets this cookie to remember a user's language setting.
languagesessionThis cookie is used to store the language preference of the user.
lidc1 dayLinkedIn sets the lidc cookie to facilitate data center selection.
optimizelyEndUserId1 yearOptimizely uses this cookie to store a visitor's unique identifier which is a combination of a timestamp and a random number. Different variations of web parts are shown to users that optimizes the website's user experience.
tableau_localesessionTableau uses this cookie to determine the preferred language and country-setting of the visitor - This allows the website to show content most relevant to that region and language.
UserMatchHistory1 monthLinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
CookieDurationDescription
AWSELBCORS20 minutesThis cookie is used by Elastic Load Balancing from Amazon Web Services to effectively balance load on the servers.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
CookieDurationDescription
__gads1 year 24 daysThe __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites.
_ga2 yearsThe _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_gcl_au3 monthsProvided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
_gid1 dayInstalled by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
ajs_anonymous_idneverThis cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before.
ajs_group_idneverThis cookie is set by Segment to track visitor usage and events within the website.
ajs_user_idneverThis cookie is set by Segment to help track visitor usage, events, target marketing, and also measure application performance and stability.
browser_id5 yearsThis cookie is used for identifying the visitor browser on re-visit to the website.
CONSENT2 yearsYouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
sid1 yearThe sid cookie contains digitally signed and encrypted records of a user’s Google account ID and most recent sign-in time.
uid1 yearThis is a Google UserID cookie that tracks users across various website segments.
vuid2 yearsVimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website.
WMF-Last-Access1 month 21 hours 5 minutesThis cookie is used to calculate unique devices accessing the website.
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
CookieDurationDescription
_dc_gtm_UA-1038974-41 minuteUsed to help identify the visitors by either age, gender, or interests by DoubleClick - Google Tag Manager.
_fbp3 monthsThis cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.
_pxhdpastUsed by Zoominfo to enhance customer data.
fr3 monthsFacebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.
IDE1 year 24 daysGoogle DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile.
test_cookie15 minutesThe test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
VISITOR_INFO1_LIVE5 months 27 daysA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSCsessionYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devicesneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt-remote-device-idneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt.innertube::nextIdneverThis cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
yt.innertube::requestsneverThis cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
Others
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
CookieDurationDescription
049fc2ef5beb27056b07d9e4c4d13fd3sessionNo description
akaalb_http_misc_subssessionNo description
AnalyticsSyncHistory1 monthNo description
BIGipServermsocu-web-2-rr.webfarm.ms.com.10882sessionNo description
bm_misessionNo description available.
CX_4061522881 yearNo description
DCID20 minutesNo description
debugneverNo description available.
DrupalVisitorMobilesessionNo description available.
ep2033 monthsNo description available.
frbatlanta#langsessionNo description
geo_info1 yearNo description available.
GoogleAdServingTestsessionNo description
li_gc2 yearsNo description
loglevelneverNo description available.
loom_anon_commentsessionNo description available.
loom_referral_videosessionNo description
mkjs_group_idneverNo description available.
mkjs_user_idneverNo description available.
MorganStanley.ClientServ.Common.IPZipAccess.IPZipCookie.DEFAULT_COOKIE_NAMEpastNo description
NSC_us_nbsl-83+63+21+25-91sessionNo description
nyt-a1 yearThis cookie is set by the provider New York Times. This cookie is used for saving the user preferences. It is used in context with video and audio content.
nyt-gdpr6 hoursNo description available.
nyt-purr1 yearNo description available.
OCC_Encrypted_CookiesessionNo description
polleverywhere_session_id14 daysNo description
ppnet_2020sessionNo description available.
ppnet_2777sessionNo description available.
reuters-geosessionNo description
shell#langsessionNo description
smcx_0_last_shown_atsessionNo description available.
tableau_public_negotiated_localesessionNo description available.
vary1 monthNo description
www#langsessionNo description
X-Vive-CountrysessionNo description
xn_uuid1 monthNo description
Save & Accept
Powered by CookieYes Logo