General and document settings

Configure invoice legacy Base64 QR content

Apply the invoice-only Base64 option when compliance mode is disabled. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM staffPermission: AdministratorModule v2.1.1
Jump to steps
Where to goAdmin Area → Setup → Settings → QR Code Compliance → Invoices
Before you start
  • 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 you’ll accomplish

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.

Follow these steps

  1. Set Compliance enabled to No in General.
  2. Go to the Invoices tab.
  3. Set Base64 legacy content according to the receiving system.
  4. Configure invoice legacy QR content.
  5. Generate and decode a test QR.

Fields and options to review

Action scopeApply the invoice-only Base64 option when compliance mode is disabled.
Module version2.1.0
NavigationAdmin Area → Setup → Settings → QR Code Compliance → Invoices
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • The Base64 option applies only to invoice legacy content and is not used for compliance signing URLs.

How to confirm it worked

  • 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.