Reconcile payments faster. Extract payment reference, payer, payee, totals, and the paid-invoice table from remittance advice PDFs. Free, no signup.
The full guide: Read a remittance advice into invoice rows
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
It turns the advice into data your AR process can match: payment reference and date, payer and payee, payment method, total payment amount, and a paid-invoices table listing each invoice number, its original amount, discounts taken, deductions, and the net amount paid.
Yes. IBAN, BIC or SWIFT code, the creditor account, structured creditor references (such as RF references), and free-text remittance information all have dedicated fields.
Any remittance advice rendered as a PDF. The field set mirrors ISO 20022 remt.001 and UBL RemittanceAdvice concepts, so advices generated by ERP and banking systems map naturally.
You can download CSV or XLSX for spreadsheet import, or JSON if you script the load. The invoice table exports with one row per settled invoice.
PDF only, 10MB maximum size, 100 pages maximum length.
No. Processing happens via the Talonic API and documents are not retained for training or 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.