Details
-
Type:
Improvement
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: Short Term
-
Component/s: None
-
Labels:None
Description
Someone had brought up the fact that when the cron does not run every day, and Blesta back-bills for service renewals, these service renewals still get added to a single invoice.
An invoice should be due when the service renews. This means we can only group services onto a single invoice if they all renew on the same day. In the case of back-billing old services, it's possible that all of the old services and all of the current renewals get added to a single invoice that is due today.
Consider that the cron did not run in a week and the following services need to be renewed for a single client:
Today: 2017-02-15
Invoice Days Before Renewal: 1
| Service Renew Date | Expected Invoice Due Date | Actual Invoice Due Date | Invoice Due Date if Cron Ran Every Day |
|---|---|---|---|
| 2017-02-10 | 2017-02-15 | 2017-02-15 | 2017-02-10 |
| 2017-02-13 | 2017-02-15 | 2017-02-15 | 2017-02-13 |
| 2017-02-15 | 2017-02-15 | 2017-02-15 | 2017-02-15 |
| 2017-02-16 | 2017-02-16 | 2017-02-15 | 2017-02-16 |
The incorrect date is highlighted in bold.
Thus, in the case of back-billing service renewals, missed services can cause some services to be due today, or on the first service's renew date, rather than the renew date of the specified service.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
Someone had brought up the fact that when the cron does not run every day, and Blesta back-bills for service renewals, these service renewals still get added to a single invoice.
An invoice should be due when the service renews. This means we can only group services onto a single invoice if they all renew on the same day. In the case of back-billing old services, it's possible that all of the old services and all of the current renewals get added to a single invoice that is due today. Consider that the cron did not run in a week and the following services need to be renewed: *Today: 2017-02-15* ||Invoice Days Before Renewal||Service Renew Date||Expected Invoice Due Date||Actual Invoice Due Date||Invoice Due Date if Cron Ran Every Day|| |1|2017-02-10|2017-02-15|2017-02-15|2017-02-11| |1|2017-02-13|2017-02-15|2017-02-15|2017-02-14| |1|2017-02-15|*2017-02-16*|*2017-02-15*|2017-02-16| Thus, in the case of back-billing service renewals, missed services can cause some services to be due today, or on the first service's renew date, rather than the renew date of the specified service. |
Someone had brought up the fact that when the cron does not run every day, and Blesta back-bills for service renewals, these service renewals still get added to a single invoice.
An invoice should be due when the service renews. This means we can only group services onto a single invoice if they all renew on the same day. In the case of back-billing old services, it's possible that all of the old services and all of the current renewals get added to a single invoice that is due today. Consider that the cron did not run in a week and the following services need to be renewed for a single client: *Today: 2017-02-15* ||Invoice Days Before Renewal||Service Renew Date||Expected Invoice Due Date||Actual Invoice Due Date||Invoice Due Date if Cron Ran Every Day|| |1|2017-02-10|2017-02-15|2017-02-15|2017-02-11| |1|2017-02-13|2017-02-15|2017-02-15|2017-02-14| |1|2017-02-15|*2017-02-16*|*2017-02-15*|2017-02-16| Thus, in the case of back-billing service renewals, missed services can cause some services to be due today, or on the first service's renew date, rather than the renew date of the specified service. |
| Description |
Someone had brought up the fact that when the cron does not run every day, and Blesta back-bills for service renewals, these service renewals still get added to a single invoice.
An invoice should be due when the service renews. This means we can only group services onto a single invoice if they all renew on the same day. In the case of back-billing old services, it's possible that all of the old services and all of the current renewals get added to a single invoice that is due today. Consider that the cron did not run in a week and the following services need to be renewed for a single client: *Today: 2017-02-15* ||Invoice Days Before Renewal||Service Renew Date||Expected Invoice Due Date||Actual Invoice Due Date||Invoice Due Date if Cron Ran Every Day|| |1|2017-02-10|2017-02-15|2017-02-15|2017-02-11| |1|2017-02-13|2017-02-15|2017-02-15|2017-02-14| |1|2017-02-15|*2017-02-16*|*2017-02-15*|2017-02-16| Thus, in the case of back-billing service renewals, missed services can cause some services to be due today, or on the first service's renew date, rather than the renew date of the specified service. |
Someone had brought up the fact that when the cron does not run every day, and Blesta back-bills for service renewals, these service renewals still get added to a single invoice.
An invoice should be due when the service renews. This means we can only group services onto a single invoice if they all renew on the same day. In the case of back-billing old services, it's possible that all of the old services and all of the current renewals get added to a single invoice that is due today. Consider that the cron did not run in a week and the following services need to be renewed for a single client: *Today: 2017-02-15* ||Invoice Days Before Renewal||Service Renew Date||Expected Invoice Due Date||Actual Invoice Due Date||Invoice Due Date if Cron Ran Every Day|| |1|2017-02-10|2017-02-15|2017-02-15|2017-02-10| |1|2017-02-13|2017-02-15|2017-02-15|2017-02-13| |1|2017-02-15|2017-02-15|2017-02-15|2017-02-15| |1|2017-02-16|*2017-02-16*|*2017-02-15*|2017-02-16| Thus, in the case of back-billing service renewals, missed services can cause some services to be due today, or on the first service's renew date, rather than the renew date of the specified service. |
| Description |
Someone had brought up the fact that when the cron does not run every day, and Blesta back-bills for service renewals, these service renewals still get added to a single invoice.
An invoice should be due when the service renews. This means we can only group services onto a single invoice if they all renew on the same day. In the case of back-billing old services, it's possible that all of the old services and all of the current renewals get added to a single invoice that is due today. Consider that the cron did not run in a week and the following services need to be renewed for a single client: *Today: 2017-02-15* ||Invoice Days Before Renewal||Service Renew Date||Expected Invoice Due Date||Actual Invoice Due Date||Invoice Due Date if Cron Ran Every Day|| |1|2017-02-10|2017-02-15|2017-02-15|2017-02-10| |1|2017-02-13|2017-02-15|2017-02-15|2017-02-13| |1|2017-02-15|2017-02-15|2017-02-15|2017-02-15| |1|2017-02-16|*2017-02-16*|*2017-02-15*|2017-02-16| Thus, in the case of back-billing service renewals, missed services can cause some services to be due today, or on the first service's renew date, rather than the renew date of the specified service. |
Someone had brought up the fact that when the cron does not run every day, and Blesta back-bills for service renewals, these service renewals still get added to a single invoice.
An invoice should be due when the service renews. This means we can only group services onto a single invoice if they all renew on the same day. In the case of back-billing old services, it's possible that all of the old services and all of the current renewals get added to a single invoice that is due today. Consider that the cron did not run in a week and the following services need to be renewed for a single client: *Today: 2017-02-15* ||Invoice Days Before Renewal||Service Renew Date||Expected Invoice Due Date||Actual Invoice Due Date||Invoice Due Date if Cron Ran Every Day|| |1|2017-02-10|2017-02-15|2017-02-15|2017-02-10| |1|2017-02-13|2017-02-15|2017-02-15|2017-02-13| |1|2017-02-15|2017-02-15|2017-02-15|2017-02-15| |1|2017-02-16|*2017-02-16*|*2017-02-15*|2017-02-16| The incorrect date is highlighted in *bold*. Thus, in the case of back-billing service renewals, missed services can cause some services to be due today, or on the first service's renew date, rather than the renew date of the specified service. |
| Description |
Someone had brought up the fact that when the cron does not run every day, and Blesta back-bills for service renewals, these service renewals still get added to a single invoice.
An invoice should be due when the service renews. This means we can only group services onto a single invoice if they all renew on the same day. In the case of back-billing old services, it's possible that all of the old services and all of the current renewals get added to a single invoice that is due today. Consider that the cron did not run in a week and the following services need to be renewed for a single client: *Today: 2017-02-15* ||Invoice Days Before Renewal||Service Renew Date||Expected Invoice Due Date||Actual Invoice Due Date||Invoice Due Date if Cron Ran Every Day|| |1|2017-02-10|2017-02-15|2017-02-15|2017-02-10| |1|2017-02-13|2017-02-15|2017-02-15|2017-02-13| |1|2017-02-15|2017-02-15|2017-02-15|2017-02-15| |1|2017-02-16|*2017-02-16*|*2017-02-15*|2017-02-16| The incorrect date is highlighted in *bold*. Thus, in the case of back-billing service renewals, missed services can cause some services to be due today, or on the first service's renew date, rather than the renew date of the specified service. |
Someone had brought up the fact that when the cron does not run every day, and Blesta back-bills for service renewals, these service renewals still get added to a single invoice.
An invoice should be due when the service renews. This means we can only group services onto a single invoice if they all renew on the same day. In the case of back-billing old services, it's possible that all of the old services and all of the current renewals get added to a single invoice that is due today. Consider that the cron did not run in a week and the following services need to be renewed for a single client: *Today: 2017-02-15* *Invoice Days Before Renewal: 1* ||Service Renew Date||Expected Invoice Due Date||Actual Invoice Due Date||Invoice Due Date if Cron Ran Every Day|| |2017-02-10|2017-02-15|2017-02-15|2017-02-10| |2017-02-13|2017-02-15|2017-02-15|2017-02-13| |2017-02-15|2017-02-15|2017-02-15|2017-02-15| |2017-02-16|*2017-02-16*|*2017-02-15*|2017-02-16| The incorrect date is highlighted in *bold*. Thus, in the case of back-billing service renewals, missed services can cause some services to be due today, or on the first service's renew date, rather than the renew date of the specified service. |
| Rank | Ranked higher |