# Laufzeiten Damit nicht die gleichen Vertragsmodalitäten in jedem Produkt neu definiert werden müssen, werden diese in hostware in sogenannten "Laufzeiten" definiert. Eine Laufzeit kann dann einem oder mehreren Produkten zugewiesen werden, was für eine einheitliche Konfiguration sorgt. ## Invoicing You can define the number of days a customer has to pay the invoice after it has been created.\ ![](https://1141670261-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHupRK3qVDTomY8g3pcFA%2Fuploads%2FyR1fJxbdnJags212kgT2%2Fimage.png?alt=media\&token=8a191d50-51cc-4492-b7a0-f68f05dfdbab) If the invoice does not get paid within the days defined in this setting, it gets marked as overdue. ### Offset invoice creation You can set the invoice to be created not in the renewal date, but a number of days before the renewal.

If set to 0, than the invoice will just be created on the renewal date.
## Cancellation requests flow The cancellation approval mode is configured per contract payment period. \ It can be handled in two ways: * Automatic * Manual If it is set to **Automatic**, the customer can submit a cancellation and it is created immediately with the normal confirmation email.

\ If it is set to **Manual**, the service cancellation request will need the admin approval, the customer gets a “request received” message, and an admin must confirm it in `Billing > Cancellations`. During that admin confirmation step, the cancellation date can be adjusted before the final confirmation email is sent.