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

Vendor Management Considerations in an Acquisition Environment

GonzoBankerbyGonzoBanker
January 3, 2013
in Archive
Reading Time: 6 mins read
0
Share on Facebook

130103aThe CEO of almost every bank we talk to is either looking to sell or has his/her eyes open for the right acquisition opportunity. While things have slowed down from where they were during our recent “troubled bank” period, most bank decision makers feel there is further consolidation coming. It’s a rare CEO that isn’t getting a regular diet of exploratory “buy” or “sell” calls, and with a boatload of investor money continuing to be made available, bank CEOs are feeling the need to prepare their banks to take on another bank – whether or not they really want to.

So how does this play into vendor management? Consider this Reader’s Digest condensed “real-life” example:

Neighborhood Bank is pursuing acquisition of Corner Bank. Following a review by representatives from both banks’ I.T. and Operations departments of all of Corner Bank’s third party agreements, the merger is approved and the integration begins. Before long, Neighborhood Bank’s CFO gets that dreaded call: “We have a problem. We just learned from Corner Bank’s vendor that someone at the bank signed a seven-year agreement right before the merger became final. The buyout is $___ million.” Before even getting started, Neighborhood Bank kisses its first and/or second quarter profits goodbye. The bank’s board of directors is a bit troubled by this, and all of a sudden the CFO’s priorities shift to a new focus on vendor management.

We have seen this happen countless times with various price tags attached. Many CEOs have heard the stories, and they’ve prepared themselves for the possibility of this phenomenon with a typical knee-jerk reaction of cautioning staff to enter into very short agreements. We would like to recommend a more detailed direction that includes some best practices on both sides of the “acquisition fence.”

130103bThe Acquirer

As an acquirer starts to look at an acquisition opportunity, it will be calculating the earnings potential of the consolidated bank. To do this, it needs a birds-eye view of ongoing revenue from the combined institutions, the ongoing expenses, and the one-time expenses associated with the integration. The acquiring bank can look to its existing vendors to determine what its ongoing expenses will be, but it needs to look at the target bank’s contracts to know what the one-time expenses associated with setting aside those agreements will be.

With some careful consideration and the adoption of a number of tried-and-true best practices, an acquiring bank can minimize the likelihood of show-stopper contract surprises. Our recommendations follow:

  1. The acquiring bank must look at the target bank’s existing third party agreements with the same care that it would use to look at loan quality. The CFO should get a list of what each vendor has been paid for the last year and identify the vendors with the highest spending. To determine the key vendors, the CFO should use the 80/20 rule to take the 20 percent of the vendors with 80 percent of spending.
  2. The due diligence team should obtain copies of each agreement associated with the key vendors identified. If the target bank is unable to provide these, it absolutely must retrieve them from the vendors. This has been the single biggest “miss” that we have found in our review of the deals that went bad, i.e., the target bank could not provide the agreements, the decision making was far along and fast paced, and the acquiring bank decided to proceed with the acquisition without reviewing the agreements.
  3. Once found, the agreements and the current invoices should be reviewed by the individuals who have been responsible for negotiating similar agreements at the acquiring bank. If James down in card processing has been renegotiating the debit processing agreement for the bank for the last two decades, it is James – not the CAO, the COO or the CIO – who should be reviewing the target bank’s debit processing agreement and invoices.
  4. The liquidated damages should be estimated for each of these agreements. The best way to obtain a liquidated damages estimate is for the target bank to ask the vendor account rep to provide one. We totally get how confidential the process needs to be during the due diligence process. However, we would submit that there is no need to tell the account rep why the bank is asking for the quote. The vendor’s job is to provide this type of basic information, and they are getting many similar requests these days. Second best method is to do the calculations in-house and then validate with the vendors at the earliest opportunity.

As the due diligence team goes through the process of deciding what systems and services the combined institution will use, they will have at their fingertips the potential ongoing and one-time costs associated with the target bank. Decision making will be improved and surprises will be minimized.

130103cThe Target Bank

A note of caution: a bank’s long-term third party agreements can make it unattractive to potential suitors. Banks that may be in play for an acquisition should have an organized plan for managing these vendor agreements. Our recommendations:

  1. The bank with an awareness of standard contract term lengths stands a better chance of obtaining competitive pricing. For most of the major services (core, Internet banking, debit processing, mortgage servicing, etc.), this would be three to five years, with five being the more commonplace. The bank should stick with these standards and focus on getting “best in land” pricing. Going shorter on term and paying two times market is not going to make for a more attractive partner. The reason? The liquidated damages can often be higher for a bank that is going short on term and paying premium pricing for that privilege.
  2. The right vendor/services coupled with the best pricing in the land can make a target bank more desirable to a suitor. They can also increase the odds that during integration, the bank’s systems will be the survivor or at least considered for the consolidated bank’s business. There is value associated with a good long term agreement just like there is with a good lease of a branch.
  3. Even if approached tomorrow for a merger, there will be a significant time period from the point of initial approach to when the agreements will be terminated following full integration. This time period needs to be taken into account when looking at potential term lengths for agreements. We suggest reserving 12 to 18 months for the total integration time period depending on the acquirer’s skills and experience in integrating acquisitions.
  4. A bank that stands to be sold during the term of an agreement should negotiate heavily on termination penalties. It should also try to get a declining scale for liquidated damages in the latter years of the agreement.
  5. De-conversion costs should be clearly defined in the agreement. This will paint a clear picture of what an acquirer would need to pay to move the bank to its systems.
  6. The bank’s vendor owners/negotiators should all follow the same strategy for negotiating with the vendors regarding length of term and ability to execute agreements. All it takes is one person to go long on a bad agreement to make a big negative difference.
  7. All of the bank’s agreements should be packaged and ready for a good due diligence look. This would include the master agreement and all addendums for each of the key vendors. While this is a good habit to get into anyway, it is extremely important that this step be completed prior to the start of serious discussions.

These tips and techniques were presented with the intent of helping management teams understand the different activities that take place during a potential or realized merger opportunity. Our goal is to help banks get all of the systems and third party agreements integrated without fanfare so they can concentrate on the really hard part of the integration – i.e., the people side.
-ber


Managing vendors is serious business

Whether inventorying your infrastructure, assessing your current vendor relationships or looking to choose a new data processing system provider, you can count on Cornerstone Advisors’ unmatched vendor experience to guide you in making educated technology decisions.

From systems evaluation to vendor selection to contract negotiation to conversion oversight, Cornerstone has done it all – and we’ve done it many, many times.

And we take it very, very seriously.

Tell us your needs and we’ll talk.

Cornerstone-logo

Tags: Best PracticesVendor Buzz
Previous Post

Bank Innovation TV: Banking By Design from Union Bank

Next Post

Jobs Calculator Updated with Employment Data, Revisions

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

Jobs Calculator Updated with Employment Data, Revisions

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