Prepare vendor identity details when a W-9 arrives
For Vendor onboarding and accounts payable teams
Capture selected W-9 fields in a consistent record for your vendor onboarding queue. Begin with identity and address information and decide separately whether your process requires sensitive identifiers.
25 free credits/month · No card needed
See the workflow and review checks{
"taxpayer_name": "Example Vendor LLC — synthetic",
"business_name": "Example Field Services",
"classification_text": "Limited liability company; classification entered as C",
"mailing_address": "200 Example Avenue",
"city_state_zip": "Sample City, CA 00000",
"signature_date": "2026-08-03"
}Synthetic data, not a live extraction. Real responses also include confidence, validation, and result status.
When this work lands on your desk
A new supplier returns a W-9, and vendor operations must compare the submitted details with the onboarding request before activating the record.
The name on a supplier’s invoice can differ from the name on its W-9. Trade names, classification selections and mailing addresses need to be kept distinct so the reviewer can resolve them. A focused schema avoids treating a successfully extracted form as a verified vendor or a completed tax review.
Start with the documents you already collect
- Completed W-9 PDFs
- Scanned supplier W-9 forms
- Replacement W-9 submissions for existing vendors
PDF, JPEG, PNG, TIFF, or WEBP. Send one file per extraction call; create separate schemas when the document types need different fields.
Define the fields
Open the starter schema. Edit field descriptions, mark the values your process requires, and save it in your account.
Extract at intake
Send the document and saved schema slug to
POST /api/v1/extract, or collect the file through a branded upload site.Hand off reviewed data
Your vendor team compares the names and address with the onboarding record, reviews classification questions and performs any required identity or taxpayer checks. Vendor activation and sensitive-data handling remain customer-owned.
A schema shaped around the next step.
Start with these fields, then adjust them to match your documents and destination system. The example above shows the data object you are asking Dokyumi to extract.
Download editable starter schemaStarter fields are optional until you choose which are required. Nested line items need a defined structure if you want validation of their individual values.
| Field | Type | What to capture |
|---|---|---|
taxpayer_name | string | Name printed in the form’s primary name field. |
business_name | string | Business or disregarded entity name when supplied. |
classification_text | string | Visible classification selection and accompanying text. |
mailing_address | string | Address as printed for your separate address checks. |
city_state_zip | string | City, state and ZIP as stated on the form. |
signature_date | date | Written date when legible; not proof of signature validity. |
Give exceptions a clear path to review.
Dokyumi returns a model-reported confidence map, validation details, and a completed or review status for produced results. Check required fields and your business rules before passing data onward.
A completed extraction describes the extraction result. Your application and reviewers own matching, approvals, routing, and updates to other systems.
Read the response contractChecks for this process
- Business name differs from primary taxpayer name
- More than one classification box appears selected
- Replacement form conflicts with the current vendor record
- Date or handwritten entry is unreadable
Prove the fit on a representative batch.
Evaluate an authorized set with trade names, updated addresses and varied classification entries. Keep the initial schema limited to fields your reviewer needs and compare every result with the submitted form.
Compare extracted values with a reviewer’s reference set. Record corrections, unresolved fields, review time, and credits used before connecting downstream actions.
The free plan’s credit limits apply. Assisted pilots are scoped with Dokyumi before work begins.
Expand when the next process is ready
Use paid capacity for ongoing supplier onboarding. Add separate schemas for supplier applications and certificates when those documents become part of the same intake process.
For a tailored implementation
Discuss custom volume and schema assistance for multiple business units with distinct vendor intake requirements.
Talk through document mix and volumeStart small. Add capacity as intake grows.
All self-service plans include the REST API, upload-site webhooks, custom confidence thresholds, and schema inference. Choose by volume, schema count, and upload sites.
Each document uses one credit per 5 pages, rounded up. An 8-page file uses 2 credits. Self-service files can be up to 50 pages; larger files, custom-built schemas, and additional volume are quoted through Enterprise. Full pricing details
Questions about vendor w-9 onboarding
Does this validate a taxpayer identification number?
No. Extraction does not perform government matching or validate tax status. This starter schema deliberately excludes taxpayer identification numbers.
Can a completed extraction activate the vendor?
Your process decides activation after its required checks. Extraction status is not a vendor approval or a legal assessment of the form.
Can sensitive fields be added?
A custom schema can request additional printed fields. Add them only when your authorized workflow needs them and has appropriate handling controls.
How do I test this workflow on my own documents?
Start free with 25 credits per month, 2 schemas, and 1 branded upload site. The starter schema opens in the schema builder after sign-up. Edit the fields, save it, and upload a representative file through your account or the extraction API. Account documents are stored according to Dokyumi’s privacy policy; contact hello@dokyumi.com for deletion requests and retention requirements.