Kyriba vs Bottomline for Fedwire ISO: 3-Way 2026

The category decision is whether you are buying a treasury-management system or a payments / cash-management messaging stack. Kyriba vs Bottomline for Fedwire ISO 20022 MX is that comparison. Neither product is the Fedwire Funds Service. Neither is your core GL.

ISO 20022 MX messages replaced the older FAIM-style Fedwire formats. pacs.008: 1 FI-to-FI credit type according to ISO 20022 (2026). A treasury-management system plans cash, in-house banks, and payment factories. A payments messaging stack originates and repairs wires. Buying a TMS and expecting a FedLine Direct translator, or buying a messaging stack and expecting cash positioning, is how MX cutover becomes a second night job.

This page is published from the homepage. No vendor paid for inclusion.

TL;DR: Choose Kyriba when the work is treasury-management: cash, payments factory, and bank connectivity as a TMS. Choose Bottomline when the work is payments and cash-management messaging, including high-value wires. Stay on your bank’s FedPayments Manager if dual control already works. Orchestrate only when TMS, messaging, and the GL still disagree after a named treasury review.

Fedwire MX vs FAIM in plain English

The Fedwire Funds Service completed the ISO 20022 migration so funds message formats align with other high-value systems. FRB Services documents that shift in the ISO 20022 Implementation Center. MX is the XML message family. FAIM is the legacy Fedwire format you should no longer be designing to.

Successfully processed Fedwire messages still carry IMAD and OMAD identifications, according to FRB Services (2026). Investigations use nonvalue camt.110. Return requests use nonvalue camt.056. If your TMS cannot show those message names, you are still operating as if FAIM never left.

On August 27, 2026, FRB Services announced that the November 2026 Fedwire release was rescheduled to November 2027. Treat that as a calendar fact, not as permission to delay MX operating procedures.

Adjacent reading: KYC onboarding, bank reconciliation, beneficiary review, and the financial services playbook.

pacs.008 mapping checklist

A customer credit on Fedwire is a pacs.008. The creditor name, account, and instructing agent have to survive the TMS, the messaging stack, and the bank. Dual control belongs on name mismatches, not only on amount.

Fedwire November release year: 2027 according to FRB Services (2026), after the Aug. 27, 2026 reschedule of the November 2026 drop. Designing new maps in FAIM is a defect.

Same-Day ACH is still $1,000,000 according to Nacha (2026). Do not “fix” a Fedwire MX repair by sending a $4.2 million item as Same-Day ACH. That is the wrong rail and the wrong cap.

Key Takeaways

• Kyriba is treasury-management; Bottomline is payments / cash-management messaging.

• pacs.008 is the customer credit; camt.056 and camt.110 are the nonvalue cousins.

• IMAD and OMAD still identify a successful Fedwire.

• The November 2026 Fedwire release moved to November 2027.

• Orchestrate only after beneficiary masters, dual control, and message IDs exist.

Evaluation weights for an MX payments factory

Weights assume a corporate or bank-sponsored treasury that sends Fedwire credits and must live in MX. A single-entity AP shop that sends two wires a month should raise “bank portal” and drop TMS weight.

Cash positioning weight is high for Kyriba-class buys and should be lowered if you already have a TMS and only need messaging.

Normalized feature matrix

Scores from public product pages checked 2026-09-06: 2 = first-party description of this job; 1 = adjacent, confirm in contract; 0 = not found for Fedwire MX. The USTA column is first-party design numbers for this page (1 named hold, 1 recipe, 8 publish gates).

Kyriba wins the TMS and cash-positioning story. Bottomline wins payments messaging. In our own library, 6,958 pages earned at least one impression over a 12-month window — proof that a message log nobody reads is the same as an unindexed page.

Pricing and TCO (checked 2026-09-06)

Both vendors quote. Example: 1 treasury center, 5 users, 20 Fedwire credits per week. Bank FedLine fees are separate (see FRB 2026 wire fees).

Ask for MX message coverage (pacs.008, camt.056, camt.110), FedLine Direct vs Advantage path, dual control, and message export in one quote. A cheaper TMS that still emails wires is not cheaper.

