When Business Central Holds the Right Data but Work Still Happens Elsewhere
A warehouse picker finds fewer items in a bin than the order requires. Business Central holds the inventory records, but resolving the discrepancy means updating a spreadsheet, messaging a supervisor and checking whether someone has corrected the stock.
The ERP may be working exactly as designed. The problem is everything happening around it.
For businesses running Microsoft Dynamics 365 Business Central, this creates a difficult investment decision: improve the existing system, change the process or introduce another application?
When should you extend Business Central with Power Apps?
Start by checking whether existing Business Central functionality or better procedures can resolve the problem. Microsoft 365 connections may remove unnecessary steps without custom development. A tailored Power App becomes worth considering when a task genuinely needs a different interface or workflow, provided ERP controls remain intact and the operational benefits justify the additional cost.
Better access to ERP information can remove unnecessary work
Business Central already works with familiar Microsoft 365 applications. Used appropriately, these connections can make information easier to access without creating another system to maintain.
For example:
- Outlook can bring relevant customer information and sales documents into everyday email interactions, reducing the need to repeatedly search ERP records.
- Microsoft Teams allows colleagues to share Business Central records and discuss operational issues with the relevant information in view, subject to access permissions.
- Excel supports analysis and, for supported Business Central data, controlled editing. It need not become a separate source of operational records.
Power Platform extends these possibilities. Power Automate can coordinate notifications and approvals, while Power Apps can provide task-specific interfaces for employees who need simpler ways to work with business information.
The distinction matters: giving someone easier access to information does not automatically justify moving transaction processing outside the ERP.
The hidden cost is often between systems, not inside them
The 2024 Intuit QuickBooks Business Solutions Survey found that respondents reported spending an average of 25 hours per week on manual data entry or reconciliation across applications.
The survey covered 630 US business owners and executives from organisations employing 10–99 people. It is not a Business Central benchmark, but it illustrates the wider commercial burden of disconnected workflows.
Repeated entry consumes time. Inconsistent records generate corrections. Unclear responsibilities create delays that managers must resolve.
Adding another application without addressing those underlying problems can increase software expenditure and maintenance obligations rather than remove the original inefficiency.
This is why GO ERP approaches connected business applications as an operational design decision, not simply a development opportunity.
The objective is to make work easier while preserving reliable ERP records and keeping ongoing costs under control.
Before choosing the technology, the business needs to understand precisely where the workflow breaks down.
Before Building Another App, Find Out Where the Process Breaks
A request for a new application often starts with a reasonable complaint: “Business Central makes this task harder than it should be.”
Yet an awkward screen, a poorly designed procedure and a genuine functionality gap are three different problems. Each demands a different response.
Before commissioning development, trace the troublesome workflow from the first action to the final confirmed transaction.
Follow the work, not just the software
Consider a warehouse discrepancy that requires supervisor approval.
The picker records the problem, sends a message and continues working. The supervisor investigates later, while someone else updates Business Central.
Where does the delay occur? Is the missing functionality preventing the picker from recording the discrepancy? Does the supervisor lack the information needed to act? Or is nobody clearly responsible for completing the correction?
These questions uncover something a software requirements list frequently misses: the gap between recording work and completing it.
A useful process review should identify who performs each step, where information is stored, which action changes the authoritative record and how exceptions are resolved.
The WORK-FIT test: seven questions before approving development
GO ERP’s proposed WORK-FIT diagnostic provides a practical way to examine one operational workflow before choosing a solution.
- W — Workflow friction: Which specific actions create delays, unnecessary clicks or repeated entry?
- O — Ownership: Who initiates, approves and completes the transaction?
- R — Record authority: Which system holds the definitive inventory or transaction information?
- K — Keeping ERP controls intact: Which validations, permissions and posting rules must remain within Business Central?
- F — Frontline usability: Can employees complete the task effectively using existing interfaces and devices?
- I — Integration requirements: What information must move between systems, and what happens when a transfer fails?
- T — Total lifecycle cost: What will development, licensing, training, monitoring and ongoing support cost?
The test distinguishes a genuine need for tailored functionality from problems better resolved through configuration, clearer procedures or existing Microsoft tools.
Weak process inputs create expensive downstream consequences
| What the review finds | Business risk | What must change |
| Two applications maintain the same inventory information | Conflicting stock records and reconciliation work | Define one authoritative record and controlled updates |
| Nobody owns unresolved discrepancies | Delayed corrections and unclear accountability | Assign an exception owner and escalation route |
| Staff bypass required transaction checks | Inaccurate records and weak auditability | Preserve validations and authorised posting procedures |
These findings should become measurable requirements, not merely observations.
Record the number of exceptions, time spent resolving each one, frequency of corrections and manual steps involved. This establishes a baseline against which any proposed change can be assessed.
A well-designed Power App can make a difficult task easier. It cannot compensate for undefined responsibilities or unreliable transaction rules.
Once the real cause is clear, the business can compare its options without treating custom development as the inevitable answer.
When Is Standard Business Central Enough, and When Does Power Apps Make Sense?
Once the operational requirement is clear, the question becomes which solution delivers the necessary functionality with the least avoidable cost and complexity.
Custom development may offer a better user experience, but it also introduces responsibilities that extend well beyond the initial build.
Three options, one business requirement
The right decision depends on functional fit, how employees perform the task and which approach can be maintained reliably.
| Option | When it makes sense | Main consideration |
| Business Central configuration | Existing ERP functionality can meet the requirement through configuration, permissions or supported features. | Preserves established transaction controls, with potentially lower additional support costs. |
| Process redesign | The system works, but unnecessary steps, unclear procedures or approvals delay completion. | Requires operational ownership and training, often without new application development. |
| Connected Power App | Employees need a tailored mobile interface, guided data capture or a workflow spanning multiple systems. | Introduces licensing, integration, security, testing and ongoing maintenance responsibilities. |
These options are not mutually exclusive. A revised process may need a small Business Central configuration change, while a Power App may still depend on existing ERP functionality.
Keep critical ERP logic where it belongs
Business Central should remain responsible for authoritative inventory transactions, financial postings and the controls governing them.
Where standard functionality falls short, an AL extension within Business Central may be more appropriate than recreating transaction logic in Power Apps.
A connected Power App serves a different purpose.
For example, warehouse employees might use a simplified mobile screen to capture information and submit it through an approved Business Central API. Power Automate could then notify a supervisor through Teams.
The app improves access to the workflow without becoming a separate inventory system.
Architecture matters here. The Business Central connector and Dataverse virtual tables offer different integration patterns, with capabilities dependent on the available APIs and solution design. Neither removes the need to validate permissions, transaction handling and failure recovery.
Compare total ownership costs, not just development estimates
A working prototype is not evidence of an affordable production solution.
Before approving investment, compare the options over a defined period, such as three years. Include application and connector licensing, development, testing, deployment, employee training, maintenance, upgrade testing and support ownership.
Licensing deserves particular attention. Business Central subscriptions do not automatically grant unrestricted Power Apps usage; entitlements depend on the users, connectors and application scenario.
Set these costs against a measurable benefit.
For example, calculate annual labour capacity released using:
Monthly exceptions × minutes saved per exception × 12 ÷ 60
Then assess the financial value alongside reduced correction rates, faster fulfilment and stronger transaction control.
GO ERP’s approach is to design tailored applications around justified operational needs, supported by appropriate ERP architecture and long-term ownership.
The preferred solution is the one that improves daily work without creating a disproportionate maintenance burden.
A realistic warehouse scenario provides the final test of whether that investment stands up in practice.
Put the Decision to Work: A Warehouse Picking Discrepancy
Consider a warehouse picker preparing an order for 12 units. Business Central shows sufficient stock in the designated bin, but only 10 units are physically available.
The picker needs to report the discrepancy, obtain a decision and continue working without creating inaccurate inventory records.
Should the business change its procedures, use existing Business Central warehouse functionality or introduce a mobile Power App?
Test the workflow before choosing the technology
Start with what Business Central can already do.
Depending on the warehouse configuration and available functionality, existing processes may support the necessary quantity validation, discrepancy handling and inventory corrections. Better training or a revised escalation procedure could resolve the problem without another application.
A connected Power App becomes more attractive when the main difficulty is how employees capture and communicate information.
A tailored mobile workflow might allow the picker to:
- Scan the item and bin barcode to identify the relevant records.
- Enter the actual quantity and reason for the discrepancy.
- Submit the exception through an approved Business Central interface.
- Trigger a Teams notification for supervisor review.
The supervisor would follow the authorised procedure, with Business Central retaining responsibility for controlled inventory transactions.
The critical distinction is between recording a discrepancy and authorising a stock adjustment. A convenient mobile interface must not bypass the controls protecting inventory accuracy.
A successful demonstration is not a production-ready solution
Before approving a pilot, test what happens when the workflow goes wrong.
What if the barcode identifies the wrong bin? The employee loses connectivity? A submission fails or is repeated? The supervisor lacks permission to authorise the correction?
The solution must handle these situations without creating duplicate transactions or losing the audit trail.
Microsoft sample applications can provide useful prototype references, but production use requires separate validation of integration reliability, security, licensing, deployment controls and support ownership.
A controlled pilot should measure exception-resolution time, record accuracy, adoption and support effort against the original process.
Four questions worth resolving before investment
Can Power Apps replace Business Central?
Power Apps can extend operational workflows, but it should not unnecessarily reproduce Business Central’s core ERP transaction controls.
Does every user need additional licensing?
Not necessarily. Requirements depend on existing entitlements, the application architecture, connectors and user scenario.
Can warehouse apps work without reliable connectivity?
Some Power Apps designs support offline operation, but synchronisation, conflict handling and Business Central transaction validation require careful design and testing.
Who maintains the application after deployment?
Ownership should be agreed before development, including monitoring, security, updates, incident handling and user support.
Make the next investment decision defensible
The strongest Business Central and Power Platform solutions begin with a clearly defined operational requirement, not a preferred application.
GO ERP can help assess one priority workflow through a focused Business Central and Power Apps discovery workshop, examining existing functionality, process weaknesses, integration requirements and commercial viability.
The outcome should be a practical recommendation: improve what already exists, redesign the workflow or proceed with a properly scoped pilot.
The goal is not another application. It is less operational friction, better control and a solution the business can confidently maintain.
