The Bank Sees an Account, Vendors See Income - 228 Potential Cost Points, Click to Purge
BackPocketCIO Mapped 228 Potential Cost Points From Click to Purge |
Not every vendor charges every fee (yet), but your bank has the most leverage to lock down these costs before signing the contract. |
“We need more accounts” is one of banking’s great, agreeable sentences. The board nods. Marketing sees a goal. The branch sees activity. Treasury sees deposits. Nobody has to call legal. The sentence is not wrong. It is simply missing its more expensive half:
What does each additional account ask the institution and its vendor stack to do, and what do all those actions cost?
A new account does not arrive alone. Before the customer sees a balance, the path may include a paid click, a form, an application, an API call, an identity check, a text message, a funding transaction, a disclosure, a customer record, a card order and a digital enrollment.
Then the account begins generating statements, logins, payments, alerts, fraud signals, data feeds, support work and storage. Someday it may also generate a renewal question, a deconversion file, a retention obligation and a purge.
The bank celebrates one relationship. The vendor stack may have already heard a dozen little meters click.
That is not an accusation. Vendors should be paid for technology that works and service that helps. A fraud check is not waste because it has a price. A payment rail is not suspicious because it has a meter. The problem is not that the commercial model exists.
The problem is that the vendor usually has a clearer view of its model than the bank has of the account’s full external economics.
Every Invoice
Can Be Right
This is where capable people get handed an impossible picture and then blamed for not seeing the whole thing.
Finance sees invoices. Technology sees platforms. Operations sees work queues and exceptions. Compliance sees controls. Marketing sees acquisition. Vendor management sees agreements. Each group may be doing its job well. The customer opened one account.
Every invoice can be correct while the combined picture is incomplete.
Contract terms have a way of rewarding the person who keeps reading.
That is how a digital migration can reduce branch touches while adding authentication, data, messaging, platform and support expense. Faster onboarding can still produce abandoned applications; verification retries and duplicate records. More volume can improve fixed-cost absorption.
The ordinary reports will not necessarily expose the difference. Contracts price users, items, messages, API calls, cases, gigabytes, environments, hours and monthly minimums. Nobody has ever left a budget meeting inspired by an “API call”.
If nobody at the bank can name the unit and the owner, the vendor's billing system is in charge, not the Bank.
This is not a staff failure. The institution divided itself into manageable pieces. The pieces became manageable. The economics did not volunteer to reassemble themselves.
The Four Economic Zones |  |
Acquire and Open
The first 61 potential points sit across acquisition, application, verification, funding and opening. This is where trouble begins. Cost per application started is not cost per successfully funded account. An abandoned application may still have created a click, form event, API call, identity check and message. A duplicate may be disappointing to the growth report and perfectly real to a usage meter.
Serve and Transact
The next 73 points cover service, payments, cards and digital access. This is the largest zone, and it explains why a quiet account is not always a free account. Statements, archives, online access, alerts, minimums, storage and support can continue even when transaction volume is low. Digital activity also changes the shape of the work. A payment that sails through may cost little and consume no staff time. An exception can touch a processor, a fraud tool, a case system, a message service and an employee who still has six other things open. The customer sees one transaction. The institution may inherit a small family reunion.
Protect and Connect
Another 61 potential points sit in risk, compliance, data, interfaces, treasury and lending. These costs are often parked in enterprise overhead, which is understandable and occasionally convenient. Accounts nevertheless create the records, alerts, cases and data volumes those systems process.
Cost discipline here must not become code for weakening controls. The useful question is not, “Can we stop screening?” It is, “Which tools are doing what work, where do they overlap, what event drives cost and what evidence shows the control is working?” Paying twice for useful protection is still paying twice. Paying once for a control nobody can explain is not automatically thriftier.
Support Change and Exit
The final 33 potential points are easy to ignore because growth plans tend to face forward. Support hours, professional services, testing, training, custom work, renewal uplifts, holdover terms, dual processing, data egress and deconversion do not fit neatly into the opening celebration.
The account may be closed while the meter is still running. A fee discovered after signature is still a fee. It has simply lost all interest in being negotiated.
Measure Growth With Both Eyes Open
When BackPocketCIO helps negotiate a new core contract or renegotiate an existing one, we check potential cost points. We sort what is irrelevant, what is bundled, what is metered, what is minimum-bound, what escalates and what can be negotiated.
We do not assume every point is a fee. Vendors know which events create revenue, and their billing systems rarely suffer from institutional memory loss.
“We need more accounts” may still be exactly right. Finish the thought: We need more accounts at a lifecycle cost we can explain, with work our people can absorb and a price point we are willing to own.
Comments