When a customer pays, they often send a remittance advice — a note that explains which invoices the payment covers and how the total was arrived at. Docyield reads that note from a PDF or an image and returns it as structured data: the payer and payee, the payment date, reference, and method, the currency and total paid, and the list of settled invoices with their gross amounts, deductions, and net amounts. Export it as CSV, Excel, JSON, or XML.
Remittance advice is the missing link in cash application. A bank feed tells you money arrived; the remittance tells you what it was for. Pulling the settled-invoice list into named fields lets you match a lump-sum payment back to the individual invoices it clears, so accounts receivable can close them off accurately instead of guessing how a payment splits across an open ledger.
What a remittance advice parser extracts
The parser turns a payment note into the structured record a receivables system needs. At the header level it captures who paid and who was paid, the date the payment was made, the reference or transaction identifier that ties it to a bank entry, the method used — ACH, wire, cheque, and so on — and the currency and total amount paid.
Beneath that sits the detail that makes the document useful: the list of invoices the payment settles. Each entry is returned with its invoice number and date, the gross amount, any deduction or discount the payer applied, and the net amount actually paid against it. That breakdown is what lets you reconcile a single remittance against several open invoices line by line.
Cash application and AR reconciliation
Cash application is the work of matching incoming payments to the invoices they clear, and remittance advice is its primary source. A customer paying twenty invoices in one transfer leaves accounts receivable with a single bank credit and twenty open items to close. The remittance explains the split — but only if the settled-invoice list can be read as data rather than re-keyed from a PDF.
Extracting that list into structured fields lets a receivables team, or an automated cash-application engine, mark each invoice paid with its net amount, account for any short-payment or early-settlement discount via the deduction field, and confirm the entries sum to the total paid. What used to be a manual reconciliation against the open ledger becomes a lookup keyed on the invoice number.
Who uses remittance advice extraction
- Accounts receivable teams applying customer payments against open invoices.
- Credit-control teams clearing aged items and chasing genuine shortfalls.
- Finance teams reconciling bank receipts to the sales ledger.
- Shared-service centres processing remittances from many customers at volume.
- Treasury staff matching consolidated payments back to their components.
- Developers building cash-application or AR-automation software that ingests remittances.
Handling deductions and short payments
Payers rarely pay exactly the gross amount of every invoice. They take early-settlement discounts, withhold for disputed lines, or deduct credit notes, and the remittance is where those adjustments are explained. Capturing the deduction separately from the gross and net amounts on each invoice line means you can see not just that a payment was short, but by how much and against which item.
That distinction matters for credit control. A net amount that matches the gross is a clean settlement; a deduction signals an adjustment to investigate or write off. Keeping the three figures — gross, deduction, net — as their own fields lets a team triage payments automatically, clearing the straightforward ones and surfacing only the entries where the deduction needs a decision.
Accuracy, validation, and review
No extraction is perfect, and in cash application a wrong figure quietly mis-applies a payment, so honesty about limits is the right policy. Docyield reads clean remittances reliably, and where a field is genuinely absent — a remittance with no stated method, say — it returns the field empty rather than guessing. A blank that prompts a check is far safer than a fabricated amount applied to the wrong invoice.
A simple reconciliation gives you confidence: the net amounts of the settled invoices should sum to the total paid. When they tie out, the invoice list is almost certainly complete; when they do not, that points you straight at the line to review. Faint scans, long multi-page invoice lists, and unusual layouts are the cases most worth comparing against the original.
Why remittance formats defeat template tools
Every customer designs their remittance differently. Some send a tidy table; some bury the invoice list in the body of an email converted to PDF; some attach a spreadsheet export with idiosyncratic column headings; large payers route them through portals in yet other layouts. A template-based reader has to be configured per customer and breaks the moment one of them changes their format — which, in a receivables team handling hundreds of payers, is a constant maintenance burden.
Reading the document in context sidesteps that. Because Docyield interprets what a remittance is rather than matching a fixed grid, it returns the same fields — payer, reference, total, settled invoices — whether the note arrived as a polished statement or an ad-hoc email attachment. That is what makes it practical to automate cash application across a diverse customer base instead of only the few who happen to send a consistent layout.
Output formats, API, and batch
CSV is the default because reconciliation happens in spreadsheets and AR systems — one row per settled invoice, ready to match against the open ledger. The same result is also available as Excel, JSON, or XML, so you can push the data into a cash-application engine, an ERP, or a custom workflow without re-uploading.
The free tool processes one remittance at a time, which suits the occasional payment. For shared-service centres and high-volume receivables, the Docyield API and batch dashboard run the same extraction at scale with webhooks and your own validation rules — for instance, requiring the settled invoices to reconcile to the total before a record is accepted. The schema does not change between the free page and the API.
What the remittance advice parser extracts
Each remittance advice is returned against a fixed schema. Fields not present on the document come back empty rather than guessed.
- Payer
- The party making the payment.
- Payee
- The party receiving the payment.
- Payment date
- The date the payment was made.
- Payment reference
- The payment or transaction reference that ties it to a bank entry.
- Payment method
- How the payment was made — ACH, wire, cheque, and so on.
- Currency
- The ISO currency code or symbol used.
- Total paid
- The total amount paid in the remittance.
- Invoices
- Each settled invoice, with its number, date, gross amount, deduction, and net amount paid.
How to extract data from a remittance advice
- 1Upload the remittance advice — drop a PDF, PNG, JPG, or WEBP onto the box above, or click to choose a file.
- 2Wait a few seconds while Docyield reads the document and lists the settled invoices.
- 3Check that the net amounts of the invoices sum to the total paid to confirm the list is complete.
- 4Choose your output tab — CSV, Excel, JSON, or XML.
- 5Download the file or copy the data into your accounts receivable or cash-application system.
Frequently asked questions
Processing documents at scale?
Batch upload, an extraction API, and webhooks for 100+ documents a month.