BeyondERP.Newsletter
Menu

Setup step on the Mass termination table clean up page · Subscription billing

Set how long mass termination records are kept

Delete old staging records without losing ones still in use.

Business process
Bill subscriptions
Menu item
SubBillMassTerminationTableCleanupBatchProcessing
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 batch job that deletes the records left in the mass termination tables after the mass termination data entity has been used to change terminations in bulk.
What you do hereUse this page to keep the mass termination tables small by deleting their records older than the number of days or months you enter.
ExampleFor example, BEAT runs it monthly with Days and 30, so mass termination records more than 30 days old are deleted once each bulk change has been processed.
Mass termination table clean up 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 accounts receivable › Bill subscriptions
Menu pathSubscription billing › Recurring contract billing › Periodic tasks › Mass termination table clean up
Set up firstMass termination processing Microsoft Learn
Used next byGenerate invoice batch jobs Microsoft Learn
Related pagesMass termination processing Microsoft Learn
In this process Choose the termination type and credit · Archive only finished terminated schedules
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 itAfter mass terminations imported through the mass termination entity are fully processed.
How oftenOn demand after mass termination imports, or as a recurring batch job.
Batch settingsBatch processing is Yes by default; schedule it as a recurring background job so the staging tables don't grow.
What the output showsMass termination table records older than the period you entered are cleared. Billing schedules and their terminations aren't affected.

Source: Microsoft Learn

Setup steps on this page

Set how long mass termination records are kept

Delete old staging records without losing ones still in use.

Steps from Microsoft

  1. Go to Subscription billing > Recurring contract billing > Periodic tasks > Mass termination table clean up.
  2. Under Parameters, choose Days or Months and enter the Number of days or months, which sets how old the mass termination records must be before they are cleared.
  3. Use a period long enough that terminations still in progress through the mass termination entity aren't cleared.
  4. After the run, confirm that the old mass termination records are gone and new imports through the entity still work.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExample
Select by days or monthsWhether the age of the records is counted in days or months.Checked in Dynamics 365Days
Number of days or monthsHow old the mass termination records must be before they are deleted.Checked in Dynamics 36530
Batch processingYes by default, so the clean up runs in the background.Checked in Dynamics 365Yes

Common errors and fixes

MessageWhat to do
A bulk termination change loses its records before it is processedUse a number of days or months longer than the time between importing and processing, so records still in use aren't deleted. Microsoft Learn

Test checklist

  1. Change terminations in bulk through the mass termination data entity and process them.
  2. Run the clean up with Days and 0.
  3. Check the processed records are gone from the mass termination tables.
  4. Check the billing schedules themselves are unchanged.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Set how long mass termination records are keptA recurring monthly batch job with an age of at least 30 days.The job deletes records older than the age you set; a short age can delete records of a bulk import that hasn't been processed.How long are mass termination records kept?Running it with 0 right after an import, before the terminations are processed.Test: Only old records are deleted

Feature management and licence

Feature to turn onSubscription billing (Must be on)Recurring contract billing (Must be on)
Licence or add-inTurn off the Revenue recognition feature first: Subscription billing can't be used while it is on. Then, in Feature management, turn on Subscription billing and after it Recurring contract billing. Revenue recognition was deprecated in January 2024 and replaced by Subscription billing. Subscription billing managers run this task.

Microsoft Learn

Solution architect

5Design impact

Can it be undoneIrreversible: Deleted mass termination records can't be restored; the billing schedules aren't changed.
If you change it laterDeletes records from the mass termination tables; terminated billing schedules stay as they are. Microsoft Learn
Technical architect

6Technical

Menu itemSubBillMassTerminationTableCleanupBatchProcessing Checked in Dynamics 365
FormSysOperationTemplateForm Checked in Dynamics 365
Roles to set it up and use itTo use itSubscription billing manager SubBillBillingMaintainSubscription billing allocation, deferral, and billing manager SubBillMaintainGive people one of these roles. On this system, 2 roles can run this page.Checked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=SubBillMassTerminationTableCleanupBatchProcessing
Data migrationLoad order: Mass termination table clean up has no data entity in Data management, so there is nothing to load from a file or a configuration template. It deletes staging records only; set up its recurring batch job in each environment.Microsoft Learn
Everyone

8Sources

To cite this step: SB-PER-070, Set how long mass termination records are kept. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/SB-PER-070