How can I edit a customer invoice

[whoppe2001]

I understand you would want to , however in many (most?) jurisdictions invoices are considered a legal document and you are not allowed to edit them after they've been issued. 

With that said,  There are probably ways to stay legally compliant everywhere and still make it really simple to use.

 

[LittleCreek]

4 hours ago, whoppe2001 said:

I understand you would want to , however in many (most?) jurisdictions invoices are considered a legal document and you are not allowed to edit them after they've been issued. 

With that said,  There are probably ways to stay legally compliant everywhere and still make it really simple to use.

 

But it doesn't make sense to enforce a policy on everybody including ones where this is not a legal requirement. Maybe its "most." I don't care. I just care about my country and where I live. Don't force me to comply with other country's laws.

[RStream]

We are already running into issues with this change. We had to add the line of code to config  just to make some changes to a client wanting to upgrade their account which required the invoice to be updated.  We need the ability to edit an invoice. Service upgrades, downgrades, additions, removals, you name it.  This should obviously be something we choose to enable.. not force it on us.

REMOVE THIS FEATURE 

 

 

[d4zza]

I would love to know what county in the world doesn't let you amend and UNPAID invoice.

So utterly ridiculous that you need to just keep cancelling and generating invoices if you need to update an invoice.

QuickBooks lets you edit invoices.
Xero lets you edit invoices.
Sage lets you edit invoices.

[whoppe2001]

3 hours ago, d4zza said:

I would love to know what county in the world doesn't let you amend and UNPAID invoice.

So utterly ridiculous that you need to just keep cancelling and generating invoices if you need to update an invoice.

QuickBooks lets you edit invoices.
Xero lets you edit invoices.
Sage lets you edit invoices.

Honestly, quite a few.

Across much of Europe, an issued invoice is treated as an accounting document that must remain traceable for VAT and audit purposes. You generally should not be able to overwrite it in a way that destroys the original record, especially when the customer may already have booked the invoice and claimed input VAT from it.

If an issued invoice is wrong, the normal process is to credit or reverse it and issue a corrected invoice.

That said, I think you are focusing on the accounting mechanism rather than the actual usability problem. WHMCS should make this process almost invisible:

You click Edit invoice, make the required changes, and WHMCS automatically credits the original invoice and creates a corrected replacement. The customer receives the corrected invoice and pays it as normal.

There is no reason the user should have to manually cancel, recreate and resend everything. Preserving an audit trail is reasonable; making the workflow unnecessarily cumbersome is not.

 

[d4zza]

On 7/13/2026 at 3:25 PM, whoppe2001 said:

Honestly, quite a few.

Across much of Europe, an issued invoice is treated as an accounting document that must remain traceable for VAT and audit purposes. You generally should not be able to overwrite it in a way that destroys the original record, especially when the customer may already have booked the invoice and claimed input VAT from it.

If an issued invoice is wrong, the normal process is to credit or reverse it and issue a corrected invoice.

That said, I think you are focusing on the accounting mechanism rather than the actual usability problem. WHMCS should make this process almost invisible:

You click Edit invoice, make the required changes, and WHMCS automatically credits the original invoice and creates a corrected replacement. The customer receives the corrected invoice and pays it as normal.

There is no reason the user should have to manually cancel, recreate and resend everything. Preserving an audit trail is reasonable; making the workflow unnecessarily cumbersome is not.

 

The problem is, if WHMCS is integrated into your accounting software like mine it, it creates an EPIC mess of invoices and credit notes and and and

[whoppe2001]

Let me be very clear, i'm not defending the implementation. I'm defending why it had to be done 🙂

 

Edited 6 hours ago by whoppe2001

[LittleCreek]

Here is the original request: https://requests.whmcs.com/idea/prevent-invoices-from-being-changed

WHMCS went well beyond the original request. The original request was supposed to be optional.

The good news is that I can probably get claude.ai to build a work around. Its just a database that be changed. The invoice is not really immutable. 

[whoppe2001]

Where I stand is this: They are moving in the right direction and the idea here is correct for any jurisdiction.

However the current implementation needs refinement. Once that is done (assuming they'll listen) I dont see how it makes a material difference for you if you edit an existing invoice or if by the act of editing it credits the existing and creates a new invoice).

Further behaviour should be driven by knobs which define whats wanted.

 

 

[d4zza]

17 minutes ago, LittleCreek said:

Here is the original request: https://requests.whmcs.com/idea/prevent-invoices-from-being-changed

WHMCS went well beyond the original request. The original request was supposed to be optional.

The good news is that I can probably get claude.ai to build a work around. Its just a database that be changed. The invoice is not really immutable. 

My argument is though, use any DECENT accounting software such as QuickBooks, Xero, Sage, etc. Invoice can be edit, amended, etc.

 

[Juanzo]

22 minutes ago, d4zza said:

My argument is though, use any DECENT accounting software such as QuickBooks, Xero, Sage, etc. Invoice can be edit, amended, etc.

 

Agreed, if even dedicated accounting software allows this, no need for WHMcs to complicate our work.

I hope they keep it optional.

[LittleCreek]

They closed the request to keep it optional so they are not even going to listen to us. https://requests.whmcs.com/idea/making-non-draft-invoices-are-immutable-optional

Maybe if we opened 1000 requests they would listen.

[d4zza]

24 minutes ago, LittleCreek said:

They closed the request to keep it optional so they are not even going to listen to us. https://requests.whmcs.com/idea/making-non-draft-invoices-are-immutable-optional

Maybe if we opened 1000 requests they would listen.

I love how they say, here is the work around.

But when you enable the workaround, in the backend it tells you that it will be disabled in future releases.

[bear]

2 minutes ago, d4zza said:

I love how they say, here is the work around.

But when you enable the workaround, in the backend it tells you that it will be disabled in future releases.

It's always been the way of things here. Cause some workflow hardship, claim it was asked for, then when complaints get loud enough grant a temporary reprieve. Less complaints in general when they "give you time to reflect on fixes" kind of feeling and then re-pull that rug from under it.