Employee Self-Service Mobile App

The problem

Most of your workforce will never open a Dynamics 365 Finance & Operations workspace. Warehouse operators, field engineers, drivers, retail staff and shift workers do not sit at a desk, do not have an F&O licence sized for occasional use, and will not navigate a browser-based ERP on a phone. So the self-service work that F&O is perfectly capable of holding — a leave request, a timesheet line, a payslip lookup, an approval — leaks back out into paper forms, WhatsApp messages to a supervisor, and an HR inbox that becomes the system of record by default.

The result is predictable. Leave balances in F&O drift from what people actually took. Timesheets arrive late, so project cost and payroll both wait. Approvals sit with a manager who only sees them when they next open a laptop, which on a Friday afternoon means Monday. And every payslip request becomes a manual task for someone in HR who has to find, export and email a document that already exists in the system.

What ECOSIRE builds

ECOSIRE builds a mobile self-service application that talks to your Dynamics 365 Finance & Operations environment through secured, purpose-built data entities. There is no shadow database and no nightly copy of HR data sitting somewhere else — the app reads and writes F&O, and F&O remains the single system of record.

The F&O side

On the F&O side we build an X++ extension model, with no overlayering, that exposes exactly the surface the app needs and nothing more: data entities for leave types and balances, leave requests, timesheet lines, payslip metadata, worker profile fields and pending approval work items. Each entity is bound to dedicated security roles, duties and privileges, so a self-service identity can read its own leave balance and cannot read anyone else's compensation. Row-level filtering is applied against the Worker record resolved from the signed-in identity, so the entity itself enforces the boundary rather than trusting the client.

Requests submitted from the phone enter the standard F&O workflow framework. A leave request created on a phone is the same work item, on the same approval hierarchy, with the same audit trail as one raised in the browser — approvers can act in either place, and the decision history is identical. Timesheet lines post against the same Projects setup, project categories and activities you already use, so hours flow into project cost and invoicing without a bridge.

The mobile side

The app is delivered for iOS and Android and is built to work on the network your people actually have. Leave balances, submitted requests, recent payslips and pending approvals are cached locally, so a warehouse basement or a site with no signal still shows current data and queues new submissions. When connectivity returns, queued items sync and any conflict — a leave request approved elsewhere in the meantime, a timesheet period locked — surfaces to the user rather than being silently discarded.

We implement authentication against your Microsoft Entra ID tenant with the same conditional access policies you apply elsewhere, so there is no separate password to manage or revoke. Push notifications alert approvers to new work items and inform requesters when a decision is made. Payslips are retrieved as documents from F&O and displayed in-app; they are not re-rendered or recalculated by the mobile client.

Approvals and beyond leave

Because the app reads pending work items from the workflow framework, the approval inbox is not restricted to leave. Purchase requisitions, expense reports, timesheets and any other workflow-enabled document you choose to include can be approved from the phone, with the document detail rendered for review. Which document types appear is a scoping decision, not a hard limit.

Where it makes sense for your estate, we can integrate with Power Platform — for example surfacing an approval in Power Automate alongside the app, or reusing Dataverse-side identity — but the core app does not require it. Dual-write is used only if you already run it and want the app to read customer-engagement data alongside F&O.

Who it is for

Organisations on Dynamics 365 Finance & Operations with a large deskless or shift-based workforce; businesses where timesheet capture delays project cost and payroll; and companies where approval latency, not approval policy, is the actual bottleneck. It suits environments where issuing full ERP access to every employee is neither licensable nor practical.

How delivery works

This app is built to order for your environment. It is not a published store app you install today.

1. Scoping call. We agree the exact feature set — which leave types, which timesheet structure, which payslip source, which approval document types — plus your branding, languages, device estate, and whether offline capture is required. 2. Fixed quote. You receive a written scope covering the F&O extension, the mobile application, the security model, the store or enterprise distribution route, and a fixed price and timeline. Typical build time is two to four weeks. 3. Build. We develop the F&O extension model and the mobile client together, testing against a sandbox seeded with representative worker, leave and project data. 4. Install in test. The deployable package goes to your sandbox via LCS; the app is distributed to a pilot group through your mobile device management or a test track. The pilot runs a full cycle — request, approve, timesheet, payslip — before anyone signs off. 5. Production. The package is promoted through your LCS pipeline to production and the app is released to your workforce through your chosen distribution channel. We support the first weeks of live use. 6. Support. A defined support window follows go-live, covering defects, configuration changes and assistance with store or MDM distribution.

You own the F&O extension source. Distribution under your own developer account keeps the app in your name and under your control.