Create a QR compliance record by generating a PDF | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/create-a-qr-compliance-record-by-generating-a-pdf Publisher: Pixie Technologies LLC Record creation, snapshots and PDF output Create a QR compliance record by generating a PDF Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Trigger get-or-create through the supported PDF close hook. Audience: CRM staff; Permission: Administrator or authorised staff with normal document access; Module v2.1.1; Where to goAdmin Area → Sales → Open supported document → View or download PDF 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 this guide helps you do Trigger get-or-create through the supported PDF close hook. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow. Follow these steps - Enable compliance and the relevant document QR setting. - Go to an invoice, payment, credit note, estimate or proposal. - Generate its PDF. - Go to QR Compliance Records and locate the new pending record. Fields and options Action scopeTrigger get-or-create through the supported PDF close hook. Module version2.1.0 NavigationAdmin Area → Sales → Open supported document → View or download PDF EvidenceVerify the stored record, status, output, email, event or log produced by the code path. Rules and limits - Generating the PDF is the creation trigger; there is no separate Create Record form. - The unique document-type/document-ID rule reuses an existing record. Check 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. Related guides QR Code Compliance module overview (https://pixiecrm.com/help-centre/qr-code-compliance-module-overview)Understand supported QR document types (https://pixiecrm.com/help-centre/understand-supported-qr-document-types)Understand QR document and client snapshots (https://pixiecrm.com/help-centre/understand-qr-document-and-client-snapshots)Export invoices and sales PDFs (https://pixiecrm.com/help-centre/export-invoices-and-sales-pdfs)Create a credit note (https://pixiecrm.com/help-centre/create-a-credit-note)