Personalized Community is here!
Quickly customize your community to find the content you seek.
Automatic Update Policy for Project Service
The Project Service (PS) solution will enable system-driven, automatic updates, in alignment with other Microsoft announcements that have highlighted the improved update process for Dynamics 365.
Learn more about Automatic Update Policy
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Tested on:Dynamics 365 version 9.0
I have previously written about how Actuals are formed in Dynamics 365 Project Service Automation. This blog post will explain some of the most relevant fields of the Actual entity so that it's easier to identify what the status on an Actual is. The point of this post is not to list every single field but to point out fields that in my opinion need additional clarification for analyzing Actuals. I want to strongly emphasize that Actuals are sacred. They are a central and key component of PSA. One of the most vital goals of implementing and using PSA should be that Actuals are created according to needs driven by your business. As Actuals are the key financial data PSA produces, you will want to make sure everything is just right so that your customers are getting correct invoices.
Created On, createdonDate and time when the record was created. Very useful when filtering Actuals.
Accounting Date, msdyn_accountingdateWhen an invoice is confirmed, the resulting Billed Sales and reversed Unbilled Sales Actuals will have an Accounting Date that matches the date the invoice was confirmed on. The original Unbilled Sales and Cost Actuals will have an Accounting Date that matches the date of the related Time Entry.
Adjustment Status ID, msdyn_adjustmentstatusShows the Adjustment Status ID of the transaction. Applies to invoices when they are corrected.
Billing status ID, msdyn_billingstatusThis field is one of the most important fields of the Actual entity. The field indicates whether an Actual is on an invoice, not on an invoice or on a confirmed invoice. The field is important especially for reporting purposes.
Data from an Unbilled Sales Actual set to Canceled is not pulled on an Invoice Line Detail when an invoice is created.
If the Billing status ID field of an Unbilled Sales Actual is empty, a matching Invoice Line Detail does not exist. The field's value is empty when a Time Entry has been approved but has not yet been invoiced.
Billing type ID, msdyn_billingtypeBilling type ID indicates if an Actual is Chargeable, Non Chargeable or Complimentary.
Document Date, msdyn_documentdateTransaction date of the related business event. For example the date of a Time or Expense Entry.
External Reference Date, msdyn_externalreferencedateStores a date from an external system, such as a journal entry voucher date from an ERP system.
External Reference ID, msdyn_externalreferenceidStores an ID from an external system, such as a journal entry voucher date from an ERP system.
Transaction Class, msdyn_transactionclassificationShows the transaction classification of a transaction.
Transaction Type, msdyn_transactiontypecode
Describes a transaction's type.
I hope these article allows you to leverage Actuals in Dynamics 365 Project Service Automation so that the financial data PSA produces is more accurate. For a complete list of fields for the Actual entity, see docs.microsoft.com here.
Disclaimer: All my blog posts reflect my personal opinions and findings unless otherwise stated.
Edits:June 7th 2018. Corrected Transaction Class of Tax.June 17th 2018. Billing type ID was incorrectly referenced as Billing status ID.
Business Applications communities