Recurring Billing Restructure
The Recurring Billing Issue has been a long-standing problem wherein the child invoice generated keeps on referencing the parent invoice - or the first invoice in the recurring billing line. This update aims to create a more consistent, reliable, and error-free billing process across all service agreement and recurring invoice scenarios.
This ensures that recurring invoices are treated as independent, stable entities, unaffected by unrelated record changes. It also aligns billing behavior across monthly, quarterly, and annual cycles - whether or not auto-renew is enabled.
Key Changes:
This update introduces key behavioral changes and standardizations to ensure predictable billing outcomes:
Future Invoice Numbers:
There is no more future invoice number generated or displayed in the Upcoming Recurring Billing Report until the Next Billing Date, when the recurring invoice is actually created.Recurring Invoice Independence:
Recurring invoices are now treated as standalone schedules. Changes to the parent/original invoice or last generated invoice will no longer affect future recurring invoices.Stable Auto-Renewal Logic:
Only two Service Agreement changes can affect recurring billing:When Service Agreement Pricing is set to "Use Current Price" and the price changes, so the new price takes effect upon auto-renew.
When Auto-Renew flag is removed wherein billing will still complete to the End of its term but will no longer auto-renew after the term.
Stable Deletion Logic:
Users must delete associated recurring invoices before canceling a service agreement.Frequency Handling:
Monthly, quarterly, and annual recurring billings now follow consistent start, renewal, and end-date rules, eliminating discrepancies between term lengths.
Screenshots
Future Invoice Numbers Removed
Notes:
All recurring billing types - monthly, quarterly, annual, with or without auto-renew - now follow unified rules for creation, modification, and cancellation.
Recurring invoices remain unaffected by edits to parent invoices or service agreements once created.
While backend logic has been standardized, user-facing processes remain familiar for a smooth transition.
Comments
0 comments
Please sign in to leave a comment.