Configure Invoice QR code settings
Enable or disable QR output, set PDF coordinates and configure legacy content for invoice PDFs.
Exact navigationAdmin Area → Setup → Settings → QR Code Compliance → Invoices
Before you begin
- Use an authorised account and confirm the source CRM record or setting is correct.
- Follow the exact route shown above; do not force database values to imitate a completed action.
What this guide covers
Enable or disable QR output, set PDF coordinates and configure legacy content for invoice PDFs. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Set Show Invoice QR Code to Yes or No.
- Enter both Invoice QR X and Y coordinates for manual placement, or leave a coordinate blank to use the automatic current PDF position.
- When compliance is disabled, review the legacy Invoice QR content and merge fields.
- Save and generate a test PDF.
Fields, choices and supported possibilities
Action scopeEnable or disable QR output, set PDF coordinates and configure legacy content for invoice PDFs.
Module version2.1.0
NavigationAdmin Area → Setup → Settings → QR Code Compliance → Invoices
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- The supplied default is enabled.
- When compliance is enabled, QR content is the secure public signing URL rather than the legacy merge-field textarea.
Expected result and verification
- The requested record, output or setting is created or updated through the supported module flow.
- Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action.
- An error message is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify the correct customer, lead, sales document or recipient before processing.
- Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy.
- Test configuration changes with controlled records before production-wide use.
- Retain or delete evidence only under an authorised retention process.