This is a build-to-order extension, not a one-click AppSource install. After a short scoping call to confirm your expense categories, policy limits, approval tiers and reimbursement method (AP or payroll), typical delivery is about one working week: we build the AL extension, deploy it to your sandbox for user-acceptance testing, then install it as a per-tenant extension on your production Business Central environment. The lead time depends on how custom your approval routing and posting rules are; we confirm a firm date in writing before work starts.

ECOSIRE retains the AL source and supports the extension on your environment. The price includes a post-deployment support window covering bug fixes and a compatibility check against Business Central's monthly platform updates, so a Microsoft release won't silently break your expense flow. Beyond that window, ongoing support, new features (extra approval tiers, integrations, report changes) and version upkeep are available on a maintenance agreement or per-change basis.

No. It is installed as a per-tenant extension directly on your Business Central environment, not distributed through the public AppSource marketplace. That is deliberate — it lets us tailor the data model, policy rules and posting behaviour to your organization rather than ship a locked, generic app. You get an extension that behaves like a native AppSource app but is shaped to your policy.

Yes. The extension supports two reimbursement paths and we configure the one you need at build time. Approved claims can post as a Purchase Invoice or general journal to AP for direct vendor/employee payment, or be exported into a payroll run so reimbursements appear on the employee's pay. Both can coexist if different claim types are handled differently.

Yes. It is written in AL using standard, upgrade-safe extension patterns (table/page extensions and event subscribers — no base-app code modification), so it installs on Business Central online (SaaS) and supported on-premises versions. The OCR receipt capture uses Business Central's Incoming Documents OCR; if you run on-prem we confirm the OCR service configuration during scoping.

Receipt capture and claim submission work in the Business Central mobile and web clients out of the box. If you want a lighter front end, we can optionally wire the extension to the Power Platform — a Power App for submission or a Power Automate flow for approvals via Dataverse, and the claim data is also exposed on the Business Central REST/OData API for HR or travel-system integration. That Power Platform layer is scoped as an add-on.