This is built to order, so there is no instant download. After a short scoping call we confirm your document types, approval policy and matching rules, then build the AL extension. Typical lead time is roughly one working week depending on how many invoice formats and approval tiers you have. We install it first on your Business Central sandbox as a per-tenant extension, validate against your real vendor documents, then promote it to production with you.

No. It is a per-tenant AL extension that ECOSIRE builds specifically for your tenant and installs for you. That is what lets it match your exact chart of accounts, dimensions, vendor master and approval hierarchy. There is no public AppSource listing and no self-install link — we handle the build, deployment and configuration on your environment.

Every build includes a defined warranty period for defect fixes. Beyond that, an optional support and maintenance plan covers compatibility with Business Central's major and minor updates (the AL object model and APIs do change between releases), enhancement requests and priority response. Because you also receive the AL source, you are never locked to us, but we recommend the plan so the extension stays current through BC upgrades.

The extraction layer is pluggable. We integrate the capture round-trip over the Business Central REST/OData v4 API and connect it to the OCR/AI service you prefer or already license. We confirm the chosen engine during scoping based on your invoice volume, languages and budget, and we handle the mapping of extracted fields to Business Central Purchase Invoice header and lines.

Yes. Three-way matching tolerances (quantity and price), default dimensions, number series, GL coding from posting setup, and approval amount limits with delegation and substitutes are all configured to your policy during the build. Unmatched, duplicate or low-confidence documents are held in an exception queue rather than posted automatically, so a human always confirms before anything hits the ledger.