Jack Henry’s Deposit Plan: Where Does the Money Stay?

SG Group View: retained deposits matter through banks’ use of funds

Jack Henry announced planned Google Cloud Universal Ledger (GCUL) deposit-tokenization integration on 16 October 2026.^[1] Google’s August Preview documentation distinguishes off-ledger tracking from authoritative pool allocation. The announcement selects neither.^[2]

SG Group sees what the record establishes about funds allocation as the starting point for assessing costs at each bank. Retaining a deposit relationship need not leave resources available for other uses in the same form. Reading expanded payment capabilities alongside the funds needed to sustain them makes the route to regional-bank competition and business finance more concrete.

Separate customers’ deposits from the assets a bank holds

The deposit balance in a bank’s app represents the customer’s claim on the bank. On the other side are assets the bank holds or obtains to meet payments. The BIS distinguishes commercial-bank deposits from the central bank money supporting interbank settlement.^[3] A customer-facing balance alone does not reveal where the bank has placed its assets.

Consider two hypothetical banks handling the same amount of deposits for comparable customers. One places more payment resources in a single arrangement; the other distributes them across several payment methods. Identical customer balances can coexist with different preparations for other payments and different work to move funds again. This comparison is not an accounting description of a particular service. It illustrates why liabilities and assets should not be counted as the same thing.

In tracing where resources sit, distinguish ownership by the bank as a whole from immediate availability for a particular use. Even a right to receive funds back can leave a need for other resources if procedures or conditions delay their actual movement. Changes in funds placement require attention to both total amounts and availability.

This distinction also helps when reading connections between the financial statements. If a bank’s obligations to customers remain unchanged while its asset composition changes, comparing totals alone can miss the transaction’s significance. Assessing retained deposits requires asking what the bank holds against them and where it can move those resources.

Matching numbers can serve different authoritative roles

Authoritative here means a technical or operational reference for handling allocations. The description alone does not determine how a court would assess rights or rank claims in insolvency. Legal effects depend on separate rules and contracts; they cannot be inferred from the terminology of a technical specification.

The distinction becomes most visible when update sequences diverge. When a recipient prepares its next payment, which record supports the available amount? Must it wait for reconciliation to finish, or can it proceed under specified conditions? That choice affects business waiting times and banks’ preparation of resources.

Collecting information in one place does not resolve this by itself. Participants also need arrangements for who can correct records, how to handle payments made using a previous allocation, and what other participants must be told. Operational agreements stand between sharing more numbers and being able to act on them together.

Avoid counting a record change and a funds reallocation twice

Assessing economic effects requires a consistent perimeter for what has moved. Several record updates accompanying one payment do not create the same amount of money several times. Changes to a customer display, a bank’s internal books and allocations among participants can be different views of one sequence of transactions.

Conversely, a shared record does not necessarily unite ownership, custody and conditions of use. The convenience of a single display and the freedom to deploy assets for one purpose require separate assessment. An arrangement might change how resources are used without increasing the total the bank manages.

For a comparison at the individual-payment level, trace whose available amount falls and whose rises between the start and finish. At the whole-bank level, do not assume the same funds can serve multiple purposes simultaneously. Before adding balances across payment methods, check whether separate records represent the same entitlement.

When one record follows another, where does reconciliation occur?

Consider an arrangement with separate records for authoritative funds information and the balances users employ for payments. Until both updates finish, an operator must distinguish an ordinary transaction in progress from an error requiring correction. A delay and a loss of record reliability are not the same event.

Value in this arrangement comes from more than faster reconciliation. Knowing which transactions a figure includes lets a receiving bank anticipate the remaining processing and prepare. Matching timestamps alone is insufficient if the transaction populations differ. The time of the figure and the scope of transactions it covers need to travel together.

For a corporate treasurer, the issue is the interval between notification of a receipt and being able to use it for another payment. A bank using its own funds to bridge that interval can shorten the customer’s wait while assuming a burden itself. Waiting instead affects the business’s payment sequence and cash cushion.

Reconciliation savings therefore cannot be assessed solely through a department’s transaction count. Costs move differently depending on whether the bank absorbs the waiting interval or the business prepares separate funds to avoid waiting. Compare improvements in processing time alongside changes in who bears the burden.

Sharing the allocation reference changes the order of checks

