Billing Overview #

Chargeable ~.Dimensions.~ features are invoiced on a monthly basis in advance. As a service provider, you will be invoiced for all of your reseller's customers in a single monthly bill.

note
This section will only be available if you are billed directly for the ~.Dimensions.~ service. If resellers are billed directly by ~.Dimensions.~, the billing section will not be available.

Provisioning #

Each reseller can provision customers and features manually through the Reseller Portal or automatically using the REST API.

Any new customers provisioned or additional features added to existing customers will be invoiced during the following billing run. Features will be invoiced based on pro-rata daily usage of the system prior to the billing period and then in advance for the next monthly period.

Example 1 – New customer/features provisioned on March 15th

On the April 1st Billing Run, an invoice will be produced for each feature provisioned from the March 15th until April 30th. Features will then continue to be invoiced one month in advance, unless terminated (please refer to the termination section).

Example 2 – A new feature is provisioned for an existing customer on April 27th

On the May 1st Billing Run, an invoice will be produced for existing features from the May 1st until May 31st. The new feature will be invoiced pro-rata from April 27th to the May 31st. Features that are provisioned for a user and then removed the same day will not be charged. Provisioning the same feature for a user and removing it during the same billing period will result in the feature being billed as per the process outlined above.

note
Any license only enabled for a single day of a billing period will not be invoiced.

Trial Features #

Where agreed in advance, features can be trialled by a customer. When this occurs, a zero-rated item on the invoice will be produced for the trial features. If the customer chooses not to continue with the trial and is terminated on the system before the end of the trial period, no further invoicing will be produced for the customer. If the customer chooses to continue with the product, the features will be billed from the first day after the trial ends. Invoicing for features will continue as previously documented.

note
Currently individual features cannot be trialled, only entire customer accounts.

warning
Trial customers must be disabled before the end of the trial period to avoid charges.

Canceling Features #

Features can be removed from a user/customer either manually through the reseller's Reseller Portal or automatically using the REST API. Features will cease to be billed from the date they are removed from a customer/user.

Example 1 – A feature is added on May 25th then removed on the June 18th

On the June 1st billing run, the feature will have two invoice items, one back billing from the 25th May to the 31st May and a second in advance for the 1st June to the 30th June. On the July 1st billing run, a credit will be produced for this feature from June 19th until 30th June to credit the amount billed in advance which was not used.

Example 2 – A feature is provisioned on the August 15th then removed August 20th

On the September 1st billing run, an invoice will be produced for this feature from August 15th until 20th August.

Example 3 – A feature is provisioned on August 1st then removed August 4th, then provisioned again on August 20th and removed on August 25th

On the September 1st billing run, two invoice items will be produced for this feature, one from August 1st until 4th August and another from August 20th until 25th August.

Terminating Customers #

Customers can be terminated immediately or on a specific day. On the day a customer is terminated, features will be invoiced/credited as they are described under the ‘Canceling Features’ section.

Automatic Provisioning #

Some features of the system are automatically provisioned based on the data being processed and other features of the system that are being used. The table below outlines features which are automatically provisioned by ~.Dimensions.~: