Automate cash application
Unstract reads each remittance as it arrives, ties the payment to the customer and their open invoices, and posts applied cash to your ERP or accounts receivable system.
Trusted by finance teams around the globe
The cash arrives in the bank, the remittance arrives somewhere else
A check lands in the lockbox or an ACH credit shows up on the bank file. The list of invoices it pays comes days later as an email, a stub or a portal download, and someone in AR pairs the two by hand.
The remittance email turns up days after the cash
A lockbox stub scanned crooked, the bank stamp over the amount
A short pay with a deduction code and no backup
Remittance lines keyed into AR as month-end closes in
An invoice the customer paid, still open and still chased
Until each payment is matched to its remittance and applied, it sits as unapplied cash, collectors call customers who have paid, and short pays age past the window to dispute them.
Unstract picks up the remittance wherever it arrives, reads every invoice it pays, applies the cash against open items in your ERP or accounts receivable system, and sends an AR specialist only the payments that don't fit.
From the lockbox and the remittance inbox to the ERP, without the keying
Five steps, run on their own for every payment. Parsing by LLMWhisperer, extraction by Document Studio, the whole run by Flow.
Pick up remittances wherever they land
The payment and its explanation travel apart. Checks come through the lockbox with a stub image, ACH and wire credits show up on the bank file, and the invoice detail arrives as a customer email, a PDF or a download from the customer's AP portal. Each piece is collected as it arrives and paired with its payment by check number, trace number or amount, one record per payment.
A remittance that turns up three days late still finds its payment.
Read every remittance, then pull each invoice it pays
LLMWhisperer reads the check, the stub and the remittance as text with their layout kept, so a crooked lockbox scan or a retailer's spreadsheet of several hundred lines keeps every invoice on its own row. Document Studio then extracts the fields you named: payer, payment amount and date, check or trace number, and every invoice paid with its amount, short pay and deduction code.
Each customer labels your invoice number differently. The record comes back the same.
Check every line against the open invoices before anyone keys it
The payer is tied to a customer in your customer master, and each remittance line is matched to that customer's open invoices in your ERP. Full payments apply, partial payments apply line by line, and a coded deduction is split off against its invoice. A line that pays less than the invoice by more than your threshold stops in a review screen with the remittance, the open item and the deduction side by side.
Set the human-in-the-loop rules once (no matching invoice, an unknown payer, a deduction above threshold) and every other payment keeps moving.
Hand AR specialists only the payments that don't fit
Every payment runs through the same exception checks: a payer your customer master knows, invoices that are open and unpaid, a deduction code you recognise, and a lockbox batch that ties to the bank deposit total. A deduction under your threshold goes straight to deductions. One above it, an unidentified payment or a missing invoice goes to an AR specialist or a collector with the reason attached.
The specialist starts from the open items and the remittance, not from a blank search screen.
Post applied cash where receivables already works
Applied cash posts to your ERP or accounts receivable system, such as NetSuite or QuickBooks, against the invoices it paid. Each deduction opens in your deduction management queue with the remittance attached, and finance gets a daily summary of cash applied, cash unapplied and deductions opened in its Slack channel.
Every decision an AR specialist made is recorded against the payment it touched.
Watch a day of your own payments get applied.
Bring one day's lockbox file and the remittances that came with it. We run them live and show each match, each deduction and each exception.
Every remittance, check and bank file behind a payment
Documents
- Remittance advices
- Checks and check stubs
- Lockbox image files
- ACH payment advices (CCD+ and CTX)
- Wire transfer confirmations
- Email remittances
- Customer portal remittance downloads
- Bank account statements
- BAI2 and bank deposit files
- Deduction and chargeback notices
- Proof of delivery and promotion agreements
- Credit memos
- Invoices
- Open invoices and customer records from your ERP
Fields captured
Our agents are extroverts.
Cloud storage like S3, Google Drive, Dropbox and Box. Databases and warehouses like Snowflake, BigQuery, Postgres and SQL Server. Accounting, ERP and CRM systems like QuickBooks, Xero, SAP, NetSuite, Salesforce and HubSpot. Project trackers like Jira, Asana, ClickUp and Linear. And anything with an API.
Live on one lockbox first
No developers on your side and no switch-over weekend. The run is built on your own remittances and proven on one lockbox before any other payment channel joins it.
Book a consultation
We go through a day of your payments together: which customers pay how, where their remittances turn up, and which deductions your team disputes.
Built on your documents
The fields, the matching rules against your open invoices, your deduction codes and thresholds, and the posting to your ERP are set up on your own remittances.
Pilot on one lockbox, then roll out
One lockbox runs live within days. When the applied cash holds up, ACH, wire and portal remittances follow with the same exception rules.
Built for the teams that apply and collect cash
Payments applied the morning they land, with only short pays, unknown payers and unmatched invoices left on a specialist's screen.
An open-items list that reflects what customers have paid, so nobody chases an invoice that was settled last week.
Unapplied cash near zero at month-end, and accounts receivable automation with a recorded decision behind every manual application.
One run across every client and entity, each with its own customer master, deduction codes and ERP.
Cash applied the day it lands, deductions opened the same day
Customer payments and bank details, handled with care
Remittances and check images carry your customers' bank account and routing numbers, what they paid and what they refused to pay. A check image alone holds enough to forge a check against that account.
- Encrypted in transit and at rest.
- Remittances, check images and bank files are never used to train models.
- Access by role, entity and customer, with every manual application and correction recorded against the payment.
- Retention you set: check images and remittances are deleted on your schedule.
- Self-hosted deployment for treasury and AR teams whose bank data must stay inside their own environment.
What AR managers ask before they start
Point the run at your lockbox files and your remittance inbox. LLMWhisperer turns each check, stub and remittance into text with its lines intact, Document Studio pulls the payer and every invoice paid, and Flow matches those lines to open invoices in your ERP and posts the applied cash. Only the payments that fail a check wait for a person.
Extraction alone leaves your team holding a spreadsheet of remittance lines. Unstract reads the remittance, matches each line to the customer's open invoices, splits off coded deductions and posts the result, so the extraction and the application run as one process.
Most accounts receivable automation software handles invoicing, dunning and the bank file well, and leaves the remittance to a person when it arrives as an email, a stub or a portal download. Unstract reads those remittances in the customer's own layout and feeds the application your current tools already run.
At the remittance. The payment amount on the bank file is clean; the list of invoices it covers is not. Customers name your invoice number their own way, combine payments, take deductions with a code and no backup, or send the detail days later. Reading that remittance reliably is what lets the match run without a person.
Each short pay is applied against its invoice and the difference is split off as a deduction with its code and reason. Below the threshold you set, it opens in your deduction queue on its own. Above it, or with a code you don't recognise, it stops for an AR specialist with the remittance and the open item side by side.
It waits as unapplied cash and is matched again when the remittance arrives. If nothing arrives within the window you set, it goes to a collector or an AR specialist with the payer, the amount and the customer's open invoices that come closest.
To your ERP or accounts receivable system, such as NetSuite or QuickBooks, posted against the invoices it paid. Deductions go to your deduction management queue, and finance gets a daily summary in Slack. Flow posts as part of the run, so no one downloads and keys the result.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Check images and remittances are encrypted in transit and at rest, never used to train models, and kept only as long as you choose. Self-hosted deployment keeps processing inside your own environment.
No developers needed. In a consultation we build the run around your own remittances, deduction codes and ERP, put one lockbox live, and most teams are running there within days. Other payment channels join once the applied cash holds up.
Bring a day of payments to the consultation
One lockbox file and the remittances that came with it, the crooked stubs and the short pays included. We apply them live in front of you.