We noticed that in Acumatica, the Customer field on a Project can still be changed even after the project is active and has existing transactions or invoices.
From an accounting and audit standpoint, this appears risky because the existing AR invoices remain linked to the original customer, while new invoices would go to the updated customer — which can lead to inconsistent reporting and billing.
I just wanted to confirm — is there a specific business scenario or setup where this behavior is intentional, or am I missing something in the configuration that should prevent changing the customer once transactions exist?
If it is intentional, could you please clarify Acumatica’s recommended best practice for handling situations where a project’s customer needs to be changed after billing has started (for example, whether the preferred approach is to close the old project and create a new one under the new customer)?

