Services › Business analysis › Finance ERP / D365 BSA
Business analysis engagement typeFinance ERP / D365 BSA
Business systems analysis on Microsoft Dynamics 365 Finance & Operations: procure-to-pay, vendors, AP, travel & expense and approval workflows, through UAT and cutover.
You are the CEO of your world; this engagement type tells EliosTech where you want us. Vice-president–level ownership takes vice-president–level money, while a narrow individual or external-consultant focus can carry significant discounts. Contracts set the boundaries, EliosTech work is proprietary, and service continues while paid. How it works →
What this work is
An ERP project succeeds when finance, IT and the implementation partner agree on what "done" looks like. EliosTech, Inc. sits in the middle as the business systems analyst: we translate how your finance team actually works into configuration, workflow and integration requirements, and we stay through testing and cutover.
What EliosTech does in this engagement type
- Fit-gap analysis for procure-to-pay, vendor onboarding, AP, T&E and approvals.
- Workflow and Power Automate requirements, with clear approval rules and limits.
- Integration requirements for banks, payment platforms and the systems around D365.
- Data migration mapping: vendors, open items, chart of accounts and history.
- UAT scripts written with finance users, plus defect triage through sign-off.
- Cutover checklist, hypercare and the hand-off to the support team.
What you get
- Fit-gap and decision log
- Workflow and approval matrix
- Integration and data migration maps
- UAT scripts and sign-off log
- Cutover runbook
- Written estimate and budget tracker
Good fit when…
- A D365 F&O rollout or phase 2 is underway
- Approvals and vendor onboarding live in email
- The implementation partner needs a client-side analyst
- UAT keeps slipping because nobody owns the scripts
Tools we bring to your development team
Over many engagements, EliosTech, Inc. has worked side by side with development teams on the tools they already run. We work inside your licenses, repositories and boards; we do not resell software or lock you into ours. The point is simple: a business analyst who speaks the team's tools turns requirements into working, tested software faster, with fewer surprises at demo time.
Microsoft .NET teams
We have spent years helping teams that build on Microsoft .NET: Web APIs, background services, integrations and the configuration around them. We read a solution well enough to know where a change lands (controller, service, data layer, config), write stories that match how the code is organized, and check each pull-request demo against its acceptance criteria. Your developers write the production code; we keep the requirements and the code honest to each other.
In this engagement type: integration services around D365 are often built in .NET and Azure; we write the stories and check the demos.
Postman
Shared Postman collections and environments for every endpoint in scope, so analysts, developers, testers and partners call the same requests with the same examples. Collections double as living documentation and can run in the team's pipeline (for example with Newman) as a quick API smoke test.
In this engagement type: we exercise the D365 and integration endpoints so data mapping matches what really moves.
Jira, Confluence & Azure DevOps
The board is where the plan lives. We set it up to match the Epic kickoff (epics, features, stories, tasks), write acceptance criteria, refine and size the backlog, link stories to tests and defects, and keep the dashboards that show progress and budget every sprint. Same discipline in Azure DevOps Boards or similar tools.
In this engagement type: or Azure DevOps Boards, which many D365 teams use: fit-gaps, configuration and UAT on one board.
SmartBear / ReadyAPI
Functional and data-driven API tests in ReadyAPI (the SmartBear suite that grew out of SoapUI): REST and SOAP, assertions tied to acceptance criteria, test data sets for the edge cases business users care about, and suites the team can rerun every sprint instead of re-testing by hand.
In this engagement type: regression tests on integration points before each release window.
What our BAs do in Jira (and similar)
- Structure the board to match the Epic kickoff: epics → features → stories → tasks, so what you approved is exactly what the team works.
- Write stories developers can build and testers can prove: clear user stories with Given / When / Then acceptance criteria, data rules and examples.
- Refine and size the backlog with the team before each sprint, with agreed definitions of ready and done.
- Trace everything: link stories to API contracts, test cases, defects and the Confluence (or wiki) pages that explain the decisions.
- Report in the open: sprint dashboards, burn-down and a budget view, plus the written progress and change report you get with every demo.
- Triage and route defects so the right person fixes the right thing, and nothing new enters a running sprint without your written approval.
- Keep a fit-gap and decision log linked to the stories, so configuration choices are never re-argued.
Jira and Confluence, Azure DevOps Boards or the tracker you already use. We work in your instance and your workflow.
How it runs: Epic kickoff → Sprint 0 → Sprint 1
- 20-minute intro call → Epic kickoff: we walk the whole project (features, stories, tasks) and you decide whether the work and price are right for you.
- Sprint 0 needs the down payment first. About 2 weeks and up to about 30 days of investigation. It produces your Sprint 1 plan.
- You may decline Sprint 1. If you accept it, that scope is honored and demoed as completion. Then the next payment is due.
- After that, two-week sprints: steady two-week payments, a demo every sprint and a written progress and change report.
Rates and how this engagement type starts
| Engagement shape | Typical rate |
|---|---|
| Long-term remote engagement (roughly 1–2 years) | from ~$80/hr (typically $80–$140) |
| Onsite or heavier hybrid, Cook / Lake counties | ~$130/hr |
| Operating domain + crew (EliosTech runs analysts, developers, testers) | $140–$200/hr or an annual program |
| Short C2C surge, rescue or go-live push | ~$200/hr |
| Discovery = Sprint 0 (default start) | $8,000 down payment before Sprint 0 starts, confirmed in written terms |
| Sprint 1 and later sprints | Billed per two-week sprint from your accepted Sprint plan |
Senior bands, stated up front: domain ownership, not commodity staff augmentation. C2C through EliosTech, Inc. preferred. Longer terms and prepaid work move the rate down; short notice and onsite days move it up.
Configure this engagement type
- Configure the job below
- Estimate — a rough range, instantly
- Terms — read and accept
- Down payment — we invoice; kickoff goes on the calendar
Other business analysis engagement types
Domain Build / Senior Technical BA
One accountable lead who maps the domain, opens the boards, writes specs and acceptance criteria, and runs estimates through delivery.
Read about this work →Business AnalysisPayments modernization BA
Lockbox, cash application, payment APIs, processor onboarding and data maps, done terms-first with written estimates.
Read about this work →Business AnalysisDiscovery / Sprint 0 leadership
Open the accounts, find the subject-matter experts, size what effort really remains, and leave you with a Sprint 1 plan and a budget tracker.
Read about this work →Business AnalysisQA, UAT, test plans & automation
Test plans, QA, UAT and automated API and regression testing. Hire EliosTech to take over the testing job as scoped sprint stories.
Read about this work →Rather talk it through?
A 20-minute scope call is free and tells you whether we are the right fit. Discovery (Sprint 0) is paid work that ends in a Sprint 1 plan you may accept or decline.