Extract data from payment vouchers
Unstract reads payment vouchers, check request forms and payment request forms, typed or signed and scanned, and sends the payee, amount, coding and approvals, checked, to your ERP or accounting system for payment.
new vendor — W-9 requested 10/24
Attach quote or invoice. Over $5,000 needs CFO sign-off.
{ "voucher_number": "PV-26-0814", "payee": "Brightwater Event Rentals LLC", "amount": 4860, "payment_method": "CHECK", "gl_account": "6420", "cost_center": "CC-310", "reference": "Non-PO, quote BQ-5512", "requested_by": "M. Delgado", "approved_by": "R. Whitcombe", "confidence": 0.96}
Trusted by finance teams around the globe
Every department fills in its own version of the form
A typed voucher from the finance team's template is the easy one. Requests for payment reach AP in plenty of other shapes.
Printed for a signature, then scanned back at an angle
Check requests, vouchers and non-PO forms, each laid out its own way
GL codes struck through and rewritten by the approver
Voucher, quote, W-9 and receipt scanned as one file
A shared log of requests waiting on a signature
AP retypes each voucher and chases each missing signature by email, so urgent payments go out late and a request split to stay under an approval limit gets paid twice.
Unstract reads each voucher or check request as it lands, extracts the payee, amount, coding and signatures, checks them against your vendor master and approval rules, and posts the approved ones to your ERP or accounting system.
Read the request, check the approvals, pay it, on one platform
One product reads the form, one turns it into a payment record, one runs the approval and posting around it. Each works alone, and they stack.
Parse payment vouchers and check requests with every signature and date kept
Get the full text of a voucher whether someone typed it into your template, filled in a printout by hand or photographed it on a desk. Check request form OCR keeps each box beside its label: the amount stays in the amount box, the CHECK, ACH or WIRE box shows as marked or empty, and the requester's and approver's names stay next to the dates they signed.
Send the text to your own LLM, or make parsing the first step of payment voucher processing.
Learn more about LLMWhispererExtract payment voucher data into one record per payment
Name the fields once, from payee and remit-to address to GL account, cost center, business purpose and each approver, and every voucher, check request or advance payment request returns the same JSON record. A form one department redesigned last year fills the same fields as the finance template. The record is checked as it is built: a payee missing from the vendor master, or a second request for the same amount days after the first, comes back flagged with what it matched.
Call it as an API from your request portal, run it as an ETL pipeline on the AP mailbox, or make it one step in an orchestrated payables process.
Learn more about Document StudioRun payment vouchers through the same approval and posting as invoices
Describe how your payment vouchers and check requests should be handled, in plain English, and Flow's agents build the workflow. A request reaches the AP inbox with its quote or invoice attached, is read and coded, and is matched to its PO and goods receipt when it cites one. Non-PO requests carry that label instead. Repeat payees and amounts, new bank details and totals that disagree with the attachment are caught next, and approved vouchers post to your ERP or accounting system, such as NetSuite or QuickBooks. You approve the workflow once, and every voucher then goes through it the same way.
Decide where a person steps in: a request with no PO, a payee not yet in the vendor master, an amount above the signer's limit, a possible duplicate, changed bank details. Those vouchers stop with the reason attached for an AP specialist, who sends them on to the budget owner.
Learn more about FlowExtract voucher data today. Automate payment approvals later.
Start for free and run your own check requests through parsing and extraction now. Routing and posting them end to end begins with a consultation.
Vouchers, check requests and the paperwork attached to them
Documents
- Payment vouchers
- Check request forms
- Payment request forms
- Non-PO payment request forms
- Advance payment requests
- Requests for payment approval forms
- Cash disbursement vouchers
- Petty cash vouchers
- Wire and ACH payment requests
- Customer refund requests
- Supplier invoices
- Vendor quotes and estimates
- W-9 forms
- Receipts
Fields captured
For the teams that request, approve and release payments
Vouchers arrive coded and with their signatures read, so AP releases payments without retyping forms or emailing managers for a missing approval.
Non-PO requests are visible as they come in, so purchasing can see which recurring spend should move onto a purchase order.
Every payment ties back to a signed request, an approver within their limit and a GL account, which is what auditors ask for first.
One setup reads each client's own voucher and check request forms, so a new entity starts without a template per department.
Payments released sooner, with every approval on file
Protect payee bank details and approval signatures
A payment voucher pairs a payee's bank or remit-to details with an amount and the signature that releases it. Fraudulent payments go out exactly this way: a forged approval or a swapped account number on a form that looks routine.
- Encrypted in transit and at rest.
- Payment requests are never used for model training.
- Access by role, entity and approval limit, and every edit to a payee, amount or approver on a voucher is logged.
- Retention follows your disbursement records policy, and vouchers are deleted when the period you set ends.
- Self-hosted deployment for treasury and AP teams that keep payee bank data inside their own network.
What AP teams ask about vouchers and check requests
A check request is how an employee asks AP to pay someone when there is no supplier invoice to process, such as a deposit, a fee or a refund. A payment voucher is the record AP keeps for any payment, with the coding and approvals that authorize it. Many companies use one form for both, so Unstract reads them into the same record.
By the rules you set: department, amount, GL account or payee. Flow reads the requester and cost center from the voucher, sends it to the budget owner, and adds a second approver when the amount is above that person's limit. A voucher returned for changes goes back to the requester with the reason, and each decision is logged.
Parse the scan with its layout kept first, then extract fields by meaning rather than by position. LLMWhisperer keeps each box beside its label and reads handwritten names and dates, and Document Studio returns the same record for every version of the form, so a redesigned template does not break anything.
Yes. The reference box is read as written, so a PO number sends the request to the PO and goods receipt match, and "non-PO" or a quote number marks it as non-PO spend. Your rules then decide what non-PO spend needs, such as an extra approver above a set amount.
It reads the names and dates written beside each signature line and records whether each line is signed or blank. A voucher with an empty approver line is held before payment, and the record shows which signature is missing.
Each voucher is compared with recent requests and posted invoices by payee, amount, date and reference. Two requests for the same payee and amount a few days apart, or several just under one approver's limit, come back flagged for AP to review before either is paid.
The voucher stops for an AP specialist with the payee name and remit address it read. The specialist sets the vendor up with a W-9 or links the request to an existing vendor, and the payment continues from where it stopped.
JSON, in a schema you define. A typical record holds the voucher number, payee, address, amount, currency, payment method, PO or quote reference, GL account, cost center, business purpose, and each requester and approver with their dates. A box nobody filled in comes back empty for a person to complete.
Deploy an API endpoint for payment requests and call it from your request portal, or run an ETL pipeline on the AP mailbox. Approved records post to NetSuite, QuickBooks, SAP or Xero, or land in the import file your accounting system already reads.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Vouchers are encrypted in transit and at rest, never used to train models, and deleted at the end of the retention period you choose, with self-hosting for teams that keep payee bank data on their own servers. Details are in the Trust Center.
Bring a month of check requests and payment vouchers
Typed, hand-signed and scanned, with the quotes and receipts attached. We read them live and show the coding, the approvals and every request that would have stopped.