Extract data from remittance advices
Unstract reads remittance advices and the checks that come with them, from lockbox images, customer emails and portal downloads, and sends the payer, the payment and every invoice paid to your ERP or accounts receivable system.
| INVOICE / REF | INV. AMOUNT | DEDUCTION | PAID |
|---|---|---|---|
| BPC-55120 · inv. Sep 18 | 4,820.00 | — | 4,820.00 |
| BPC-55187 · code 07 short shipment | 3,615.40 | (241.00) | 3,374.40 |
| BPC-55203 · code 14 promo allowance | 2,960.00 | (148.00) | 2,812.00 |
| BPC-55241 · inv. Oct 2 | 6,240.75 | — | 6,240.75 |
| CM-8812 · credit memo taken | (412.50) | — | (412.50) |
| Total payment | 17,223.65 | (389.00) | 16,834.65 |
07 — POD signed for full qty, dispute
Deduction codes: 07 short shipment · 14 promotional allowance
{ "payer": "Harbor Point Foods", "payee": "Brightline Paper Co.", "payment_date": "Oct 24, 2026", "payment_method": "ACH CCD+", "trace_number": "091000019284417", "vendor_number": "V-30871", "invoice_total": 17223.65, "deductions": 389, "amount_paid": 16834.65, "confidence": 0.96}
Trusted by finance teams around the globe
Customers pay one way and explain it another
The payment lands in the bank. The explanation of what it covers turns up separately, and rarely in the same shape twice.
Lockbox images of checks and stubs, grey and off-square
Three customers, three labels for your invoice number
Check stubs filled in by hand, with an amount corrected in pen
A day's lockbox batch of checks, stubs and envelopes in one file
A retailer's remittance as a spreadsheet of hundreds of invoices
Cash application clerks key each remittance against open invoices by hand, so payments sit unapplied, collectors chase customers who have already paid, and deductions age past the window to dispute them.
Unstract reads each remittance and check in the customer's own layout, extracts the payer, the payment and every invoice it covers, matches them to open items, and posts applied cash to your ERP or accounts receivable system.
From remittance to applied cash on one platform
Parse the remittance, extract the payment and its invoices, run cash application around them. Each product works alone; stacked, they apply cash with nobody keying.
Parse remittance advices and check stubs with each invoice on its own line
Get the full text of a remittance, whether it came as a lockbox image, an emailed PDF, a portal download or a few lines in the body of an email. Invoice number, invoice amount, deduction and amount paid stay on the same row, a credit memo keeps its minus sign, and the check number and amount on the check image are read with the stub beside it.
Send the text to your own LLM, or make parsing the first step of a cash application workflow.
Learn more about LLMWhispererTurn remittance advices into payment records your AR team can apply
Name the fields you apply cash with, from payer and trace number down to each invoice's amount paid and deduction code, and every remittance comes back in one JSON structure. A handwritten stub and a retailer's spreadsheet produce the same record. Each value is checked as it comes out: a deduction your proof of delivery contradicts, or a credit memo missing from your ledger, returns flagged with the reason.
Call it as an API from your cash application tool, run it as an ETL pipeline from the lockbox folder or the remittance inbox, or make it one step in an orchestrated receivables process.
Learn more about Document StudioRun cash application from the lockbox to posted cash
Describe how your team handles remittances in plain English and Flow's agents build the workflow. Lockbox files, ACH and wire advices, and customer emails are collected as they arrive, each remittance is read, the payer is tied to a customer, and every line is applied to that customer's open invoices, partial payments and deductions included. Applied cash posts to your ERP or accounts receivable system, such as NetSuite or QuickBooks. You approve the workflow once, and every payment follows it the same way.
Choose when a person steps in: no matching invoice, a paid amount that differs from the invoice, a payer nobody recognises, or a deduction above your threshold. Only those payments stop, with the remittance and the open items side by side for an AR specialist or a collector. Deductions go to the team that disputes them, and finance gets a daily summary in Slack.
Learn more about FlowExtract remittance data now. Automate cash application when you're ready.
Start for free and run your own remittances and check images through parsing and extraction today. Matching to open invoices and posting to your ERP begins with a consultation.
Remittances, checks and the paperwork behind each payment
Documents
- Remittance advices
- Checks
- Check stubs and vouchers
- Lockbox image files
- ACH payment advices (CCD+ and CTX)
- Wire transfer confirmations
- Email remittances
- Customer portal remittance downloads
- Remittance spreadsheets
- Deduction and chargeback notices
- Credit memos
- Debit memos
- Customer statements
- Invoices
Fields captured
For the teams that apply cash and chase what is still owed
Remittances read and applied for you, so the cash application team works unidentified payments and short pays instead of keying invoice numbers off stubs.
Accounts show what customers have actually paid the same day, so collectors stop calling about settled invoices and see every deduction while it can still be disputed.
Unapplied cash shrinks and DSO reflects real collections, with a record of every manual match for month-end close and audit.
One extraction setup for each client's lockbox and every customer layout, so a new receivables client goes live without templates.
Cash applied sooner, fewer payments left unmatched
Built for customer bank details and check images
Remittances and check images carry your customers' routing and account numbers, signatures and the amount paid on every invoice, the exact details a check forger or a payment-redirection scam needs.
- Encrypted in transit and at rest.
- Customer remittances and check images are never used for model training.
- Access by role, entity and customer portfolio, with every manual match and edited value recorded against the payment.
- You set retention: check images and remittances are deleted when your banking and audit policy says they can go.
- Self-hosted deployment for treasury and AR teams whose controls keep customer bank details inside their own environment.
What cash application teams ask before they start
Unstract does it in two layers. LLMWhisperer is the OCR engine: it turns a lockbox scan, PDF or photo into text with every invoice line kept in place. Document Studio then uses an LLM to extract payer, payment and each invoice paid into the fields you define, and checks that the lines add up to the payment.
Point an ETL pipeline at the remittance inbox, the lockbox folder or an S3 bucket, or call an API endpoint from your cash application tool. Each advice is parsed and extracted as it arrives, so no one opens an email to read an invoice list.
Describe the fields once: payer, trace number, invoice number, amount paid, deduction code. Document Studio finds them under whatever label each customer prints, so "Your ref", "Inv #" and "Document no." fill the same field and a new customer needs no template.
Yes. Email remittance capture reads the PDF attachment or the table in the email body, and portal downloads go through the same pipeline. Spreadsheets from large retailers, often covering hundreds of invoices, come back as one record per invoice.
LLMWhisperer reads the check number, amount and date on the check image and the invoice lines on the stub, including handwritten amounts. The extraction ties the two together, so the check amount must equal the stub total before the payment is applied.
Check scanning software captures the check image and the amount for deposit. Unstract goes on to read the remittance behind it, apply each line to an open invoice and route deductions, so check scanning becomes the first step of cash application rather than the last.
No. Checks, stubs, envelopes and remittance pages in a lockbox batch are classified and read in one run, and each check is paired with the remittance that explains it.
Every deduction is extracted with its amount, the invoice it was taken against and the customer's reason code. Deductions under your threshold post automatically; larger ones stop for a collector, with the remittance and the invoice side by side.
Applied payments post to NetSuite, QuickBooks, SAP or Xero, or into the cash receipts import file your accounts receivable system already reads. Deductions can go to your deduction management tool at the same time.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Remittances and checks are encrypted in transit and at rest, never used to train models, and deleted on the schedule you set. Teams that keep bank details in-house can self-host; see the Trust Center.
In a consultation we set it up around your lockbox files, your customers' remittance layouts and an export of open items, and most AR teams apply their first live payments within days. To try the extraction now, start for free and upload a remittance.
Bring a day of remittances and lockbox files to the consultation
Emailed advices, handwritten check stubs, a retailer's spreadsheet and the short pays nobody has worked yet, with an open-items export. We run them live and show each match and every deduction.