SynapticThe Next Computing Bill
Chapter 10 · Interactive edition

A bank that keeps its mainframe

Follow a proposed correction through the people who can release it. The line an AI service can win sits beside the core licence.

Give the payments desk a receipt for $240 and a customer who cannot see the money. The bank has received the funds. The reference that would ordinarily tell it which account to credit did not survive a change of format. Its books still balance. The sum sits in an account for money received and awaiting allocation. To the customer, the balance that matters is $240 short. To the bank, there are now two jobs. Someone must establish who owns the money. Someone with authority must change what the bank records that it owes each party.

This is an invented case. It has a surprisingly concrete procurement consequence. A supplier can put a fine new screen in front of the payments officer, find the missing reference and prepare both entries. The bank can buy all of that and pay exactly the same annual fee for the software that keeps its books. An investor looking for evidence of the sale in the incumbent's maintenance revenue would be watching the wrong invoice. Start with the purchase the supplier made possible. Which expense would the bank have incurred to resolve the same receipt without it?

The estate behind a single entry

Installed software is unusually easy to overvalue as a prize because the word covers so much. A bank may operate the code, rent the machines from a service provider, license the database from a third company and retain the engineers who wrote its original deposit application. For the next renewal, those are four different negotiations. An operations team can stop paying an agency to work the evening queue. It cannot thereby terminate a perpetual licence that was bought years ago, cancel this year's support agreement or reclaim the salaries of engineers who have already moved to another queue.

There is a defensible, narrower denominator. Futurum's April 2025 forecast, published that July, put calendar 2026 on-premises enterprise applications at $91.8 billion across twelve product segments. Cloud-delivered applications appear separately in the same forecast. An internal banking program written by the bank has no software vendor sale simply by virtue of continuing to run. The figure supplies a scale for a commercial applications business. It leaves unanswered how much the owners of those systems pay to operate them, answer queries about them or keep the next release compatible with them. 26

SAP provides the view from a supplier's books. In the September quarter of 2026 it recorded €147 million in software licence revenue and €2.434 billion in software support revenue. Together that is €2.581 billion, or €10.324 billion at four identical quarters. Support accounted for roughly ninety-four cents of every euro in the quarterly sum. The annualisation is an arithmetic comparison. It makes no allowance for seasonal buying. SAP sells applications to many industries, and its accounts do not identify the installed base at our specimen bank. The example tells a bidder why support deserves its own line in a commercial analysis. 30

The term of that line can outlast several automation pilots. SAP offers mainstream maintenance through the end of 2027 for specified Business Suite 7 core applications and eligible enhancement packages. Its optional extended period through 2030 carries a premium of two percentage points on the maintenance basis. A buyer who puts a new service alongside an eligible installation still has to decide how to support that installation. The working interface that wins the AI pilot may even make the older system easier to retain for another year. In that event the challenger has created value for a supplier it once expected to displace. 64

Where a customer has already done the engineering

In Italy, Gruppo BCC Iccrea connected services outside the bank to banking applications running on its IBM Z infrastructure. IBM's account describes an important detail of the direction of travel. Programs on the mainframe invoked external services through z/OS Connect. The team also sent operational records into the bank's existing Elasticsearch monitoring environment. A person investigating a problem could follow work across the boundary without relying on separate teams to reconstruct each end by hand. The bank retained the core and changed the cost of reaching across it. 60

IBM reports 65 per cent less integration effort in a comparison with alternative technologies. It also describes forty person-days saved annually in incident management and half a full-time equivalent saved in monitoring. These observations refer to different activities. Adding them would require schedules showing whether the same people and hours appeared in both estimates. The account includes a named bank representative and identifies the products the bank used. It gives us no invoice for an AI supplier and no payroll comparison. I take it as evidence that the incumbent can deliver part of the efficiency a challenger might promise in its pitch. 60

This is a serious competing bid. In our bank, an engineer might add the missing reference to the queue with a deterministic lookup. Once the relevant fields have been mapped, ordinary software can assemble the common receipts cheaply. A vendor relying on language interpretation has to find enough difficult but resolvable cases to cover what it charges. Its best trial would include messages that arrived under an earlier format, ambiguous remitter names and receipts for two customers with the same trading name. A trial drawn entirely from the easy queue would establish very little about why the bank needs this particular supplier.

What the machine may read

