Study guide
5.1 Native Workflow Templates & Approval Hierarchy
Microsoft Dynamics 365 Business Central Functional Consultant MB-800
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Company Creation & Data Migration
1.1 Creating Companies & Assisted Setup Wizards 1.2 Configuration Packages & RapidStart Worksheets 1.3 Opening Balances & Data Migration Strategies
2 Chapter 2: Security, Profiles & Auditing
2.1 Users, User Setup & Role Center Profiles 2.2 Permission Sets & Security Group Management 2.3 Security Filters, Change Log & Security Auditing
3 Chapter 3: Core System Configuration, Number Series & Copilot
3.1 Company Information, Number Series & Job Queues 3.2 Report Layout Management & Copilot AI Capabilities
4 Chapter 4: Dimensions Architecture & Governance
4.1 Dimension Concepts & Dimension Values 4.2 Global Dimensions vs Shortcut Dimensions 4.3 Default Dimensions, Combinations & Priorities
5 Chapter 5: Workflows & Approvals
5.1 Native Workflow Templates & Approval Hierarchy 5.2 Workflow User Groups & Notification Configuration
6 Chapter 6: Financial Setup, Periods & Currencies
6.1 General Ledger Setup & Accounting Periods 6.2 Payment Terms, Payment Methods & Deferrals 6.3 Multi-Currency Setup & Exchange Rates
7 Chapter 7: Chart of Accounts, Categories & Allocations
7.1 Chart of Accounts Structure & G/L Account Cards 7.2 Account Categories, Subcategories & Financial Reporting 7.3 General Ledger Allocation Accounts & Sharing
8 Chapter 8: Posting Groups & Posting Setup
8.1 Specific Posting Groups: Customer, Vendor, Bank & Inventory 8.2 General Posting Groups & General Posting Setup Matrix 8.3 Inventory Posting Setup & Alternative Posting Groups
9 Chapter 9: General Journals & Recurring Methods
9.1 Bank Account Cards & Posting Setup 9.2 General Journal Templates, Batches & Number Series 9.3 Recurring General Journals & Allocation Methods
10 Chapter 10: Accounts Payable & Accounts Receivable Setup
10.1 Purchases & Payables Setup & Vendor Master 10.2 Sales & Receivables Setup & Customer Master 10.3 Payment Journals, Cash Receipts & Payment Registration Setup
11 Chapter 11: Fixed Assets Setup & Depreciation Books
11.1 Fixed Asset Setup, Classes & Depreciation Books 11.2 Fixed Asset Cards, Main/Component Assets & Depreciation Methods
12 Chapter 12: Inventory Setup, Costing & Locations
12.1 Inventory Setup, Item Types, Categories & Variants 12.2 Costing Methods (FIFO, LIFO, Average, Standard) & Ledger Architecture 12.3 Locations, Transfer Routes & Stockkeeping Units (SKUs)
13 Chapter 13: Logistics Master Data, Pricing & Discounts
13.1 Shipping Agents, Locations & Vendor Lead Times 13.2 Sales Prices, Purchase Prices & Price Lists 13.3 Line Discounts, Invoice Discounts & Thresholds
14 Chapter 14: User Interface, Views, Inspection & Excel
14.1 Personalization, Profile Customization & Designer 14.2 Searching, Advanced Filters, Saved Views & Page Inspection 14.3 Edit in Excel, OneDrive & Data Analysis Mode
15 Chapter 15: Purchase & Sales Order Execution
15.1 Purchase Orders, Receiving, Over-Receipt & Undo 15.2 Purchase Invoicing, Recurring Lines & Blanket Orders 15.3 Sales Quotes, Availability Checks & Order Conversion 15.4 Sales Shipping, Invoicing, Undo & Blanket Orders
16 Chapter 16: Invoices, Credit Memos & Document Corrections
16.1 Direct Invoices, Credit Memos & Document Reopening 16.2 Correct, Cancel & Corrective Credit Memo Procedures 16.3 Combined Shipments/Receipts & Prepayment Workflows
17 Chapter 17: Cash Management, Bank Reconciliation & Ledger Applications
17.1 Processing Payment Journals & Cash Receipt Registrations 17.2 Applying, Unapplying & Reversing Customer/Vendor Entries 17.3 Bank Account Reconciliation & Statement Matching Rules
18 Chapter 18: Operational Adjustments, Inventory & Asset Accounting
18.1 Exchange Rate Adjustments & Dimension Corrections 18.2 Inventory Adjustments, Transfers & Physical Counting 18.3 Fixed Asset Acquisitions, Depreciation Runs & Disposals
5.1 Native Workflow Templates & Approval Hierarchy
Key Takeaways Explain This Topic AI
Business Central workflows operate on a three-part Event-Condition-Response architecture: When Event Occurs (trigger), On Condition (filters and thresholds), and Then Response (subsequent actions).
Pre-configured native workflow templates cover major operational scenarios across purchase documents, sales documents, customer/vendor master data changes, and general journal batches.
The Approval User Setup table (Page 663) establishes the approval hierarchy, defining each user's direct Approver ID, specific monetary approval limits, unlimited approval overrides, and substitute delegates.
Business Central evaluates approval routing using four distinct Approver Limit Types: Approver Chain (hierarchical escalation), Direct Approver, First Qualified Approver, or Specific Approver.
Documents under approval follow an immutable lifecycle: beginning in Open status, transitioning to Pending Approval upon submission, and converting to Released only after all designated approvals are granted.
Last updated: September 2026
5.1 Native Workflow Templates & Approval Hierarchy
Quick Summary: Dynamics 365 Business Central provides a built-in native workflow engine that automates document approvals, record restrictions, and internal notifications without requiring external cloud integrations. Workflows operate on an Event-Condition-Response model and are initialized from standard out-of-the-box templates. The Approval User Setup table establishes the core governance structure, defining managerial chains of command via Approver IDs, monetary approval thresholds for sales and purchases, unlimited approval overrides, and substitute delegates. When an approval workflow is active, documents transition through an immutable lifecycle from Open to Pending Approval , unlocking into Released only when all criteria and limits are satisfied.
The Native Workflow Engine: Architecture & Execution Model
Dynamics 365 Business Central includes an integrated, database-native workflow engine designed to enforce internal controls, segregation of duties, and regulatory compliance (such as Sarbanes-Oxley or ISO quality standards). Because the engine is compiled directly into the application runtime (AL code and business logic events), it executes synchronously within the database transaction boundary. This ensures that no document or transaction can bypass approval controls due to network timeouts, latency, or external service interruptions.
The Three-Tier Workflow Anatomy
Every workflow in Business Central is modeled around three fundamental building blocks displayed on the Workflow page (Page 1501): ┌─────────────────────────┐ ┌─────────────────────────┐ ┌─────────────────────────┐
- │ WHEN EVENT OCCURS │ ──► │ ON CONDITION │ ──► │ THEN RESPONSE │
- │ (Trigger / Entry Point)│ │ (Filter / Rule Matrix) │ │ (Action / Execution) │
- └─────────────────────────┘ └─────────────────────────┘ └─────────────────────────┘
When Event Occurs (Trigger): The business event that initiates the workflow step. Examples include:
- An approval of a purchase document is requested
- An approval of a sales document is requested
- A customer record is changed
- A vendor record is changed
- A general journal batch is to be posted
On Condition (Filters & Thresholds): Defines the exact logical criteria that must evaluate to true for the event to execute its associated responses. Conditions apply table filters against the record being processed, such as:
- Document Type: Order
- Status: Open
- Amount Including VAT: > 5000
Pending Approvals: 0 Conditions can also evaluate child conditions in multi-step branching workflows using hierarchical step indentation.
Then Response (Actions & Next Steps): One or more automated actions executed in sequence when the event occurs and the condition is met. Responses can perform operations such as:
Create an approval request for the record using approver type Approver and approver limit type Approver Chain.
Restrict record usage.
Send notification.
Show message.
Revert record status.
Hierarchical Step Indentation
In the Workflow Steps table, lines can be indented under parent lines. An indented line represents a subsequent event that listens only after the parent step's response completes. For instance, an approval workflow features a parent event ( An approval of a purchase document is requested ), followed by child events indented underneath ( An approval request is approved and An approval request is rejected ), each triggering its own respective response (such as releasing the document or sending a rejection notification).
Native Workflow Templates & Operational Coverage
Rather than building complex workflows from scratch, Business Central provides dozens of pre-configured Workflow Templates (accessed via Page 1505). Templates serve as immutable blueprints that encapsulate Microsoft's recommended business logic and best practices.
Important
Templates are Read-Only: Users cannot directly edit, modify, or enable records on the Workflow Templates page. To use a template, an administrator must navigate to the Workflows page (Page 1500) and choose New -> New Workflow from Template . This action copies the template structure into an active, editable workflow record.
Core Workflow Template Categories
Category Typical Workflow Templates Key Event Triggers Primary Responses
Purchase Documents Purchase Order Approval Workflow; Purchase Invoice Approval Workflow; Purchase Quote Approval Workflow; Purchase Credit Memo Approval Workflow An approval of a purchase document is requested Creates approval requests based on purchase amount limits; restricts document changes; sets document status to Pending Approval ; releases document upon final sign-off.
Sales Documents Sales Order Approval Workflow; Sales Invoice Approval Workflow; Sales Quote Approval Workflow; Sales Credit Memo Approval Workflow An approval of a sales document is requested Creates approval requests based on sales amount or credit limits; blocks order processing until authorized; sends notifications to sales representatives.
Master Data Customer Approval Workflow; Vendor Approval Workflow; Item Approval Workflow A customer/vendor/item record is changed or created Restricts usage of the master record; blocks selection of the vendor/customer on operational documents until approved; notifies data stewards.
General Journals General Journal Batch Approval Workflow; General Journal Line Approval Workflow A general journal batch/line is to be posted Verifies batch balance; routes approval to financial controllers before posting; prevents unauthorized G/L journal commits.
Master Data Record Restrictions
When a master data workflow is enabled (such as the Vendor Approval Workflow ), Business Central introduces a critical operational safeguard: Record Restrictions .
When a user creates a new vendor or modifies sensitive fields (such as bank details, payment terms, or VAT registration numbers), the workflow automatically logs a record in the Restricted Record table.
While the record remains visible in the master list, any attempt to select that vendor on a Purchase Order or post a transaction referencing that vendor triggers a hard system validation error: "The record is restricted by a workflow."
Only when the designated approver approves the request does Business Central execute the response Remove record restriction , permitting operational use.
Approval User Setup: Hierarchy, Limits & Governance
The Approval User Setup page (Page 663) forms the foundational bedrock of all document approval routing in Dynamics 365 Business Central. It defines who can request approvals, who approves for whom, and the exact financial authority each user wields. Approval User Setup Architecture:
- User ID Approver ID Sales Limit Purchase Limit Unlimited Substitute Admin
- ───────── ─────────── ─────────── ────────────── ───────── ────────── ─────
- BUYER1 MGR_PURCH $0 $0 [ ] BUYER2 [ ]
- MGR_PURCH DIR_FIN $10,000 $25,000 [ ] MGR_ALT [ ]
- DIR_FIN VP_EXEC $50,000 $100,000 [ ] CFO [ ]
- VP_EXEC [BLANK] $0 $0 [X] CEO [X]
- Core Configuration Fields on Approval User Setup
User ID: The Business Central login ID of the employee. Every user who submits documents or participates in an approval chain must have a dedicated record.
Approver ID: The User ID of this user's direct supervisor or immediate approver. By linking User IDs to Approver IDs, Business Central constructs a hierarchical linked list (chain of command).
Sales Amount Approval Limit: The maximum total monetary value (in LCY) on a sales document that this user is authorized to approve. A value of 0 means the user cannot approve any sales document.
Purchase Amount Approval Limit: The maximum total monetary value (in LCY) on a purchase document that this user is authorized to approve.
Request Amount Approval Limit: The maximum monetary limit for non-document requests (e.g., quotes or custom request records).
Unlimited Sales / Purchase / Request Approval: Dedicated boolean checkboxes. Checking this flag grants the user infinite approval authority, completely bypassing numeric monetary limits. At least one executive or top-tier manager in the chain must have this flag checked to prevent approval requests from dead-ending with insufficient authority.
Substitute: The User ID of the designated replacement approver. When an approver is out of the office, pending approval requests can be delegated to this substitute.
E-Mail: The corporate email address used to dispatch notification alerts when approval actions occur.
Approval Administrator: A high-level administrative privilege. A user marked as an Approval Administrator possesses system-wide authority to view all pending approval entries across all users, cancel stuck or orphaned approval requests, and delegate requests on behalf of other users.
Warning
User Setup vs. Approval User Setup: Do not confuse the User Setup page (Page 119) with the Approval User Setup page (Page 663). While User Setup defines individual posting date ranges ( Allow Posting From / Allow Posting To ) and register time flags, Approval User Setup governs approval chains, monetary limits, and substitute delegates.
Approver Types & Limit Types
When configuring the response Create an approval request for the record... in a workflow, two critical parameters govern how Business Central traverses the user hierarchy:
1. Approver Type
Approver: Traverses the standard supervisory chain defined by the Approver ID field in the Approval User Setup table.
Salesperson/Purchaser: Routes the approval request to the specific user mapped to the Salesperson/Purchaser Code stamped on the document header.
Workflow User Group: Bypasses the 1-to-1 manager hierarchy entirely and routes the request to a multi-member group.
2. Approver Limit Type
When Approver Type is set to Approver , the Approver Limit Type dictates how managerial thresholds are evaluated:
Approver Limit Type Routing Behavior & Mechanics Typical Business Scenario
Approver Chain The request routes to the requester's direct Approver ID . If the document amount exceeds that manager's limit, the manager must approve first, after which Business Central automatically routes a subsequent request to their manager, continuing sequentially until a user with sufficient limit approves. Standard corporate governance where every supervisory tier must review and endorse expenditures within their operational scope before escalating.
Direct Approver The request routes strictly and solely to the requester's direct Approver ID , regardless of whether that approver's monetary limit is high enough to approve the document. Lightweight review where a manager must sign off on operational validity, but financial limits are enforced through other auditing mechanisms.
First Qualified Approver The engine inspects the Approver ID chain, skips any intermediate managers whose limits are insufficient, and routes the approval request directly to the first manager in the chain whose limit covers the document amount. Streamlined processing for high-velocity environments, eliminating unnecessary intermediate approvals by unqualified supervisors.
Specific Approver The request routes to an explicitly specified User ID designated in the workflow response argument, completely ignoring the requester's manager chain. Specialized document routing (e.g., all hazardous material purchases must be approved by the Safety Director).
The Document Approval Lifecycle: State Machine Mechanics
Documents governed by approval workflows progress through an immutable state machine managed by the Status field on the document header: ┌──────────────┐
- │ OPEN │ ◄────────────────────────┐
- └──────────────┘ │
- │ │
- Send Approval Request Cancel / Reject
- │ │
- ▼ │
- ┌──────────────┐ │
- │ PENDING │ ─────────────────────────┤
- │ APPROVAL │ │
- └──────────────┘ │
- │ │
- All Approvers Approve │
- │ │
- ▼ │
- ┌──────────────┐ │
- │ RELEASED │ ──── Reopen Document ────┘
- └──────────────┘
- │
- Post Document
- │
- ▼
- ┌──────────────┐
- │ POSTED │
- └──────────────┘
- Document Status States
Open:
The initial state of a newly created sales or purchase document.
All fields (quantities, prices, dimensions, vendor/customer details) are freely editable.
Posting is strictly prohibited; clicking Post triggers a validation error stating the document must be approved and released first.
Pending Approval:
Initiated when the user selects Request Approval -> Send Approval Request .
The document header and line fields are locked to prevent tampering while under review.
One or more records are inserted into the Approval Entry table (Table 454) with Status = Open .
If the requester's own approval limit exceeds the document amount (and the workflow permits self-approval), the engine bypasses pending approval and immediately transitions the document to Released .
Released:
Triggered when all necessary approval entries are marked as Approved .
The document is unlocked for downstream warehouse operations (creating warehouse shipments, receipts, or inventory picks) and final financial posting.
Fields remain locked from accidental editing.
Reopening and Modifying Documents:
If a pending document requires changes, the requester can choose Request Approval -> Cancel Approval Request , reverting status to Open and canceling open approval entries.
If a released document requires correction before posting, an authorized user must choose Release -> Reopen . Reopening sets the status back to Open . If the document is modified, it must go through the entire approval workflow again before it can be re-released and posted.
- Step-by-Step UI Setup Paths
- 1. Initializing an Approval Workflow from Template
Open Tell Me ( Alt+Q ), type Workflows , and select the Workflows list page (Page 1500).
On the action bar, select New -> New Workflow from Template (Page 1505 opens).
Expand the Purchase Documents category and select Purchase Order Approval Workflow .
Business Central generates a new workflow record with pre-populated event-condition-response lines.
In the header, review the Code and Description .
2. Configuring the Approval User Setup Matrix
Open Tell Me ( Alt+Q ), type Approval User Setup , and select Approval User Setup (Page 663).
Select New to create a line for each operational user:
Enter User ID (e.g., JDOE ).
Select Approver ID (e.g., MSMITH ).
Specify Purchase Amount Approval Limit (e.g., 5000 ) or check Unlimited Purchase Approval .
Select a Substitute user ID and enter the user's E-Mail .
Designate at least one senior finance user with the Approval Administrator checkbox enabled.
3. Modifying Conditions & Enabling the Workflow
On the Workflow card, locate the first line under Workflow Steps where Event is An approval of a purchase document is requested .
Click the link in the On Condition column to open the Event Conditions modal.
Adjust the filter criteria (e.g., set Amount Including VAT to > 2500 if approval is only required for orders above $2,500).
In the header FastTab, switch the Enabled toggle from No to Yes .
Common Pitfalls & Exam Gotchas
Editing an Enabled Workflow: Attempting to modify steps, conditions, or responses on an active workflow results in the runtime error: "Enabled must be equal to 'No' in Workflow: Code=... Current value is 'Yes'." The workflow must always be disabled before editing.
Circular Approval Chains: Configuring User A's Approver as User B, and User B's Approver as User A creates an infinite loop. When an approval request is triggered, Business Central detects the circular reference and halts with an error.
Missing Approval Administrator: If an approver leaves the organization or takes unexpected leave without designating a substitute, their open approval requests freeze the affected documents. Without a user configured with the Approval Administrator flag, no one can cancel or delegate those requests.
Zero vs. Blank Approval Limits: An approval limit of 0 means the user has zero approval authority (they cannot approve any document exceeding $0). Leaving a user out of the Approval User Setup table entirely causes an error when they attempt to send an approval request: "The approval user setup does not exist for User ID..."
Self-Approval Trap: If an employee's approval limit is $10,000 and they create a purchase order for $4,500, a workflow using Approver Chain will automatically approve and release the document upon submission unless the workflow condition explicitly requires managerial review regardless of limits.