Subscription Backdating

Subscription backdating allows you to create a Subscription with a start date in the past. This is helpful when you need to align billing with an earlier service date or correct a delayed entry.

What Is Subscription Backdating?

Subscription backdating begins on a date that is earlier than the day it is created. This allows you to accurately reflect a Customer’s billing timeline, especially in scenarios such as:

• The Customer had access to the Plan or service before completing a formal signup.
• You are migrating Subscriptions from another system and need to honor historical start dates.

When backdating Subscriptions, here are a few things to keep in mind:

• You can only backdate a Subscription by one billing period (for example, one month for monthly billing).
• You cannot backdate a Subscription earlier than your configured lock or close date.
• If no lock or close dates are defined, the backdate must fall within the previous billing period.
• If a backdated Subscription is created with automatic payment enabled, and the payment attempt fails, the Subscription will still be created and immediately enter dunning.
• Even if a Subscription is backdated, the first invoice date will always be today's date.
• You cannot create a backdated Subscription within a Subscription group.

Enabling Subscription Backdating

To enable Subscription backdating, you must configure the appropriate settings in your site.

1. Turn On Dynamic Subscription Creation

   Your site must have Dynamic Subscription Creation enabled to support backdated start dates.

2. Set Lock and Close Dates (Optional)

   Lock and close dates control how far back a Subscription can begin. If you don't define these dates, the system automatically figures out the earliest allowed start date. It uses a default window of one billing period, but it also considers:

   • Plan Trials
     The trial duration gets subtracted from the default window.
   • Product Billing Intervals 
     Any Product-specific billing periods are factored into the calculation.

3. Consider Order Date Constraints

   The Order Date must fall within the lock date and Subscription start date range. It automatically updates if you change the Subscription start date.

Backdating Restrictions

Manage Subscription backdating with Transaction Lock and billing period boundaries to maintain financial data integrity and ensure reporting accuracy. Merchants can use this automated validation to prevent accidental backdating into closed financial periods or across billing boundaries.

How Backdating Restrictions Work

When editing a Subscription and choosing a past effective date, the system validates the date against two separate boundaries:

• The Transaction Lock Date configured for your Site.
• The most recent start date of the current billing period for the Subscription.

The datepicker disables and prevents the selection of any date that falls before whichever of these two dates is more recent. This ensures that Subscription changes cannot be backdated into closed periods or across restricted billing boundaries.

To apply a Past Effective Date to a Subscription:

1. Navigate to the Subscriptions list and select the Subscription you wish to edit.
2. Click Edit Subscription.
3. In the Effective Date section, select Past Date.

4. Use the datepicker to choose your desired date.

   Dates earlier than your Transaction Lock Date or the current billing period start will be unavailable for selection.

5. Complete your changes and click Save.

Controlling Dunning Behavior

You can control whether backdated Subscriptions trigger dunning (collections) processes. This determines whether customers receive notifications about unpaid balances from prior billing periods.

Enable dunning if you want the system to automatically pursue collections and send reminder emails for any past-due amounts.

Disable it if the backdating is used for internal adjustments or data clean-up and you do not intend to collect outstanding payments.

To avoid triggering dunning in these scenarios, either disable dunning for the Subscription or use a manual payment method during creation.

Impact on Invoicing and Reporting

Subscription backdating can affect how your system handles invoices, revenue reporting, and recognition. Consider the following:

• Invoice Generation
  Invoices may be issued immediately to reflect the retroactive start.
• Revenue Recognition
  Revenue is recognized from the historical start date, which impacts revenue schedules and accounting reports.
• Automated Adjustments
  Revenue recognition timelines are recalculated to align with the backdated timeline.

Troubleshooting and Best Practices

Here are some common errors you might encounter:

• The selected start date is earlier than your lock or close date.
• Backdating exceeds the allowed billing period range.
• Dunning is unintentionally triggered.

For best results, consider these practices:

• Review your site’s lock and close settings before backdating a Subscription.
• Avoid backdating Subscriptions that belong to Subscription groups.
• Turn off dunning when retroactively entering a Subscription that should not initiate collections.
• Communicate with your billing or finance team before creating backdated entries to avoid confusion in reporting.
• Use monthly billing if you require calendar billing.
• Toggle Evergreen status carefully, if future billing behavior is critical.
• Keep the live preview open for visibility into how your changes affect billing.