Keep a complete private backup
Back up the database, config/accounts.php and private storage/ together. The original encryption keys must remain paired with the data. Store backups outside the web root with restricted access.
Prove the recovery
Restore to a private isolated environment first. Verify balances, documents, attachments and decryption before planning a live cutover. Review mail, payment connections and queued work so the test copy cannot contact customers or providers accidentally.
Change the licensed domain
The listed one-time USD 69 package covers one changeable domain. Prepare the new hostname and HTTPS, use the available licence-transfer process, then update the installation's canonical address in accordance with its release instructions. A transfer does not authorize two live production copies.
Do not upload executable ZIP updates through a legacy browser tool or force a reinstall to change a hostname. Use a reviewed product release and the matching backup procedure. Updates, branding and support terms are confirmed separately with the purchase.
Prepare the host
Use PHP 8.2+ on a 64-bit host with PDO MySQL, OpenSSL, mbstring, cURL, fileinfo, GD, Zip, session, ctype and JSON. Create a new empty MySQL 8.0+ or MariaDB 10.6+ database with a dedicated user.
Extract the verified release outside the web document root. Serve only its public/ directory through HTTPS. The application root, config/, storage/, install/, schema/, engine/ and modules/ must remain private.
Check and enable setup
From the private application root run:
php bin/install.php --check
php bin/install.php --enable-web
Keep the generated setup token private. It expires after one hour and is entered into the form rather than placed in the URL. Open the HTTPS workspace and create your own administrator and first business. No default administrator password is supplied.
Finish deliberately
Review issuer details and numbering before enabling billing. Add separate financial users and assign their businesses. Configure SMTP and any payment connections with your own credentials.
Back up config/accounts.php, private storage/ and the database together. Never delete setup state to force installation into an existing database. Use the exact release's interrupted-setup instructions and retain the original independent encryption keys.
Configure the business first
Confirm the issuing company, invoice numbering, currency and approval policy. Then configure the payment connection for that installation using the administrator's own merchant credentials.
The included product workflows support configured Stripe and eWAY invoice payments and payment-request links. eWAY collects AUD using the saved conversion quote. A browser's success page alone is not evidence that an invoice was settled.
Verify before accepting payments
Complete the gateway's test procedure and confirm a verified receipt and correct invoice allocation. Review the gateway's currency and merchant requirements. Do not switch to live payments just because configuration was saved.
Configure workers once
The release includes bin/process-mail.php for outgoing mail and modules/customer-payment-requests/bin/worker.php --run for bounded payment-request reconciliation. Follow the supplied operations guide to schedule each job with the installation's PHP executable.
These workers can send mail or contact configured providers. Avoid duplicate jobs. Review outstanding requests and reconcile provider outcomes before attempting another charge.
Review the first business
After installation, confirm the business and issuing-company details, legal identity and invoice numbering before creating real invoices. Set up the business's currencies, bank or cash accounts and posting policies.
Add local users
Open Administration → Users. Create the people who need access and assign the appropriate local roles. Assign Owners and Accountants to the businesses they are responsible for and grant only the payment accounts they need.
The installation administrator manages system configuration. Financial entries still follow the saved approval policy; administrator access is not automatic approval for posting.
Check access before using real records
Use a controlled test with the intended role. Confirm that the user can reach assigned businesses and accounts and cannot see unrelated ones. Review permissions when somebody changes responsibility or leaves the business, and revoke obsolete sessions.
This product does not import users or sessions from Hub or PCMO. Each installation owns its own users, keys and settings.