Put the arrival record, the bank statement and the customer's remittance advice on one desk. The captured amount is $240 on all three. Two documents carry the payment reference. One identifies the intended account. A payments officer can now ask a useful question of an assistant. Which two pieces of evidence link this receipt to this beneficiary, and where in the original documents can I inspect them? A useful answer returns the records together with the proposed match and any inconsistency. A match that relies only on the amount remains in the queue. Other customers can send $240 on the same day.

Payment networks have developed identifiers for this reason. Swift describes a 36-character Unique End-to-end Transaction Reference that accompanies payment instructions on its network and can be carried through the chain to help track and reconcile the payment. The reference travels with the payment. A bank still decides which of its own records corresponds to that payment and whether a proposed internal allocation is authorised. In the exhibit the shortened receipt number is a local specimen identifier. There is no connection to a payment network. 62

The assistant has a copy of the relevant evidence and permission to propose the entry. A bank employee acts as maker by checking the identity, amount, currency and account, then attaching the proposal to the case. Another authorised employee acts as checker. She can return it if a document is missing. The existing posting service accepts her instruction and commits both sides to the bank's journal together. The machine that prepared the evidence has no ledger-writing role in this design. IBM documents that z/OS Connect can expose existing functions through APIs and allow applications on the platform to call out. The identity that may call a particular function, and the circumstances in which it may do so, remain decisions for the institution. 19

Exhibit 24 / Double-entry model

The bank’s double entry

One $240 receipt. Try the second copy, then inspect a reversal. The display follows the bank's liabilities for this receipt alone.

Posting deskSynthetic case L-240
CHECKERC–11✓RECEIPTR–0240DEPOSITS$240CLOSING BALANCEJ–240–AUNAPPLIED$0CLOSING BALANCEJ–240–A

The core writes the paired entries together. The two balances below divide one $240 receipt.

Allocation state

Posted

Unapplied receipts
$0
Customer deposits
$240

The bank owes the same $240 in total. The proposed customer now has the allocation.

Core journal · USD
JournalLiability accountDebitCredit
J-240-AUnapplied receipts$240—
J-240-ACustomer deposits—$240
Posted totals$240$240
Three possible histories of the same receipt · USD
HistoryJournal pairsIn suspenseIn deposits
Allocation posted1$0$240
Receipt repeated1$0$240
Reversal approved2$240$0
Figure 24. The two front registers show the split of one received payment. The rear tray holds the evidence and the brass desk represents the bank's independent approval. Each journal adds equal debits and credits. Repeating a receipt adds no entries. A reversal requires fresh approval. The diagram models an internal held allocation. Interface context
Inspect the case file

Watch the accounts from the bank's side. Money held for its customers is a liability. Debiting the unapplied receipts liability reduces it by $240. Crediting customer deposits increases that liability by $240. The bank still owes the same amount in total. It has changed its record of whom it owes. Neither entry by itself would describe the transaction, and the bank does not release a half-posted journal for someone to complete later. In the exhibit the customer column begins at zero for this receipt alone. It makes no claim about the customer's other deposits or available balance.

When the same receipt arrives twice

Imagine that the posting succeeds and the acknowledgement arrives late. The caseworker's screen still looks open. A second copy of the same receipt then appears. If the desk treated each arrival as new work, the customer would get two credits for one incoming payment. A well-designed core records a stable posting reference and returns the existing result when that same authorised instruction is presented again. Both ledger balances stay where the first posting left them. The history can record another message received without claiming another dollar received. This is a feature of our specimen, which the buyer should require a prospective supplier to demonstrate against its own systems.

Look at the supplier's invoice too. A service priced on accepted corrections can earn one fee here. If it bills the second message or a read-back as another resolution, every interruption becomes a sales opportunity. A buyer could prevent that by defining the billable event as one accepted outcome against a unique case, subject to a stated reopening window. It would also need a rule for genuinely separate receipts made by the same customer for the same amount. A counter so crude that it suppresses the second legitimate payment would introduce another class of complaint. This distinction is worth settling before a volume discount obscures the unit being purchased.

Now let the desk discover that the remittance advice belongs to a different beneficiary. In our specimen the funds remain under an internal hold, and the bank can correct this internal allocation under its agreed procedures. The maker records the new evidence. The checker independently approves a linked reversing journal. The second pair debits customer deposits and credits unapplied receipts. The original pair remains legible with its own time and authorisation. The customer service team can explain which entry appeared first, why the money returned to suspense, and who owns the open investigation. Money already sent onwards or made available under other terms would require a different procedure.

