Extract data from vendor registration forms
Unstract reads vendor registration and supplier onboarding forms, typed, hand-filled or scanned, and returns the legal name, tax ID, remit-to bank details and payment terms, checked, to your ERP or accounting system.
W-9 + voided check attached. New bank as of Nov.
Halden Foods Vendor Registration (Rev. 2025)
{ "legal_name": "Marlow Creek Packaging Co.", "dba": "Marlow Creek Pack", "tax_id": "**-***4321", "bank_name": "Lakeshore Community Bank", "routing": "*****3456", "account": "******4417", "payment_terms": "NET 30", "form_1099": "NO", "diversity": "WBE", "confidence": 0.95}
Trusted by finance teams around the globe
Every buyer has its own vendor form, and every supplier fills it in differently
A supplier that types into your fillable PDF saves AP ten minutes. Most new vendor forms come back looking like this.
Printed, filled in by pen, signed and scanned back skewed
Your own form, an old revision and the supplier's own layout
Bank numbers written by hand, one of them crossed out and rewritten
Registration form, W-9, voided check and COI in a single email
Bank change requests piling up next to the vendor master
Procurement emails the form, AP rekeys every box into the vendor master, and a single wrong digit in a routing number sends the vendor's first payment back, or to an account nobody checked.
Unstract reads each vendor registration form as it arrives, extracts the company, tax, bank and terms fields, checks them against the W-9 and the bank letter, and creates the vendor in your ERP or accounting system.
Read the vendor form, check the bank details, create the vendor
Parsing, extraction and the onboarding run each have their own product. Use one on its own, or chain all three from inbox to vendor master.
Read vendor registration forms with every box, tick and bank digit kept
Get the full text of a vendor registration form, whether the supplier typed it into your PDF, filled it in with a pen, or sent its own company profile instead. The layout survives: the ticked payment terms keep their label, the 1099 box shows yes or no, and the routing and account numbers stay in the boxes they were written in, in the order they were written.
Pass the text to your own LLM, or make it the first step of vendor setup.
Learn more about LLMWhispererA supplier onboarding form parser that returns one vendor master record
List the fields your vendor master needs, from legal name, DBA and tax ID to remit-to address, bank account, payment terms, 1099 status, diversity certification and insurance expiry. Each registration form comes back as the same JSON record, whatever layout the supplier used. A tax ID that differs from the W-9, or bank details that differ from the voided check, come back flagged with the document they disagree with.
Call it as an API from your supplier portal, run it as an ETL pipeline on the vendor setup mailbox, or make it one step in an orchestrated vendor onboarding run.
Learn more about Document StudioTake a new supplier from registration form to vendor master
Describe your vendor onboarding in plain English and Flow's agents build the workflow. The vendor registration form comes in with the W-9 or W-8BEN, a bank letter or voided check, the insurance certificate and the contract, by email or your supplier portal. Every document is read, the registration form is matched to the W-9, the bank details to the letter, insurance to your limits, and the supplier to your existing vendors so nobody is set up twice. Approved vendors land in NetSuite, QuickBooks, Coupa or SAP Ariba with their documents attached. You approve the workflow once, and it handles every new vendor the same way after that.
You decide where a person steps in: a legal name or tax ID that doesn't match the W-9, bank details that differ from the letter, a missing W-9, insurance below your minimum. Those suppliers go to procurement or AP with the gap spelled out, and any new or changed bank account always goes to a second reviewer.
Learn more about FlowExtract vendor form data now. Automate onboarding later.
Start for free and run your own vendor registration forms through parsing and extraction today. Onboarding end to end starts with a consultation.
Vendor registration forms and everything a new supplier sends with them
Documents
- Vendor registration forms
- Vendor master data forms
- New vendor forms
- Supplier onboarding forms
- Vendor information forms
- Bank account verification forms
- Vendor bank change requests
- ACH and direct deposit authorization forms
- Voided checks and bank letters
- IRS W-9 tax forms
- Certificates of insurance
- Supplier diversity certificates
Fields captured
Processes the vendor form feeds
For the teams that own the vendor master and pay what's in it
Remit-to bank details, terms and 1099 status in the vendor master without retyping a form, and every bank change checked against a letter before the next payment run.
New suppliers approved from a complete, checked file, so a sourcing decision isn't stalled by a missing tax ID or an unsigned form.
One record per vendor with the source form behind every field, so an audit of bank changes or duplicate vendors takes minutes.
Each client's own vendor form read by one setup, so onboarding for many entities needs no layout per client.
Suppliers set up faster, with bank details you can trust
Protect the bank details every payment depends on
A vendor registration form holds the account your payments go to, next to the vendor's tax ID and the names of the people who can change it. A forged form or a changed bank account is how most vendor payment fraud starts, so these details need tighter handling than the rest of the file.
- Encrypted in transit and at rest.
- Vendor forms and bank details are never used to train models.
- Role-based access, so full routing and account numbers are visible only to the reviewers you name, and each edit to a vendor's bank record is logged.
- Retention set by you: forms are removed once your record-keeping period ends.
- Self-hosted deployment for finance teams that keep vendor bank data on their own infrastructure.
What AP and procurement ask about vendor registration forms
Send the documents to Unstract by API, email or a watched folder. LLMWhisperer reads each one with its layout kept, and Document Studio returns the vendor's legal name, tax ID, address, contacts, bank details and terms as JSON in the schema you set. That is how teams extract vendor information from documents at scale without keying.
Yes. Unstract needs no template per form, so your own registration form, an older revision and a supplier's company profile all return the same record. You describe the fields once, and new layouts work without setup.
Yes. The registration form, W-9 or W-8BEN, voided check or bank letter, insurance certificate and contract are each identified and read, and the fields are joined into one vendor record with the source document named for each value.
The tax ID and legal name against the W-9, the routing and account numbers against the bank letter or voided check, insurance limits and expiry against your minimums, and the vendor against your existing vendor list. Supplier onboarding form processing with Unstract stops on any mismatch instead of creating the vendor.
Yes. LLMWhisperer reads handwriting alongside printed text, so a routing or account number written by pen comes through digit by digit. A number that was crossed out and rewritten is reported as written, and the check against the bank letter catches any digit that differs.
Yes. Checked and unchecked boxes both appear in the parsed text, so the record shows which terms the supplier ticked, whether it marked itself 1099 reportable, and which diversity certification it claims.
They are read like a registration form and compared with the bank details already on the vendor record. A changed account never goes straight to the vendor master: it waits for a second reviewer, with the old and new details side by side.
The vendor stops in a review queue for procurement or AP, with the field that differs named and both documents open. The reviewer fixes the record or asks the supplier for a corrected form, and the decision is logged against the vendor.
Yes. Describe the onboarding in plain English and Flow's agents build it: collect the packet, read each document, run the checks, route the approvals and create the vendor in NetSuite, QuickBooks, Coupa or SAP Ariba. You review the workflow before it runs, and every supplier goes through the same steps.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Vendor forms are encrypted in transit and at rest, never used for model training, and kept only as long as you choose, with self-hosting available for teams that keep bank data in-house. Read the full controls in the Trust Center.
Start for free, upload a vendor registration form and see the record in minutes, with no code. For onboarding end to end, we build the workflow with you in a consultation around your form, your approval chain and your vendor master.
Bring last month's new vendor forms to the consultation
Scanned, hand-filled and supplier-made layouts included, with the W-9s and bank letters that came with them. We run them live and show each field, each check and each vendor that would stop for review.