The announcement
On November 5, Huntington announced Intelligent Treasury, developed with Kyriba. The bank describes consolidated balances and transactions across connected banks, cash forecasting, ERP connectivity, supported payments and payment acknowledgements. Fees, adoption and measured customer benefits were undisclosed. B(ornot)2B has not tested it.
The factual basis appears at the start. We then examine incentives, risks and possible actions. Examples do not describe these companies’ undisclosed contract provisions.
A balance needs a time stamp
Our analysis starts with the difference between information and permission. A consolidated view can shorten the search for cash. It still needs to tell the user which bank supplied each number and when. An available balance, a booked balance and a forecast can support different decisions. Putting them beside each other becomes valuable when their meaning survives the integration.
Consider a finance team preparing a supplier payment. Before authorizing it, the team needs to know whether another payment has already reduced the usable funds. A clear screen could help expose that dependency. The launch announcement alone cannot establish how quickly every connected source updates or what happens when a connection fails.
Payment status has a commercial consequence
The handoff continues after approval. A team may need to distinguish a payment instruction accepted by its platform, accepted by a bank and credited to the recipient. These are questions to put to a provider, rather than verified capabilities of this product. If a supplier is waiting to release goods, an ambiguous status can trigger duplicate investigation or an unnecessary second instruction.
Forecasting adds another layer. The forecast needs an owner for assumptions about receipts, payment dates and exceptions. Automation can transport an expected date accurately while the commercial assumption behind that date is wrong. Reconciliation should let the team connect the eventual movement of cash with the invoice and decision that produced it.
What a useful evaluation would measure
A practical evaluation could follow one payment from an approved invoice to confirmation and reconciliation, including an exception. Record who can authorize it, what each status means and where the team intervenes. Then compare handling time and unresolved items with the existing process. This gives a basis for judging the product beyond the number of connected systems.
The distribution model also deserves attention. A bank offers partner technology within an existing customer relationship. The buyer should establish who supports a failed connection, who answers a disputed status and which charges apply across banks. Central access is most valuable when responsibility remains traceable at every handoff.