A record that survives the supplier

I would ask the person negotiating the contract to imagine a complaint six months later. A customer has a statement showing the credit and the subsequent debit. The model version has changed. The employees who ran the pilot have moved to other work. The customer asks why their money was moved. A record held only in the supplier's chat history would put the bank in the position of asking permission to read its own decision. A case file that carries durable receipt, evidence, maker, checker and journal references lets an authorised reviewer give a specific answer, even if the service no longer runs.

Exhibit 25 / Audit and cash

What a bank must see before it pays

Reconstruct who could read, who could sign and which entries reached the core. Each specimen selects the same case in the posting desk above.

Case registerLocal time · synthetic
  1. Receipt received

    Bank intake · R-0240

    Incoming amount sits in unapplied receipts. Hold remains active.

  2. Allocation proposed

    Bank maker · M-07 · E-01

    The maker checked the receipt and remittance advice, and attached the two proposed entries.

  3. Allocation posted

    Bank checker / core · J-240-A

    Independent checker approved. The core committed both sides of one journal.

Figure 25. The left-hand register follows the selected specimen in time. Each decision retains its evidence and record reference. A repeat changes the event history. An approved reversal adds a second journal. Identifiers, times and account values are synthetic. Payment reference context · Responsibility under EU DORA
Price the work around the core

12,000 accepted reconciliations a year, five minutes released per case, $50 per overtime hour. The lab asks $9,000 annually and the bank pays $4,000 to qualify the route. Core support and regular payroll stay in both budgets.

Year one · proposed saving
-$500
Year two · proposed saving
+$3,500
Two-year AI fee awarded
$18,000

250 hours of overtime qualify each year. The bank needs an annual fee below $10,500 to save cash over two years. The awarded route saves the bank $3,000.

The reviewer should also be able to reconstruct the decision that was available at the time. A document corrected on Tuesday can make Monday's approval look indefensible, unless the evidence attached to Monday's file has its own version. A trail that preserves the record used on each occasion protects the customer who needs a correction and the employee who acted in accordance with the information then available. It gives a procurement manager something much more valuable than the vendor's general promise of explainability. She can hand a colleague the file and see whether the colleague reaches the same journal and the same two amounts.

There is a legal reason for many European banks to care who can do this after the supplier leaves. Article 28(1)(a) of the EU's Digital Operational Resilience Act keeps covered financial entities responsible for their obligations under the regulation and applicable financial services law when they contract for ICT services. It does not prescribe our particular two-person desk. In this example the checker authorises a posting under the bank's policy, the payments operations manager owns unresolved cases and the bank remains the customer's counterparty. Commercial terms can make a supplier reimburse certain failures. The customer still has a bank to call. 63

A thousand hours and a small cheque

Put a price on the desk. Assume it handles 12,000 comparable reconciliations each year. Suppose that after ordinary improvements to the existing queue, a proposed service still saves a net five minutes of bank effort on each accepted case, including review, returns and support. At constant volume and service quality that releases 60,000 minutes, or 1,000 hours. A schedule reconstructed from the roster shows that a quarter of those hours would have incurred overtime at an incremental cash cost of $50 an hour. The other 750 fall within salaries the bank has committed to pay. On these assumptions the expense it can remove is $12,500 per year.

The lab asks $9,000 annually for the workflow, equivalent to seventy-five cents per accepted case at this volume. The bank expects to pay another $4,000 once to qualify access and test the integration, with no further increase in access charges. Its core licence, maintenance and ordinary staff payroll continue on both routes. In the first year the bank spends $13,000 to avoid $12,500. In the second it spends $9,000 to avoid $12,500. At the end of two years the lab has billed $18,000 and, ignoring discounting, tax and any change in volumes, the bank is $3,000 ahead in cash. These are proposed terms and an illustrative award, conditional on the bank agreeing to fund the first-year shortfall.

Change the purchase order by a single word. Make the $4,000 access and test charge annual. The bank now loses $500 in each year. If it awards only contracts that save cash within two years, the lab at this price gets no sale. If payments management values shorter customer waits, it could still fund the service and write that objective next to the cost. A bank that promises shorter waits should measure the time from receipt to corrected customer balance, including the time a case spends waiting for a checker. Measuring only the seconds to prepare a draft would make it easy to deliver the wrong improvement.

