Extract data from payment authorization forms
Unstract reads signed wire transfer, ACH and direct debit authorization forms from faxes, scans and email attachments, checks the beneficiary and signers against what you hold on file, and sends each approved instruction to your payment or core banking system.
new beneficiary, call back before release
Form WT-200 · fictional bank and parties
{ "originator": "Halvorsen Marine Supply LLC", "amount": "48,250.00", "currency": "EUR", "value_date": "06 Nov 2026", "beneficiary_name": "Kestrel Fabrication GmbH", "beneficiary_bank": "Elbmark Handelsbank AG", "swift_bic": "ELBMDEHHXXX", "beneficiary_iban": "DE** **** **** **** **72 18", "callback": "10:42 / RT", "beneficiary_on_file": false}
Trusted by lending and onboarding teams around the globe
Payment instructions reach the wire desk in every shape a client can send
Corporate clients fax a signed form, scan it at an angle, or attach a spreadsheet of forty payees to a one-page payment order. Each one moves money once someone releases it.
Faxed wire requests with a smudged digit in the beneficiary account
One beneficiary account, three labels across three banks' forms
Amounts corrected by hand and initialled beside the strike-through
Four kinds of payment instruction scanned into one PDF
Payment orders that point to a spreadsheet of payees
Operations staff key every beneficiary, account number and amount from the form into the payment system and compare signatures by eye, so a changed bank account on a familiar supplier name can reach the release queue unnoticed and the money is gone before anyone asks.
Unstract reads the form as it arrives, extracts the payment details and signers, checks them against your beneficiary file, signer list and limits, and releases clean instructions to your payment or core banking system.
From a signed form to a released payment, with the fraud checks in between
Read the form, extract the instruction, then run the checks your wire desk already performs. Each product runs alone, and the three together hold back the request that does not match what you have on file.
Wire transfer form OCR that reads payment authorization forms box by box
LLMWhisperer turns a faxed or scanned payment form into text with the layout intact, so the originator's account never swaps places with the beneficiary's. It reads the amount in figures and in words, the SWIFT code and IBAN character by character, the ticked payment type and the handwritten signatures and call-back initials, from faxes, skewed scans and phone photos.
Pass that text to your own LLM, or make it the first step of the wire release run.
Learn more about LLMWhispererTurn wire, ACH and direct debit authorization forms into one payment record
List the fields your payment system needs, and Document Studio returns them in one JSON shape whether the form is a bank's own wire template, a client's letterhead request or a direct debit mandate. Wire transfer authorization form extraction compares the amount in figures with the amount in words, matches the beneficiary account with the account you hold for that payee, and flags a new or changed one with the reason.
ACH authorization form data extraction runs the same way for payroll and supplier debits. Call it as an API from your treasury portal, run it as an ETL pipeline over the fax inbox, or make it one step of an orchestrated release run.
Learn more about Document StudioRun wire release from the signed request to the payment system
Describe how your desk handles a wire transfer authorization form in plain English, and Flow's agents build the workflow. Each request is read, its signers are checked against the account's authorized signer list, the amount is compared with the client's limits, and a new beneficiary is marked for a call-back to the number already on file. You approve the workflow once, and every form runs through it the same way.
You choose where a person steps in: changed beneficiary bank details, an amount above the signer's limit that needs a second approver, a signature that does not match, or figures and words that disagree. Only those requests stop, and an operations analyst sees the form beside the payee record with the difference marked.
Learn more about FlowRead your clients' payment forms today. Automate wire release when you're ready.
Start for free and run your own wire, ACH and direct debit forms through parsing and extraction now. Signer checks, call-back holds and release to your payment or core banking system start with a consultation.
Wire, ACH and direct debit forms, and the payment orders behind them
Documents
- Wire transfer authorization forms
- Outgoing wire transfer requests
- International wire request forms
- Recurring wire templates
- ACH authorization forms
- ACH debit and credit authorizations
- Direct debit authorizations
- SEPA direct debit mandates
- Standing orders
- Payment orders
- Bulk payment schedules
- Payroll payment authorizations
- Change of bank details forms
- Authorized signer lists
- Corporate resolutions naming signers
- Funds transfer agreements
Fields captured
For the teams that send money out and answer for every wire
The wire desk stops keying forms. Each request arrives with the beneficiary, amount and signers already extracted, and only the ones with a new payee or an over-limit amount wait for a person.
Supplier and intercompany wires go out on the value date the treasury team asked for, and a payment order with a schedule of payees is read line by line instead of retyped into the bank portal.
Vendor payments leave with the same bank details the vendor master holds, and a supplier's emailed request to change accounts is held until someone confirms it by phone.
Every changed beneficiary, failed signer match and call-back is logged against the request, so an investigator can show which wires were held and who released them.
Wires checked before they are released
Keeping signed payment instructions out of a fraudster's hands
Account and routing numbers plus a signature are what a fraudster needs to move money. A payment authorization form puts all three on one page, beside the name of a supplier the bank already trusts, which is why a copied form or a quietly edited IBAN ends in a wire that cannot be recalled.
- Encrypted in transit and at rest.
- Payment forms and client account details are never used to train models.
- Access by role and payment queue, with every edited field, held wire and call-back result logged against the request.
- You set retention: form images are deleted on your record-keeping schedule, and the extracted instruction and its audit trail stay.
- Self-hosted deployment for banks that keep payment instructions and signer data inside their own network.
What payment operations and treasury teams ask about reading payment forms
It is the signed instruction a client gives its bank to send a wire: the originator's account, the amount, the value date, the beneficiary and their bank, the SWIFT or routing code, and one or two authorized signatures. Unstract reads each of those boxes and returns them as one record your payment system can use.
Send the form to Unstract instead of to a keying queue. LLMWhisperer reads the fax or scan, and Document Studio returns the beneficiary, bank, account, amount and signers as JSON. Start for free on your own forms, then run the same extraction from an API or a watched inbox.
Yes. Handwritten amounts, initials and call-back notes are read alongside the printed text, and each signature box is reported as signed or blank. The amount in figures is compared with the amount in words, so a corrected digit shows up as a mismatch.
The extracted beneficiary name, bank and account are matched against the payee you already hold for that client. A new payee or a different account under a familiar name stops the request for a call-back to the phone number on file, never one printed on the form.
The request waits for a second approver. Flow holds it with the form, the signer's limit and the amount side by side, and resumes the run once the approval is recorded.
An ACH authorization lets a company debit or credit an account, often on a schedule, and carries a routing number, account type and start date instead of a SWIFT code and value date. Unstract reads both into the same payment record, with the fields each one carries.
Yes. Direct debit mandates and authorizations are read for the payer, the creditor, the mandate reference, the account and the frequency, then checked against the account holder's signature before the debit is set up.
Yes. Standing order form OCR reads the payee, amount, first payment date, frequency and end date, so a recurring payment is set up from the form the customer signed rather than from a retyped copy.
Yes. The signed payment order and its attached schedule are read together, each payee row becomes its own instruction, and the row total is checked against the total on the order.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Forms are encrypted in transit and at rest, never used to train models, and deleted on the schedule you set. Banks that keep payment data in-house can self-host it.
Bring a week of signed wire and ACH forms to the consultation
Faxed wire requests, a direct debit mandate, a payment order with its payee schedule and the request where the beneficiary account changed. We read them live and show the fields, the signer check and every hold.