Invoicing Issues - Revision history

JoshQ: /* Double Invoices/Charges/Blank Invoices */

2024-05-22T16:03:15Z

‎Double Invoices/Charges/Blank Invoices

JoshQ: /* Double Invoices/Charges/Blank Invoices */

2024-05-22T16:02:51Z

‎Double Invoices/Charges/Blank Invoices

SarahK at 20:07, 11 May 2022

2022-05-11T20:07:28Z

SarahK at 19:04, 25 April 2022

2022-04-25T19:04:24Z

SarahK at 14:12, 4 August 2020

2020-08-04T14:12:56Z

SarahK at 18:35, 29 April 2020

2020-04-29T18:35:38Z

AlexN at 06:08, 20 May 2019

2019-05-20T06:08:07Z

John at 13:43, 21 October 2015

2015-10-21T13:43:06Z

John: /* Tax Not Applied to Invoices */

2015-07-24T06:47:35Z

‎Tax Not Applied to Invoices

John at 12:50, 28 May 2015

2015-05-28T12:50:35Z

@@ Line 49: / Line 49: @@
 There are several invoicing issues that a common misconfiguration can cause. The system may generate two invoices for the same service and due date, may double-charge a client for the same invoice, or may generate a completely blank invoice.
-A cron job running twice at the same time can cause this. The cron job should only run once per day, and should never run simultaneously. To confirm this, review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > [[System Logs]]''' ('''Utilities > Logs''' in WHMCS 7.x and earlier). There should only be one ''Cron Job: Starting Daily Automation Tasks'' and one ''Cron Job: Completed Daily Automation Tasks'' entry per day. If there is more than one of either of these entries, check the server's cron job configuration to ensure there is only one entry for the <tt>cron.php</tt> file. For more information, see our [[Crons]] documentation.
+A cron job running twice at the same time can cause this. The cron job should only run once per day, and should never run simultaneously. To confirm this, review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > [[System Logs]]''' ('''Utilities > Logs''' in WHMCS 7.x and earlier). There should only be one ''Cron Job: Starting Daily Automation Tasks'' and one ''Cron Job: Completed Daily Automation Tasks'' entry per day. If there is more than one of either of these entries, check the server's cron job configuration to ensure there is only one entry for the <tt>cron.php</tt> file.
 ==Tax Not Applied to Invoices==

@@ Line 49: / Line 49: @@
 There are several invoicing issues that a common misconfiguration can cause. The system may generate two invoices for the same service and due date, may double-charge a client for the same invoice, or may generate a completely blank invoice.
-A cron job running twice at the same time can cause this. The cron job should only run once per day, and should never run simultaneously. To confirm this, review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > [[System Logs]]''' ('''Utilities > Logs''' in WHMCS 7.x and earlier). There should only be one ''Cron Job: Completed'' entry per day. If there is more than one, check the server's cron job configuration to ensure there is only one entry for the <tt>cron.php</tt> file in accordance with our [[Crons|our documentation]].
+A cron job running twice at the same time can cause this. The cron job should only run once per day, and should never run simultaneously. To confirm this, review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > [[System Logs]]''' ('''Utilities > Logs''' in WHMCS 7.x and earlier). There should only be one ''Cron Job: Starting Daily Automation Tasks'' and one ''Cron Job: Completed Daily Automation Tasks'' entry per day. If there is more than one of either of these entries, check the server's cron job configuration to ensure there is only one entry for the <tt>cron.php</tt> file. For more information, see our [[Crons]] documentation.
 ==Tax Not Applied to Invoices==

@@ Line 9: / Line 9: @@
 Invoice generation, payment reminders, and account suspensions and terminations are some of the tasks that the daily [[Crons|cron job]] handles in accordance with your [[Automation Settings|automation settings]]. If you find that some or none of the above are occurring, this could indicate the cron job is not running successfully.
