# Inferio

> Inferio is an AI-powered OCR platform that turns invoices, receipts, bank statements, contracts, and KYC documents into validated, system-ready data. Japan-compliant out of the box (T-number + Electronic Bookkeeping Law). Built for AP, compliance, and integration teams.

Built by LAR Technology. Canonical site: https://inferio.xyz · Developer docs: https://docs.inferio.xyz.

## Key facts

- **Category:** AI-powered OCR / intelligent document processing for invoices, receipts, bank statements, contracts, and KYC / identity documents.
- **Extraction:** Layout-aware field extraction powered by Claude Vision — vendor, T-number, line items, tax breakdown, dates, and amounts — not template-bound positional OCR.
- **Japan compliance:** Built for the Qualified Invoice System — T-numbers are validated in real time against the National Tax Agency (NTA) public API. Documents are archived with cryptographic timestamps to meet Electronic Bookkeeping Law (電子帳簿保存法) requirements.
- **Validation & accuracy:** Domain-specific validators (T-number, IBAN/BIC, date/amount consistency) run on every document; low-confidence fields (< 0.75) surface in a human-in-the-loop correction UI, and corrections feed back into the model.
- **Integrations:** Direct sync to freee, MoneyForward, Salesforce, NetSuite, SAP, or a custom ERP. Core REST API (idempotent, retry-safe, batch-friendly) plus Node / Python / Go SDKs.
- **Inputs:** PDF / PNG / JPG / TIFF via drag-drop, email webhook, or REST API. Multi-page and batch documents supported.
- **Pricing:** Pay per page. No setup fee, no subscription, no charge on rejected pages. Trial credits cover the first batches; the per-page rate falls automatically with monthly volume, down to about $0.005 per page at scale. Enterprise volumes get a custom rate card.
- **Enterprise:** Inferio Enterprise handles B2B document processing for banking, logistics, and large SMEs (trade invoices, letters of credit, KYC), with a paid proof-of-concept on your own documents.

## Ways to use Inferio

- **Web dashboard** — Drag-drop supplier invoices into the Admin UI. Approve or correct exceptions before sync. T-number validation, freee + MoneyForward auto-journals, full audit trail — no code required.
- **Inferio Enterprise** — B2B document processing for banking, logistics, and large SMEs. Trade invoices, letters of credit, bank statements, payroll records, KYC docs — all on the same engine. ERP integration via REST + webhook.
- **Core REST API** — Plain HTTP + JSON. Idempotent, retry-safe, batch-friendly. Drop the same engine into your own product or AP automation pipeline — no middleware required.

## How document processing works

1. **Ingestion** — PDF / PNG / JPG / TIFF via drag-drop, email webhook, or REST API. Multi-page documents and scanned images handled with automatic format detection.
2. **Pre-processing** — Auto-deskew, noise reduction, contrast enhancement, and upscaling for low-quality scans. Consistent normalised input regardless of source quality.
3. **AI extraction** — Claude Vision performs layout-aware field extraction: vendor, T-number, line items, tax breakdown, totals. Structured JSON with per-field confidence scores.
4. **Validation** — Domain-specific validators: T-number via NTA public API, IBAN/BIC for banking, date and amount cross-checks. Anomalies flagged for human review.
5. **Human-in-the-loop** — Low-confidence fields (< 0.75) surface in a lightweight correction UI. Corrections feed back as fine-tuning signals — accuracy improves with usage.
6. **System integration** — Validated data syncs to freee, MoneyForward, Salesforce, NetSuite, SAP, or custom ERP via REST + webhook. Full audit trail maintained per document.
7. **Compliant archival** — Documents archived with cryptographic timestamps (Electronic Bookkeeping Law compliant). Metadata indexed for full-text search. 7-year retention by default.

## Frequently asked questions

### Is Inferio compliant with Japan's Invoice System (the Qualified Invoice System)?

Yes — that's the headline use case. Every extracted T-number is validated against the National Tax Agency public API in real time, with the response (valid / invalid / not-found) stored on the document record. Tax-rate classification (8% reduced vs. 10% standard) runs per line item. The system surfaces invalid registrations before they hit your accounting books.

### Does the archival meet the Electronic Bookkeeping Law requirements?

Yes. Documents are archived with cryptographic timestamps, metadata is indexed for full-text search (vendor, date, amount, document type), and the default retention period is 7 years. The audit trail captures every extraction, validation action, correction, and sync — exportable per request as an Electronic-Bookkeeping-Law-grade evidence chain.

### Which accounting systems sync directly?

freee and MoneyForward via direct OAuth 2.0 API integration — extracted invoices land as journal entries in real time. For ERP systems (SAP, NetSuite, Salesforce, in-house) we integrate via REST + webhook. Custom downstream pipelines wire up the same way — sign the webhook receiver and we'll handle delivery + retries.

### What documents can Inferio handle today?

Seven document types ship pre-tuned with their own JSON schemas: JP trade invoices (with T-number), letters of credit (40+ fields including Incoterms), bank statements (IBAN/BIC + balances), payroll records (salary + deductions + tax), KYC / identity docs (MRZ + fields), receipts, and purchase orders. For anything else, define a JSON schema in the dashboard and the extractor adapts without retraining.

### Can Inferio read handwriting?

Yes — the vision-language engine reads handwriting in context (a handwritten total on a printed invoice, amounts and dates on forms, short notes), which traditional character-matching OCR could not do. Handwriting accuracy is always lower than printed text, so every extracted field carries a confidence score and anything below the 0.75 threshold routes to human review instead of posting silently.

