Embedded Files
A new functionality is added to enhance the billing functionality. It allows for an operator to display the due date in different areas of SIMPLer. Instead of having the due date only visible on the invoice it can now be seen on the End User Portal (EUP) as well.
To make use of this feature:
1. Proceed to menu Settings > Modify SPID
2. Find the section 'Due Date Settings'
Fig 1: Due Date Settings
3. How to configure the different settings for the Due Date
Billing - Invoice Due Date Offset: the number entered here, uses the invoice date to calculate the due date e.g. in this example if invoice date is 1st then due date is 10th (1 + 9 = 10)
Billing - Invoice Due Date Offset: First Invoice: The number entered here uses the first invoice date to calculate the due date of the first invoice.
Billing - Invoice Due Date Offset: SAND Deferred:
Display Due Date for Custom Invoice: Enables or Disables displaying the due date for the custom invoices in pdf or customer portal (EUP). This option is ignored when template-defined due date is selected, because the due date is controlled by the invoice template.
Invoice Due Date Type: Select how the invoice due date is determined. Choose one of the predefined options to allow for the duedate to be displayed in the portal (with the exception of template-defined due date). Applies only if <TMPL_VAR NAME=EFFECTIVEINVOICEDUEDATE> is used on the invoice template. Fig.2.
Show Due Date in EUP: Displays the invoice due date in the customer portal. Fig.3. Default value: Disabled. Note: Only available when Due Date Type is not set to Template-Defined due date.
Use First Invoice Due Date Override: When enabled, the first invoice will use the First Invoice Due Date instead of the due date selected by Due Date Type. Default value: Disabled. Note: Only available when Due Date Type is not set to Template-Defined due date.
Fig 2: Invoice Due Date Type
3. Invoice Due Date Type
Standard due date: Uses the standard invoice due date calculated from the invoice due date and billing settings.
Deferred due date: Uses the later of the standard due date and the deferred payment date (if available)
Deferred due date (-1 day): Uses one day before the later of the standard due date and the deferred payment date.
Template defined due date: Uses the due date determined by the invoice template. This keeps the existing template behavior unchanged and provides full backward compatibilty. Since the final due date is resolved dynalically by the template, it cannot be displayed in the customer portal.
> Default value: Template-defined due date
Fig 3: Due Date in EUP
4. Dispay Due Date for Custom Invoices
Controls whether the due date is displayed on custom invoices in both the generated PDF and the customer portal.
Default value: Disabled.
Note: Only available when Due Date Type is not set to Template-Defined due date.
Backward Compatibility:
The default configuration is Template-Defined due date, which means existing systems continue to behave example as they do today. No invoice tempalte need ot be changed after this feature is introduced.
Operator who want the due date availble in the customer portal can switch to one of the redefined due date calculation methods.
Summary:
All due date related settings are grouped together in one place to make configuration easier and more intuitive.
By default,nothing changes for existing Operators. Administrators can gradually move from template-driven due dates to one of the predefined calculation methods if they want to display the due date in the customer portal or use the additional due date options.
Published Date: July 8, 2026
Published By: AS
Engineer: PD
Operator: SCC
Contact Azotel Support:
Need more help? Save time by creating a maintenance ticket to Azotel through your instance or email support@azotel.com.
Page updated
Report abuse