Reference
Every feature, one page
The complete capability list, one sentence each. For the story, take the product tour; for the practice, open the live demo — most links below land in its built-in documentation, the same docs a customer's team uses.
Capture
Email capture (M365 / Gmail / IMAP)
Monitored mailboxes ingest attachments and HTML-body documents automatically; each inbox can pin a document type or auto-classify.
Drag-and-drop upload
PDF, scans, photos, Excel, HTML, forwarded .eml — with per-file progress and a batch summary.
EDI intake (X12)
850, 860, 810, 856 parsed exactly; 855 and 997 join the documents they answer instead of becoming queue items.
E-invoices (UBL/Peppol, Factur-X, cXML)
Parsed deterministically at confidence 1.0 — no AI call, nothing to misread.
Extraction
AI extraction, no templates
Claude reads layouts it has never seen; the prompt is generated from your field schema.
Train on your samples
Upload real documents per type; review the guidance before it goes live.
Learning from corrections
Reviewer edits aggregate into new guidance automatically — one systematic fix, not row-by-row.
Plain-English processing rules
Ordinary sentences applied to every document; toggle each rule on or off.
Model & key as configuration
Choose the model, rotate the key, tune caching — takes effect on the next document, no restart.
Checks & intelligence
Validation tied to fields
Every issue carries a stable code and highlights the exact field that caused it.
Duplicate vs. reissue detection
Same number, same total = resend (warning). Same number, different total = reissue (error). Only the later copy is flagged.
Two- & three-way matching
Invoice ↔ PO, optionally ↔ receipt; receipts from captured packing slips or the ERP's own records.
Vendor statement reconciliation
Each line resolves to matched / never-captured / amounts-disagree / listed-twice, to the cent.
Credit memo linkage
Linked to the invoice offset; over-crediting flagged cumulatively; posted as vendor credits, never payables.
Related documents
The paperwork trail around any document, computed on demand.
Supplier collaboration
Order confirmations without a portal
A signed link; confirm, propose changes, or decline. No supplier account, ever.
Inbound shipment board
In transit / received / invoiced, overdue on top, promise never counted as delivery.
Supplier scorecards
Five measures from documents you already capture; dashes, never fake zeros.
Workflow & controls
Auto / Review lanes
Clean documents flow; flagged ones queue for a human, per document type.
Approval routing
Rules by amount / vendor / GL / type; delegation; reminders; signed no-login approve links.
Straight-through posting
Optional auto-post gated on the lowest field confidence, with a circuit breaker on failures.
Payment-file export
Proposal CSV or NACHA ACH from approved bills; no money movement, by design.
GL-code suggestions
From your keyword rules, then from how the same item was coded before.
Audit trail with actors
Append-only history of every ingest, edit, transition, and export — with before/after diffs.
Export & integration
ERP export with field mapping
A visual per-type map shapes the exact payload; required fields block export until filled.
13+ ERP connectors
QuickBooks, Xero, Business Central, F&O, NetSuite, Sage Intacct, Acumatica, Infor XA, SAP, Sage 50, REST, CSV.
Outbound EDI
997, 855, 865, 856, 810 — generated only for clean documents, with per-partner implementation guides as config.
Export-once protection
A successful post can't silently repeat; a deliberate re-post is confirmed and recorded.
Event webhooks
HMAC-signed lifecycle events to your endpoints.
Read-only API
Versioned /api/v1 with hashed bearer keys; writes refused by design.
Book a working session, not a sales call
Bring two or three of your real documents — your ugliest invoice, a customer PO, an EDI file. In 30 minutes we'll run them through extraction, validation, and a mapping to your ERP, live. You'll leave knowing exactly what your rollout would look like, and you'll get the founder, not a sales team.