Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
we're evaluating PSA atm, and while most things look great, I've stumbled upon an issues that troubles me. I'd like to ask for recommendations how to best handle this or the desired behavior can be customized by an expert/psa consultant with reasonable amount of effort. Thanks
- Our sales people usually contract projects with multiple order lines, each line being fixed price (usually). For simplicity you may think of them as different phases of a project that are quoted seperately but in one project contract.
- Invoicing/ invoice plans however should be for the contract as a whole. Also the project management / WBS hast to be a single project entity for all phases.
How would you best handle this situation?
As far as I could find out it is not possible to link one project to multiple contract lines - which I would have thought as a solution.
Hi. Indeed the official limitation with Projects per Billing Method is as follows:
"The combination of project and transaction classes of time, expense, and fee that are associated with a quote line or contract line must be unique. If the same association of project and transaction class is used on more than one contract line or quote line, project service automation will not work correctly."
Would this, however, solve your problem:- Create a Fixed Price Order Line- Create Project Contract Line Details for each respective phase- When invoiced, the total contracted amount for an Order Line will be pulled on an invoice based on set Invoice Schedules (Periodic Milestones)
Order Line with Project Contract Line Details. Note the Contracted Amount.
Four Periodic Milestones. As the Contracted Amount was 2000, the amount per Milestone is 500. You can add/remove Milestones.
thank you very much for your response and thoughts.
This might be an option. However, In our case it has one significant drawback.
- We charge fixed prices for every phase (which would be line details in this solution). To my knowledge, line details can only be time & expenses though. Which leads to three problems
--- I can only select one role / task per phase and not multiple ones (i.e. 10h PM, 10h analyst ...)
--- I cannot report project progress / cost vs. the fixed price as the detail line will change according to planned and actual project progress
--- The sales team cannot track progress and profitability on a per phase level on the order/contract entity
correct? Or am I missing something?
Ok, would the following work:- Create a Fixed Price line that has Include Time/Expense/Fee all set to Yes.- Import your WBS to Project Contract Line Details.- Create an on-demand Periodic Milestone for the specific task that you want to invoice and then invoice it. You can associate the Milestone with a Project Task.- Users can submit Time Entries normally against the tasks they have worked on. As this is a FP Order Line, only Cost Actuals are formed. This way the cost incurred on the Project Contract increases and you can analyze profitability.
Here are the Project Contract Line Details. Imported from a Project WBS.
Here are 2 milestones which I have invoiced on-demand. They are associated with related Project Tasks.
This is after an approved Time Entry. See how the Time Entries impact Cost Incurred to Date.
Here are the Actuals.
thank you again for your answer and time.
I guess this will do. It's still not optimal as it requires the sales team to create a single order line in the opportunity and work with detail lines. From their user experience perspective this is a bit complicated.
Also when using the detail lines for our phases we need to use a mixed price/cost list for these lines as we cannot specify a single role for the phases and the sales team is used to only think is price for phases not for single roles.
As I said - it will do and maybe the sales team can adopt to a new process, thinking in roles/time needed instead of fixed price for phases (where pricing is based on "sales teams experience").
I will try talk to a consultant if we can customize something to make it easer but it will do.
For invoicing Fixed Price projects the line details are something we can't escape if we want to do a granular listing of that we have on an order line. However as to the roles. Does cost differ based on a person or is your cost price the same for everyone?
If it's the same for everyone, you could simply create a role called "Fixed Price Projects" and instruct users to submit time against that role. You can also mark that role for every task.
If the cost price varies (John costs X while Jim costs Y), you could still use a single role but differentiate the cost with pricing dimensions, starting a few weeks from now with the general availability of V3 of PSA on the Unified Client Interface. Please see the Spring '18 release notes for more information. A single task can also have several roles and as each role can have its own cost price, you can incur cost on a task based on roles on task (image below).
"To maximize flexibility to meet different business requirements, the updated Project Service solution supports discrete application of pricing dimension sets to cost and bill rates. Dimension values can be set as the default and propagated across the costing and pricing process from resource profiling to time entry to project actuals. Customer-specific configuration and modification or extension leverages standard Dynamics 365 customizability infrastructure."
Yes the cost differs on role level and ideally also on a per person level.
I found your other post concering PSA V3/ UCI and multidimensional pricing. It was very helpful - thanks - and looks like a good solution for our case.
Business Applications communities