Feature reference

Reports, exports, audit history and WHMCS review

Review operational totals and imported history without silently migrating or repricing financial records.

Platform
Laravel / PHP
Laravel
13
PHP
8.4
Database
Dedicated MySQL-compatible production database

Reports and exports

Open Business → Reports with reports.view. Choose the relevant period, seller and supported report/export kind. Totals remain separated by currency; a single combined sum without an explicit conversion basis would be misleading. The application does not turn a saved conversion rate into a rewrite of issued invoices or settlement history.

Exports are sensitive financial/customer data. Download through the authenticated route and store privately. An export button does not grant permission to records the staff member cannot otherwise access. Compare totals with original ledger records and provider statements before relying on a report for accounting.

Audit and operational history

Review customer activity, provider actions, mail recovery, automation runs and extension failures through their respective workspaces. A successful application action may mean queued, submitted or confirmed depending on its contract; inspect its actual outcome. Error messages are sanitised to avoid exposing customer data or credentials. Preserve private application logs for the owner instead of posting raw transcripts publicly.

WHMCS migration review

The newer source groups these workflows in Migration centre; earlier licensed releases use WHMCS migration review. This workspace is restricted to an administrator with report/settings capabilities. Imported archives and reconciliation show existing history, server/group inventory and unresolved mappings. They are not a general promise of one-click automatic WHMCS migration into a fresh installation. See the migration centre guide for the newer workflow.

The fresh-install procedure requires an empty database. Never point it at a WHMCS database. Migration tools require the separate reviewed migration plan, private archive protection, backup, reconciliation and accepted cutover evidence. Imported provider credentials, old price options and account IDs are not assumed safe for native automatic fulfilment.

Accept a reconciliation

Check owning customer, seller, currency, invoices/receipts, recurring periods, domains, service provider identities and unresolved attempts. Protect immutable imported records until the displayed review process permits changes. Do not change stored monetary rows or old invoice numbers directly to make a report reconcile. Keep original archives alongside verified backups.

← All EmailaBiller guidesGet help →

Need help with EmailaBiller?

Tell us the product version and what you are trying to do. Keep passwords and private keys out of your message.

Contact Emaila