web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Fixed-Price Projects: sales price, baseline & fee vs on-account transactions

(0) ShareShare
ReportReport
Posted on by 15

Hello, 

We are trying to set up a Fixed-Price project and manage it through its WBS over its complete life-cycle in D365 FinOps "Project Management and Accounting" using PMI's EVM methodology. 

In our case, project's sales price has not a 1:1 relationship with hours/items/expenses, so we don't use these transactions "sales price" to define the project's sales price. My first doubt is:

  1. What transaction type should I use to define the project's sales price? 

Once defined the project's WBS with all its forecasted costs and sales price, I transfer the WBS to O_Forecast and I want to have the project budget's P&L with the estimated sales price, costs and expected margin. To do so, I've used the "Fee transaction" to define the sales price in the O_Forecast model, but I don't fully understand what are the difference between "Fee" and "On-Account" transactions to define the sales prices and the accounting implications. 

If rather than using "Fee" I use "On-Account" transactions to define the project's sales price, I've been unable to get the budget P&L: the system only shows the forecasted costs but not the forecasted revenues (that in this cases equals the project's sales price).

The second doubt I've got is about how to use the WBS, the forecast models and estimates to manage the project using PMI's EVM methodology.

EVM methodology defines basically three inputs to every WBS's Leaf node for managing the project's progress and budget:

AC (Actual Costs): this is obtained automatically by D365 with all the transactions posted against the tasks of the WBS

EV (Earned Value or Progress): this is with respect the project's baseline. In D365 it can be set "manually" at project level but not at task level; although I don't know if there are other ways for setting it.

ETC (Estimate to Complete): estimation of the Project Manager of the remaining costs (hours/items/expenses) up to the end of the project, independently of the project's baseline.

  1. My doubt is how can I define the EV/ETC of each Leaf Node (using Forecasts and/or Estimates?) for managing the Fixed-Price project over its complete life-cycle.

Thanks a lot for your help!

I have the same question (0)
  • Suggested answer
    Ludwig Reinhard Profile Picture
    Microsoft Employee on at

    Hello Hector,

    For no 1:

    "Fee" and "On-Account" are two different transaction types.

    Fee related postings can be made to create an invoice to a customer that gets the fee posted invoiced.

    This is usually not needed for fix price projects where you invoice on-account transactions. .

    So, what the customer get's invoiced are 'on-accounts'

    For no 1.a: On accounts & P&L:

    On account transactions are related to balance sheet transactions.

    That is they are cash related and don't have an impact on your profitability.

    That's why they don't appear in your P&L

    The profit in a fix price project is made of the costs that you post and the revenue accruals that are posted with the so-called project estimate functionality.

    For no 2: EVM

    D365FO does not have a EVM module or a special functionality included.

    It is somehow a bit hidden.

    What you get when you calculate the project estimate is a POC that is usually on a cost-by-cost basis.

    That is forecast vs. actual costs gives you the POC.

    The POC is then used to accrue the revenue based on the on-account amounts that you have recorded.

    If this calculation of the 'value earned' is not sufficient then you can tweak the standard functionalities in a way that you make use of different forecast models that you use for the cost comparison that ultimately gives you the POC and the revenue accrued. I put an example on my blog and in my book that illustrates what you can do in this respect in the standard application.

    Best regards,

    Ludwig

  • HectorM Profile Picture
    15 on at

    Hi Ludwig,

    Thanks a lot for your explanation.

    What I'm still struggling with D365 on Fixed-Price projects is how to set the project's price, how to see it quickly, and how to get the original estimated margin based on the cost structure set on the project's WBS. Especially if we don't use the Project Quotations.

    Héctor

  • Suggested answer
    Ludwig Reinhard Profile Picture
    Microsoft Employee on at

    Hello Hector,

    Well, to see the profitability quickly you can use e.g. the tracking views, which has a kind of EVM like structure.

    What is missing there though is the revenue side. This is something that might need adjustments. 

    Alternatively, you can make us of the project statements control form. 

    if those forms don't help then use PowerBI to extract and structure the data in the way you want to report. 

    Most of the time we use PowerBI because the standard forms are currently 'not perfect'. 

    Best regards, 

    Ludwig

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 646 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 529 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 285 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans