Open the invoice and record its number, status, original amount, current balance, transactions and ledger entries. Determine whether the error is in a draft description, published price or tax field, payment allocation, late fee, or underlying service configuration. Those problems should not all be handled by recreating the same charge.

Check whether the customer has paid, whether credit was applied, and whether the invoice triggered a service renewal or domain action. If payment has already caused an external operation, correcting the document does not automatically undo that operation.

With the required invoice-management permission, open Manage Invoice for a Draft. Correct its items and settings, verify the total and dates, then choose the intended publishing action. Review the customer's identity and tax details before publication because this is the point at which ordinary content editing ends.

1. Open the client's Invoices tab and select the invoice requiring correction.
2. Use Duplicate Invoice to create a new Draft. Record the relationship between the original and replacement.
3. Edit the new draft and review every copied item, date and payment method. Confirm that the replacement contains only the intended charges.
4. Publish the corrected version, choosing whether to send its creation email at that point.
5. Return to the original invoice and use the documented cancellation action. Check its adjustment record and confirm that the customer is not left with two payable versions.
6. Review the customer's invoice list and explain which document replaces which. Include the new payment link when payment is still due.

The duplication procedure does not remove the need to reconcile previously received funds. Check how existing payments or client credit must be allocated under the approved accounting process. Do not record the same incoming payment twice simply to mark the replacement paid.

For service-linked invoices, compare the service's paid-through period before and after the correction. A second payment event against a copied renewal charge could have operational consequences. If the correct treatment is uncertain, keep the draft unpublished while the billing owner reviews the allocation and automation.

Ask a reviewer to follow the complete document chain from the customer's invoice list. They should be able to identify the payable document, any adjustment and the payment allocation without relying on an administrator's memory. Include that check before sending a revised payment request.

WHMCS creates credit and debit notes for applicable actions such as cancellation, refunds, applying credit or late fees. Review those documents in the invoice ledger together with the payment history. The current amount due is not always identical to the original published total.

Avoid direct database edits that bypass this model, including older examples intended for editable invoice versions. Keep the reason for correction, reviewer and related service record in the internal notes. Finally, fix the source of the error, such as an incorrect recurring price or tax rule, so the next renewal does not repeat it.

• Why is a WHMCS invoice still unpaid after the customer paid?
• Process and reconcile a WHMCS refund
• Configure WHMCS tax rules for your approved billing policy
• Change a WHMCS service due date without creating a billing gap

• WHMCS: reissue an invoice
• WHMCS 9.0 invoice management
• WHMCS credit and debit notes
• WHMCS Products/Services tab