Configure invoice legacy Base64 QR content
Apply the invoice-only Base64 option when compliance mode is disabled.
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
Apply the invoice-only Base64 option when compliance mode is disabled. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Set Compliance enabled to No in General.
- Open the Invoices tab.
- Set Base64 legacy content according to the receiving system.
- Configure invoice legacy QR content.
- Generate and decode a test QR.
Fields, choices and supported possibilities
Action scopeApply the invoice-only Base64 option when compliance mode is disabled.
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 Base64 option applies only to invoice legacy content and is not used for compliance signing URLs.
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.