Accountants and auditors median wage: $83,680 according to BLS (2025). Treasury ops hours spent repairing MX name fields are accounting hours you did not close.

Accountant jobs: 1,595,200 according to BLS (2025). The constraint is message quality, not headcount slogans.

Kyriba and Bottomline profiles

Kyriba — best for treasury-management

Kyriba is a treasury-management platform. Best fit: corporates that need cash positioning, a payment factory, and bank connectivity in one TMS, including Fedwire credits in MX. Limitations: implementation is heavy; confirm the exact MX messages and FedLine path on the edition you buy; it is not a GL. Implementation: map entities, bank accounts, beneficiary masters, then send 12 pacs.008 credits in a test window with dual control. Primary evidence: Kyriba public product pages. Disqualifier: you only needed a wire-messaging translator.

Bottomline — best for payments messaging

Bottomline is payments and cash-management messaging. Best fit: banks and corporates that need to originate, repair, and investigate high-value payments, including ISO 20022 wires. Limitations: it is not a full TMS cash-forecasting suite by default; confirm Fedwire MX coverage and dual control. Implementation: map message types, repair queues, and who owns camt.110. Primary evidence: Bottomline public product pages. Disqualifier: you needed in-house banking and cash positioning more than messaging.

Keep FedPayments Manager — best when dual control already works

If credentialed users already create or import Fedwire payments in FedPayments Manager with dual control, adding a second originator without a beneficiary master is how you duplicate IMADs. Best fit: one message path, one dual-control policy, one export. Limitations: native automations stop at the FedLine wall. Disqualifier: repairs still live in a shared inbox.

Cross-system MX holds

When Kyriba marks a payment released but Fedwire still lacks an IMAD, a proposed US Tech Automations path could match the end-to-end ID, pause for treasury, and only then notify AP that the vendor was paid. Prerequisites: TMS export or API, Fedwire message log, beneficiary master, and a human who will catch a creditor-name mismatch on pacs.008. Configurable capability, not a live treasury result. The finance-accounting agent path is the allowlisted route for that hold.

A second proposed path: a camt.056 return request waits for a match to the original IMAD, then opens a treasury hold before any second credit is released. Output: hold queue, IMAD, amount, and a yes/no on resend. Same rules: no implied deployment.

Zapier plus Make plus n8n can connect a TMS or messaging stack to Slack and the GL and can keep run histories, retries, error branches, and audit evidence when configured. The operator still owns observability, idempotency, escalation, access controls, retention, and maintenance. A proposed US Tech Automations design would require the treasury hold before any vendor-visible “paid” notice and write the decision back to the payment record.

Worked wire: 12 credits, $4.2 million, 3 repairs

A treasury desk sending 12 Fedwire credits averaging $4.2 million with 3 name repairs in a week can treat a pacs.008 customer credit as the message that must pass a human hold when the creditor name fails a 2-field match against the beneficiary master. The 12, $4.2 million, and 3 figures are a worked scenario; pacs.008 is a real ISO 20022 message. If Kyriba is the TMS, keep cash positioning there. If Bottomline is the messaging stack, keep repairs there. Dual-writing “sent” in email and “unsent” in Fedwire is how you pay twice.

Who this is for

This comparison is for treasury and payments-ops teams that send Fedwire customer credits in ISO 20022 MX and still repair names in email. Stack: TMS and/or messaging plus FedLine plus GL. Pain: MX cutover complete on paper, dual control missing in practice.

Red flags: a shop that sends two domestic ACH credits a month and never uses Fedwire; a FedPayments Manager path that already has dual control and IMAD/OMAD logging; a buyer who will not connect message logs or name a treasury owner for vendor-visible paid notices.

Beneficiary master and repair queue

MX did not remove the need for a beneficiary master. It made a bad master more expensive. pacs.008 carries richer name and address fields. If AP still types the creditor name from an invoice PDF, you will repair the same vendor every week. Put the master in the TMS or the messaging stack, not in a shared inbox. Dual control on amount without dual control on name is how you pay the right amount to the wrong creditor.

