InvoiceThang guide
Troubleshooting and administration
Resolve delivery, numbering, recurring, and mobile problems with the right evidence.
A button does nothing
Confirm the record permits that action: only drafts can be edited; reminders require a sent invoice with a balance; Send Receipt requires a fully paid standard invoice and a completed payment. Proxies omit customer delivery actions.
Confirm any action prompt and inspect dashboard alerts and the invoice timeline. Refresh the page to load updated assets. When reporting a problem, include the page, invoice number, action label, and visible error without posting customer tokens or credentials.
Recurring invoices are missing
Check that the schedule is Active, the client is active, and the next run date is due. Inspect occurrence history before generating again. A generated draft may be waiting for delivery retry.
Check the cPanel cron command, supported PHP version, timezone, and output. A failed email and a failed invoice generation are different problems: retrying a delivery should reuse the existing invoice.
Mobile layout or scrolling
Close any open modal or menu and check whether the problem affects the whole page, a search results list, or an embedded document. Record that distinction when reporting it. Native loader and WebView changes require the current APK; website CSS changes may need a fresh page load.
The dashboard uses expandable cards on small screens to reduce horizontal overflow. If document text overlaps, note whether it occurs in the hosted invoice, receipt, credit note, or downloaded PDF so the correct template can be fixed.
Installation requirements
The current source requires PHP 8.5 or newer with curl, json, pdo, and pdo_mysql, plus MySQL-compatible storage. Use the same supported PHP handler for web requests and cron. This supersedes the project’s early PHP 7.4 deployment target.
Private configuration supplies the application URL, database and email credentials, optional Turnstile keys, and optional InvoiceHelper settings. Keep credentials outside version control. Storage and backups are protected by server rules; public branding uploads must remain non-executable. The installer is disabled unless deliberately enabled.
Invoice