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
What happens when one advice pays two hundred invoices?
The paid-invoices table returns as an ordered array with one row per settled invoice, so an advice covering two hundred items comes back as two hundred rows. Each row carries the invoice number, original amount, discount taken, deduction, and net amount paid, and the total of the net amounts is checked against the header remitted amount.
How are short-pays and deductions represented?
A deduction or short-pay is captured on its own invoice row next to any early-payment discount, so the gap between the original amount and the amount paid is explicit rather than hidden. When the payer states a reason in the free-text remittance note, that text is preserved so the AR team can work the dispute.
Does it read the structured payment reference?
Yes. A structured creditor reference such as an ISO 11649 RF reference on a SEPA payment is parsed into its own field, while an unstructured pointer like a wire memo or a lockbox batch number is kept as remittance information. Either one can drive the match to an open item.
Can the output post straight into SAP or Oracle?
The structured advice exports to CSV for a spreadsheet reconciliation or to JSON for an automated cash-application load. The paid-invoices rows map to open-item keys in the AR subledger; mapping into a specific ERP happens in your integration layer.
What fields are extracted from remittance advice?
Talonic returns remittance advice as schema-validated, typed fields. Common fields include Payment Reference, Payment Date, Payer, Payee, and more, each normalized (dates to ISO 8601, amounts as numbers) and mapped to a stable key so the output shape stays the same across layouts.
How accurate is extraction from remittance advice, and how is confidence reported?
Every extracted cell carries a confidence score from 0.0 to 1.0 and a provenance pointer back to the source page and region, so low-confidence values can be reviewed against the original before the data is trusted downstream. There is no single accuracy number: confidence is reported per field so you can gate on it.
Can I use remittance advice extraction in production?
Yes. The same engine behind this guide is available as a production REST API and Node SDK with sync, async, and streaming modes, schema versioning, signed webhooks, and EU-resident processing. Start free with an API key, then scale on usage-based pricing.
What does it cost to extract data from remittance advice?
There is a free tier for prototyping and agent evaluation with no credit card. Paid usage is credit-based at 1,000 credits per euro: page ingestion is 100 credits per page and registry-resolved queries are free. See talonic.com/pricing for current rates.
Ready to extract from your own remittance advice?
- GDPR
- HIPAA
- ISO 27001 / 42001 aligned
- DIN SPEC 91491 co-author
- EU-resident infrastructure
Author note
Reviewed by Talonic engineering · last reviewed 2026-07-04