Investigations are camt.110. Returns are camt.056. If those message names do not appear in your ticket system, you are still operating as if Fedwire were an email. Map IMAD and OMAD into the ticket. A ticket without IMAD is a rumor. FRB Services’ Funds FAQ is explicit that successfully processed messages contain IMAD and OMAD.

Repairs need a queue with an owner, a clock, and a stop on the second credit. The worked example’s 3 name repairs in a week are a process target. If repairs sit in the same mailbox as marketing newsletters, they will not clear before cutoff. Kyriba will not save you from that. Bottomline will not save you from that. A named treasury person will.

Do not announce “paid” to a vendor from the TMS release flag alone. Release is an intent. IMAD is evidence. The proposed hold compares them. If you never send vendor-visible paid notices from a second system, you do not need that hold. If you do, you need a human in the middle.

Keep Same-Day ACH and Fedwire on separate runbooks. A $4.2 million customer credit is a Fedwire problem. Pushing it to Same-Day ACH because “it is faster” hits the $1,000,000 cap and still is not MX Fedwire.

Put FedLine path in the contract: Advantage (manual or file import) vs Direct (computer-to-computer). A TMS that can only email a PDF to a FedLine user is not an MX factory. Ask for a test IMAD on a pacs.008 and a test camt.110 before you sign. If the vendor cannot produce those message names in a sandbox, you are buying a dashboard.

Kyriba implementation weeks in the TCO table are a planning range, not a quote. Bottomline is the same. Bank fees for Fedwire sit on FRB’s 2026 wire fee schedule — separate from SaaS. A “cheaper” TMS that leaves you on FedPayments Manager with no dual control is not cheaper.

Name the treasurer who owns vendor-visible paid notices. If that seat is empty, do not orchestrate. If that seat is full and IMAD already equals “paid,” do not orchestrate. The only remaining case is disagreement between TMS release and Fedwire evidence.

Decision checklist

1. Name the TMS vs messaging job (one primary).

2. List pacs.008, camt.056, and camt.110 in the contract.

3. Export beneficiary masters twice.

4. Pilot 12 credits: match, mismatch, return.

5. Confirm November 2027 release calendar with your bank.

6. Only then connect Slack, using the same end-to-end ID.

Frequently asked questions

Is Kyriba or Bottomline better for Fedwire MX?

Kyriba is the better default when you need a TMS with a payment factory and cash positioning. Bottomline is the better default when you need payments messaging, repairs, and investigations. Confirm pacs.008 coverage on the edition you buy.

Did Fedwire finish ISO 20022?

Yes. FRB Services describes the Fedwire Funds Service migration to ISO 20022 as in place, with MX aligning to other high-value systems. Upcoming Fedwire software releases are a separate calendar (November 2027 after the 2026 delay).

When should treasury skip a cross-product hold?

Skip US Tech Automations when Kyriba or Bottomline (or FedPayments Manager) already posts Fedwire with dual control and IMAD/OMAD logging, when you will not connect message logs, or when no treasurer will own a hold. Zapier plus Make plus n8n are enough if your team will own logs, retries, and access control. A proposed design here is a mandatory hold before vendor-visible paid notices, plus write-back.

Can we keep email as the investigation tool?

You can keep email for people. Do not let an email thread be the source of truth for camt.110. The messaging stack owns the investigation; the TMS owns cash; the GL owns the books.

What is the first migration object?

The first migration object is beneficiary masters plus bank account identifiers, not historical FAIM samples. Unique beneficiaries first. Then pacs.008. Then investigations.

How should we test a return request?

Test camt.056 against a known test IMAD. Confirm amount match, hold, and no automatic second credit. If the vendor cannot show that path, do not automate live returns.

Pick TMS or messaging, then the hold

Pick Kyriba for treasury-management or Bottomline for payments messaging. Put MX message names in the quote. Pilot match, mismatch, and return. Export twice. If you still need a treasury hold between released and vendor-visible paid, review the finance-accounting agent.