### Does it handle scanned PDFs, multi-page files, and phone photos?

Yes. The product ingests PDF, PNG, JPG, and TIFF including multi-page documents — a scanned PDF is read page by page the same way as a photographed receipt. Phone photos are pre-processed (deskew, noise reduction, contrast) before extraction, so a slightly tilted shot taken at a desk is normal input, not an edge case.

### Can the extracted data feed my own AI or analytics?

That's the point of structured extraction: every document becomes queryable fields (vendor, dates, line items, tax, totals) instead of a dead image. Pull it through the REST API or signed webhooks into your database or warehouse, and it becomes the data foundation your internal analytics, reconciliation, or AI assistant answers from.

### How accurate is it on real Japanese documents?

99%+ field-level accuracy on JP mixed-script invoices and 99.2% on letter-of-credit fields in our banking deployment. Claude Vision is layout-aware and reasons about context, so it handles handwriting, rotated phone shots, and noisy scans far better than traditional OCR. Fields below 0.75 confidence are flagged for human review — we treat that as a feature, not a failure mode.

### How does the enterprise paid POC work?

Fixed fee — $3,200 / ¥500,000 for 2 weeks. We run live extraction on 3–5 of your real document types in a sandboxed environment, benchmark per-field precision against your ground truth, connect to your test accounting / ERP system, and deliver a written accuracy report. If the benchmark hits your targets, we agree on production scope; if not, you've spent two weeks of fixed-fee learning.

### What's the cost per page at volume?

Pay-as-you-go per processed page. Public ladder: $0.012 / page under 1,000 pages / month → $0.008 from 1,000–10,000 → $0.005 from 10,000–100,000. Past 100,000 pages / month customers qualify for enterprise per-document pricing ($0.03–$0.20 per doc depending on type complexity + SLA) or a monthly seat license for predictable cost.

### Where do my documents live?

Originals stay on your infrastructure by default. Inferio processes them in-memory only — the AI provider does not retain or train on your documents. Hosted plans have an optional short-retention staging bucket (configurable, default 7 days) for replay. Enterprise contracts can deploy the model on-premise for maximum data isolation.

### Do you have any production deployments to point at?

Yes. We've shipped an end-to-end letter-of-credit extraction system for a major financial institution (40+ fields, 99.2% accuracy, replaced a 6-person manual review team), a payroll OCR platform processing 10,000+ documents / month with direct accounting integration, a RAG-based enterprise support bot deflecting 78% of queries from human agents, and a multi-agent document router classifying 15 document types and dispatching to downstream workflows.

### Is there a Node / Python / Go SDK?

Not yet — but the REST API is plain HTTP + JSON, so `axios.post` / `requests.post` / `http.Post` works today. We're shipping idiomatic SDKs for Node, Python, and Go next; the proposal stack uses Python / FastAPI on the server side so a Python SDK lands first. Drop your email in the Developers section to get the beta invite.

### What does implementation look like?

Five phases over ~6 weeks for a standard rollout. Phase 1–2 (weeks 1–3): core pipeline + T-number validation + Electronic-Bookkeeping-Law archival on your tenant. Phase 3 (weeks 4–5): freee / MoneyForward (or your ERP) integration + correction UI wired into your AP workflow. Phase 4 (week 6): full QA cycle, security review, audit-trail walkthrough. Phase 5 (post-launch): multi-doc-type expansion (LC, payroll, KYC) as new document classes come online.

### How does the partner program work?

System integrators, accounting firms, and ERP consultancies apply for a partner code. When referred customers sign up and start processing, you earn a base commission on their monthly bill plus a tier boost (Silver → Diamond) as you bring more on. White-label revenue share available for system integrators bidding on AP automation projects.

## Guides on automating documents with AI OCR

- [What is AI OCR (and how is it different from traditional OCR)?](https://inferio.xyz/blog/what-is-ai-ocr)
- [Why AI is only as accurate as your data (and why OCR comes first)](https://inferio.xyz/blog/ai-needs-your-data)
- [Template vs AI freeform extraction: which one for your documents?](https://inferio.xyz/blog/template-vs-freeform-extraction)
- [How do you turn a photo into structured data, not just raw text?](https://inferio.xyz/blog/image-to-structured-data)
- [How do you extract data from a PDF (digital or scanned)?](https://inferio.xyz/blog/extract-data-from-pdf)
- [Can OCR read handwriting? An honest answer](https://inferio.xyz/blog/handwriting-ocr)
- [How do you consolidate invoice data from dozens of vendors into one table?](https://inferio.xyz/blog/consolidate-invoice-data)
- [How do you turn paper documents into a searchable digital archive?](https://inferio.xyz/blog/paper-to-digital-archive)
- [Automating accounts payable for small teams](https://inferio.xyz/blog/automate-ap-for-sme)

## Links

- [Home](https://inferio.xyz)
- [Pricing](https://inferio.xyz/pricing)
- [OCR tool](https://inferio.xyz/tools/ocr-demo)
- [Developer documentation](https://docs.inferio.xyz)
- [Start with trial credits](https://merchant.inferio.xyz)
- [Sitemap](https://inferio.xyz/sitemap.xml)
- Sales / partnerships: contact@lartech.xyz

---
Generated from the same source copy as the website. Canonical source: https://inferio.xyz