-Review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > [[System Logs]]''' ('''Utilities > Logs > [[Activity Log]]''' in WHMCS 7.x and earlier) and make sure that you see a number of entries beginning with ''Cron Job'' each day. The final entry every day should be ''Cron Job: Completed''.
+Review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > [[System Logs]]''' ('''Utilities > Logs''' in WHMCS 7.x and earlier) and make sure that you see a number of entries beginning with ''Cron Job'' each day. The final entry every day should be ''Cron Job: Completed''.
 * If you see no cron job entries, this means you have not configured your automation cron job correctly. You must do this per our installation instructions. For more information, see [[Crons|Crons]].
@@ Line 49: / Line 49: @@
 There are several invoicing issues that a common misconfiguration can cause. The system may generate two invoices for the same service and due date, may double-charge a client for the same invoice, or may generate a completely blank invoice.
-A cron job running twice at the same time can cause this. The cron job should only run once per day, and should never run simultaneously. To confirm this, review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > [[System Logs]]''' ('''Utilities > Logs > [[Activity Log]]''' in WHMCS 7.x and earlier). There should only be one ''Cron Job: Completed'' entry per day. If there is more than one, check the server's cron job configuration to ensure there is only one entry for the <tt>cron.php</tt> file in accordance with our [[Crons|our documentation]].
+A cron job running twice at the same time can cause this. The cron job should only run once per day, and should never run simultaneously. To confirm this, review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > [[System Logs]]''' ('''Utilities > Logs''' in WHMCS 7.x and earlier). There should only be one ''Cron Job: Completed'' entry per day. If there is more than one, check the server's cron job configuration to ensure there is only one entry for the <tt>cron.php</tt> file in accordance with our [[Crons|our documentation]].
 ==Tax Not Applied to Invoices==

@@ Line 3: / Line 3: @@
 ==Invoices/Payment Reminders not Generated==
-Make sure that you have deselected the '''Overdue Notices''' option on the client's '''Profile''' tab. Selecting the option will prevent the system from sending overdue notices to the client.
+Make certain to deselect '''Overdue Notices''' in the client's '''[[Clients:Profile Tab|Profile]]''' tab. This prevents the system from sending overdue notices to the client.
-If the '''Email Templates''' are not present, the system will be unable to send an email. Review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Email Templates''' and ensure the ''Invoice Created'' and ''Overdue Notice'' emails templates are present.
+If the email templates do not exist, the system cannot send an email. Go to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Email Templates]]''' or, prior to WHMCS 8.0, '''Setup > Email Templates''' and ensure the '''Invoice Created''' and '''Overdue Notice''' email templates display.
-Invoice generation, payment reminders, and account suspensions and terminations are some of the tasks that the daily [[Crons|cron job]] handles in accordance with your [[Automation Settings]]. If you find that some or none of the above are occurring, this could indicate the cron job is not running successfully.
+Invoice generation, payment reminders, and account suspensions and terminations are some of the tasks that the daily [[Crons|cron job]] handles in accordance with your [[Automation Settings|automation settings]]. If you find that some or none of the above are occurring, this could indicate the cron job is not running successfully.
-Review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Logs''' ('''Utilities > Logs > Activity Log''' in WHMCS 7.x and earlier) and make sure that you see a number of entries beginning with ''Cron Job'' each day. The final entry every day should be ''Cron Job: Completed''.
+Review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > [[System Logs]]''' ('''Utilities > Logs > [[Activity Log]]''' in WHMCS 7.x and earlier) and make sure that you see a number of entries beginning with ''Cron Job'' each day. The final entry every day should be ''Cron Job: Completed''.
 * If you see no cron job entries, this means you have not configured your automation cron job correctly. You must do this per our installation instructions. For more information, see [[Crons|Crons]].
-* If you see some cron job entries, but none after ''Cron Job: Running Usage Stats Update'', your cron job is getting stuck at the '''Usage Stats Update''' stage. The most likely cause of this error is that you have an old server in '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Servers''' that is no longer available.<br />To resolve this, update or remove any inactive or offline servers from '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Servers''' so that they can all connect successfully. Alternatively, you can disable '''Update Usage Statistics''' under '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Automation Settings'''.
+* If you see some cron job entries, but none after ''Cron Job: Running Usage Stats Update'', your cron job is getting stuck at the '''Usage Stats Update''' stage. The most likely cause of this error is that you have an old server in '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Servers]]''' or, prior to WHMCS 8.0, '''Setup > Products/Services > Servers''' that is no longer available.
-* If you see some cron job entries, but no ''Cron Job: Completed'' entry, this suggests that your server is prematurely terminating the cron job. Increase the <tt>memory_limit</tt> setting in your server's <tt>php.ini</tt> to 64 MB or 128 MB, which is usually sufficient. Then, check whether you start getting the cron job report again over the next few days.
+* If you see some cron job entries but no ''Cron Job: Completed'' entry, your server may be prematurely terminating the cron job. Increase the <tt>memory_limit</tt> setting in your server's <tt>php.ini</tt> file to 64 MB or 128 MB. Then, check whether you start getting the cron job report again over the next few days.
-If the cron job still doesn't complete with the increased memory limit, make sure that <tt>display_errors</tt> is enabled in the server's PHP configuration. Enable the '''Setup > General Settings > Other > Display Errors''' option, and then visit the <tt>cron.php</tt> file in your browser to run the cron manually. You should now see error output. For more information about the most common errors and their causes, see:
+If the cron job still doesn't complete with the increased memory limit, make sure that <tt>display_errors</tt> is enabled in the server's PHP configuration. Enable '''Display Errors''' in the '''[[Other Tab|Other]]''' tab at '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > General Settings''' or, prior to WHMCS 8.0, '''Setup > General Settings'''. Then, visit the <tt>cron.php</tt> file in your browser to run the cron manually. You should now see error output.
 *[[Server Modules]]
