Invoices before approval
Extract supplier, invoice number, due date, totals, VAT rows, IBAN, and payment reference from PDF invoices.
Use cases
Use cases for document-heavy teams.
Start with the documents that slow approvals, records, and ERP imports. exdata turns PDFs, scans, email attachments, and e-invoices into structured fields your systems can route.
Industries and sectors
Choose the workflow that needs structured fields first.
Each sector starts with the same dependable pattern: upload the document, extract evidenced fields, then hand normalized JSON to the system that already owns the process.
Searchable records
Enrich archived PDFs and scans with names, dates, amounts, references, tax IDs, and document categories.
Cleaner ERP imports
Normalize document fields before they enter ERP import queues, validation jobs, or customer-specific workflows.
Payment readiness
Capture payment details, gross and net amounts, dates, references, and parties before review or payment runs.
Supplier document intake
Route supplier invoices, order references, period dates, and cost center data into the right operational queue.
Extraction inside client portals
Use one API to add extraction to accounting platforms, archive products, workflow tools, and custom client portals.
Incoming record handling
Turn incoming PDFs and scans into searchable records with dates, parties, references, and routing context.
Consistent processing across teams
Give multiple business units the same extraction API while keeping account access, usage, and support context separated.
Extensions on request
Request extensions for your custom documents.
When your sector uses forms, statements, or records that standard extraction does not cover yet, exdata can scope the document type and fields into the same API flow.
Extension scope
Add the fields your sector needs.
Extensions stay focused: a document type, a field group, and enough examples to make the result useful in the API.
Capture the forms your sector uses.
- Customs declarations
- Delivery notes
- Account statements
- Public forms
Return the details standard extraction should not guess.
- Industry codes
- Routing references
- Line context
- Review flags
Keep the same API surface.
Custom fields are returned as typed JSON so your review queue, validation rules, and downstream systems can use them without a second workflow.
Where to start
Pick the first workflow by operational signal.
The best first use case is usually a document flow with repeated fields, a clear owner, and a downstream system that already waits for the data.
Start with recurring business documents.
Use this when the team already reviews the same invoices, statements, receipts, delivery notes, or archive PDFs every week.
- Good signal
-
- Known fields
- Repeated files
- Manual copying today
Use an extension for sector-specific fields.
Use this when the document has industry codes, line context, regulatory references, or review flags that standard extraction should not guess.
- Good signal
-
- Special document type
- Sector codes
- Custom validation
Add extraction where files enter your product.
Use this when customers, internal teams, or branch offices already upload documents into a portal, inbox, or review queue.
- Good signal
-
- Existing upload flow
- Visible review queue
- API owner
Next