Hire Microsoft Dynamics 365 experts
Hire Microsoft Dynamics ERP consultants
In short
MS Dynamics Guys provides Microsoft Dynamics 365 enterprise resource planning (ERP) consultants for Business Central, Finance and Supply Chain Management. We scope each role by workstream, such as source to pay or inventory to deliver. The role also covers the handoffs between workstreams, such as receipt to invoice. The consultant configures those processes, writes test scripts and checks that postings reconcile with the general ledger. Your project lead directs the work. Your process owners sign off acceptance tests, and your controller signs off reconciliations.
When an ERP consultant from MS Dynamics Guys fits
An ERP consultant is a functional consultant. The consultant owns the setup, the test scripts and the checks for one or more business process workstreams, such as source to pay. The handoffs between those workstreams are part of the role. The work crosses modules, and in a group of companies it can cross Business Central and Finance. Your people keep the decisions. The role fits these team situations:
Team situations that call for an ERP consultant
- A process that no module owns. Your program gives sales, the warehouse and receivables separate owners. Nobody owns the path from sales order to customer payment as a whole, or the handoffs inside it.
- A trial load that does not reconcile. After a trial data load, open payables or inventory value disagree with the general ledger. Each workstream says that the difference belongs to another one.
- Acceptance tests across workstreams. User acceptance testing (UAT) must follow a purchase from order to payment, or a sale from order to cash receipt. Nobody has written scripts that cross the workstream lines.
- A new company that every workstream must set up. You are adding a company in Business Central or a legal entity in Finance. Purchasing, sales, inventory and the ledger each need setup before the first transaction. Nobody owns the order of that setup or the first period-end check at each handoff.
- Process tests before Microsoft updates. Your regression scripts test one module at a time. Before each update to Business Central or Finance and Supply Chain Management, your process owners need scripts that cross modules. Each script should end with the handoff checks.
When a different role, or no hire, fits better
- Most of the backlog is code: extensions in AL, the Business Central programming language, or in X++, the programming language of Finance and Supply Chain Management. That is work for a Business Central developer or a finance and operations developer.
- The open work is environments, integration settings or specifications for developers. That is technical consultant work: compare the consultant roles before you write the brief.
- Nobody has decided which system owns each record, or how apps and integrations connect. That design question belongs to a solution architect.
- The gap is extracting, mapping and loading data. A data migration engineer runs the loads, and an ERP consultant checks that the results reconcile.
- You have not chosen between Business Central and Finance and Supply Chain Management. Make that choice first: compare Business Central with Finance and Supply Chain Management, or let a consulting engagement assess the fit.
- Nobody in your program has the authority to settle which workstream owns a handoff. A consultant can map the options, but only someone on your side can decide.
Which ERP consultant fits your product and workstream?
Start from where the open work sits. An ERP consultant fits when a process crosses modules and its handoffs need one owner. When the work stays inside one product area, a single-product role is a closer match.
| Where the open work sits | Role that fits |
|---|---|
| Setup inside Business Central, such as finance setup, posting groups or inventory costing, with no handoff in doubt | A Business Central consultant, who can cover one or several setup areas |
| The ledger, payables, receivables or the close in Finance | A Finance consultant |
| Procurement, receiving, inventory or warehouse work in Supply Chain Management | A Supply Chain Management consultant |
| A process that crosses modules, such as source to pay, and the handoffs inside it, such as receipt to invoice | An ERP consultant, scoped by workstream as this page describes |
| Business Central in some companies and Finance at head office | An ERP consultant assessed in each product |
Four workstreams in two products: what an ERP consultant owns
We name workstreams after the top-level process scenarios in Microsoft's business process catalog. Each scenario covers two or more business process areas, so one workstream usually spans several departments. The Business Central, Finance and Supply Chain Management consultant pages divide the same work by setup area or module instead. Microsoft describes the scenarios in business terms, not in software terms, so we use the same names in Business Central projects.
For each workstream they own, the consultant keeps six documents up to date in your workspace:
- Scope sheet: the processes owned, the handoffs in and out, and who signs off each one.
- Decisions log: each process rule, the person who decided it and the date.
- Configuration list: each setting, built and tested in a sandbox or test environment, then moved to production through your change process.
- Handoff map: the documents that cross each handoff, and the setup that decides each posting.
- Reconciliation checks: one period-end check per handoff, with its expected result.
- Acceptance test scripts: written with your process owners, and following each process across workstream lines.
| Workstream | Setup in Business Central | Setup in Finance and Supply Chain Management | Handoff to prove | Signed off by |
|---|---|---|---|---|
| Record to report | Chart of accounts, and the posting groups that map customers, vendors and items to general ledger (G/L) accounts | Chart of accounts and main accounts, and the posting setup that links each subledger to its ledger accounts | Each subledger agrees with its ledger accounts at period end | Your controller |
| Source to pay | Purchase orders, purchase invoices, vendor posting groups and vendor payments | Purchase orders, vendor invoices, invoice matching policies and vendor payments | Each vendor invoice agrees with its order and its receipt, or an approver accepts the difference | Your payables lead |
| Order to cash | Sales orders, sales invoices, customer posting groups and customer payments | Sales orders, customer invoices, receivables and customer payments | Each shipment is invoiced once, at the agreed price | Your receivables or credit lead |
| Inventory to deliver | Receipts, shipments, locations, the Inventory Posting Setup and the routine that posts inventory cost to the ledger | Product receipts, packing slips, inventory posting profiles, and the item model group and parameter settings that decide what posts to the ledger | Inventory value agrees with the inventory accounts in the ledger | Your controller, with your warehouse lead |
Two catalog boundaries matter for staffing. In Microsoft's definitions, source to pay does not include the goods receipt, and order to cash does not include order fulfillment. Receiving, shipping and inventory costing belong to inventory to deliver. So two handoffs, receipt to invoice and shipment to invoice, cross a workstream line, and each needs a named owner. Your program can draw the lines elsewhere, but the scope sheet must show where they are.
In Finance and Supply Chain Management, the single-product roles split this work by module. A Supply Chain Management consultant covers purchasing and receiving setup, and a Finance consultant covers payables and invoice matching. Source to pay needs both sides: purchase orders on one side, invoice matching and vendor payments on the other. An ERP consultant who owns source to pay works across that split, and the scope sheet says who owns the receipt-to-invoice check.
Your lead subject matter expert for each workstream sets its process rules. Microsoft's implementation guidance asks each project to define what every workstream delivers and how it interacts with the other workstreams. The scope sheet and the handoff map record that definition for the workstreams this role owns.
Three handoffs, and the check that proves each one
A reconciliation difference can start where one workstream passes a document to another. For each handoff, the consultant maps the setup that posts it and the standard check in your product.
| Handoff | Workstreams it joins | In Business Central | In Finance and Supply Chain Management |
|---|---|---|---|
| Receipt to vendor invoice | Inventory to deliver, then source to pay | Get Receipt Lines puts several posted receipts from one vendor on one purchase invoice. Posting the invoice updates the Quantity Invoiced field on each order. Get Order Lines can instead match an invoice line to order lines, with or without a posted receipt. With Receipt on Invoice turned on, posting the invoice first creates the receipt for the matched quantity. | Posting the product receipt sets the receipt status to Received, and the invoice sets it to Purchased. Under three-way matching, the invoice price is compared with the order and the invoice quantity with the matched product receipts. |
| Shipment to customer invoice | Inventory to deliver, then order to cash | Get Shipment Lines, or the Combine Shipments batch job, puts several posted shipments for one customer on one sales invoice. Posting it updates the Quantity Invoiced field on each order. | Posting the packing slip sets the issue status to Deducted, which is the physical update. Posting the invoice sets it to Sold, the financial update. |
| Inventory value to the ledger | Inventory to deliver, then record to report | Run Adjust Cost - Item Entries. Then run Post Inventory Cost to G/L, unless Automatic Cost Posting is on. The Inventory - G/L Reconciliation page shows the remaining differences. With Show Warning selected, it explains them in warnings. | Inventory posting profiles decide the ledger accounts. The standard Inventory value report can print ledger balances next to inventory value. The Inventory value report storage report has no ledger balances, so compare it with trial balances. Leave out amounts that were not posted to the ledger. |
In Finance and Supply Chain Management, your invoice matching settings decide whether a difference beyond tolerance needs approval before the invoice posts.
The consultant adds checks of their own. For example, at period end every receipt and every shipment is invoiced or has a written reason. The consultant tries the standard pages and reports first. If a check still needs a report that the product lacks, the consultant writes the requirement, and a developer or report author builds it.
Can one MS Dynamics Guys consultant cover finance and supply chain workstreams together?
Sometimes. One person can own record to report and source to pay for a single company with standard processes. Three things decide whether one person is enough:
- Product and handoffs. The person must know the setup on both sides of every handoff in scope, such as receiving and vendor invoicing. In a group that runs Business Central in some companies and Finance in others, that means both products. The candidate takes our exercise in each product that your brief names.
- Volume. Count the companies or legal entities, the processes and the test scripts in each workstream. One workstream across several legal entities can fill a whole role. Two small workstreams in one company may not.
- Parallel work. Workstreams need their consultant at the same moments: test cycles, trial loads and period-end checks. When two workstreams peak in the same weeks, one person becomes the bottleneck.
Inside one Business Central company, the Business Central consultant page explains which setup areas one consultant usually covers.
One owner for two linked workstreams has a real advantage. The handoff between them has a single owner, so neither side assumes that the other one checks it. With two consultants, write the split at each handoff into the scope sheet. Name who owns the receipt, who owns the invoice and who runs the check between them.
Covering both also needs wider access and more review. Receiving goods and paying the vendor are duties that your controls may keep apart. Give the consultant setup rights in both areas, but no rights to post receipts or payments in production. Ask your controller to approve that combination. For Finance, the Finance consultant page covers segregation of duties.
Before anyone is introduced, our scope review tells you in writing whether one consultant, two consultants or a smaller first scope fits your plan.
How MS Dynamics Guys assesses an ERP consultant
Each candidate works in the product that your role brief names: Business Central, or Finance and Supply Chain Management. The setup and the checks differ between the two, so a result in one product says nothing about the other. A reviewer scores each part against written criteria, and you receive a written summary before your interview.
| Skill | Exercise and review | Artifact you receive |
|---|---|---|
| Scoping | Read a short description of an invented program. Mark the processes the role would own, the handoffs to other workstreams and the person who signs off each one. | A scope sheet |
| Handoffs | Follow one receipt from the purchase order to the posted vendor invoice in your product. Mark each point where the work passes to another workstream. Name the setup that each workstream owns on the way, and place the check that proves each handoff. | A handoff map: each step, the workstream that owns it, the setup that controls it and its check |
| Reconciliation | Write the period-end check for each handoff on the scope sheet, with the standard page or report in your product. | A reconciliation checklist with the expected result of each check |
| Acceptance testing | Write one test script that crosses two workstreams and contains a quantity mismatch, such as an invoice for more units than were received. The reviewer acts as the process owner and runs the script without the candidate's help. | A test script that a process owner can run alone |
The exercise uses invented data and no client systems. A role that spans both products means one exercise in each product, and the summary names the product behind each result. How we assess specialists explains the reviewer's part and what no assessment can show.
Example first work package: a source-to-pay acceptance pack
How an ERP consultant can join your program
Choose the model once you know how many workstreams need an owner and whether they share one test and period-end calendar.
| Option | Who plans the work | Who answers for the result | Fits when |
|---|---|---|---|
| One consultant inside your program: staff augmentation | Your project lead, who assigns tasks through your own plan | Your program owns the outcome; the consultant answers for their own setup, scripts and checks | One workstream, or two linked ones, lacks an owner |
The agreement for each engagement sets the weekly hours, notice period, any minimum term, replacement terms and the hours that overlap with your team. Staff augmentation versus project delivery sets the three models side by side.
Do you want one provider to answer for a whole Business Central go-live instead? See Business Central implementation projects.
From role brief to an approved scope sheet
Timing depends on your brief and on how fast decisions are made, so the steps carry no fixed durations. The first thing the consultant delivers is the scope sheet.
Your role brief
Name the product and how you run it, online or on-premises. List the companies or legal entities, the workstreams in scope and the person who signs off each one. Add the hours to cover, the overlap you need and the expected duration.
Scope review
We map your workstreams to the top-level process scenarios in Microsoft's catalog and mark each handoff. Then we tell you in writing whether one consultant, two or a smaller first scope fits, and whether we can staff the role.
Our assessment
Candidates complete the scoping, handoff, reconciliation and test script exercises in your product. You receive a written summary for each candidate who passes.
Your interview
Your workstream leads interview each candidate. Bring one real handoff problem, such as a receipt still not invoiced at period end, and ask how the candidate would trace it. Leave out personal and confidential data. You decide who joins.
Agreement in writing
The agreement names the workstreams and handoffs from the scope review. It also sets hours, overlap, term, notice, replacement, confidentiality and ownership of documents. Nobody gets access before it is signed.
Access limited to the workstream
Your administrator creates a named account with setup permissions for the workstream's areas only, in a sandbox or test environment first. Before any production access, your controller reviews the rights of a role that spans two workstreams.
Scope sheet first
The first deliverable is the scope sheet. Your project lead approves it before any configuration changes.
What you can check: the method and a demonstration scope sheet
No client names, cases or consultant profiles appear on this page.
You can check the method. How we assess specialists explains how the tasks are designed, who reviews them and what an assessment cannot show. Your interview then tests each candidate on one of your own handoffs.
The table below is an original demonstration that MS Dynamics Guys wrote for this page. It shows the first deliverable for an invented distributor, with invented processes and no client data. It is not a client case and not a candidate's answer.
| Process | Setup owner | Hands over to | Check that proves the handoff | Signs off |
|---|---|---|---|---|
| Purchase orders and approvals | Consultant | Receiving | Each receipt line points to an approved order line | Purchasing lead |
| Receiving at the main warehouse | Consultant | Vendor invoicing | At period end, each receipt line is invoiced or has a written reason | Warehouse lead |
| Vendor invoices | Consultant | Payables | Invoice quantity and price agree with the receipt and the order, or an approver accepts the difference | Payables lead |
| Vendor payments | Consultant | Record to report | Open vendor balances equal the payables account in the ledger | Payables lead and controller |
| Inventory value at period end | Inventory to deliver lead, outside this scope | Record to report | Inventory value agrees with the inventory accounts, checked with the standard page or report | Controller |
| Tax codes on purchase invoices | Consultant, from your tax advisor's written decision | Payables | Test invoices carry the tax codes that the advisor approved | Controller |
The consultant owns the setup, the scripts and the checks. The people in the last column decide whether each check passes. Rows outside the consultant's scope stay on the sheet, so every handoff has a named owner.
Questions about hiring Microsoft Dynamics ERP consultants
Can a Business Central consultant also work in Finance or Supply Chain Management?
Only with proven experience in that product. The accounting ideas carry over, but the setup and the checks do not. Business Central decides postings with posting groups and the Inventory Posting Setup. Finance and Supply Chain Management decide them with inventory posting profiles and item model groups, and check vendor invoices with invoice matching policies. They are separate products, not a larger edition of Business Central. A group that runs Finance at its head office and Business Central in its subsidiaries can need both products in one role. Then ask your interviewers to bring one handoff from each product, because a candidate can be strong in one product and new to the other.
Who signs off reconciliations and acceptance tests when one consultant covers several workstreams?
Your people do, and the scope sheet names the signer of every check and every test script. A script that crosses two workstreams gets a signer from each side. For example, your receiving lead accepts the receipt steps, and your payables lead accepts the invoice steps. Your controller signs every reconciliation where a workstream hands over to the general ledger. If two leads disagree about a handoff, your project lead decides, and the decisions log records the outcome. The consultant prepares the evidence and fixes setup defects, but does not approve their own work.
Can the consultant trace a reconciliation difference after go-live?
Yes. The scope sheet shows where to start, because each check belongs to one handoff. The consultant finds the handoff that the difference crosses and compares the source documents with the setup that posted them. Possible causes include an invoice posted without its receipt, inventory cost not yet posted to the ledger, or setup that changed during a period. The consultant writes down the cause and proposes a fix. Your controller decides on any correcting entry, and the new case joins the period-end checklist.
Our companies close in different time zones. How are the consultant's hours agreed?
In writing, for each engagement. Staggered closes change the work, not only the hours. Each company runs its handoff checks on its own period-end dates, and one person cannot always be online for all of them. In the role brief, list each company or legal entity with its time zone, its period-end dates and its test weeks. The inquiry form also asks for your time zone and working hours. The scope sheet then names who runs each check while the consultant is offline. Before any introduction, we confirm in writing which hours the consultant would cover.
When the consultant rolls off, who owns each handoff check?
A named person on your side, one for every check. Before the last weeks, the consultant updates the handoff map and the reconciliation checklist and gives every open difference an owner. The consultant then walks each workstream lead through their checks on real period-end data. The scope sheet, decisions log, checklists and test scripts stay in your workspace, under the ownership terms of the written agreement.
How is the price set when one consultant covers two workstreams?
On the same basis as for one workstream: the pricing basis is agreed in writing per engagement, and this site publishes no rates. A second workstream adds three kinds of work. It brings its own setup, the handoff checks it shares with the first one, and test scripts that cross both. Our scope review lists that work before you choose one consultant or two. Any support at period end or in test weeks outside the agreed hours is also set in the agreement. Microsoft licenses are a separate purchase and are not part of our price.
Describe the workstreams that need an owner
Tell us your product and how you run it, the companies or legal entities in scope, the workstreams and who signs off each one. Add the hours to cover and for how long. Before any introduction, we reply with a proposed scope and say whether we can staff it. Are all your workstreams in one product? Start from a Business Central program or a Finance and Supply Chain Management program.
Product documentation referenced on this page
- About the business process catalog Microsoft Learn, checked October 4, 2026
- Overview of the business process scenarios Microsoft Learn, checked October 4, 2026
- Introduction to source to pay Microsoft Learn, checked October 4, 2026
- Introduction to order to cash Microsoft Learn, checked October 4, 2026
- Introduction to inventory to deliver Microsoft Learn, checked October 4, 2026
- Organize your Microsoft Dynamics 365 project team Microsoft Learn, checked October 4, 2026
- Posting group setup (Business Central) Microsoft Learn, checked October 4, 2026
- Reconcile inventory costs with the general ledger (Business Central) Microsoft Learn, checked October 4, 2026
- Combine receipts or purchase order lines on a single invoice (Business Central) Microsoft Learn, checked October 4, 2026
- Combine shipments on a single invoice (Business Central) Microsoft Learn, checked October 4, 2026
- Accounts payable invoice matching overview Microsoft Learn, checked October 4, 2026
- Set up accounts payable invoice matching validation Microsoft Learn, checked October 4, 2026
- Inventory posting profiles Microsoft Learn, checked October 4, 2026
- Inventory value reports Microsoft Learn, checked October 4, 2026
- Extensibility home page for finance and operations apps Microsoft Learn, checked October 4, 2026
- Programming in AL Microsoft Learn, checked October 2, 2026
- X++ language reference Microsoft Learn, checked October 4, 2026