4 min read

Illustrative image. Photo: Vitaly Gariev / Unsplash.
Executive Perspective
By Avril Howes, VP | Innovation & Business Applications ISV
A change to a vendor’s banking details, a customer’s credit terms or a price list deserves a clear answer: who has to approve it? Business Central supports approval workflows for sensitive record changes. The question is whether the right controls have been configured, enabled and tested in your environment.
Executive overview
- Coverage gap: confirm which master records and document types currently have no approval workflow configured, and whether that is intentional.
- Change exposure: identify who can alter sensitive details today without a second sign-off.
- Ownership: establish who is accountable for reviewing workflow coverage as new entities, fields or risks emerge.
- Cost of closing it: assess existing configuration and extension options before assuming every gap requires custom development.
The workflow you don’t have is still a decision
Business Central includes workflows for common documents and master-data changes. Microsoft’s documentation explicitly describes approvals for new customers, vendors and items, and for changes to sensitive fields such as vendor bank account numbers, customer credit limits and item sales prices.
That capability does not establish which approvals are active in a particular organisation. A process can still have a gap because a workflow was never enabled, its conditions no longer match the business, or a new record type or extension has been added. The first step is to inspect the controls that actually run.
Not configuring a control is still a control decision. It should be deliberate, owned and periodically reviewed, rather than left as an assumption from implementation.
Where that gap gets exploited
The ACFE’s Occupational Fraud 2026: A Report to the Nations analysed 2,402 investigated cases worldwide and reported a median loss of US$104,000 per case. More than half of the cases involved either a lack of internal controls or an override of existing controls.
For a finance team, the practical question is what happens when sensitive supplier or payment information changes. Is another person required to review it? What evidence remains of the request, decision and resulting change? A configured approval is one part of that control process; it does not replace appropriate permissions, segregation of duties or follow-up.
What King V asks of the people who could close it
The Institute of Directors in South Africa’s King V background paper retains risk governance as a cornerstone of organisational resilience and identifies substantial changes in its treatment of data, information and technology governance. That provides a useful governance context for reviewing how operational systems support the organisation’s controls.
A workflow gap is a practical example of a decision that can sit below the level a governing body sees directly. Who owns the approval process? Who checks whether the system still implements it? Who decides how to address a new gap?
Operational responsibility remains with the people who define, configure and review the controls.
What to check now
Start with three records already in the system: a vendor master record, a price list, and a document type important to your business. For each, check whether the relevant change requires a second approver. If it does not, establish whether that was a deliberate decision, a configuration gap or a requirement the current workflow does not cover.
Review the available Business Central configuration first. Where you need additional coverage, Braintree’s PowerFlow extension provides a configuration-led approach using Business Central and Power Automate. Supported master-record approval and change workflows can be configured without writing code, including record-change monitoring for supported non-system tables and fields from standard Business Central, ISV extensions and customisations.
Two generic Power Automate flows support record changes and document approvals, with email notifications and user responses handled through Power Automate. Document coverage remains specific: additional or unsupported document workflows may require development. Confirm the records, conditions, permissions and licensing needed for your environment before committing to the approach.
The useful outcome is a control you can demonstrate: a change requested, the right person asked to approve it, and a result that can be reviewed. For supported cases, configuration can make that work easier to maintain as the business changes.
Read the PowerFlow documentation or talk to Braintree about the approval processes you need to review.
Sources
CONNECTED EXPERTISE

