Share
Report
14We currently use the standard Recurring Sales Lines feature (via Report 172 – Create Recurring Sales Invoices, run through a Job Queue Entry) to generate recurring invoices for a customer.
The issue: the Order Date and Posting Date are saved as fixed values on the report's request page parameters. Every time the job runs, it reuses the same dates from when it was originally set up — it doesn't automatically advance to the current period. So each month, someone has to manually go into the Job Queue Entry, put it on hold, open the Report Request Page, update both dates, and reactivate it.
My question: Is Subscription Billing (the Microsoft first-party app) a better solution for this specific problem? My understanding is that it calculates Posting Date/billing period automatically based on the contract's Billing Rhythm, rather than requiring a manually saved static date each cycle.
Specifically:
Does Subscription Billing actually auto-advance the billing period/dates each run without manual intervention?
Is there still a way to manually override the date for a specific run if needed (e.g., a one-off exception)?
Are there any migration considerations moving from Recurring Sales Lines to Subscription Billing for an existing customer relationship?
All responses (
Answers (
