Trusted by teams turning documents into production data
Cross-industry
Invoices document what was sold, the amount owed, and when payment is due. Every vendor formats invoices differently, from accounting software exports to manual PDFs. Sensible converts invoice data into structured JSON for accounts payable automation and three-way matching.
Validated JSON
Schema-enforced output; every field matches your contract
Source coordinates
Every value links back to page + bounding box for audit
Per-document pricing
Predictable cost. No token-volatility surprises
Trusted by teams turning documents into production data
Every vendor formats invoices differently, and headers, totals, and line-item tables land somewhere new on each one. Hybrid extraction absorbs the variation; deterministic validation re-checks the math before the data hits your books.
01
QuickBooks exports, SAP invoices, handwritten bills, and custom ERP outputs each place fields differently. LLM parsing reads any layout; SenseML rules map the result to your AP schema consistently.
02
Multi-page tables, merged cells, multi-line descriptions, and varying tax codes. Line items get extracted with quantity, unit price, tax, and total intact. Page breaks are handled transparently.
03
Do line items sum to the subtotal? Does the tax match the rate? Sensible validates these calculations and flags discrepancies with confidence scores. Your AP team reviews exceptions, not every invoice.
Managed services
Solutions engineers handle plan, build, deploy, and adjust on your behalf. You see clean JSON in your API response. Same engine as self-serve, just with the configuration work outsourced.
What's included
01Plan.Engineers review your samples and pick the right method
02Build.SenseML configs written from your samples
03Deploy.Same engine as self-serve, ready for production
04Adjust.We update configs when formats shift or new edge cases appear
05Integrate.Help with custom integration into your downstream systems
Every invoice is different, so we build the config around your exact schema rather than a fixed list. These are the fields AP teams request most; we map whatever else your AP-automation workflow needs.
01
Header
Invoice number, invoice date, due date, PO number, vendor name, vendor address, bill-to name, bill-to address, payment terms
02
Line items
Description, quantity, unit price, unit of measure, discount, tax amount, extended amount, SKU/part number
03
Totals
Subtotal, discount total, tax total, shipping/freight, grand total, amount paid, balance due, currency
config.json
SenseML
{ /* SenseML: invoice extraction */
"fields": [
{
"method": {
"id": "queryGroup",
"queries": [
{ "id": "invoice_number", "description": "invoice number, invoice #, invoice no" },
{ "id": "invoice_date", "description": "invoice date, date of invoice, bill date" },
{ "id": "total_amount", "description": "total amount due, grand total, total, amount due" },
{ "id": "vendor_name", "description": "vendor name, from, billed by, seller name" }
// + more fields, mapped to your schema
]
}
}
]
}Sensible processes invoices from any vendor, any accounting system, any country. New formats can be configured in hours. The extraction logic is explicit in SenseML, not hidden in prompt tuning.
QuickBooks, Xero, NetSuite, SAP, Oracle, FreshBooks, Wave, custom/manual invoices
Standard invoices, credit memos, debit notes, proforma invoices, recurring invoices, construction progress billing
Answers about vendor format support, line item extraction, and calculation validation.
Sensible extracts PO reference numbers from invoices. You can match these against purchase orders processed through Sensible to verify quantities, pricing, and terms programmatically.
Yes. Validation rules cross-check that line item totals sum to the subtotal, that tax calculations are correct, and that the grand total matches. Discrepancies are flagged automatically.
Sensible reads each line item with description, quantity, unit price, and total across any invoice layout, combining multi-page tables and resolving subtotals, tax, and grand totals. The columns it captures are defined in configuration, so you can add fields like SKU, GL code, or unit of measure when an invoice carries them.
Yes. Sensible processes invoices regardless of format or vendor, with no per-vendor setup required to start. Common fields like invoice number, date, due date, vendor name, and totals come out of the box, and you add or reshape fields in configuration to fit what your AP workflow needs.
Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.
Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.
Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.
Document data is stored indefinitely by default. Custom retention policies are available and can be configured for same-day deletion if needed.
Yes. Sensible offers a 14-day free trial on the Growth plan. No credit card required to start.
Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.
Sensible provides REST APIs and SDKs for Python and Node.js. Most integrations take a few hours. Webhooks, Zapier, and direct API calls are all supported.
Sensible processes PDFs (native or scanned), Microsoft Word (DOC, DOCX), spreadsheets (XLSX, XLS, CSV), single-page images (JPEG, PNG), multi-page images (TIFF), and email bodies with attachments.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence signals.
Processing speed depends on document size, page count, OCR requirements, and which extraction methods are used. Simple single-page documents process in seconds. Larger or more complex documents that use LLM-based extraction take longer.
Start free
Free 14-day trial. No credit card required. Start extracting in minutes.