Billing Logic

This document explains the billing and invoicing logic used in the WHMCS software. Having an understanding of these core elements of the software will ....COMPLETE ME***

Ordering

When a new visitor places an order a number of new records are created which contain the various pieces of information captured on the order form:

1. A client record is created to store the customer's contact details and payment preferences.
2. The service and domain record(s) are then created which contain the details of the service the client selected on the order form.
3. Next an invoice record is created which records the amount to be paid, when it is due to be paid and how payment should be made.
4. Finally, an order record is created which ties all of the above together and records the fraud report details (if enabled). The order is a static record which reflects the prices and items at the time of ordering, subsequent changes will not be reflected on the order.

Invoicing

When an invoice is created by an initial order, the default behaviour is that the invoice is due on the day of ordering. The exception being if the Order Grace Days setting is used, in which case the invoice due date will be set x days to the future.

Upon payment of the initial invoice, the automation is triggered which executes the module Create function and the service's Next Due Date value is incremented forward one billing cycle (ie. 1 month, 3 months, 6 months, 1 year, 2 years or 3 years).

The date at which the next payment is due is controlled by the Next Due Date of the service. When the cron executes the daily automation tasks the following actions are performed:

• The Next Due Date of all Active, Pending and Suspended services are analysed
• Determine if the date is equal to or less than the number of days in the future specified by the Invoice Generation setting
• Ensure no invoice item exists for the service on the next due date
• If the above points are evaluated to be true, then a new invoice is generated.
• The InvoiceCreation Action Hook point is triggered
• The InvoiceCreationPreEmail Action Hook point is triggered
• The Invoice Created email is sent to the client
• The InvoiceCreated Action Hook point is triggered
• The Next Invoice Date of the service is incremented forward by one billing cycle.

In this way, WHMCS will never generate two invoices for a given product, service or domain with the same due date - even if the original invoice has been deleted.

Payments

Automation upon payment is triggered by a transaction applied to an invoice which fully pays the balance, reducing it to 0.00 and marking an invoice paid. This means that editing an invoice and changing the status to Paid will not trigger automation. Upon adding payment to an invoice which is associated with a product/service or domain, the following actions occur:

• A transaction is entered into the database
• The transaction amount is subtracted from the invoice balance
• If the invoice balance is now 0, the invoice is marked as paid.
• The invoice status is changed to Paid
• The InvoicePaidPreEmail Action Hook point is triggered
• A payment confirmation email is sent to the client
• The Next Due Date of the associated service/domain is incremented forward by one billing cycle.
• The InvoicePaid Action Hook point is triggered

Overpayments

Credited

Billing Cycles

A billing cycle is considered a calendar period, so "1 month" is not a consistent period of days. When you agree to bill by the month, you are charging the same amount of money for different amounts of service. WHMCS uses the php date function's computation to figure out the next due date. We tell it to add a month and return the date, which we set as the Next Due Date.

February

Due to the shorter length of February this can cause some unique behaviour which does not happen for the other 11 months of a year:

Order Date	Renewal Date	Number of Days
January 29	March 1	31 days
January 30	March 2	31 days
January 31	March 3	31 days
February 1	March 1	28 days
February 2	March 2	28 days
February 3	March 3	28 days

Suspension

The date at which services are suspended is controlled by the Next Due Date of the service. When the cron executes the daily automation tasks the following actions are performed:

• The Next Due Date of all Active and Pending services are analysed
• Determine if the date is equal to or less than the number of days in the future specified by the Suspension Days setting
• Determine if Automated Suspension is enabled
• If this is evaluated to be true, the PreModuleSuspend Action Hook point is triggered
• The services is suspended
• If the module returns a success response, the AfterModuleSuspend Action Hook point is triggered
• If the module returns a failed response, the AfterModuleSuspendFailed Action Hook point is triggered.

Unsuspension

When payment is made against an invoice which is associated with a service in Suspended status with a suspension reason of "Overdue on Payment" the service can be automatically unsuspended. The Enable Unsuspension option must be enabled in Automation Settings.

When used in conjunction with continuous invoice generation, paying a recent invoice whilst leaving an older invoice unpaid will keep the service suspended. The exception being if the payment were to increment the Next Due Date forward to a date at which the service was no longer within the Suspension date range - in that case the service would be unsuspended.

Termination

The date at which services are terminated is controlled by the Next Due Date of the service. When the cron executes the daily automation tasks the following actions are performed:

• The Next Due Date of all Active, Suspended and Pending services are analysed
• Determine if the date is equal to or less than the number of days in the future specified by the Termination Days setting
• Determine if Automated Termination is enabled
• If this is evaluated to be true, the PreModuleTerminate Action Hook point is triggered
• The services is terminated
• If the module returns a success response, the AfterModuleTerminate Action Hook point is triggered
• If the module returns a failed response, the AfterModuleTerminateFailed Action Hook point is triggered.