A build-to-order Frappe app that captures supplier invoices, receipts, and POs via AI/OCR and turns them into draft ERPNext Purchase Invoices and Expense Claims — with line-item, tax, supplier, and item auto-matching. ECOSIRE scopes, builds, installs, and supports it for you. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $499.00 USD; request a quote for a scoped proposal.

A build-to-order Frappe app that captures supplier invoices, receipts, and POs via AI/OCR and turns them into draft ERPNext Purchase Invoices and Expense Claims — with line-item, tax, supplier, and item auto-matching. ECOSIRE scopes, builds, installs, and supports it for you.
今すぐのお支払いはありません。これはチームへの見積もり依頼を送信します。価格と次のステップをメールでご案内します。
Finance and AP teams running ERPNext still key most supplier documents by hand. A PDF invoice arrives by email, someone opens it, retypes the supplier, the dates, every line item, the tax, and the totals into a new Purchase Invoice, then files the original in a shared drive. ERPNext core gives you the destination DocTypes and a clean posting workflow, but nothing in the box reads an inbound document — there is no OCR, no email-to-invoice ingestion, and no AI that maps unstructured text to Purchase Invoice Item rows. As volume grows this manual lane becomes the bottleneck: slow month-end closes, transposition errors, missed early-payment discounts, and no audit trail linking the posted record back to the source file.
Custom Frappe app with its own module, DocTypes, and `hooks.py` — installed on your v15/v16 bench, not a fragile bundle of site customizations
AI/OCR extraction pipeline for supplier invoices, receipts, and purchase orders across PDF and image (scan/photo) inputs
`Document Extraction Job` staging DocType with attached source `File`, per-field confidence scores, and a status workflow (Queued, Extracted, Needs Review, Posted, Failed)
Email-inbox ingestion via ERPNext `Email Account` incoming rules plus a `scheduler_events` job that pulls attachments and creates jobs automatically
Drag-and-drop upload screen (client script) for ad-hoc documents that bypass the mailbox
Line-item table extraction into structured child rows — description, quantity, rate, UOM, and per-line tax
ECOSIRE builds a dedicated Frappe app that closes that gap end to end. We ship a proper custom app (its own module, DocTypes, and hooks.py) rather than a pile of loose customizations. Inbound documents arrive two ways: a monitored email inbox (via ERPNext Email Account incoming rules and a scheduler job that pulls attachments) and a drag-and-drop upload screen backed by a File-attached staging DocType we call Document Extraction Job. Each job runs the PDF or image through an AI/OCR pipeline — a configurable extraction provider plus a normalization layer — and the parsed result is written to structured child-table fields: header data (supplier, invoice number, dates, currency, totals) and a line-item table with description, quantity, rate, and tax. A confidence score is stored per field so low-confidence extractions route to human review instead of posting silently.
Technically the automation lives where Frappe expects it. A before_insert/on_update server-side flow (registered through doc_events in hooks.py) validates the extracted payload, runs supplier auto-matching against the Supplier master and item auto-matching against Item (fuzzy match on name, supplier part number, or a learned alias table), applies your tax templates, and creates a draft Purchase Invoice or Expense Claim linked back to the source File. Whitelisted methods expose the pipeline to the REST API so an external mail gateway or RPA bot can post documents in, and client scripts add a review-and-approve UI on the job form. Scheduler events (scheduler_events in hooks.py) poll the inbox and retry failed jobs. Access is controlled with a dedicated Role Profile and DocType permissions so AP clerks can review while only approvers can submit the resulting invoice. It targets Frappe/ERPNext v15 and v16.
Because this is build-to-order, nothing is a generic download. We start with a short scoping call, confirm your document types, tax rules, matching logic, and target DocTypes in writing, then build against that scope — typical delivery is 2 to 4 weeks from confirmed scope depending on the number of document layouts and integrations. You get the installable source, a UAT pass on a staging bench with a rollback plan, documentation, a training session, and a post-go-live support window. ECOSIRE installs it on your bench (self-hosted or Frappe Cloud private bench) and hands over the git repository so the app is yours to run and extend.
Owns the invoice-to-pay lane and wants supplier invoices to arrive as reviewable draft Purchase Invoices instead of a stack of PDFs to retype. Needs confidence scoring and a review queue so clerks approve rather than key data.
Answerable for close speed and accuracy. Wants extracted tax reconciled against tax templates, a clean audit trail from posted invoice back to the source file, and fewer transposition errors slowing the close.
Runs the bench and cares about how the automation is built. Wants a proper Frappe app with clean DocTypes, `hooks.py` doc events, scheduler jobs, and role-scoped permissions — plus the git repo so it can be maintained in-house.
Does the day-to-day capture today. Needs a fast review-and-correct UI, item and supplier auto-matching that learns their common suppliers, and a way to fix low-confidence fields before anything posts.
ecosire.com でライセンスを購入し、アカウント ダッシュボードから AI Document & Invoice Extraction アプリの ZIP をダウンロードします。
ZIP をベンチのアプリ フォルダーに抽出するか、抽出されたアプリへのパスを指定して「bench get-app」を実行します。
`bench --site SITE_NAME install-app APP_NAME` を実行し、続いて `bench maigrate` を実行して、AI Document & Invoice Extraction をインストールし、そのスキーマを適用します。
サイトの ECOSIRE ライセンス設定を開き、ライセンス キーをアクティブ化します。無料の ecosire_connect アプリと ecosire_license_client アプリが必要です。
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Delivery model | Built to your confirmed scope, installed on your bench | You spec and build it in-house | Generic download, one-size-fits-all | |
| Invoice/receipt OCR | AI/OCR tuned to your document layouts | Whatever you have time to build | Fixed templates, limited layout coverage | |
| Auto-create Purchase Invoice | Draft PI/Expense Claim via `doc_events`, linked to source | Depends on your engineering | Often stops at extracted data, no posting | |
| Supplier & item matching | Fuzzy match + learnable alias tables | Build and maintain yourself | Basic name match, little learning | |
| Review & confidence routing | Per-field scores route low-confidence to Needs Review | Extra work to design | Limited or all-or-nothing | |
| Frappe architecture fit | Proper app: DocTypes, hooks, scheduler, Role Profile | Only as clean as your team keeps it | Varies; may bolt on site customizations | |
| Ownership & extensibility | Full git repo handover — yours to extend | You own it but built it yourself | Vendor-controlled, closed roadmap | |
| Support & v15/v16 upgrades | Post-go-live window + optional retainer | Self-supported | Shared support queue |
No. This is a build-to-order engagement, not a Frappe Marketplace download. ECOSIRE scopes, builds, installs, and supports the app for your specific document types, suppliers, and tax rules. You receive installable source and the git repo at handover — but it is built to your confirmed scope first.
Typical delivery is 2 to 4 weeks from confirmed scope. It starts with a short scoping call to lock document types, matching logic, tax handling, and target DocTypes in writing. The exact timeline depends on how many document layouts and external integrations (mail gateways, scanners) are in scope; we confirm dates once scope is agreed.
We build for Frappe/ERPNext v15 and v16. The app is a standard Frappe app installed on your bench and works on both self-hosted deployments and Frappe Cloud private benches. Tell us your current version and channel during scoping and we pin the build to it.
Every engagement includes a post-go-live support window for bug fixes and rule adjustments (extraction and matching tuning). Because you receive the full git repository, your team can maintain and extend the app in-house. We also offer ongoing support and version-upgrade retainers separately if you'd prefer ECOSIRE keep maintaining it.
Every extracted field carries a confidence score. Fields below your configured threshold route the `Document Extraction Job` to a Needs Review status so an AP clerk corrects it before anything posts — nothing is submitted silently. Corrections feed the supplier and item alias tables, so matching accuracy improves for recurring suppliers over time.
The extraction provider and normalization layer are configurable. Depending on your data-residency requirements we can use a hosted extraction API or a self-hosted OCR backend on your own infrastructure. Access to the extraction jobs and resulting invoices is controlled through a dedicated Role Profile and DocType-level permissions in ERPNext.
Yes. Beyond the monitored email inbox and the upload screen, the pipeline exposes whitelisted methods over the Frappe REST API. An external mail gateway, RPA bot, or scanning appliance can submit documents programmatically and they flow through the same extraction, matching, and review workflow.
A build-to-order Frappe app that captures supplier invoices, receipts, and POs via AI/OCR and turns them into draft ERPNext Purchase Invoices and Expense Claims — with line-item, tax, supplier, and item auto-matching. ECOSIRE scopes, builds, installs, and supports it for you.