A common allocation reference could remove a stage of waiting for confirmation that another participant’s internal records have changed. Eliminating part of the exchange in which information is received, entered into a local balance and reported back may accelerate customer notifications and subsequent processing.

But a shared reference makes the conditions for updating it more consequential. Whose approval changes an allocation, which state is used if processing stops partway through, and how corrections are communicated can affect several banks together. Less back-and-forth verification places greater weight on participation conditions and change procedures.

The economic comparison is between the cost of checks repeated at individual banks and the cost of maintaining a common reference. More participants do not guarantee larger net benefits. Extensive individual work connecting different internal processes to that reference can grow alongside participation.

The useful outcome is how much sooner recipients can proceed, rather than the mere existence of a shared record. Removing one interbank reconciliation step may leave final payment timing unchanged if a business’s internal approval process stays the same. Identifying where an improvement stops makes the infrastructure’s benefits measurable within a concrete scope.

Customer service and a bank’s allocation are different objects

Continuing to provide a convenient payment service is compatible with changing where a bank places funds. Customers benefit from not needing to change banks, but their continuity does not establish that the bank holds the same assets as before.

Suppose a bank commits resources to a common payment arrangement and uses an allocation within it. The bank may keep the customer-facing relationship while accepting different conditions for some resources. Whether funds have moved from their original location and whether the customer relationship remains can have separate answers.

Custody location alone is insufficient for assessment. Resources held in the same place can offer different choices if their permitted uses change. Conversely, a change of location might impose little practical constraint if dependable means allow funds to return when needed. Read location, rights and conditions for action together.

A binary question about whether the bank’s money stays or disappears obscures the nature of the change. Its value to the bank lies in the services those resources support and the room to choose other uses. Compare both income from continued customer use and the deployment of assets sustaining that relationship.

The benefit of placing funds and the cost of forgoing another use

Funds held ready for payments are not necessarily wasted merely because they sit unused for a time. The ability to meet customer instructions and reach more recipients has value. A bank’s comparison is between that value and the benefit of deploying the same resources elsewhere.

Interest alone may not capture the comparison. Procedures needed to retrieve funds, room to meet unexpected requests and treatment of unused capacity can also affect costs. An option yielding more in ordinary conditions may require additional funding if resources cannot be moved when needed.

Changes in interest rates can alter the opportunity cost of an unchanged allocation. As with the transmission of rates to households and businesses, effects run through assets held and funding terms. There is no simple rule that service charges change in proportion to a policy-rate move. Alternative uses available to the bank and the functions customers purchase stand in between.

Banks also have different payment profiles. A few large transactions may call for different preparations from many small, dispersed ones. Equal total value need not imply an identical allocation needed temporarily. Sharing a service does not mean participating banks will place funds in the same way.

How does a bank expand usable capacity before payments grow?

When new customers begin using a service, spare processing capacity and spare payment resources need not expand together. More transactions can be processed while banks still have to decide what allocation to provide. Announcements of growing registrations do not directly establish growth in the capacity to supply payments.

Compare, as operating choices, preparing extra room in advance and adding it when demand appears. The former may make customer instructions easier to meet while keeping unused resources committed for longer. The latter can shorten that period but makes the procedures for expansion consequential when demand concentrates. Who has authority to add resources, and what information that decision uses, affects practical usability.

What the bank promises customers also influences the choice. A narrow purpose might make preparations easier to estimate. Broader uses require allowing for customers deploying funds at unexpected times. Between the number of payment functions and the range a bank can reliably support sit funds allocation and operational decisions.

Banks receiving funds and banks whose payments leave first

Suppose customers of one bank receive more funds while those of another concentrate their payments earlier. Even with the same tariff and infrastructure, the banks may want to replenish allocations at different times. A bank receiving first may have more room to support subsequent payments. A bank paying first must prepare for the interval even if it expects receipts later.

This is not a ranking based solely on end-of-day differences. A bank normally receiving more may see flows reverse around its customers’ tax or purchasing dates. Net receipts over a period and spare resources at the required moment are different properties. Demand for usable allocations connects to customers’ business cycles.

If banks holding more resources can make them available to others in some form, spare capacity could be shared. The provider would then need to consider compensation and conditions for retrieving it. This does not assert such a mechanism in actual GCUL contracts. It identifies conditions for evaluating ways to address uneven allocations.

