BeyondERP.Newsletter
Menu

Setup step on the Delete revenue recognition page · Project management and accounting

Delete wrongly created revenue recognition

Remove a period created with wrong settings.

Business process
Manage project financials
Menu item
action:ProjControlPeriod_DeleteV2
Setup steps
1 on this page
Show what matters for
SETUP GUIDEHow to set it up8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA periodic job that deletes the revenue recognition records of a period code and date, and optionally the forecast created with them, so the period can be created again.
What you do hereUse it when a period's records were created with the wrong settings, such as the wrong date, cost to complete method or forecast model. Posted periods are corrected with Reverse revenue recognition, not deleted.
ExampleBEAT created October 2026 revenue recognition for period code MONTH with forecast model FC-2025 by mistake. Before anything is posted, the project accountant deletes the 14 records for 10/31/2026 with Delete forecast on, then creates them again with FC-2026.
Delete revenue recognition page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

Business processManage project financials
Menu pathProject management and accounting › Periodic › Revenue recognition › Delete revenue recognition
Set up firstRevenue recognition inquiry Microsoft Learn
Used next byCreate revenue recognition Microsoft Learn
Related pagesReverse revenue recognition (for posted periods) Microsoft Learn
In this process Set up Indirect cost component groups · Set up Indirect cost component group assignment rules
End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

When to run it

When to run itOnly when a period's records were created with wrong settings and aren't posted yet.
How oftenOn demand.
Batch settingsRun in the background if many projects are involved.
What the output showsThe records for the period code and date are removed, with their forecast when Delete forecast is on.

Source: Microsoft Learn

Setup steps on this page

Delete wrongly created revenue recognition

Remove a period created with wrong settings.

Steps from Microsoft

  1. Go to Project management and accounting > Periodic > Revenue recognition > Delete revenue recognition.
  2. Open the Revenue recognition inquiry first and check that the period you will delete isn't posted.
  3. On the General tab, choose the Period code and the Revenue recognition date.
  4. Turn on Delete forecast only if the forecast created with the revenue recognition must go too, and filter on the projects to clean up.
  5. Run the job, check the inquiry, then create revenue recognition for the period again.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExample
Period codeThe period code of the records to delete.Checked in Dynamics 365
Revenue recognition dateThe date of the records to delete; it follows the period code.Checked in Dynamics 36510/31/2026
Delete forecastWhen on, the forecast created with the revenue recognition is deleted too.Checked in Dynamics 365Yes
Show InfologShows messages about the processed projects.Checked in Dynamics 365Yes

Common errors and fixes

MessageWhat to do
A posted period must be corrected.Don't delete it: use Reverse revenue recognition, then create and post again; later periods must be reversed too. Microsoft Learn

Test checklist

  1. Check in the inquiry that October 2026 is Created, not Posted.
  2. Delete records for MONTH, 10/31/2026.
  3. The inquiry shows no October records for those projects.
  4. Create them again and check 14 records exist.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Delete wrongly created revenue recognitionDelete only unposted periods, filtered on the affected projects; leave Delete forecast off unless the forecast was created with the wrong model.Posted periods need a reversal; deleting the forecast changes forecast-based reports.Delete or reverse?Deleting when the period should be reversed, or deleting the forecast without need.Test: Delete an unposted period

Feature management and licence

Licence or add-inOn the live system, Project manager uses this page.

Checked in Dynamics 365

Solution architect

5Design impact

Shared or per companyPer company: it deletes the revenue recognition records of the legal entity you run it in. Microsoft data model
Can it be undoneIrreversible: Deleted records can't be restored; recreate them.
If you change it laterDeletes the period's revenue recognition records and, with Delete forecast on, the forecast created with them; the period must be created again before it can be posted. Microsoft Learn
Technical architect

6Technical

Menu itemaction:ProjControlPeriod_DeleteV2 Checked in Dynamics 365
FormProjControlPeriod_Delete Checked in Dynamics 365
Roles to set it up and use itTo use itProject manager ProjProjectManagerGive people one of these roles. On this system, 1 role can run this page.Checked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=action:ProjControlPeriod_DeleteV2
Data migrationLoad order: Delete revenue recognition has no data entity in Data management, and the revenue recognition period table (ProjControlPeriodTable) has none either. Migrate WIP and accrual balances, then create revenue recognition in the target system from the first open period.Microsoft data model
Everyone

8Sources

To cite this step: PM-JOB-270, Delete wrongly created revenue recognition. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/PM-JOB-270