Trusted by teams turning documents into production data
Sensible is the extraction layer under your AP workflow: schema-validated and traced to source coordinates, so your finance team can trust the data without checking it by hand.
| Description | Qty | Amount |
|---|---|---|
| Strategy workshop facilitation | 2 | $3,700.00 |
| UX research interviews | 8 | $3,400.00 |
| Design system audit | 1 | $4,200.00 |
| Account management | 12 | $2,220.00 |
| Travel & expenses | 1 | $684.00 |
| Description | Qty | Amount |
|---|---|---|
| Strategy workshop facilitation | 2 | $3,700.00 |
| UX research interviews | 8 | $3,400.00 |
| Design system audit | 1 | $4,200.00 |
| Account management | 12 | $2,220.00 |
| Travel & expenses (NTE) | 1 | $700.00 |
| Description | Qty | Amount |
|---|---|---|
| Account management: hours credited | −2 | −$370.00 |
Hover a field to trace it to the source. Sample data; output is illustrative.
Per field
LLM or deterministic method
Per document
pricing, whatever the page count
SOC 2 + HIPAA
independently audited
No credit card
14-day free trial
Trusted by teams turning documents into production data
Headers, totals and line-item tables land somewhere different on every vendor’s document. Hybrid extraction handles the variation, and validation re-checks the math before anything reaches your ledger.
QuickBooks exports, SAP invoices, handwritten bills, custom ERP outputs: each one places fields somewhere different. Hybrid extraction (LLM parsing plus SenseML rules) absorbs the variation instead of breaking on it.
Multi-page tables, merged cells, multi-line descriptions and varying tax codes. Quantity, unit price, tax and amount stay attached to the right row, and page breaks are handled without you noticing them.
Do the line items sum to the subtotal? Does the tax match the rate? Does the grand total reconcile? This check catches a bad extraction before it reaches the ledger, not after.
An invoice’s PO number is only useful if it can be checked against the PO and goods receipt it references. Extraction has to keep that reference clean enough to match on, not just capture it as a string.
Grouped the way AP teams ask for them. Each field comes back typed, keeps the text as printed, and points to where it sits on the page.
invoice_numberstringinvoice_datedatesource.due_datedatepo_numberstringvendor_namestringvendor_addressstringbill_to_namestringbill_to_addressstringpayment_termsstringdescriptionstringquantitynumberunit_pricecurrencysource.unit_of_measurestringdiscountcurrencytax_amountcurrencyextended_amountcurrencyskustringsubtotalcurrencydiscount_totalcurrencytax_totalcurrencyshipping_freightcurrencygrand_totalcurrencyamount_paidcurrencybalance_duecurrencycurrencystringFive stages, and every field keeps its page and bounding box all the way through.
PDF, scan, email attachment or spreadsheet. Any source, no pre-sorting.
Document type identified (invoice, PO, credit memo, remittance) before extraction runs.
Hybrid AI plus deterministic SenseML rules pull header, line item and total fields, whatever the layout.
Calculation checks run automatically: line items to subtotal, tax to rate, PO reference format. Discrepancies are flagged for review.
Schema-enforced JSON, every field traced to page and bounding box, sent by webhook or pulled by API.
Webhook or API into your AP system, ERP or matching engine. Three-way matching, approval routing, posting and payment happen there. Sensible hands over data you can trust; it doesn’t run those steps.
Getting a number out of a PDF is the easy part. The question your finance team asks is whether it’s the right number, so Sensible checks each invoice the way an AP clerk would. When a check fails, the field is flagged and can be routed for review instead of flowing into your ledger.
We don’t publish a flat accuracy percentage. Accuracy depends on document quality and configuration, and a single number hides both.
Sensible
Solutions engineers handle plan, build, deploy and adjust on your behalf. You see clean JSON in your API response. Same engine as self-serve, with the configuration work done for you.
Engineers review your samples and pick the right method.
SenseML configs written from your samples.
Same engine as self-serve, ready for production.
Configs updated when formats shift or new edge cases appear.
Help with custom integration into your downstream systems.
The extraction logic is written out in SenseML rather than buried in prompts, so a new format can be added and reviewed.
QuickBooks · Xero · NetSuite · SAP · Oracle · FreshBooks · Wave · Custom / manual invoices
Standard invoices · Credit memos · Debit notes · Proforma invoices · Recurring invoices · Construction progress billing
Extracted against the same schema as the invoices that reference them, so the two can be compared field for field.
Received quantities captured in the same shape, so invoice lines can be matched against what actually arrived.
Payment references pulled out so they can be tied back to open invoices.
PDF (native or scanned) · Word · XLSX / XLS / CSV · JPEG / PNG · TIFF · Email bodies with attachments
Matching, duplicates, pricing, and where Sensible stops and your AP system starts.
No. Sensible is the extraction layer. It reads the invoice, the purchase order and the goods receipt, and captures the reference fields that tie them together (PO number, line quantities, unit prices, totals) in a consistent, schema-validated shape. The matching logic itself, including tolerances and exception handling, lives downstream in your AP system, ERP or matching engine.
Not as a built-in feature. Sensible’s validation rules run against one document at a time, and spotting a duplicate needs a comparison across documents you have already processed.
What Sensible does give you is a reliable duplicate key on every invoice: vendor, invoice number, invoice date and grand total, extracted the same way each time. Checking that key against your history belongs in your AP system or ERP. If you want that wired in as part of the pipeline, our managed-services team can help with the integration.
Sensible prices per document, not per token, so cost is predictable at 500 invoices a month or 50,000. There is no token-volatility surprise when a vendor sends a 40-line invoice instead of a 4-line one. Volume discounts are available for higher throughput; see pricing or talk to our team for a volume quote. Per-page pricing is also available for AP teams that prefer it. Talk to our team for more information.
Validation rules cross-check that line items sum to the subtotal, that tax matches the stated rate, and that the grand total reconciles. Discrepancies are flagged automatically and can be routed to human review. Results are delivered by webhook or API.
Accuracy depends on document quality and configuration, so we don’t quote a single flat number. What we can tell you is how the output is checked: schema enforcement and calculation validation, so weak extractions are flagged instead of passed through silently. The best way to know is to run your own invoices, including the ugly ones, through it.
Sensible is SOC 2 Type II certified and HIPAA compliant, with data encrypted in transit and at rest. Document data is stored indefinitely by default; custom retention policies are available, including same-day deletion.