To assess effects on regional banks, follow both participation and the distribution of burdens among participating institutions. Convenient shared infrastructure could still concentrate preparation at banks whose customers pay first, affecting charges or customer selection. One possible path reduces competition for deposits while making negotiation over access to allocations more consequential.

The value of being able to retrieve committed funds

The ability to retrieve resources when needed can matter as much as the amount committed. Identical rights of return can coexist with different times at which a bank can use funds elsewhere, depending on deadlines, approvals and payments already in progress. Ordinary retrieval and urgent movement may have different conditions.

If participants can share unused capacity, one bank’s withdrawal could affect another’s preparations. Where allocations are separately reserved, another bank’s available amount need not fall in the same way. Assess withdrawal through who can use each allocation, rather than the label common pool.

Advance notification of retrieval, for example, might help remaining participants prepare but requires the withdrawing bank to decide sooner. A short waiting period would distribute convenience and stability differently. No single condition is best irrespective of customer payment cycles and alternative funding. A separate case of managing institutional cash balances over time appears in the analysis of MAS cash-balance averaging and counting limits. Those regulatory rules are distinct from the operating allocations considered here.

Businesses need the ability to pay next, beyond a receipt on screen

Suppose a wholesaler places orders after receiving customer payments. Earlier bank notification leaves ordering time unchanged if the wholesaler must still wait to use the funds. An earlier determination of availability might allow a different ordering or shipping sequence. But unchanged supplier payment options or contractual deadlines can stop a bank-level improvement from advancing the whole process.

Assessing business effects therefore benefits from separate measures for receipt notification, reuse of funds and actual ordering or payment times. Customers reporting greater convenience and customers needing smaller cash cushions are different outcomes. Both can be valuable, but the intermediate steps connect a bank’s improvement to working-capital effects.

A low transfer fee does not establish low preparation costs

A clearly lower per-transfer fee makes a service easier for businesses to compare. But the resources banks must prepare, and their conditions, create costs separate from processing each transfer. Comparing only visible fees can miss preparations needed even in periods of low use.

Banks could allocate those costs through usage charges, fixed service fees, or terms involving balances and broader relationships. Customers sending the same amounts equally often may impose different burdens if one has predictable timing and another frequently gives unexpected instructions. An average transaction price can conceal differences in usage.

Alongside quoted prices, companies should compare how they can move unused resources and change arrangements. If lower fees require funds to remain committed longer, alternative uses forgone belong in the comparison. This does not predict actual pricing terms; it offers a way to read future tariffs.

Who can proceed when records disagree?

Suppose banks using a common allocation disagree about whether a transaction has been reflected. One regards funds as available; another considers processing unfinished. The choice extends beyond stopping every transaction. Identifying the affected resources and payments may allow unrelated work to continue.

Proceeding without a sufficiently narrow scope can, however, widen the corrections needed later. The benefit of moving quickly can conflict with keeping the correction perimeter small. Customers also need usable explanations: banks might continue processing while a business still cannot tell whether it should proceed with its own payment.

The organization responsible for the cause and the organization explaining matters to customers may face different burdens. A bank retaining the customer relationship is likely to handle inquiries even about shared components. After a technical correction, customers may still need to rearrange plans. Counts of successful ordinary transactions do not measure that continuing work.

Useful comparisons cover the sequence from discovery to confirmed allocation, the boundary around affected transactions, and customer notification. Clear arrangements can help prevent a single discrepancy from spreading uncertainty over the entire service. Shared records affect both speed on uneventful days and treatment of disagreements.

When can retained deposits support lending capacity?

It is premature to infer that every retained deposit translates into additional lending. Changes in resources placed for payments, other funding such as borrowing, and desired credit risk can alter lending decisions despite identical deposit balances. Retaining a relationship is not a sufficient condition for credit expansion.

The transmission becomes stronger if customers continue using the bank and the resulting income or funding stability outweighs additional preparation costs. Greater room could widen the bank’s choices over lending terms or service investment. Where it deploys that room also depends on borrowers’ demand and credit quality.

If supporting new payments requires costly resource preparation, a bank could instead revise charges or limit uses. Keeping customers can be valuable without making unlimited provision on identical terms viable for every user.

The explanation of why bank lending conditions can diverge from the policy rate offers useful background for market transmission. Following changes in funding, banks’ decisions and business investment in sequence avoids jumping straight from a technology announcement to lending volumes or stock prices.

