Extract data from payment confirmations

A payment confirmation is the receipt that a single payment completed, whatever rail it ran on. A customer pays an invoice by card, a buyer clears one by ACH, a European counterparty sends a SEPA credit transfer, and each produces a confirmation: a document number, the payer and payee, the method, the amount, the status, and the reference of the invoice or order it settled. In ISO 20022 terms the underlying event is a camt.054 debit or credit notification the bank sends the account holder. For an accounts receivable team the confirmation is the trigger to apply cash: it says one payment of a stated amount arrived, with a status of completed rather than pending, against a named invoice, so the open item can be cleared. Variety lives in the method and the status, not the size. A card receipt shows an authorization code and a masked card number, an ACH confirmation shows a trace number and an effective date, and a SEPA confirmation shows an IBAN and an end-to-end reference, yet all three answer the same question for the ledger. Status is the field that decides whether cash can post: a confirmation marked pending, or a card authorization that has not captured, must not clear the invoice, and a failed or reversed payment has to route to a different queue. The reference that ties the payment to an invoice or a purchase order ranges from a clean structured creditor reference to a free-text memo, and a receipt sometimes settles part of an invoice rather than the whole. Send the confirmation to Talonic and the payer and payee, the payment method and status, the amount and currency, the payment date, and the settled reference come back as structured fields. The method is normalized to an enum such as card, ACH, SEPA, wire, or check, the status is read as completed, pending, failed, or reversed so cash-application logic can gate on it, and the invoice reference and any structured creditor reference are parsed for matching. A card payment of 4,820 dollars confirmed 2026-04-24 with a completed status loads into an AR system ready to apply against the open invoice rather than read off a PDF by hand.

What gets extracted from payment confirmations

How extraction works for payment confirmations

Payment confirmations are issued by payment gateways such as Stripe and Adyen, bank notification feeds, and ERP accounts-receivable modules, so a card receipt, an ACH advice, and a SEPA camt.054 notification each present the same completion differently. Talonic classifies the confirmation and maps it to the payment model in the Field Registry, which normalizes the method to an enum and the status to a controlled set rather than free text. The payment status is captured explicitly so a pending or failed confirmation is not treated as cleared cash, the settled invoice or order reference and any ISO 11649 structured reference are parsed for matching, and a partial payment keeps the remitted amount distinct from the amount due. Method-specific identifiers such as a card authorization code or an ACH trace number are retained. Each value returns with a confidence score and a pixel-region pointer conforming to DIN SPEC 91491, so an AR analyst can verify a status or an invoice reference against the receipt before applying the cash.

Sample extraction

A card payment confirmation settling one invoice

{
  "document_number": "PAY-2026-04-4471",
  "document_date": "2026-04-24",
  "payer.name": "Lakeside Retail Ltd.",
  "payee.name": "Foldertree Consulting LLC",
  "payment_amount": 4820,
  "currency": "USD",
  "payment_date": "2026-04-24",
  "payment_method": "card",
  "payment_status": "completed",
  "reference_number": "INV-2026-0912",
  "end_to_end_id": "E2E-0912-A",
  "invoice_number": "INV-2026-0912",
  "due_payable_amount": 4820,
  "remitted_amount": 4820
}

Frequently asked