Accounts Payable teams still key bills in by hand. A supplier PDF arrives by email, someone opens it, reads the header for the supplier and invoice number, copies each line, re-enters quantities and rates, works out which tax template applies, and finally creates a Purchase Invoice in ERPNext. Multiply that across hundreds of bills a month and you get slow close cycles, transposition errors, missed early-payment discounts, and duplicate payments that only surface at reconciliation. ERPNext core gives you an excellent Purchase Invoice DocType and the accounting engine behind it, but it has no native OCR or document-understanding layer — the data entry is entirely manual, and the stock Email Inbox and file-attachment features stop at storing the PDF, not reading it.

ECOSIRE builds a proper Frappe application (installed via bench get-app / bench install-app, not a fragile customization) that adds an ingestion and extraction pipeline in front of the standard Purchase Invoice. Bills enter through three doors: direct upload/drag-drop, a monitored mailbox that a scheduler event polls, and the Frappe REST API for programmatic feeds. Each document lands as a new staging DocType (for example AI Bill Capture) with the original file attached, then an OCR + AI extraction step parses the supplier identity, invoice number and date, currency, line items, per-line and document-level taxes, and the grand total. Extracted fields are mapped to real ERPNext masters — Supplier, Item, Purchase Taxes and Charges Template, and the correct expense/GL accounts — with confidence scoring so low-confidence fields are flagged rather than silently trusted.

Technically, the engine runs off hooks.py doc events and scheduler_events so ingestion and extraction happen server-side without blocking the user; long-running OCR calls are pushed to the Frappe background job queue. Supplier auto-match uses tax IDs, email domains and fuzzy name matching against existing Supplier records; item and GL suggestions can be tuned per supplier so recurring bills map consistently. A whitelisted server method (@frappe.whitelist()) exposes the "create draft Purchase Invoice" action, and a client script adds a clean review-and-approve panel to the capture DocType so an AP clerk can correct any field before submission. Duplicate-bill detection runs on a composite of supplier + invoice number + amount + date and warns before you create a second Purchase Invoice for a bill you have already booked. Everything is governed by Frappe permissions and Role Profiles, so an AP clerk can review and draft while only a finance approver can submit.

Because this is build-to-order, there is no instant download — we build it against your actual bill formats, chart of accounts, tax templates and approval rules. Engagement starts with a short scoping call, after which we confirm scope, sample your real supplier documents, and deliver a working app on a staging site for UAT before go-live. Typical delivery is one working week from confirmed scope, and we support Frappe/ERPNext v15 and v16. You receive the full source in a Git repository along with install and configuration docs, so the app is yours to run, extend, or maintain independently.