QR Code Compliance module overview
This guide explains PDF QR generation, public recipient signing, cryptographic evidence, admin review and verified stamps. 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.
Where to goAdmin Area → Setup → Settings → QR Code Compliance
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
Understand PDF QR generation, public recipient signing, cryptographic evidence, admin review and verified stamps. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Configure general and per-document QR settings.
- Generate a supported document PDF to create or reuse its compliance record.
- Ask the authorised recipient to scan and sign.
- Check the locked record in QR Compliance Records.
- Regenerate the PDF to display the verified stamp when enabled.
Fields and options to review
Action scopeUnderstand PDF QR generation, public recipient signing, cryptographic evidence, admin review and verified stamps.
Module version2.1.0
NavigationAdmin Area → Setup → Settings → QR Code Compliance
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- Supported document types are invoice, payment, credit note, estimate and proposal.
- A record is created on PDF generation only when compliance mode and that document type are enabled.
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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.