When the Pricing API Changes, Does Your Project Billing Still Calculate Correctly?
Wave 1 2026 changes the pricing API and timesheet framework in D365 F&O. For professional services firms, that means the logic behind your project billing, revenue recognition and resource allocation needs validation - before a client invoice tells you something went wrong.
Wave 1 2026 - What It Means for Professional Services D365 Environments
Wave 1 2026 brings changes to the pricing API, journal framework and Project Operations module in D365 F&O. For professional services firms, these updates directly touch the workflows that calculate client billing, recognise revenue and validate timesheet data.
Pricing API Changes
The updated pricing API requires validation against your project billing rules, milestone structures and time-and-materials rate cards - before it reaches your billing cycle.
Journal Framework Updates
Changes to how D365 handles journal entries affect GL posting accuracy across multi-entity professional services structures and your period-close workflows.
Project Operations Module
Wave 1 updates to Project Operations touch resource booking, WBS validation and project cost tracking - all need regression testing against your specific project configuration.
Timesheet & Expense Framework
Updated timesheet logic needs testing against your custom approval workflows and client billing integrations before it affects an invoice.
The D365 F&O Risks Specific to Professional Services
These are the specific patterns we see in professional services D365 environments - before and after every Wave release.
Revenue Recognition After a Wave Update
ASC 606 and IFRS 15 compliance depends on D365 configuration being correct after every update. Wave changes to the pricing API or journal framework can silently alter how revenue recognition schedules behave - creating compliance risk without any visible alert.
- Revenue recognition schedule regression
- ASC 606 / IFRS 15 configuration testing
- Milestone billing rule validation
- Project financial close testing
Client Billing Logic Built on Customisations
Your billing engine is not vanilla D365. Time-and-materials rate cards, fixed-fee milestone rules and client-specific billing structures are configured logic. The Wave 1 pricing API update needs testing against every custom billing rule in production.
- Custom billing rule regression
- T&M and fixed-fee validation
- Invoice calculation accuracy
- Credit note and adjustment testing
Timesheet and Approval Workflows
Custom timesheet approval hierarchies, expense routing and resource booking logic are built on top of D365 Project Operations. Each Wave release puts that configuration at risk - and client billing deadlines expose it hardest.
- Timesheet approval workflow regression
- Expense routing validation
- Resource booking logic testing
- Billable vs non-billable classification
Multi-Entity Financial Close
Professional services firms often operate across multiple legal entities with intercompany billing. Wave updates to the journal framework can disrupt the exact GL posting behaviour that your period-close and consolidation depends on.
- Intercompany billing regression
- Multi-entity consolidation testing
- GL posting accuracy post-Wave
- Period-close workflow validation
What We Test in Your D365 F&O Professional Services Environment
Built from real D365 Project Operations workflows - covering the billing, revenue and approval logic your finance and delivery teams depend on.
- Revenue recognition (ASC 606/IFRS 15)
- Milestone billing regression
- T&M rate card validation
- Invoice accuracy testing
- Credit note processing
- WBS validation and project budgets
- Resource booking workflows
- Project cost tracking
- Timesheet approval flows
- Expense routing regression
- GL posting accuracy post-Wave
- Intercompany billing testing
- Multi-entity consolidation
- Period-close workflows
- Currency revaluation testing
- CRM to D365 billing sync
- Pricing API compatibility (Wave 1)
- Custom approval workflow regression
- Azure DevOps CI/CD pipeline
- Opkey automated flow coverage
How Crestech Approaches D365 QA for Professional Services
A billing-first approach - built around your client invoice cycle and Microsoft's release calendar.
Pre-Wave Billing Impact Map
Before each release we map which Wave 1 changes touch your project billing, revenue recognition and timesheet workflows - so you know exactly where your configuration is exposed before testing starts.
Billing-First Test Execution
We prioritise the workflows that drive client revenue - project billing, milestone recognition and timesheet processing - because a billing error in production has immediate client-facing consequences.
Compliance Configuration Validation
We validate your ASC 606 and IFRS 15 configurations after every Wave update - not just on first go-live. Revenue recognition rules need re-confirming every time the underlying journal framework changes.
Continuous Release Confidence
Opkey automation covers your repeatable billing and approval flows. Your team receives a clear report showing what passed, what needs attention and what changed between releases.
Why Professional Services D365 Teams Bring Crestech In
Our functional team includes specialists who understand D365 Project Operations the way your finance and delivery teams do - not just the way an IT team does. That matters when you are testing billing logic, not just button clicks.
We Understand Project Billing in D365
Our functional experts know the difference between a standard D365 billing workflow and a customised one. We test the logic behind your revenue - not just whether the screen loads.
Opkey Automation for Project Operations
We run automated regression on your repeatable billing, timesheet and approval flows using Opkey - integrated into Azure DevOps for continuous coverage across every Wave release.
Compliance Is Part of Every Test Cycle
We treat ASC 606 and IFRS 15 configuration as regression test items - not assumptions. Every Wave update that touches the journal or pricing framework triggers a compliance configuration check.
Request a D365 QA Health Check
Tell us about your professional services D365 environment. Our specialists will identify your highest-risk gaps before your next Wave release.
Wave 1 Has Changed the Pricing API. Has Anyone Tested Your Project Billing Since?
Our D365 specialists will review your professional services environment and identify your billing, revenue recognition and approval workflow risks - before your next client invoice cycle.
Talk to a D365 QA ExpertD365 Insights for Manufacturing
Published by Crestech's D365 QA specialists - observations from real environments, not theoretical guides.
Most D365 Regression Suites Are Growing. Very Few Are Becoming Smarter. Read more →
Your D365 Passed UAT. It Will Still Break in Production. Here's Why. Read more →
