+1 480 485 7373
Microsoft Teams
Automate the rule, keep people on the exceptions
Every business has a handful of steps that follow the same rule each time: a purchase order over a set amount needs a manager, a new vendor needs a second pair of eyes on the bank account, a customer over their credit limit gets held. These are the steps that benefit most, because a machine applies the rule the same way on a busy Friday as on a quiet Tuesday.
The exceptions are different. A disputed invoice, an unusual discount or a supplier in trouble needs someone who knows the context. Good automation routes those to the right person quickly and records what they decided, rather than trying to decide for them.
The tools we use and what each is best at
Business Central workflows
Native approval workflows for purchase and sales documents, general journal batches and changes to customer, vendor and item cards, with approvers and limits held in Business Central.
- ✓Purchase and sales document approvals
- ✓Journal batch approval before posting
- ✓Record change approvals
- ✓Delegation when an approver is away
Power Automate cloud flows
Flows react to events in Business Central or Dataverse and carry out steps in Outlook, Teams, SharePoint and hundreds of other services through connectors.
- ✓Approvals answered from Teams
- ✓Files saved to the right SharePoint folder
- ✓Notifications to customers or vendors
- ✓Hand-offs between Sales and Business Central
Document capture
Vendor invoices arriving by email are read, matched to vendors and purchase orders, and turned into draft documents for a person to check and post.
- ✓E-Documents features in Business Central
- ✓AI Builder invoice processing
- ✓Established capture apps from AppSource
- ✓Mismatch queues for review
Alerts and scheduled jobs
Job queue entries and scheduled flows run checks overnight and tell someone only when there is something to do.
- ✓Overdue receivables digests
- ✓Low stock and late receipts
- ✓Failed integrations
- ✓Expiring contracts and certificates
Flows finance and operations teams ask for most
Tiered purchase approval
Orders route by amount and department, with a stricter path for capital items and one-off vendors.
Vendor bank change control
Any edit to a vendor's bank account blocks payment until a second person confirms it by a separate channel, a simple defense against payment fraud.
Month-end checklist
Close tasks are created, assigned and tracked each period, and the controller sees what is still open without chasing.
Sales order release
Orders from customers on credit hold or with margins below a threshold stop for review before they reach the warehouse.
When we advise against automating
- ✓The process itself is still being argued about. Automating it freezes a disagreement into software.
- ✓It happens a few times a year. A checklist is cheaper and easier to change.
- ✓Nobody will own the flow once it is live, so failures would go unnoticed.
- ✓The data it depends on is unreliable, for example approver lists that are out of date.
- ✓A standard Business Central setting already does the job and just needs switching on.
Our build and handover routine
- 1
Draw the current path
We map who does what today, including the workarounds, and agree which steps become automatic and which stay manual.
- 2
Build under a service account
Flows run under a dedicated account with only the permissions they need, so they do not stop working when an employee leaves.
- 3
Test the unhappy paths
Rejections, timeouts, missing approvers and duplicate triggers are tested on purpose, because those are where live flows break.
- 4
Hand over with a runbook
Your team receives a short document for each flow: what starts it, what it does, where errors appear and who to call.
Questions about approvals and automated flows
Should we use Business Central workflows or Power Automate?
Use Business Central workflows for approvals of documents and records inside the ERP, since the approval status then blocks posting natively. Use Power Automate when the process reaches outside Business Central, such as Teams, email, SharePoint or another application. Many clients combine them, with Business Central holding the approval and Power Automate delivering the request where people will see it.
Can approvers respond from their phone or Teams?
Yes. Business Central approval requests can be answered through Power Automate approvals, which appear in Teams, Outlook and the Power Automate mobile app. The decision flows back into Business Central and the document is released or rejected there.
What happens when a flow fails?
A well-built flow tells someone. We add error handling that sends a clear message to a named owner with the record involved, and we keep run history so the cause can be traced. Silent failures are the main risk with automation, so this part is never skipped.
Does automation weaken our internal controls?
Done properly it strengthens them, because approval rules are applied every time and every decision is logged with a name and time. The risk comes from flows that run with broad admin rights or bypass approvals. We use least-privilege accounts and keep posting and payment steps behind human approval.
Is document capture accurate enough to trust?
For regular suppliers with consistent layouts it is usually good, and it improves as the system learns vendor formats. It still makes mistakes, especially with handwritten or unusual invoices. That is why captured documents land as drafts for a person to check before anything posts.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.