Extract the payer, payee, IBANs and BICs, amount, method, references, and settled invoices from a payment order or payment instruction PDF. No signup.
The full guide: Payment order batch with beneficiaries and control sum
Need to scale? Create an API key, then run this from your own code or an agent.
Create an API keyFree account required
Upload a file or pick a sample, and see the fields come back.
No signup · nothing stored
A payment order is the instruction that initiates a payment, before it settles. The extractor reads the document number and date, the payment date, the total amount and currency, the payment method (ACH, wire transfer, check, or SEPA CT), the free-text payment reference (purpose), and the payer and payee names and identifiers.
Yes. The payer IBAN and BIC, the payee IBAN and BIC, the receiving bank account number, routing number, and name, the end-to-end id, the structured creditor reference (such as an ISO 11649 RF reference), and the payment information batch id all come back as their own fields for straight-through processing.
The referenced invoice number and date, the remitted amount, and the due-payable amount are read, and the paid invoices table returns one row per settled invoice with its number, date, due-payable and remitted amounts, currency, structured creditor reference, payee, and end-to-end id.
The number of transactions in the batch and the payment information id come back for a bulk run, and the approver name and signature (the authorizing party) are read too. The field set follows the ISO 20022 pain.001 payment-initiation message definition.
PDF only, up to 10MB and 100 pages. The payment order is processed via the Talonic API for extraction, is not retained for training, and is not shared.
The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.
See invoice data extraction if you run this for finance and AP teams, or the extraction API if you are building it in.