We recently deployed D365 Finance cloud (10.0.40) and are encouraging managers to use the mobile app for expense report approvals. However, we’re getting mixed feedback about the mobile experience versus desktop. Some managers love the convenience of approving on-the-go, while others find the mobile interface limiting and prefer desktop.
Performance also varies - mobile approvals seem slower when reviewing reports with multiple line items or attachments. We’re trying to understand if these differences are inherent to mobile versus desktop architecture, or if there are optimization opportunities we’re missing.
For organizations using D365 cloud with both mobile and desktop expense approval workflows, what’s your experience with performance and usability differences? How do you balance encouraging mobile adoption while ensuring managers have the tools they need for thorough expense review?
Mobile vs. desktop expense approval in D365 Finance cloud involves genuine architectural differences, not just UX preference — some gaps are optimizable, others are structural.
Mobile expense approval runs through the Dynamics 365 Mobile App (Power Apps-based shell), which fetches data through additional API layers compared to the full browser client. When a report contains multiple line items or attachments, the mobile path typically triggers sequential or batched REST calls rather than the set-based data loading the browser client uses. Attachment rendering is particularly expensive on mobile — each file is streamed on-demand rather than pre-cached. These are real architectural constraints, not configuration gaps.
The desktop browser client benefits from persistent session state, broader memory allocation, and direct OData endpoints with less intermediary processing. For complex reports (10+ lines, multiple receipts), this gap is measurable.
Criteria Comparison
Criteria
Mobile App
Desktop Browser
Approval speed (simple reports)
Comparable
Comparable
Approval speed (complex reports)
Noticeably slower
Fast
Attachment review
Limited zoom, sequential loading
Full rendering, multi-tab
Line-item detail visibility
Truncated on small screens
Full grid
Audit trail / comments
Supported but limited UI
Full rich-text, history visible
Policy violation flags
Visible, but less contextual
Inline, color-coded
Offline capability
Partial (verify in your version)
No (cloud, browser-dependent)
Convenience / location flexibility
High
Low
Delegation workflow handling
Basic
Full
Optimization Opportunities
These are legitimate levers before accepting performance as fixed:
Expense workflow configuration: In Workflow editor, reduce the approval steps visible to mobile users to only actionable decisions — avoid surfacing full audit history in the mobile step, which inflates payload.
Attachment policy: Enforce maximum attachment size limits in Expense management parameters → General to reduce streaming overhead.
Network baseline: Mobile slowness on corporate Wi-Fi vs. LTE often points to MDM proxy or split-tunnel VPN configuration, not D365 itself. Test both paths.
Power Apps component performance: If your org has customized the mobile expense app via Power Apps, check for non-delegable queries or excessive formula complexity (verify current delegation limits in your version).
Report complexity thresholds: Some organizations route reports above a line-item or amount threshold directly to desktop queues via workflow conditions — a pragmatic hybrid approach.
Balancing Adoption
Segment your manager population by approval pattern. High-volume approvers reviewing itemized T&E with receipts will consistently underperform on mobile. Approvers handling simple mileage or single-vendor submissions are well-suited for mobile. Forcing a uniform channel creates friction in both directions.
Ultimately, which approach fits depends on context / your requirements — specifically your report complexity distribution, attachment policies, and manager workflow patterns.
This draft is based on general Microsoft Dynamics 365 knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.
The mobile app is optimized for quick actions, not detailed review. For expense reports with 10+ line items or large PDF receipts, desktop is definitely faster. Mobile shines for simple approvals - single receipt, clear business purpose, under approval threshold. We tell managers to use mobile for routine approvals and switch to desktop for anything requiring detailed scrutiny.
We’ve found that mobile performance depends heavily on network quality and attachment sizes. Reports with high-resolution scanned receipts can be slow to load on mobile, especially on cellular data. We implemented a policy requiring employees to compress receipt images before submission, which helped mobile approval speed significantly. Also, the mobile app caches recent approvals, so managers who check regularly have better performance than those who approve in batches weekly.
Laura, that’s interesting about the caching. We haven’t communicated that to our managers. Jason’s point about use case suitability makes sense - maybe we need to set clearer expectations about when mobile is appropriate versus when desktop is better.
From an adoption perspective, forcing mobile-first or desktop-only rarely works. Give managers choice and guidance on when each is optimal. We created a simple decision tree: routine expenses under $500 with 1-3 line items = mobile is great; complex reports, international expenses, or anything requiring policy clarification = use desktop. User adoption improved when we stopped pushing mobile for everything and instead positioned it as a convenience tool for appropriate scenarios.
The usability differences between mobile and desktop are by design, not limitations. Mobile UX prioritizes speed for common tasks - approve, reject, request more info. Desktop provides comprehensive views for complex analysis. In cloud deployments, both interfaces access the same data and workflows, but present them differently based on device capabilities and typical use patterns. The performance gap you’re seeing with attachments is partly bandwidth (mobile networks vs office WiFi) and partly rendering optimization (mobile devices have less processing power for PDF rendering).
We’ve been running D365 cloud expense management with both mobile and desktop approvals for over a year, and here’s what we’ve learned about the performance and usability trade-offs:
Mobile vs Desktop Approval Flows - Key Differences:
Performance Characteristics:
Mobile: Optimized for quick approval actions (2-5 seconds per report for simple cases)
Desktop: Better for complex review requiring 2+ minutes of analysis
Attachment loading: Mobile is 3-5x slower for multi-page PDFs over cellular networks
Bulk operations: Desktop supports multi-select approval, mobile requires one-at-a-time
Usability Strengths by Platform:
Mobile Advantages:
Immediate notifications with one-tap approval for routine expenses
Location-independent (approve during commute, travel, meetings)
Reduced approval cycle time (managers respond within hours vs days)
Natural fit for reviewing expense reports submitted via mobile
Desktop Advantages:
Side-by-side comparison of receipts and line items
Easier to review policy compliance details and audit history
Better for expenses requiring calculator or exchange rate verification
Faster navigation between multiple pending approvals
Cloud Deployment Considerations:
Cloud architecture actually improves mobile experience compared to on-prem VPN access. The mobile app connects directly to Azure cloud services with better latency than VPN tunneling. However, attachment storage in Azure blob storage means mobile performance depends on internet connectivity quality.
Optimization Strategies We Implemented:
Receipt Image Compression: Required employees to use mobile app’s built-in photo capture (auto-compresses) rather than uploading high-res scans. Reduced average attachment size from 2MB to 400KB.
Tiered Approval Thresholds:
Under $200, single receipt: Mobile is preferred
$200-$1000, multiple items: Either platform
Over $1000 or international: Desktop recommended
Manager Training: Created 2-minute video showing mobile best practices (approve during downtime, use WiFi for reports with many attachments, desktop for policy questions).
Workflow Configuration: Set mobile notifications for expenses under $500, email summary for higher amounts directing to desktop review.
User Adoption Results:
After setting appropriate expectations:
65% of approvals now happen on mobile (up from 30% initially)
Average approval time dropped from 4.2 days to 1.8 days
Manager satisfaction improved because they choose the right tool for each scenario
Zero complaints about mobile performance once we clarified use cases
Key Insight:
The performance and usability differences aren’t problems to solve - they’re inherent characteristics to leverage appropriately. Mobile excels at quick, routine approvals that keep expense cycles moving. Desktop excels at thorough review of complex or high-value expenses. Cloud deployment makes both options equally reliable and secure, with mobile actually benefiting from direct cloud connectivity.
Stop thinking “mobile versus desktop” and start thinking “mobile for routine, desktop for complex.” Give managers both tools and clear guidance on when each is optimal. Adoption and satisfaction improve dramatically when users aren’t forced into one-size-fits-all approaches.