@@ Line 27: / Line 31: @@
 There are a couple of reasons for invoices not generating. The most obvious reason is that there's a cancellation request for the service or it's in cancelled, terminated, fraud or expired status. For domains, selecting the '''Disable Auto Renew''' option stops the system from generating renewal invoices automatically. It could also be that the cron job is not running. For more information, see [[#Invoices/Payment Reminders not Generated|the section above]].
-The system only generates invoices when the service's '''Next Due Date''' is within the '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Automation Settings > Invoice Generation''' setting.
+The system only generates invoices when the service's '''Next Due Date''' is within the '''Invoice Generation''' setting at '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Automation Settings]]''' or, prior to WHMCS 8.0, '''Setup > Automation Settings'''.
 For example, if the '''Next Due Date''' is in the future, the system won't generate an invoice. If today's date is 01/01/2012:
@@ Line 39: / Line 43: @@
 = Invoice '''not''' generated.
-If it's none of those, then it's possible that the system generated an invoice that was then deleted by a member of staff. Check the client's '''Log''' tab for any ''Invoice Deleted'' or ''Order Deleted'' entries. WHMCS never generates duplicate invoices for the same service on the same due date, so if you require a new invoice after deleting an invoice, you must manually move the '''Next Due Date''' forward or back by one day.
+If it's none of those, then it's possible that the system generated an invoice that was then deleted by a member of staff. Check the client's '''[[Clients:Log Tab|Log]]''' tab for any ''Invoice Deleted'' or ''Order Deleted'' entries. WHMCS never generates duplicate invoices for the same service on the same due date, so if you require a new invoice after deleting an invoice, you must manually move the '''Next Due Date''' forward or back by one day.
 ==Double Invoices/Charges/Blank Invoices==
@@ Line 45: / Line 49: @@
 There are several invoicing issues that a common misconfiguration can cause. The system may generate two invoices for the same service and due date, may double-charge a client for the same invoice, or may generate a completely blank invoice.
-A cron job running twice at the same time can cause this. The cron job should only run once per day, and should never run simultaneously. To confirm this, review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Logs''' ('''Utilities > Logs > Activity Log''' in WHMCS 7.x and earlier). There should only be one ''Cron Job: Completed'' entry per day. If there is more than one, check the server's cron job configuration to ensure there is only one entry for the <tt>cron.php</tt> file in accordance with our [[Crons|our documentation]].
+A cron job running twice at the same time can cause this. The cron job should only run once per day, and should never run simultaneously. To confirm this, review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > [[System Logs]]''' ('''Utilities > Logs > [[Activity Log]]''' in WHMCS 7.x and earlier). There should only be one ''Cron Job: Completed'' entry per day. If there is more than one, check the server's cron job configuration to ensure there is only one entry for the <tt>cron.php</tt> file in accordance with our [[Crons|our documentation]].
 ==Tax Not Applied to Invoices==
@@ Line 51: / Line 55: @@
 If the system has not applied tax, WHMCS may be operating as though it is not eligible under your tax rules.
-First, ensure that tax is enabled and that you have selected the relevant '''Apply Tax''' options on the ''[[Tax Configuration|Tax Rules]]'' page. If it's an invoice for a product, ensure this option is selected in the product configuration.
+First, ensure that tax is enabled and that you have selected the relevant '''Apply Tax''' options at '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Tax Configuration]]''' or, prior to WHMCS 8.0, '''Setup > Payments > Tax Configuration'''. If it's an invoice for a product, ensure this option is selected in the product configuration.
-Secondly, ensure the '''Tax Exempt''' checkbox is deselected on the client's '''Profile''' tab. A member of staff or our [[EU_VAT_Addon|EU VAT Invoicing Addon Module]] (if activated) may have selected this.
+Secondly, ensure that '''Tax Exempt''' is deselected on the client's '''[[Clients:Profile Tab|Profile]]''' tab. A member of staff or our [[EU_VAT_Addon|EU VAT Invoicing]] addon module may have selected this.
 Finally, the client might not match any of your tax rules. The state and country must be '''exact''' matches and are case sensitive. For example, if a tax rule exists for the state ''TX'' and the client's state is ''Texas'', these do not match and the system would not apply tax. This scenario would require two tax rules, one for ''TX'' and another for ''Texas''.
@@ Line 61: / Line 65: @@
 ==Multiple Invoices for the same Service==
-The system may generate multiple invoices for the same service with different due dates if the service has a due date in the past. This usually occurs with services that you import using the WHM/cPanel importer, or services  a staff member manually added, in which the '''Next Due Date''' is left at <tt>00/00/0000</tt>. As this due date is in the past, WHMCS generates all invoices between then and today to ensure the client is has paid their balance in full.
+The system may generate multiple invoices for the same service with different due dates if the service has a due date in the past. This usually occurs with services that you import or a staff member manually added, in which the '''Next Due Date''' is <tt>00/00/0000</tt>. As this due date is in the past, WHMCS generates all invoices between then and today to ensure the client has paid their balance in full.
-To correct this, change the '''Next Due Date''' to the date of the client's next payment via their '''Products/Services''' tab. You can safely delete or cancel any erroneous invoices.
+To correct this, change the '''Next Due Date''' to the date of the client's next payment via their '''[[Clients:Products/Services Tab|Products/Services]]''' tab. You can safely delete or cancel any erroneous invoices.
 {{troubleshooting}}

@@ Line 3: / Line 3: @@
 ==Invoices/Payment Reminders not Generated==
-Make sure that you have deselected the '''Overdue Notices''' option on the client's Profile tab. Selecting the option will prevent the system from sending overdue notices to the client.
+Make sure that you have deselected the '''Overdue Notices''' option on the client's '''Profile''' tab. Selecting the option will prevent the system from sending overdue notices to the client.
-If the '''Email Templates''' are not present, the system will be unable to send an email. Review Setup > Email Templates and ensure the ''Invoice Created'' and ''Overdue Notice'' emails templates are present.
+If the '''Email Templates''' are not present, the system will be unable to send an email. Review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Email Templates''' and ensure the ''Invoice Created'' and ''Overdue Notice'' emails templates are present.
 Invoice generation, payment reminders, and account suspensions and terminations are some of the tasks that the daily [[Crons|cron job]] handles in accordance with your [[Automation Settings]]. If you find that some or none of the above are occurring, this could indicate the cron job is not running successfully.
-Review '''Utilities > Logs > Activity Log''' and make sure that you see a number of entries beginning with "Cron Job" each day. The final entry every day should be "Cron Job: Completed".
+Review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Logs''' ('''Utilities > Logs > Activity Log''' in WHMCS 7.x and earlier) and make sure that you see a number of entries beginning with ''Cron Job'' each day. The final entry every day should be ''Cron Job: Completed''.
 * If you see no cron job entries, this means you have not configured your automation cron job correctly. You must do this per our installation instructions. For more information, see [[Crons|Crons]].
-* If you see some cron job entries, but none after "Cron Job: Running Usage Stats Update", your cron job is getting stuck at the Usage Stats Update stage. The most likely cause of this error is that you have an old server in Setup > Servers that is no longer available.<br />To resolve this, update or remove any inactive or offline servers from Setup > Servers so that they can all connect successfully. Alternatively, you can disable Update Usage Statistics under Setup > Automation Settings.
+* If you see some cron job entries, but none after ''Cron Job: Running Usage Stats Update'', your cron job is getting stuck at the '''Usage Stats Update''' stage. The most likely cause of this error is that you have an old server in '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Servers''' that is no longer available.<br />To resolve this, update or remove any inactive or offline servers from '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Servers''' so that they can all connect successfully. Alternatively, you can disable '''Update Usage Statistics''' under '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Automation Settings'''.
-* If you see some cron job entries, but no "Cron Job: Completed" entry, this suggests that your server is prematurely terminating the cron job. Increase the <tt>memory_limit</tt> setting in your server's <tt>php.ini</tt> to 64 MB or 128 MB, which is usually sufficient. Then, check whether you start getting the cron job report again over the next few days.
+* If you see some cron job entries, but no ''Cron Job: Completed'' entry, this suggests that your server is prematurely terminating the cron job. Increase the <tt>memory_limit</tt> setting in your server's <tt>php.ini</tt> to 64 MB or 128 MB, which is usually sufficient. Then, check whether you start getting the cron job report again over the next few days.
-If the cron job still doesn't complete with the increased memory limit, make sure that <tt>display_errors</tt> is enabled in the server's PHP configuration. Enable the '''Setup > General Settings > Other tab > Display Errors''' option, and then visit the <tt>cron.php</tt> file in your browser to run the cron manually. You should now see error output. For more information about the most common errors and their causes, see:
+If the cron job still doesn't complete with the increased memory limit, make sure that <tt>display_errors</tt> is enabled in the server's PHP configuration. Enable the '''Setup > General Settings > Other > Display Errors''' option, and then visit the <tt>cron.php</tt> file in your browser to run the cron manually. You should now see error output. For more information about the most common errors and their causes, see:
 *[[Server Modules]]
@@ Line 25: / Line 25: @@
 ==Items Not Invoicing==
-There are a couple of reasons for invoices not generating. The most obvious reason is that there's a '''cancellation request''' for the service or it's in cancelled, terminated, fraud or expired '''status'''. For domains, selecting the '''Disable Auto Renew''' option stops the system from generating renewal invoices automatically. It could also be that the '''cron job''' is not running. For more information, see [[#Invoices/Payment Reminders not Generated|the above]].
+There are a couple of reasons for invoices not generating. The most obvious reason is that there's a cancellation request for the service or it's in cancelled, terminated, fraud or expired status. For domains, selecting the '''Disable Auto Renew''' option stops the system from generating renewal invoices automatically. It could also be that the cron job is not running. For more information, see [[#Invoices/Payment Reminders not Generated|the section above]].
-The system only generates invoices when the service's Next Due Date is within the Setup > Automation Settings > Invoice Generation value. For example, if the '''Next Due Date''' is in the future, the system won't generate an invoice. For example, if today's date is 01/01/2012:
+The system only generates invoices when the service's '''Next Due Date''' is within the '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Automation Settings > Invoice Generation''' setting.
 Next Due Date: 07/01/2012<br />
@@ Line 37: / Line 39: @@
 = Invoice '''not''' generated.
-If it's none of those, then it's possible that the system generated an invoice that was then '''deleted''' by a member of staff. Check the client's Log tab for any Invoice Deleted or Order Deleted entries. WHMCS never generates duplicate invoices for the same service on the same due date, so if you require a new invoice after deleting an invoice, you must manually move the Next Due Date forward or back by one day.
+If it's none of those, then it's possible that the system generated an invoice that was then deleted by a member of staff. Check the client's '''Log''' tab for any ''Invoice Deleted'' or ''Order Deleted'' entries. WHMCS never generates duplicate invoices for the same service on the same due date, so if you require a new invoice after deleting an invoice, you must manually move the '''Next Due Date''' forward or back by one day.
 ==Double Invoices/Charges/Blank Invoices==
@@ Line 43: / Line 45: @@
 There are several invoicing issues that a common misconfiguration can cause. The system may generate two invoices for the same service and due date, may double-charge a client for the same invoice, or may generate a completely blank invoice.
-A cron job running twice at the same time can cause this. The cron job should only run once per day, and should never run simultaneously. To confirm this, review '''Utilities > Logs > Activity Log'''. There should only be one "Cron Job: Completed" entry per day. If there is more than one, check the server's cron job configuration to ensure there is only one entry for the <tt>cron.php</tt> file in accordance with our [[Crons|our documentation]].
+A cron job running twice at the same time can cause this. The cron job should only run once per day, and should never run simultaneously. To confirm this, review '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Logs''' ('''Utilities > Logs > Activity Log''' in WHMCS 7.x and earlier). There should only be one ''Cron Job: Completed'' entry per day. If there is more than one, check the server's cron job configuration to ensure there is only one entry for the <tt>cron.php</tt> file in accordance with our [[Crons|our documentation]].
 ==Tax Not Applied to Invoices==
@@ Line 49: / Line 51: @@
 If the system has not applied tax, WHMCS may be operating as though it is not eligible under your tax rules.
-First, ensure that tax is enabled and that you have selected the relevant '''Apply Tax''' options on the [[Tax Configuration|Tax Rules]] page. If it's an invoice for a product, ensure this option is selected in the product configuration.
+First, ensure that tax is enabled and that you have selected the relevant '''Apply Tax''' options on the ''[[Tax Configuration|Tax Rules]]'' page. If it's an invoice for a product, ensure this option is selected in the product configuration.
-Secondly, ensure the '''Tax Exempt''' checkbox is deselected on the client's Profile tab. A member of staff or our [[EU_VAT_Addon|EU VAT Invoicing Addon Module]] (if activated) may have selected this.
+Secondly, ensure the '''Tax Exempt''' checkbox is deselected on the client's '''Profile''' tab. A member of staff or our [[EU_VAT_Addon|EU VAT Invoicing Addon Module]] (if activated) may have selected this.
-Finally, the client might not match any of your tax rules. The state and country must be '''exact matches''' and are case sensitive. For example, if a tax rule exists for the state "TX" and the client's state is "Texas", these do not match and the system would not apply tax. This scenario would require two tax rules, one for "TX" and another for "Texas".
+Finally, the client might not match any of your tax rules. The state and country must be '''exact''' matches and are case sensitive. For example, if a tax rule exists for the state ''TX'' and the client's state is ''Texas'', these do not match and the system would not apply tax. This scenario would require two tax rules, one for ''TX'' and another for ''Texas''.
 The system will apply any changes to subsequent invoices, but will not change existing invoices.
@@ Line 59: / Line 61: @@
 ==Multiple Invoices for the same Service==
-The system may generate multiple invoices for the same service with ''different'' due dates if the service has a due date in the past. This usually occurs with services that you import using the WHM/cPanel importer, or services  a staff member manually added, in which the Next Due Date is left at 00/00/0000. As this due date is in the past, WHMCS generates all invoices between then and today to ensure the client is has paid their balance in full.
+The system may generate multiple invoices for the same service with different due dates if the service has a due date in the past. This usually occurs with services that you import using the WHM/cPanel importer, or services  a staff member manually added, in which the '''Next Due Date''' is left at <tt>00/00/0000</tt>. As this due date is in the past, WHMCS generates all invoices between then and today to ensure the client is has paid their balance in full.
-To correct this, change the Next Due Date to the date of the client's next payment via their Products/Services tab. You can safely delete or cancel any erroneous invoices.
+To correct this, change the '''Next Due Date''' to the date of the client's next payment via their '''Products/Services''' tab. You can safely delete or cancel any erroneous invoices.
 {{troubleshooting}}

@@ Line 44: / Line 44: @@
 ==Tax Not Applied to Invoices==
-If tax is not applied to an invoice this means WHMCS believe it is not eligible under your tax rules. First ensure tax is enabled and the relevant '''Apply Tax''' options are ticked on the [[Tax/VAT|Tax Rules]] page, if it's an invoice for a product ensure this option is ticked in the product configuration.
+If tax is not applied to an invoice this means WHMCS believe it is not eligible under your tax rules. First ensure tax is enabled and the relevant '''Apply Tax''' options are ticked on the [[Tax Configuration|Tax Rules]] page, if it's an invoice for a product ensure this option is ticked in the product configuration.
 Secondly ensure the '''Tax Exempt''' checkbox is unticked on the client's Profile tab. This may have been ticked by a member of staff or our [[EU_VAT_Addon|EU VAT Invoicing Addon Module]] (if activated).

@@ Line 46: / Line 46: @@
 If tax is not applied to an invoice this means WHMCS believe it is not eligible under your tax rules. First ensure tax is enabled and the relevant '''Apply Tax''' options are ticked on the [[Tax/VAT|Tax Rules]] page, if it's an invoice for a product ensure this option is ticked in the product configuration.
-Secondly ensure the '''Tax Exempt''' checkbox is unticked on the client's Profile tab. This may have been ticked by a member of staff or our [EU_VAT_Addon|EU VAT Invoicing Addon Module] (if activated).
+Secondly ensure the '''Tax Exempt''' checkbox is unticked on the client's Profile tab. This may have been ticked by a member of staff or our [[EU_VAT_Addon|EU VAT Invoicing Addon Module]] (if activated).
 Finally the client might not match any of your tax rules, the state/country must be an '''exact match''' and is case sensitive. So for example if a tax rule exists for the state "TX" and the client's state is "Texas" these do not match and therefore tax would not be applied. Therefore two tax rules would be required, one for "TX" and another for "Texas".

@@ Line 25: / Line 25: @@
 There are a couple of reasons for invoices not generating, the most obvious are that there's a '''cancellation request''' for the service or it's in cancelled, terminated, fraud or expired '''status'''. For domains the '''Disable Auto Renew''' option could be ticked which stops renewal invoices being generated automatically. It could also be that the '''cron job''' is not being run, please refer to [[#Invoices/Payment Reminders not Generated|the above]] to check that.
-Invoices are only generated once the service's Next Due Date is within the Setup > Automation Settings > Invoice Generation value, so if the '''Next Due Date''' is n the future no invoice will be generated. For example if today's date is 01/01/2012:
+Invoices are only generated once the service's Next Due Date is within the Setup > Automation Settings > Invoice Generation value, so if the '''Next Due Date''' is in the future no invoice will be generated. For example if today's date is 01/01/2012:
 Next Due Date: 07/01/2012<br />