Business Matching
Every time your institution executes a Treasury, Securities, or Commodities trade, both parties exchange SWIFT confirmation messages. Matching those sent and received confirmations -- ensuring amounts, dates, rates, and terms agree -- is essential to managing trade risk and meeting settlement deadlines.
Since the retirement of SWIFT Accord in 2017, financial institutions have needed to find replacement solutions for their business matching workflows. Many ended up with manual processes or expensive third-party services that add complexity without adding control.
The Prowide Matching module provides automated trade reconciliation directly within the Messaging Hub -- preconfigured for the most common Treasury, Securities, and Settlement message types, with flexible rules that you control. And because matching runs locally against your own sent and received messages, it works regardless of what reconciliation system your counterparty uses.
Built-in, not bolted on
Matching is a native module within the Messaging Hub. It operates on your message flows as they happen -- no external service, no data leaving your infrastructure, no dependency on counterparty subscriptions. Preconfigured for 15+ message types with rules you can extend for any additional MT.
The Matching module works on your sent and received SWIFT messages as they flow through the Messaging Hub. When a confirmation is sent to a counterparty, the module watches for the corresponding incoming confirmation -- and vice versa.
Matching rules compare the key fields of each message pair: trade date, value date, currency, amount, counterparty BIC, and instrument-specific fields. When all required fields agree, the pair is marked as matched automatically.
When fields disagree -- a different value date, a mismatched amount, or missing information -- the pair is flagged as a mismatch for manual review. Unmatched messages that have no counterpart after a configurable time window are flagged separately.
The entire process is configurable per message type. You define which fields to compare, which tolerances to apply, and how long to wait before escalating unmatched items.
FX Confirmations
Matching and chaining rules for foreign exchange trade confirmations, including spots, forwards, and swaps.
FX Options
Confirmation matching for foreign exchange option trades and option notifications.
Loans & Deposits
Reconciliation of fixed-term loan and deposit confirmations exchanged between counterparties.
Interest Rate & OTC Derivatives
Matching for interest rate swaps, derivative events, and termination or reset notifications.
Securities Confirmations
Reconciliation of client-side securities trade confirmations for equities, bonds, and other instruments.
Commodities Confirmations
Matching for commodity trade confirmations covering metals, energy, and other physical or financial commodity trades.
Business Matching
Pairs your sent confirmation with the counterparty's incoming confirmation for the same trade. Compares key fields to determine if both parties agree on the terms.
Message Chaining
Links a sequence of messages that belong to the same trade lifecycle -- from initial confirmation through amendments, terminations, or settlement instructions.
Field-Level Comparison
When a pair has disagreements, the GUI highlights exactly which fields differ -- amounts, dates, rates, or counterparty references -- so operators can identify the issue immediately.
Pending Confirmation Tracking
Confirmations that remain unmatched beyond a configurable time window are escalated for review. Operators can see all pending items and their age at a glance.
Manual Match Selection
For edge cases, operators can use the detailed message compare tool to analyze matching candidates side-by-side and manually select the correct match when automatic rules don't resolve.
The Matching module comes preconfigured for the most common Treasury, Securities, and Commodities message types -- but you're not limited to the defaults.
Rules are fully configurable via API, meaning you can add matching or chaining rules for any MT message type, adjust which fields are compared, define tolerances, and configure escalation timers.
This is particularly important for institutions with proprietary workflows or specialized instruments where the default rules need customization. Your matching logic evolves with your business, not the other way around.
Add rules for any MT
Not limited to preconfigured types -- define matching rules for any SWIFT message type in your flows.
Choose comparison fields
Select which fields to compare for each message type. Include or exclude fields based on your operational requirements.
Set tolerances
Define acceptable thresholds for amount differences, date offsets, or other numeric fields before flagging a mismatch.
Configure escalation
Set time windows for unmatched items and define escalation paths when confirmations remain pending.
Counterparty independent
Matching runs against your own sent and received messages. It doesn't depend on your counterparty subscribing to the same service -- you can reconcile every trade, regardless of what the other party uses.
On-premises data control
All matching happens locally within your Messaging Hub instance. No trade data leaves your infrastructure for an external matching service -- full data sovereignty and compliance with internal policies.
Part of your message flow
Matching is integrated into the same platform that handles message routing, validation, and archiving. No separate integration, no data export, no synchronization between systems.
Real-time processing
Matching happens as messages flow through the Hub -- not in batch. Operators see match results immediately, reducing the time between trade execution and confirmation reconciliation.
Complete audit trail
Every match, mismatch, and manual resolution is logged with timestamps, operator identity, and the full message content -- ready for audit and compliance review.
Standalone or integrated
The matching module can run as part of the full Messaging Hub or be deployed as a standalone matching solution, integrating via API with your existing message infrastructure.
Prowide Messaging Hub
The Matching module is a native component of the Messaging Hub -- your on-premises or private cloud platform for SWIFT message management, routing, validation, and archival.