Record creation, snapshots and PDF output

Understand supported QR document types

Follow this guide to use QR compliance on the five live service classes and do not claim expense support. 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: Staff loginModule v2.1.1
Jump to steps
Where to goAdmin Area → Sales → Invoices / Payments / Credit Notes / Estimates / Proposals
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

Use QR compliance on the five live service classes and do not claim expense support. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Configure only the required supported tabs.
  2. Generate the document PDF.
  3. Verify the QR appears.

Fields and options to review

Action scopeUse QR compliance on the five live service classes and do not claim expense support.
Module version2.1.0
NavigationAdmin Area → Sales → Invoices / Payments / Credit Notes / Estimates / Proposals
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • Invoice, payment, credit_note, estimate and proposal are accepted.
  • An ExpenseQRCode class is present but expense integration is disabled/unused in the supplied release.

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.