What should be compared with existing instant payments?

The Federal Reserve describes FedNow as settling individual payments around the clock through depository institutions’ central bank accounts.^[4] Operation at night or over weekends is therefore insufficient by itself to establish a benefit unique to deposit tokenization.

Compare the work banks and businesses perform to complete the same payment. If existing methods are sufficient, maintaining another connection needs improvements worth its cost. Linking processing to a subsequent transaction or reducing inquiries through shared allocations could still create value even where individual transfer speeds are similar.

Compare operating hours, recipient reach, funding preparations and exception handling on consistent terms. Prices for a broadly capable arrangement and a narrowly purposed one do not automatically cover the same work. Identifying what is replaced and what is added makes actual benefits easier to assess than technology names do.

International effects depend on where resources can be reused

International businesses need not complete their work through a single bank or payment method. When receipts in one arrangement fund payments in another, the stages at which conditions change matter. A cross-border label does not establish that the work of reallocating resources disappears.

Even a readily usable domestic allocation might require another currency or contract for an overseas supplier. The cost of currency conversion differs from the cost of making resources available before and after it. International efficiency depends on how far the same resources can continue to be used and where separate preparations begin.

Three developments distribute benefits differently

In the first development, less work is needed to establish allocations and proceed to the next payment, allowing both banks and businesses to reduce separate buffers. Shared records translate into reduced preparation. Evidence would include changes in funds held elsewhere and time spent on inquiries, alongside payment counts.

In the second, service reach expands while banks continue committing substantial resources. Businesses gain convenience, but banks must recover maintenance costs. How those costs reach charges or deposit terms changes how much of the benefit businesses retain. Growing use and improved funding efficiency are not the same outcome.

In the third, particular businesses or payments obtain high value while other uses remain with existing methods. This is not necessarily failure. Limited adoption can be viable where resource cycles and recipient requirements fit. Defining success only as widespread adoption would miss practical improvements for selected uses.

No probabilities are assigned to these developments. Assessing which is emerging requires combining banks’ placements of funds, businesses’ backup arrangements and changes in cost allocation, rather than relying on user counts. The guide to building scenarios from assumptions and contrary evidence can help organize what subsequent information would change each interpretation.

Consider the argument that sharing information is enough

A strong objection is that faster, more accurate information sharing can deliver much of the benefit without changing where funds sit. If businesses mainly struggle to locate payments, clearer status information alone can reduce calls and interrupted work. Moving resources into a common arrangement might add little.

This argument is strongest where funding is ample and communication or reconciliation causes the wait. If companies’ buffers remain unchanged after records are shared while inquiries decline, information improvement would be the principal benefit. That need not be a small achievement; it identifies where the benefit arose.

If information arrives quickly but available amounts remain insufficient, and the next payment waits for a bank to move resources, sharing records alone has limits. There may be room to alter funds placement and conditions for using allocations. Examining the stage at which processing stops can test which explanation fits.

A further objection is that improving a few uses with existing methods could cost less than broad migration. This comparison matters where connection and transition expenses arise first. Assess initial and ongoing costs against the work actually replaced, without counting all prospective use as profit in advance.

Read the relationship between funds and records before adoption totals

The first relationship to seek in subsequent disclosures is what participating banks commit and what they can retrieve. Identifying the reference record, how availability is determined and conditions for returning funds would help explain different costs at banks with equal activity.

Technical allocations do not establish customer-facing legal obligations, deposit protection or accounting treatment. Evidence is needed about the relationship between contracting parties and funds-management roles. Understanding infrastructure design and understanding rights under a particular financial product each require their own basis.

Then examine changes in resources placed for adoption and resources retained in other payment methods. More specific descriptions of actual experience could show whether another access point was added or underlying preparation changed. Reading available functions alongside the customers and uses covered helps identify that change.

Final assessment: look beyond the deposit balance to usable resources

Assessing what the plan could mean for banking competition requires examining how banks support the new functions they offer customers. The practical question is whether the benefit of retaining relationships justifies the cost of placing resources.

A common allocation reference could change reconciliation between banks and businesses’ next payments. The effect emerges in moving from shared numbers to what resources those numbers allow participants to use. Following changes in banks’ burdens and companies’ preparations connects technical novelty to economic value.