Skip to main content

Extract data from wire transfer confirmations

A wire transfer confirmation is the bank receipt that a high-value payment actually left the account. When a treasury team pushes a SWIFT payment to an overseas supplier, or sends a Fedwire or CHIPS transfer domestically, the bank returns a confirmation carrying the debit reference, the debtor and creditor, both banks with their BIC or ABA routing numbers, the amount, the value date the funds settle, and the wire fee. Underlying it in the ISO 20022 world is a pacs.008 financial-institution credit transfer and the pain.001 the originator submitted. The confirmation is what a treasury analyst files as proof the wire went, what accounts payable staples to the invoice it settled, and what a controller reconciles against the bank statement at month end. Settlement mechanics are the detail that matters, not just the amount. A cross-border wire carries two banks and often an intermediary, so the debtor BIC, the creditor BIC, and any correspondent all have to be captured, and the IBAN on a European leg follows a country-specific length while a US account uses a routing-and-account pair. When the payment converts currency the confirmation states an exchange rate and a converted amount, and the wire fee may be drawn from the principal under an OUR, BEN, or SHA charge instruction so the beneficiary receives less than the instructed sum. The end-to-end identifier and any structured creditor reference are what let the beneficiary match the receipt back to an invoice, and the value date, not the send date, is the one that reconciles to the ledger. Give the confirmation to Talonic and the debtor and creditor, both banks and their BIC or routing codes, the debtor and creditor IBAN, the amount and currency, the value date, and the fee come back as typed fields. The end-to-end ID and any ISO 11649 structured reference are parsed out for reconciliation, an exchange rate and converted amount are captured when the wire crosses currencies, and a batch confirmation covering several transfers returns each as a row whose amounts reconcile against the control sum. A EUR wire from Meridian Components to Harbor Freight Components, confirmed with value date 2026-04-30 and a 2026-04-29 send date, loads into a treasury and reconciliation system in New York ready to match against the open payable rather than keyed from a bank PDF.

What gets extracted from wire transfer confirmations

Confirmation ReferenceWT-2026-04-77120
Value Date2026-04-30
Originator (Debtor)Meridian Components GmbH
Beneficiary (Creditor)Harbor Freight Components Inc.
Debtor IBAN / BICDE89 3704 0044 0532 0130 00 / COBADEFFXXX
Creditor IBAN / BICNL91 ABNA 0417 1643 00 / ABNANL2A
Amount€185,000.00
End-to-End IDE2E-INV-20194
Wire Fee€25.00
StatusSettled

How extraction works for wire transfer confirmations

Wire confirmations come off bank portals, SWIFT gpi trackers, and treasury management systems, and a Fedwire advice, a SWIFT MT103 print, and an ISO 20022 pacs.008 render carry the same payment in different layouts. Talonic classifies the confirmation and maps it to the payment model in the Field Registry, which holds the debtor and creditor, both financial institutions, and the settlement fields rather than a single amount line. IBANs are checked by their country format and BIC codes by structure, the end-to-end identifier and any ISO 11649 structured reference are parsed for reconciliation, and where the wire crosses currencies the exchange rate and converted amount are captured against the instructed amount. A batch confirmation reconciles each transfer against the message control sum. Every value returns with a confidence score and a pixel-region pointer under DIN SPEC 91491, so a treasury analyst can check a value date or a beneficiary IBAN against the source before the payment is reconciled.

Sample extraction

A single cross-border EUR wire transfer confirmation

{
  "document_number": "WT-2026-04-77120",
  "document_date": "2026-04-30",
  "transfer_amount": 185000,
  "currency": "EUR",
  "payer.name": "Meridian Components GmbH",
  "payer.iban": "DE89370400440532013000",
  "payer.bic": "COBADEFFXXX",
  "payee.name": "Harbor Freight Components Inc.",
  "payee.iban": "NL91ABNA0417164300",
  "payee.bic": "ABNANL2A",
  "end_to_end_id": "E2E-INV-20194",
  "value_date": "2026-04-30",
  "fees": 25,
  "status": "settled",
  "invoice_number": "INV-20194",
  "remitted_amount": 185000
}

Frequently asked

How is a wire confirmation different from a remittance advice?

A wire confirmation is the bank proof that one transfer settled, carrying the value date and the fee. A remittance advice lists which invoices a payment covered. Talonic reads each on its own schema.

Does it capture both banks and the IBAN and BIC?

Yes. The debtor and creditor, both financial institutions, and the debtor and creditor IBAN and BIC or routing codes are captured, along with any intermediary bank on a cross-border wire.

What happens when the wire converts currency?

The exchange rate and the converted amount are captured against the instructed amount, so a treasury team can see what the beneficiary received after conversion.

Can it handle a batch wire covering several transfers?

Yes. Each transfer returns as a row, and the sum is reconciled against the message control sum so a batch that does not foot is flagged.

Author note

Reviewed by Talonic engineering · last reviewed 2026-07-07