What Is an Expense Approval Workflow in Dynamics 365 Business Central?
A Business Central expense approval workflow is an automated sequence of events, conditions, and responses that enforces policy compliance and control objectives before expenses post to the General Ledger. Unlike manual email chains or spreadsheet tracking, Microsoft Dynamics 365 Business Central workflows create request-for-approval mechanisms while preserving pre-approval data, ensuring separation of duties, and generating auditable evidence trails.
For Controllers, a good expense approval workflow balances three imperatives: controls (separation of duties, amount limits, policy enforcement), evidence (receipt retention, audit trails, approval timestamps), and speed (no bottlenecks at month-end, exception-only reviews, automated routing).
Business Central supports approval workflows natively for finance journals prior to posting, purchase documents, and incoming documents. When paired with expense management tools like OmniFY Expense—which offers native integration, SAP Concur connectivity, and automated processing—organizations achieve true end-to-end automation from receipt capture through reimbursement, without middleware or manual re-keying.
The Controller's Dilemma: Manual Expense Approvals Are a Control Gap Disguised as Process
You’re three days from month-end close. Payables needs final numbers. Your AP team is chasing approvers via email. One VP is on vacation. Another forwarded their approval to an admin who shouldn’t have signing authority. A third approved an expense via reply-all without reviewing the receipt, which—you discover during the audit—was a duplicate.
This Isn’t Process. It’s Improvisation.
Manual expense approvals create control gaps: no separation of duties, no evidence retention, no audit trail linking approval to policy. Email threads aren’t substitutes for controls. Spreadsheets tracking “who approved what” fail the moment someone forwards an email or bypasses the workflow.
If you can’t prove who approved what, when, and why at the transaction level—with timestamped evidence and policy alignment—you don’t have a control. You have documentation theater.
What Good Looks Like: The Controls-Evidence-Speed Triangle
A defensible Business Central expense approval workflow satisfies three imperatives simultaneously:
1. Controls (Policy Enforcement at the Transaction Level)
Amount thresholds. Category restrictions. Dimension-based routing. Duplicate detection. Missing receipt holds. Separation of duties. These aren’t features—they’re control objectives. Your workflow is the enforcement mechanism.
2. Evidence (Audit-Grade Documentation)
Who requested. Who approved. When. What policy applied. What receipt was attached. What happened if an approver was unavailable. Evidence isn’t optional—it’s the reason the control exists.
3. Speed (No Bottlenecks, Especially at Period-End)
If your workflow creates month-end delays, approvers will bypass it. If exception handling requires manual intervention, AP won’t use it. Speed isn’t a “nice-to-have”—it’s how you ensure compliance without friction.
Most organizations optimize for one or two of these. Controllers need all three.
Blueprint: Design from Controls Backward, Not Workflow Forward
Most workflow implementations start with “map the current process.” That’s a mistake. You’re automating a control gap.
Start with control objectives. Then design the workflow to enforce them.
Step 1: Define Control Objectives (Not Process Steps)
Ask:
- What prevents unauthorized expenses from posting?
- What ensures separation of duties between requestor, approver, and processor?
- What enforces policy compliance (category restrictions, amount limits, project allocations)?
- What creates auditable evidence for each decision point?
- What handles exceptions without bypassing controls (missing receipts, duplicate expenses, unavailable approvers)?
Write these as control objectives, not tasks.
Example: “No single individual can both submit and approve their own expense” (separation of duties) vs. “Manager approves expense” (task description).
Step 2: Map Control Objectives to Workflow Events
In Business Central, workflows are sequences of events (what happened), conditions (what must be true), and responses (what the system does). According to Microsoft’s workflow documentation, this event-condition-response architecture supports approval workflows for documents, journal lines, and master data changes.
For expense approvals, your core events are:
- Approval is requested (user submits expense report or journal line)
- Approval is granted/rejected (approver takes action)
- Approval is delegated (approver assigns to substitute)
Conditions determine when the event triggers a response:
- Amount exceeds threshold ($5,000)
- Category is sensitive (meals, entertainment, travel)
- Receipt is missing
- Expense matches a recent submission (duplicate detection)
- Dimension/project requires specific approver (grant compliance, cost center routing)
Responses are the actions the system takes:
- Send approval request to [designated approver]
- Restrict record usage (prevent posting until approved)
- Send notification (email, in-app note)
- Create audit log entry
- Escalate to Controller (exception handling)
Step 3: Workflow Logic Must Match Policy (Not the Other Way Around)
If your policy says “expenses over $5,000 require CFO approval,” the workflow condition must enforce that threshold at the transaction level. If your policy requires receipts for all expenses over $25, the workflow must block posting when receipts are missing.
This is non-negotiable. If the workflow can’t enforce the policy, the control doesn’t exist.
How Business Central Workflows Support Expense Approvals (Technical Foundation)
Business Central provides native workflow functionality specifically designed to enforce approval requirements before transactions post to the General Ledger. This isn’t a bolt-on feature—it’s core platform architecture.
Workflow Templates for Expense Approvals
Microsoft provides pre-configured workflow templates, including:
- General Journal Approval Workflow (for expense journal lines prior to posting)
- Purchase Document Approval Workflow (adaptable for corporate card expenses)
- Incoming Document Approval Workflow (for scanned receipts and invoices)
These templates handle common scenarios: sequential approvals, parallel approvals (multiple approvers simultaneously), approval delegation, and substitute approvers for vacation coverage.
Approval User Setup: The Foundation of Separation of Duties
Before creating workflows, you must configure Approval User Setup to define:
- Who can approve (Approver ID)
- What they can approve (amount limits, unlimited approval rights)
- Who covers when they’re unavailable (Substitute Approver)
This is where separation of duties enforcement begins. According to Microsoft’s purchase approval walkthrough, each user in the approval chain must be explicitly configured with approval rights and limits. A purchasing agent cannot approve their own expenses. An approver with a $10,000 limit cannot approve a $15,000 expense without escalation.
Event-Condition-Response Architecture
When a user requests approval (event), Business Central evaluates conditions:
- Does the amount exceed the current approver’s limit?
- Is the record type restricted?
- Is the approver available (or is a substitute needed)?
Based on these conditions, the system executes responses:
- Route to appropriate approver
- Send notification (email, internal note, push notification)
- Restrict record usage (status changes to “Pending Approval”—no posting allowed)
- Create audit log entry (who requested, when, what policy applied)
Finance Journals: Pre-Posting Approval Enforcement
For expense reimbursements processed through General Journal lines, Business Central workflows can require approval before the journal posts. This is critical: once a transaction posts to the G/L, it’s too late for approval. The control must enforce before posting.
When properly configured, a user submitting an expense journal line cannot post it without approval. The workflow holds the transaction in “Pending Approval” status, routes it to the designated approver, and only allows posting after approval is granted.
Integration with Dimensions and Jobs
Business Central workflows support conditional routing based on dimensions (department, cost center, project, grant). This allows for sophisticated approval logic:
- Expenses for Project A route to Project Manager A
- Expenses for Grant B route to Grant Administrator B (with compliance documentation requirements)
- Expenses for Department C route to Department C Controller
This dimension-based routing is essential for organizations with complex cost allocation requirements, especially those in professional services, research institutions, or grant-funded operations.
Approval Logic Patterns: From Simple Thresholds to Intelligent Routing
Amount-Based Escalation (Hierarchical Limits)
Logic:
- $0-$1,000: Direct manager approval
- $1,001-$5,000: Department head approval
- $5,001+: Controller or CFO approval
Implementation:
Configure approval amount limits in Approval User Setup. Business Central automatically escalates when a request exceeds an approver’s limit.
Control Objective:
Separation of duties + proportional oversight (higher risk = higher authority).
Category-Based Routing (Policy Enforcement)
Logic:
Certain expense categories always require Controller review, regardless of amount:
- Meals & Entertainment (T&E policy compliance)
- Client gifts (anti-bribery compliance)
- Professional memberships (policy exceptions)
Implementation:
Add workflow conditions based on Expense Type or G/L Account. Route to Controller when category matches.
Control Objective:
Policy compliance + risk mitigation for sensitive categories.
Dimension/Project Routing (Grant Compliance, Job Costing)
Logic:
Expenses allocated to specific projects, grants, or cost centers route to the responsible manager, not the employee’s direct supervisor.
Implementation:
Use dimension filters in workflow conditions to route based on project, department, or grant code.
Control Objective:
Ensure grant administrators approve grant-funded expenses (compliance requirement for many federal and research grants).
Exception-Only Controller Review (Efficiency Without Sacrificing Control)
Logic:
Controller reviews only exceptions:
- Missing receipts
- Duplicate expenses
- Policy violations flagged by system
- Amounts exceeding departmental budgets
Implementation:
Default workflow routes to direct manager. Add condition: receipt is missing OR amount exceeds budget OR duplicate detected → escalate to Controller.
Control Objective:
Proportional oversight (Controller focuses on risk, not routine approvals).
Duplicate Detection (Automated Fraud Prevention)
Logic:
System flags expenses that match recent submissions (same amount, same date, same vendor, same employee within 30 days).
Implementation:
This requires custom logic or integration with expense management tools like OmniFY Expense, which can enforce duplicate detection rules before submission reaches Business Central.
Control Objective:
Fraud prevention + error reduction (duplicate submissions are often accidental, but must be caught before reimbursement).
Missing Receipt Handling (Evidence Enforcement)
Logic:
- Expenses under $25: Receipt optional (de minimis threshold)
- Expenses $25-$75: Receipt required, but approval can proceed with follow-up
- Expenses over $75: Hard block until receipt attached
Implementation:
Workflow condition checks for attached document. If missing and amount > threshold, route to Controller for exception approval or reject automatically.
Control Objective:
Evidence retention + audit compliance (IRS requires receipts for substantiation).
Audit Controls + Evidence Retention: What Auditors Actually Look For
Separation of Duties (The Non-Negotiable Control)
What It Means:
No single individual can authorize, record, and reconcile their own transactions.
How Business Central Enforces It:
- Approval User Setup prevents self-approval (user cannot be their own approver)
- Workflow responses restrict record usage until approval granted
- Posting permissions separate from approval permissions
Auditor Evidence:
Approval User Setup configuration report + approval log showing distinct users for requestor, approver, and processor.
Approval Audit Trail (Timestamped, Immutable Evidence)
What Auditors Need:
- Who requested approval
- Who approved (or rejected)
- When (date/time stamp)
- What policy/condition applied
- Any delegation or substitute approvals
Where Business Central Stores It:
- Workflow Step Instances (archived history of each approval step)
- Approval Entries (detailed log of all approval requests/responses)
- Posted Document Comments (approval notes attached to posted transactions)
How to Configure Retention:
Microsoft’s workflow documentation recommends archiving completed workflow instances. Ensure your data retention policy preserves approval logs for the required audit period (typically 7 years for financial records).
Receipt Retention (Evidence of Transaction)
Regulatory Requirements:
IRS requires receipts for expenses over $75 (travel/entertainment). Many organizations enforce lower thresholds (e.g., $25).
How to Store in Business Central:
- Use Incoming Documents module to attach scanned receipts
- Link to journal lines or posted entries
- Retain digital copies for audit period
OmniFY Expense Advantage:
Native receipt attachment + automatic download from SAP Concur (receipts stored centrally, accessible in Business Central without manual uploads).
Policy Compliance Documentation
What Auditors Ask:
“How do you know this expense complied with policy at the time of approval?”
Evidence Required:
- Policy version in effect at transaction date
- Workflow configuration enforcing that policy
- Approval log showing policy-based routing (e.g., “exceeded $5K threshold, routed to CFO”)
Implementation Tip:
Version-control your workflow configurations. When policy changes, create a new workflow version with an effective date. Archive the old version for audit trail purposes.
Controller's Pre-Go-Live Checklist: What to Verify Before You Flip the Switch
Before enabling your Business Central expense approval workflow in production, validate these six control points:
- Approval User Setup is complete for all expense submitters and approvers (including amount limits, substitute approvers, notification preferences)
- Workflow conditions enforce policy thresholds (test: submit expense $1 below and $1 above each threshold—confirm routing changes)
- Separation of duties is enforced (test: user cannot approve their own expense; posting permissions separated from approval permissions)
- Receipt attachment requirements are enforced (test: missing receipt blocks posting for amounts above threshold)
- Dimension-based routing works correctly (test: expense for Project A routes to Project A manager, not submitter’s direct supervisor)
- Notification delivery is reliable (test: approvers receive notifications via configured method—email, internal note, mobile app)
- Exception handling works without bypassing controls (test: unavailable approver triggers substitute; missing receipt escalates to Controller)
- Audit trail is complete and accessible (test: retrieve approval log for a sample transaction; confirm all required fields are populated)
For organizations planning Business Central implementations, understanding the typical timeline and phases helps set realistic expectations for workflow configuration and testing.
UAT Plan + Month-End/Year-End Considerations
User Acceptance Testing: Test Scenarios That Matter
Don’t test happy paths. Test exceptions and edge cases—that’s where workflows break.
Critical Test Scenarios:
-
High-Amount Escalation
Submit expense exceeding each approval tier. Confirm routing to correct approver at each threshold. -
Missing Receipt
Submit expense requiring receipt without attachment. Confirm workflow blocks or escalates appropriately. -
Duplicate Expense
Submit identical expense twice within detection window. Confirm system flags duplicate. -
Dimension Routing
Submit expenses for multiple projects/departments. Confirm each routes to correct project manager, not direct supervisor. -
Approver Unavailable
Submit expense when approver’s substitute is configured. Confirm substitute receives notification. -
Month-End Cutoff
Submit expense on last day of period. Confirm period assignment, posting date validation, cutoff enforcement. -
Policy Exception
Submit expense for category requiring Controller approval. Confirm escalation regardless of amount. -
Rejection + Resubmission
Approver rejects expense. User corrects and resubmits. Confirm workflow restarts correctly.
For detailed UAT methodology, Omni Logic Solutions provides guidance on page scripting for Business Central UAT, which can help teams document test scenarios systematically.
Month-End and Year-End Specific Considerations
Period Cutoff Enforcement:
Configure workflows to validate posting dates against open accounting periods. Expenses submitted after period close should route to Controller for exception approval or automatic rejection.
Accrual Handling:
For expenses incurred but not yet approved at period-end, decide:
- Accrue based on submitted (not yet approved) expenses?
- Require pre-approval before period close?
- Post to following period (adjust policy if material)?
Document this decision in your period-end close procedures. For comprehensive year-end checklists, see Omni Logic Solutions’ Canadian SMB year-end closing guide.
Approver Availability During Holidays:
December/January closings often coincide with vacation schedules. Ensure:
- Substitute approvers are configured for all critical approvers
- Notification settings include mobile/email for remote approvals
- Exception escalation routes to available Controller if primary and substitute both unavailable
Where OmniFY Expense Fits: Native Integration, No Middleware, Full Automation
Business Central workflows provide the approval logic and control framework. OmniFY Expense provides the expense capture, processing, and integration layer.
Native Business Central Integration (No Middleware)
OmniFY Expense is built using Microsoft Dynamics native development code, functioning as a Business Central extension, not a third-party connector requiring middleware. This means:
- Direct integration with Business Central tables (Employees, G/L Accounts, Dimensions, Jobs)
- No separate database or sync delays
- Workflow triggers fire immediately upon expense submission
- Approval status updates in real-time
SAP Concur Connector (Enterprise Expense Management)
For organizations using SAP Concur for expense capture (mobile app, OCR receipt scanning, corporate card integration), OmniFY’s SAP Concur Expense connector downloads approved expense reports and receipts directly into Business Central.
Key Capabilities:
- Automated download of approved expense reports (Professional and Standard editions)
- Attached receipt images imported automatically
- Processes to employees, vendors, G/L accounts, jobs, and dimensions
- Scheduled background processing via Job Queue Scheduler (set-it-and-forget-it automation)
- One-click on-demand download for urgent approvals
Control Advantage:
Expenses approved in Concur (with Concur’s policy enforcement and receipt validation) flow into Business Central’s approval workflow for financial controls (amount limits, dimension routing, separation of duties). This layered approach separates policy compliance (Concur) from financial controls (Business Central).
As noted in Omni Logic Solutions’ overview of useful AI capabilities in Business Central, AI-powered OCR for receipt capture is one of the practical applications gaining traction in 2026, and tools like AI chatbots for expense automation can further streamline data entry.
Dimension and Job Support (Project/Grant Tracking)
OmniFY Expense integrates with Business Central’s dimension framework, enabling:
- Allocation to multiple dimensions (Department, Project, Cost Center, Grant)
- Workflow routing based on dimension values (Project A expenses route to Project A Manager)
- Job costing integration (expenses post to Jobs for client billing or project tracking)
This is critical for professional services firms, government contractors, and research institutions with grant compliance requirements.
Job Queue Scheduling (Background Processing, No Manual Intervention)
OmniFY uses Business Central’s Job Queue functionality to schedule expense downloads, processing, and posting in the background. Controllers can configure:
- Hourly sync from Concur during business hours
- Overnight batch processing for reimbursements
- Exception reporting (failed downloads, missing dimensions, duplicate detection)
Result:
AP teams spend zero time manually importing expenses. Controllers monitor exceptions, not routine transactions.
Cost and Licensing Considerations
OmniFY operates without recurring per-transaction costs. Licensing is based on Business Central users, not transaction volume. For organizations evaluating Business Central implementation costs in Canada, it’s worth noting that native extensions like OmniFY typically have lower total cost of ownership than third-party SaaS integrations requiring ongoing transaction fees.
For a broader view of available tools, Omni Logic Solutions maintains a 2026 overview of best Business Central add-ons for Canadian SMBs.
Table 1: Approval Matrix (Condition → Approver → Evidence → Rationale)
| Condition | Approver Role | Required Evidence | Rationale |
|---|---|---|---|
| Amount: $0–$1,000 | Direct Manager | Receipt (if >$25) | Routine approval; manager knows employee work context |
| Amount: $1,001–$5,000 | Department Head | Receipt + business purpose | Elevated authority for higher risk; departmental budget oversight |
| Amount: $5,001+ | Controller or CFO | Receipt + business purpose + budget justification | Material impact on financials; requires senior oversight |
| Category: Meals & Entertainment | Controller (any amount) | Receipt + attendees + business purpose | T&E policy compliance; IRS substantiation requirements |
| Category: Client Gifts | Controller (any amount) | Receipt + recipient + business justification | Anti-bribery compliance; policy exception approval |
| Missing Receipt (>$75) | Controller (exception approval) | Signed affidavit or credit card statement | IRS requires receipts >$75; exception must be documented |
| Dimension: Grant-Funded Project | Grant Administrator | Receipt + grant code + allowability justification | Federal grant compliance (OMB Uniform Guidance for U.S. grants) |
| Duplicate Suspected | Controller (hold for review) | Original expense + suspected duplicate + explanation | Fraud prevention; may be legitimate (split billing) or error |
Table 2: Controls-to-Evidence Map (Audit Preparedness)
| Control Objective | Enforcement Method | Audit Evidence | Monitoring Frequency |
|---|---|---|---|
| Separation of Duties | Approval User Setup prevents self-approval; posting permissions separated from approval rights | Approval User Setup report + approval log showing distinct requestor/approver/processor | Annual (or upon user role changes) |
| Amount Limit Compliance | Workflow escalates when expense exceeds approver’s limit | Approval entries showing escalation when limit exceeded | Monthly (exception report: approvals above authorized limit) |
| Policy Compliance (Category Restrictions) | Workflow routes sensitive categories (meals, gifts) to Controller regardless of amount | Approval log filtered by category; Controller approval required | Quarterly (sample sensitive categories) |
| Receipt Retention | Workflow blocks posting for expenses >$75 without attached receipt | Incoming Documents attached to posted entries; exception log for missing receipts | Monthly (exception report: expenses >$75 without receipts) |
| Dimension Accuracy (Project/Grant Allocation) | Workflow routes by dimension; approver validates allocation | Approval log + posted entries showing dimension values; project manager confirmation | Monthly (dimension validation report) |
| Duplicate Prevention | System flags duplicate expenses (same amount/date/vendor within 30 days) | Duplicate detection log; Controller review of flagged items | Monthly (review flagged duplicates) |
Table 3: UAT Test Matrix (Validation Before Go-Live)
| Test Scenario | Test Steps | Expected Result | Evidence Captured |
|---|---|---|---|
| High-amount expense ($6,000) | 1. User submits expense for $6,000 2. Check approval routing | Workflow routes to CFO (not direct manager or dept head) | Approval entry showing CFO as approver; notification sent to CFO |
| Missing receipt (>$75) | 1. User submits $100 expense without receipt 2. Attempt to post | Workflow blocks posting OR escalates to Controller for exception approval | Error message or approval request to Controller; expense status = Pending |
| Duplicate expense | 1. User submits expense for $250 to Vendor A on 2/10 2. User submits identical expense on 2/12 | System flags duplicate; routes to Controller for review | Duplicate detection log entry; Controller approval request |
| Dimension routing (Project expense) | 1. User submits expense allocated to Project X 2. Check approval routing | Workflow routes to Project X Manager (not user’s direct supervisor) | Approval entry showing Project X Manager as approver |
| Approver unavailable (substitute) | 1. Set Manager A as “Out of Office” or configure substitute 2. User submits expense normally routed to Manager A | Workflow routes to Substitute Approver B | Approval entry showing Substitute Approver B; notification sent to Substitute |
| Month-end cutoff | 1. User submits expense on last day of month (e.g., 2/28) 2. Posting date = 3/1 | Workflow validates posting date; either blocks (period closed) or posts to correct period | Posting date validation message; posted entry shows correct period |
| Sensitive category (Meals) | 1. User submits $45 meal expense (below $1K threshold) 2. Check approval routing | Workflow routes to Controller (not direct manager, despite low amount) | Approval entry showing Controller as approver; category = Meals & Entertainment |
| Rejection + Resubmission | 1. Approver rejects expense (missing business purpose) 2. User adds justification and resubmits 3. Approver approves | Workflow restarts; approval granted on second submission | Approval log showing: initial rejection → resubmission → approval (with timestamps) |
KPIs to Track Post Go-Live: Measure What Matters
Once your Business Central expense approval workflow is live, track these metrics to ensure it’s delivering control + efficiency:
Approval Cycle Time (Speed)
Metric: Average days from submission to final approval
Target: <2 business days for routine expenses; <1 day for urgent/month-end
Why It Matters: Long cycle times indicate bottlenecks (unavailable approvers, unclear policies, missing receipts). Monitor by approver to identify delays.
Exception Rate (Control Effectiveness)
Metric: % of expenses requiring Controller exception approval
Target: <5% (indicates policies are clear and workflows handle routine approvals)
Why It Matters: High exception rates suggest policies are unclear, thresholds are too low, or workflow logic doesn’t match actual business needs.
Missing Receipt Rate (Compliance)
Metric: % of expenses >$75 submitted without receipts
Target: <2% (should be rare exceptions)
Why It Matters: High rates indicate weak enforcement or user non-compliance. May signal audit risk.
Duplicate Detection Rate (Fraud Prevention)
Metric: Number of duplicate expenses flagged per month
Target: Monitor trend (should decrease over time as users learn system flags duplicates)
Why It Matters: Declining trend = deterrent effect. Stable or increasing trend = potential fraud or system usability issue.
First-Pass Approval Rate (Workflow Efficiency)
Metric: % of expenses approved on first submission (no rejection/resubmission)
Target: >90%
Why It Matters: Low first-pass rate indicates unclear policies, poor user training, or missing information in submission form.
Period-End Backlog (Month-End Impact)
Metric: Number of expenses pending approval on last day of month
Target: <10 (or <1% of monthly volume)
Why It Matters: Period-end backlog delays close and may require accruals. Indicates approvers aren’t responding promptly.
Audit Findings (Ultimate Control Test)
Metric: Number of audit findings related to expense approvals (internal or external audit)
Target: Zero
Why It Matters: Audit findings indicate control failures. Track root causes and remediate workflow logic or policies.
For organizations looking to quantify the broader benefits of automation, Omni Logic Solutions’ analysis of real ROI from Business Central upgrades provides data-backed frameworks for measuring efficiency gains.
FAQs
Can Business Central workflows enforce separation of duties for expense approvals?
Yes. Approval User Setup prevents users from approving their own expenses, and posting permissions can be separated from approval rights to ensure no single person authorizes, records, and processes transactions.
How long should we retain expense receipts and approval documentation?
IRS requires 7 years for substantiation of business expenses. Configure Business Central to archive workflow instances and retain Incoming Documents (receipts) for the same period.
What happens if an approver is on vacation or unavailable?
Configure a Substitute Approver in Approval User Setup. When the primary approver is unavailable, the workflow automatically routes to the substitute with no manual intervention required.
Can we route expenses by project, grant, or cost center (not just by amount)?
Yes. Business Central workflows support dimension-based routing. Expenses allocated to Project A route to Project A Manager; expenses for Grant B route to Grant Administrator B.
Do we need middleware to integrate Business Central workflows with expense capture tools?
Not with OmniFY Expense. It’s built as a native Business Central extension, so expense data flows directly into BC tables and triggers workflows immediately—no middleware, no sync delays.
Can we automate duplicate expense detection?
Yes, with proper configuration. OmniFY Expense and similar tools can flag expenses matching recent submissions (same amount, vendor, date, employee within a detection window). Flagged items route to Controller for review.
How do we handle expenses submitted after month-end close?
Configure workflow to validate posting dates against open accounting periods. Expenses with posting dates in closed periods should route to Controller for exception approval or automatic rejection with instructions to resubmit for the correct period.
What’s the difference between Business Central workflows and Power Automate flows for expense approvals?
Business Central workflows are native to the platform, enforce pre-posting controls, and integrate directly with approval user setup and security. Power Automate offers more flexibility for complex scenarios (external systems, non-BC data) but requires additional configuration.
Can approvers see attached receipts when reviewing expense requests?
Yes. When receipts are attached via Incoming Documents, approvers can view them directly from the approval request in Business Central without switching systems.
How do we test workflow logic before go-live without impacting production data?
Use a dedicated sandbox environment (Business Central supports multiple environments). Configure workflows, create test users and expenses, and validate routing logic. Once validated, export workflow configuration and import to production.
What if our expense policy changes—do we need to rebuild the workflow?
You can modify existing workflows or create new workflow versions with effective dates. Archive the old configuration for audit trail purposes. Version control ensures you can prove which policy was in effect at any transaction date.
Can we configure different approval workflows for different departments or entities?
Yes. Business Central supports workflow filtering by dimensions, user groups, or company (for multi-entity environments). Department A can have different thresholds and approvers than Department B.