A per-tenant Business Central AL extension for employee expense claims — receipt capture with OCR, per-policy spend limits, multi-level approval routing, mileage and per-diem rules, posting reimbursements straight to AP or payroll. Built, installed and supported by ECOSIRE on your environment. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $249.00 USD; request a quote for a scoped proposal.
Manifiesto de la app
Diseñado en torno a tu flujo de trabajo
A per-tenant Business Central AL extension for employee expense claims — receipt capture with OCR, per-policy spend limits, multi-level approval routing, mileage and per-diem rules, posting reimbursements straight to AP or payroll. Built, installed and supported by ECOSIRE on your environment.
Sin configuración por tu cuenta: una app funcional creada, instalada y con soporte de ECOSIRE.
Empieza con un precio único de desarrollo. Definimos el alcance contigo en el arranque.
ECOSIRE la crea, la configura y la instala en tu Dynamics 365 Business Central.
Sales en vivo en unas 2–4 semanas, con un periodo de soporte posterior al lanzamiento.
Employees still emailing receipt photos and finance still rekeying them into Business Central is where leakage, late reimbursements and policy breaches live. Expense & Reimbursement Claims for Business Central is a per-tenant AL extension that ECOSIRE builds, installs and supports directly on your Business Central environment (cloud SaaS or on-prem), so claims flow from the employee's phone through approval and into your ledgers without a spreadsheet in sight.
The extension is real AL: table and page extensions add an Expense Claim document and lines, with a Role Center, list and card pages that feel native to Business Central. Receipts are captured against Incoming Documents and run through OCR; line amounts, dates and vendor data are extracted for the claimant to confirm. Each line is validated against policy — spend limits by expense category, currency, employee group and date — using event subscribers on document release so out-of-policy claims are blocked or flagged before they reach an approver.
Approval uses Business Central's native Approval Workflow engine extended with multi-level routing (manager → department → finance), delegation and the Notification system, so nothing depends on a third-party portal. On final approval, the claim posts: either as a Purchase Invoice / journal to AP for direct reimbursement, or exported to your payroll run. Mileage and per-diem rules compute amounts from configurable rates.
Everything respects your permission sets, dimensions and number series. Heavy work (OCR, posting batches) runs on the Job Queue. Because it is built to order, the data model, approval tiers and posting behaviour are shaped to your policy — not a generic AppSource template you then fight to configure. ECOSIRE owns the AL source, the AppSource-style deployment as a per-tenant extension, and ongoing support.
Wants employees to submit expense and mileage claims from their phone with receipts attached, and to enforce the travel and spend policy automatically instead of chasing paper and email threads.
Needs approved claims to post cleanly to the correct G/L accounts, dimensions and vendors — or flow into payroll — with a full audit trail and no manual rekeying into Business Central.
Responsible for the tenant and wants a clean per-tenant extension that respects permission sets, the Job Queue and number series, and survives Microsoft's monthly platform updates without breaking.
| Criterio | ECOSIRE | Construcción personalizada | Competidor | Odoo Nativo |
|---|---|---|---|---|
| Tailored to your exact expense policy, categories and approval tiers | Incluido | Incluido | Apoyo parcial | |
| Receipt capture with OCR extraction | Incluido | Apoyo parcial | Incluido | |
| Multi-level approval routing (manager → department → finance) | Incluido | Incluido | Incluido | |
| Mileage and per-diem rule engine | Incluido | Apoyo parcial | Apoyo parcial | |
| Reimbursement via AP posting or payroll export | Incluido | Incluido | Apoyo parcial | |
| Installed and supported on your tenant by the vendor (no DIY) | Incluido | No incluido | Apoyo parcial | |
| Upgrade-safe AL extension surviving BC monthly updates | Incluido | Apoyo parcial | Incluido | |
| One-time price with no per-user monthly SaaS subscription | Incluido | Apoyo parcial | No incluido |
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 2–4 weeks: 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.
A build-to-order Odoo localization that loads Algeria's full wilaya and commune hierarchy with bilingual French and Arabic names, wired into partner addresses and reporting. ECOSIRE builds, installs, and supports it after your quotation.
A per-tenant Business Central AL extension for employee expense claims — receipt capture with OCR, per-policy spend limits, multi-level approval routing, mileage and per-diem rules, posting reimbursements straight to AP or payroll. Built, installed and supported by ECOSIRE on your environment.