AP Invoice Capture & OCR Automation

This is a build-to-order engagement, not an instant download. After a short scoping call we typically deliver in around 3–5 weeks depending on your vendor mix and approval complexity. The flow is: scope and field-mapping workshop, build the AL extension, deploy to your Business Central sandbox, validate against a sample of your real invoices, configure approvals and tolerances, then promote to production with you. Exact lead time is confirmed in writing before we start.

It is delivered as a per-tenant extension (a signed .app package), not a public AppSource listing. ECOSIRE installs it directly on your Business Central environment, first in sandbox for validation and then in production, and wires up the dedicated permission sets, job queue entry, and the Power Automate / Dataverse flow for inbox monitoring. You receive the source code and the package, so you own the build.

Every build includes a defined post-launch support window for bug fixes. Business Central ships major waves twice a year; we offer an optional ongoing maintenance plan that keeps the extension compatible across those updates, adjusts to changes in your vendor invoices or approval rules, and applies improvements. You can also maintain it yourself since you hold the source.

Both. The OCR pipeline handles native digital PDFs as well as scanned images and photographed paper invoices. Scanned and lower-quality documents naturally yield lower extraction confidence, which is exactly why low-confidence fields are flagged into an exception queue for a human to confirm before the draft purchase invoice is approved.

Yes. When a captured invoice relates to an open purchase order, the extension auto-matches the extracted lines to the existing PO lines on the Purchase Header / Purchase Line, applying your configured quantity, price, and total tolerance rules. This keeps three-way matching intact. Lines that fall outside tolerance or can't be matched are surfaced for review rather than silently posted.

Access is governed by dedicated Business Central permission sets, so capturing documents is separated from the right to post. Every captured document passes through approval routing before posting, the original PDF/image is stored and linked to the resulting purchase document for audit, and the staging/retry logic runs through Dataverse with a full trail. Nothing posts to your ledger automatically without an approver.