Daily due date calendar management strategy
To create a daily due date calendar management strategy, run the Create program calendar strategy endpoint with the strategy field set to DAILY_DUE_DATE, and specify values for the following body parameters.
- Interval in days between cycles. Set this using the
every_x_daysfield. The default value is 1, which creates a one-day cycle. However, you can setevery_x_daysto any integer between 1 and 365. For example, setevery_x_daysto 365 to create a cycle that spans one year. - Number of days between the cycle closing date and the due date. Set this using the
days_between_cycle_closing_and_due_datefield.
After creating the management strategy, use the Update account calendar strategy endpoint to assign it to an account.
Example
On March 3, you create a new program calendar strategy with the following settings.
strategy=DAILY_DUE_DATEevery_x_days= 5days_between_cycle_closing_and_due_date= 2
Now, suppose you wait until April 1 to attach the strategy to an account. The Pismo platform uses the following process to determine what to use for the first due date and cycle closing date for the account. (Use the table at the end to help you follow along.)
The Pismo platform starts calculating due dates on the day after the strategy is created. This is March 4, so the platform adds 5 to March 4 to get March 9 for the first possible due date. It subtracts 2 from that to get March 7 for the first possible cycle closing date. However, these dates have already passed. (Remember, you didn't assign the strategy to the account until April 1.) The platform can't create a statement that's already closed, so these dates don't work.
Next, the platform adds 5 to March 9 to get March 14 for the next possible due date and subtracts 2 from that to get March 12 for the next possible cycle closing date. These dates are still in the past.
The platform keeps going like this until it get to a due date of April 3. This date is after April 1. However, the corresponding cycle closing date is April 1. This is the same day that you assigned the strategy to the account. The platform can't create a cycle and close it on the same day, so these dates also don't work.
Finally, the platform calculates a due date of April 8 and a cycle closing date of April 6. Both of these dates are after April 1, so they work. The platform starts generating statements for the account.
| Cycle closing date | Due date | Do these dates work? |
|---|---|---|
| March 7 | March 9 | No |
| March 12 | March 14 | No |
| March 17 | March 19 | No |
| March 22 | March 24 | No |
| March 27 | March 29 | No |
| April 1 | April 3 | No (closing must be after April 1) |
| April 6 | April 8 | Yes (first statement) |
| April 11 | April 13 | Yes (next statement) |
| April 16 | April 18 | Yes (and so on) |
| ... | ... | ... |
Updated 3 days ago