Banno Wire Templates: Test What a Payment Edit Leaves Behind

Changing one wire should not silently rewrite the instructions used to create the next. That is the practical distinction behind Jack Henry’s forthcoming update to Banno wire templates—and the starting point for banks deciding what to validate before accepting the change.

In its October 30, 2026 announcement, the vendor says edits made while creating a wire previously updated the original template parameters. Under the announced bank workflow, “all template details remain intact and unchanged.” That describes a clearer separation between a reusable instruction and an individual payment. It does not establish that the payment itself has been properly authorized.

As of the November 5 research cutoff, the announcement targeted Banno Mobile 3.40 for the second week of November 2026, with Online expected around the same time. Those are release targets, not evidence of completed deployment.

Method and comparison boundaries

This is desk research, based on two vendor announcements and Banno’s bank entitlements documentation, using research checked November 5, 2026. No hands-on testing occurred. Mobile 3.40 is the announced target version; the evidence does not establish a deployed Online build. The entitlements page displays no publication or revision date.

The assessment uses six criteria: functionality, integration, pricing, security controls, institutional and jurisdictional eligibility, and support. Vendor documentation establishes the announced scope, not independently verified performance, fraud outcomes or production reliability.

There is a relevant historical comparator. An October 31, 2025 announcement described template-preserving wire creation as already available for Banno Business credit unions on Symitar without NetTeller. That is a specific deployment group, not evidence that every credit union—or every bank—already had equivalent behavior.

The two announcements therefore point toward a similar functional separation, but they do not prove identical implementations, permissions or approval paths.

What the evidence supports—and leaves open

The bank release and commercial statements come from the 2026 workflow announcement; the historical scope comes from the 2025 credit-union announcement. The control distinctions appear in Banno’s bank entitlements documentation.

“No additional contract” should not become “no cost” in a procurement summary. Nor should automatic availability be mistaken for completed banking software change management. A bank still needs to establish what changed in its deployment and whether its operating procedures match.

Three acceptance tests worth separating

The following are proposed tests, not completed findings. Run them in an appropriate controlled environment, record the actual Mobile and Online versions, and agree expected outcomes before execution.

1. Does the reusable template really remain unchanged?

Record every stored field in a test template. Create a wire from it, change each editable payment field in separate cases, and compare the underlying template with the baseline. Include cancellation and submission paths wherever available.

Then create another wire from the same template. It should inherit the original template values, not the changes made to the earlier payment. Repeat across Mobile and Online once each channel’s rollout is confirmed. Include a cross-channel check: make the payment-specific edit in one channel and reuse the template in the other.

The pass condition is not merely that a screen looks unchanged. The persisted template and its subsequent reuse must match the agreed baseline. If the bank cannot inspect stored values directly, it should document that limitation and agree an alternative verification method with the vendor.

2. Which permission governs the edit?

Banno’s bank documentation separately describes permission to modify repetitive—or template—wires and permission to edit one-time wires. That makes role separation a distinct test subject.

Use controlled accounts with different combinations of those permissions. Check explicit template editing separately from editing a payment created from a template. Do not assume that a template-derived payment maps to the one-time-wire permission merely because its changes are no longer persistent; confirm the entitlement mapping.

Attempt both permitted and prohibited actions through available workflow paths. A useful acceptance record should identify the user’s entitlements, the attempted operation and the resulting stored state—not just whether an edit button appeared.

3. Does approval follow the final payment?

The documentation says wires above the configured dual-control amount require a second business user’s approval. Test payments below, exactly at and above that threshold, while separately checking applicable transaction limits.

Where the workflow permits it, change an amount so that it crosses the threshold. If edits are possible after approval, verify whether they trigger the bank’s required reapproval process. Confirm what the approver sees and whether the payment ultimately submitted matches the approved details.

These checks address authorization of the current payment. They should pass independently of template-persistence testing: an unchanged template is not a substitute for an authorized wire.

The operational decision

Before accepting the release, banks should obtain deployment confirmation for both channels, resolve entitlement-mapping questions and establish a support route for discrepancies. Staff guidance should explicitly distinguish “change this payment” from “change future payments created from this template.”

The announced change is directionally sensible: it makes a payment-specific edit less likely, by design, to alter a reusable instruction. Whether it achieves that in a particular deployment remains a testable question. Whether it reduces errors or fraud requires evidence beyond the announcement.

The strongest acceptance decision rests on three separate findings: the template stayed intact, editing permissions were enforced, and the final payment received the required approval. None should stand in for the others.

Sources and References

• Jack Henry/Banno: Create Wire from Template Workflow — October 30, 2026; forthcoming bank behavior, release targets and service prerequisite.
• Jack Henry/Banno: Transmit Wires from Templates Without Disruption — October 31, 2025; historical comparator for Banno Business credit unions on Symitar without NetTeller.
• Banno Knowledge Base: Entitlements and Permissions for Banks — undated; bank editing permissions, limits and dual-control settings. All sources included in research checked November 5, 2026.