There is a limit to the lab's bargaining power even if the trial goes well. Over two years the roster releases $25,000. A one-time qualification expense leaves $21,000 for a supplier at buyer indifference. That is $10,500 a year, or 87.5 cents a case. If qualification recurs, the ceiling drops to $8,500 a year. Within the first ceiling the lab still has to pay for model calls, its support desk and any rework it has promised to absorb. Until the supplier supplies those costs, the $18,000 on its two invoices measures revenue. The bank's success on the overtime budget tells us nothing definitive about the return to the lab's shareholders.

The upside is just as instructive. If one more quarter of the hours replaces overtime on the same terms, the removable expense doubles to $25,000 per year. The AI fee stays at $9,000 unless the supplier can renegotiate. The bank keeps most of the improvement. If released hours instead go into investigating older cases, depositors may obtain long-awaited corrections without any reduction in this year's payroll. Both outcomes could justify the work. Only one puts substantially more cash into the next negotiation. Ask who owns the roster before accepting a business case priced at a thousand hours times an average salary.

The offer at the next renewal

A technically sound replacement can still impose large costs on customers. In April 2018 TSB transferred its data to a new platform. The regulator found that customers then had difficulty obtaining service across channels. Its final notice records 225,492 complaints between 22 April 2018 and 7 April 2019 and £32,705,762 paid through the redress programme. The episode concerns a particular migration and its governance. It supplies neither a failure rate for mainframe replacements nor a price for introducing an assistant. It does explain why the manager responsible for deposits might reasonably insist on a reversible trial before committing the entire book. 61

I would start the commercial comparison at a branch that handles both common receipts and disputed ones. Give the existing team time to improve its matching rules. Have the prospective supplier prepare evidence in parallel on a defined sample. Release the incumbent queue or overtime booking only after the bank observes the same accurate closures, stable reopening rates and acceptable waits through a demanding settlement period. Include the time needed to handle a service outage and hand the queue back to staff. Then ask the incumbent to price its own version of the improvement. Its knowledge of the bank's existing records may buy it a shorter implementation, even if its model costs more to run.

The rates in this chapter give the challenger a credible route into an old estate. They also give us an unusually clear way of recording a loss. A signed workflow subscription alongside continuing maintenance establishes a sale into the bank's operating budget. A reduction in the incumbent's maintenance invoice for the same scope would establish a different achievement. A faster demonstration with no change to the order book establishes neither. At this bank the earliest sign of an industrial shift may be a modest overtime line that disappears from the payments manager's budget. To learn who captured it, turn the page of the accounts until you find the new payee.

Sources and reading notes

  1. 19 · IBM z/OS Connect

    API access to existing mainframe applications. Example architecture requires client authorisation and testing.

  2. 26 · Futurum, enterprise applications market, H1 2025 edition

    Table 2, April 2025 forecast vintage. 2026 forecasts $323.3bn SaaS and $91.8bn on-premises enterprise applications. Excludes many infrastructure and middleware categories.

  3. 30 · SAP Q3 2026 consolidated results

    Table A.1, EUR millions. €2.581bn software licences and support. Vendor revenue category is a proxy for exposure to installed software.

  4. 60 · Gruppo BCC Iccrea integration, IBM customer study

    IBM describes an Italian banking group's existing core invoking external services and its monitoring integration. The supplier reports a 65% reduction in integration effort, 40 person-days annually for incident management and half an FTE for monitoring. No matched invoices, payroll or AI attribution.

  5. 61 · FCA final notice to TSB Bank plc, 2022

    Paragraphs 6.8–6.12 document service disruption, 225,492 complaints and £32,705,762 redress following the 2018 migration. This is a named operational failure, with no general estimate of migration or AI risk.

  6. 62 · Swift on the Unique End-to-end Transaction Reference

    A 36-character payment reference travels along the chain. It aids tracing and reconciliation. Our specimen's local case and journal references are invented and use a different format.

  7. 63 · EU Digital Operational Resilience Act, Regulation 2022/2554

    Article 28(1)(a) preserves the covered financial entity's responsibility for its obligations when it uses third-party ICT. The illustrative maker and checker are a local design choice.

  8. 64 · SAP Business Suite 7 maintenance strategy

    Mainstream maintenance through 2027 for specified core applications and enhancement packages. Optional extended maintenance in 2028–30 adds two percentage points to the maintenance basis. Different products and versions have different terms.