Understand e-Invoice version 1.0.0 limitations | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-e-invoice-version-1-0-0-limitations Publisher: Pixie Technologies LLC Bulk export and operational limitations Understand e-Invoice version 1.0.0 limitations Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Follow this guide to use the supplied release without claiming unsupported or defective behaviour works. Audience: CRM staff; Permission: Staff login; Module v1.0.0; Where to goAdmin Area → Setup → Settings → Finance → e-Invoice / Utilities → Bulk Export 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 Use the supplied release without claiming unsupported or defective behaviour works. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow. Follow these steps - Use validated templates and individual invoice/credit-note View/Download. - Test invoice email attachment before production. - Treat credit-note email attachment and bulk export as requiring controlled verification/correction. - Check bulk export date/status contents. Fields and options Action scopeUse the supplied release without claiming unsupported or defective behaviour works. Module version1.0.0 NavigationAdmin Area → Setup → Settings → Finance → e-Invoice / Utilities → Bulk Export EvidenceVerify the stored record, status, output, email, event or log produced by the code path. Rules and limits - No network transmission standard, government portal submission, API, webhook, scheduled cron export, UBL/PEPPOL schema validator or digital signature is implemented by this module. - Template validation checks syntax, not compliance with a jurisdictional e-invoice standard. - The bulk period field wiring and credit-note exporter defects are documented above. 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 e-Invoice module overview (https://pixiecrm.com/help-centre/e-invoice-module-overview)Understand e-Invoice local-file security (https://pixiecrm.com/help-centre/understand-e-invoice-local-file-security)Generate and export an e-invoice (https://pixiecrm.com/help-centre/generate-and-export-an-e-invoice)Send an invoice to a customer (https://pixiecrm.com/help-centre/send-an-invoice-to-a-customer)