Prepare the change
Review the target release's PHP/database requirements, exact update entitlement and supplied migration instructions. Permission to use the installed version does not automatically grant every later version. An updates-only plan assumes the required existing base entitlement.
Take a coordinated database, key and file backup. Record the current version and test the proposed procedure on an isolated restored copy with email and live provider access disabled.
Use the supported release procedure
The normal customer package is a complete publisher-signed archive with included production dependencies. Preserve its executable bytes. Do not run Composer, rebuild assets or regenerate autoload files inside a signed installation.
Legacy browser ZIP code deployment and individual executable module replacement are disabled for this independent release. The Modules & updates screen is not permission to upload arbitrary code or bypass the signed release process. The fresh installer is not an upgrade, reset or migration tool.
Verify after updating
Keep the original configuration, encryption keys, private storage and external licence identity according to the supplied procedure. Check administrator and financial-user sign-in, business/account boundaries, drafts, existing issued documents, attachments, balances and approvals. Check licence refresh, mail and payment-request jobs.
For financial or payment work, confirm actual provider outcomes before retrying pending operations. Do not treat an HTTP success page as proof that a charge or email completed exactly once.
If no upgrade path is supplied for your current and target versions, obtain a reviewed procedure before changing a working accounting installation.