Extract data from remittance advice

A remittance advice tells a supplier's accounts receivable team which invoices a customer just paid, and it is the document that decides whether a payment posts cleanly or drops into an unapplied-cash suspense account. A large buyer settling 40 invoices in one ACH batch sends an advice that lists each invoice number, the gross amount, the cash discount taken, any short-pay deduction, and the net amount remitted. The AR clerk then has to match those rows against open items in the ledger before the cash can clear. When the advice lands as a PDF attached to a bank notification, a portal download, or a faxed page from a smaller payer, none of that structure survives, so someone re-keys 40 lines by hand while the payment sits unapplied and DSO drifts upward. The awkward part is the paid-invoices table, not the header. One advice might settle a single invoice or three hundred. Deductions rarely reconcile on the first pass: a payer takes a 2% early-payment discount on some lines but not others, nets a credit note against an unrelated invoice, or short-pays a disputed freight charge and cites a reason buried in a free-text note. Payment references follow no single convention either, ranging from a structured ISO 11649 RF creditor reference on a SEPA credit transfer, to a check number on a US lockbox file, to nothing more than the payer name on an inbound wire. Currencies mix the moment a group settles EUR and GBP invoices on one advice. Talonic reads the advice against a schema modeled on ISO 20022 remt.001 and the UBL RemittanceAdvice document. The header captures the payment reference, payment date, payer, payee, payment method, total remitted amount, currency, and the creditor IBAN and BIC. Every settled invoice returns as a row carrying its invoice number, original amount, discount taken, deduction, and net amount paid, so the whole paid-invoices table arrives in your ERP ready for auto-matching rather than manual keying.

What gets extracted from remittance advice

How extraction works for remittance advice

Remittance advices are produced by ERP systems such as SAP and Oracle, by bank portals, and by lockbox providers, and no two payers format the paid-invoices table the same way. Talonic classifies each advice and maps it to the remittance schema in the Field Registry, which models the header and the settled-invoice rows rather than a fixed layout. Discounts and deductions are captured on each invoice line, and the sum of the net amounts is reconciled against the header total so an advice that does not foot is flagged. Structured references, such as an ISO 11649 RF creditor reference, are parsed out of the payment-details text and kept separate from free-text narrative. Each captured value returns with a confidence score and a pixel-region pointer into the source PDF under DIN SPEC 91491 conformity, so an AR analyst can check a short-pay or a deduction against the advice before posting the cash.

Sample extraction

A SEPA remittance advice settling three invoices in EUR

{
  "payment_reference": "RA-2026-04-1187",
  "payment_date": "2026-04-30",
  "payer.name": "Globex Manufacturing GmbH",
  "payee.name": "Harbor Freight Components Inc.",
  "payment_method": "SEPA credit transfer",
  "total_payment_amount": 48250,
  "currency": "EUR",
  "iban": "DE89370400440532013000",
  "bic": "COBADEFFXXX",
  "creditor_reference": "RF18539007547034",
  "paid_invoices": [
    {
      "invoice_number": "INV-20194",
      "invoice_date": "2026-03-02",
      "invoice_amount": 20000,
      "discount_taken": 400,
      "deduction": 0,
      "amount_paid": 19600
    },
    {
      "invoice_number": "INV-20233",
      "invoice_date": "2026-03-15",
      "invoice_amount": 18650,
      "discount_taken": 0,
      "deduction": 250,
      "amount_paid": 18400
    },
    {
      "invoice_number": "INV-20251",
      "invoice_date": "2026-03-21",
      "invoice_amount": 10250,
      "discount_taken": 0,
      "deduction": 0,
      "amount_paid": 10250
    }
  ]
}

Frequently asked