Skip to main content

Best practices for Delete job in a Zuora Tenant


Best practices for Delete job in a Zuora Tenant

  • Before attempting a mass deletion, ensure to create a backup of the data you intend to delete. This ensures that you have a copy of the data in case you need to recover it later.

  • Attempt record deletions in a sandbox or test environment initially to verify the process and its effect without impacting your production data.

  • Begin by deleting a small batch of records to ensure that the deletion process works as expected and to identify any issues early. 

  • When performing delete actions, it's crucial to ensure that the correct field from the source file is accurately mapped to the record ID in the target, Zuora tenant. The record ID is a unique identifier assigned to each record in the target system, and it is essential for accurately identifying and deleting the intended records.

  • Data Loader current functionality includes support for delete action at the Billing API level. Consider any potential dependencies that the records may have. Deleting records with dependencies could have other data in the Zuora tenant. 

  • Standalone Invoices can only be deleted if they are in the Draft State.

  • When you delete Accounting Periods, you may not be able to get the direct successful records file. A quick workaround would be to reverse the order, where recent accounting period IDs need to be placed first and uploaded for delete. 

  • Accounting Codes must be in inactive status for deletion.

  • Account deletion is an asynchronous process. For account deletion, the system will start a backend job to remove all transactions under the accounts and change the status of the accounts to 'Cancelled'. This backend job is asynchronous and will take some time, depending on the job size.

  •  An account cannot be deleted when,

  1. The account is either the invoice owner or the subscription owner of a subscription

  2. The subscription's invoice owner and subscription owner are two different accounts. 

  • However, there is an exception to this limitation. Simply set the ‘Enable Force Deletion for Account?’ setting to Yes. This will force delete an account that is the subscription owner of a subscription while the invoice owner is a different account. Force deleting this account deletes all its subscriptions, but the relevant invoices will not be impacted.
  • An account cannot be deleted if it has ever been involved in an Owner Transfer amendment or order action, either as the current owner or as the previous owner.