CalibreFrom intake to gateways, one invoice at a time.
Calibre automates supplier invoice processing end to end. Each invoice is read by our own document model, proven against GST rules and your purchase orders, decided with calibrated confidence, approved under your policy and posted to your ERP. Here is every station it passes through.
From intake to gateways. The whole movement on one plate.
Hover over any station. Invoices that pass every check clear and post; anything Calibre cannot prove goes to review, and the correction flows back into memory.
- 01
Intake
Email or upload. Every file is scanned for malware before anything reads it.
- 02
Vision
Pages turned upright, laid out and read word by word, with positions.
- 03
Reader
Our own document model reads each field and points to its words.
- 04
Proof
Four tiers of checks: form, arithmetic, GST and identity, policy.
- 05
Decision
Clears with calibrated confidence, or goes to a person with the reason.
- 06
Review
The document beside its fields, evidence one click away. Approval chains apply.
- 07
Memory
Corrections kept as evidence. Vendor memory and rules feed the next read.
- 08
Gateways
A preflight, then the invoice is posted once to your ERP with the PDF attached.
Every step leaves a record.
What the audit trail holds for one invoice. Services pass pointers, never the document, and every value records the model version and prompt that produced it.
- invoice.receivedobject=s3://t_8f2c/raw/7c1e…pdf · sha256=9b1f…
- upload.scannedmalware scan clean
- pages.readypages=1 · rotation=0° · text=native
- read.completereader=cal-r1@41ac… · prompt=v3 · grounded 14 of 14
- proof.tier1GSTIN check digit E ✓ · HSN 8-digit ✓ · invoice no. 14/16 ✓
- proof.tier2lines + tax = total (Δ ₹0.00) ✓ · amount in words ✓
- proof.tier336 → 27 inter-state ⇒ IGST ✓ · slab 18% ✓ · IRN RS256 ✓
- proof.tier4PO 4500018237 · 3 of 3 lines ✓ · not a duplicate ✓
- decisionreview · PO_REFERENCE_UNUSUAL · first invoice from vendor
- correctionpo_number confirmed · vendor memory updated
- approval.stepplant head approved · uploader excluded by segregation of duties
- erp.preflightPO open · vendor active · GL 5101 · tax IGST 18 ✓
- erp.postedbill created · key=pk_3e9… · PDF attached
When a person is needed, the evidence is already there.
Reviewers see the document beside its fields, with confidence on every value and one click to where it was found on the page. Each exception arrives with the check that raised it and the code your auditors will see.
- AdapterAuthentication and the ERP’s own operations. The only part written for each new ERP.
- MappingFields, GL accounts and tax codes. Versioned, with test cases that must pass before a mapping is published.
- PreflightPurchase order, vendor, GL account, tax code, currency, line reconciliation and duplicates, checked before any write.
- EngineA durable queue with retries, circuit breakers, quarantine and blackout windows.
- PostingWrites keyed so they happen once, the PDF attached, and the ERP document number returned.
- AuditEvery request and response kept, with the ERP’s own reply.
Questions finance teams ask
How long does a new ERP connector take?
Days, not months. Every connector is built on one platform, so a new ERP needs only its own adapter; mappings, preflight checks, retries, posting and the audit trail are already there.
Can an invoice be posted twice?
No. Every posting carries its own key, so retries and resent invoices never create a second entry in your ERP.
Do we change our chart of accounts?
No. Calibre reads your vendors, accounts and tax codes from your ERP and posts with the codes your team already uses.
Can we route invoices by amount, vendor or cost centre?
Yes. Approval policies route invoices by amount, vendor, cost centre or GL account to an ordered chain of approvers, each with their own approval limit.
See it on your own invoices.
Send us a month of invoices. We replay them against your ERP’s records and show you, vendor by vendor, what Calibre would have cleared, and why the rest would have gone to a person.