Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Reports and exports · How-to guide

Email a Bilty report PDF

Send the generated report as a PDF attachment through the existing Britixo mail stack and verify the report action log. The guide follows the Help Centre standard: exact route, prerequisites, ordered steps, verification and operational boundaries.

Audience: Administrators and authorised Bilty operations staffPermission: Relevant Bilty Management capabilityModule v1.0.0
Jump to steps
Where to goBilty Management → Reports → Email PDF
Before you startRequired access: Relevant Bilty Management capability. Work on the correct tenant and record. Use least privilege and review any dependency or protected workflow warning before continuing.

What you’ll accomplish

Send the generated report as a PDF attachment through the existing Britixo mail stack and verify the report action log. Bilty Management keeps drafts, issued records, public capability links, finance, integration events and audit evidence as connected but separately verifiable records.

How the workflow fits together

Build, save, export and email Bilty reports through the Enterprise Report Centre. Use the module's current status, permission checks, warnings and linked records to decide the next supported action. Where a downstream invoice, WhatsApp queue item, webhook, PDF, POD record or audit event applies, verify it separately.

Follow these steps

  1. Go to Bilty Management → Reports → Email PDF.
  2. Confirm the active tenant, intended Bilty record and your permission before entering or changing data.
  3. Complete the supported workflow: Send the generated report as a PDF attachment through the existing Britixo mail stack and verify the report action log.
  4. Review the displayed validation, dependent fields and any privacy, finance or integration warning before continuing.
  5. Save, submit or run the action once and wait for the module response.
  6. Reopen the relevant register or record and verify the final status, linked records and audit evidence.

Fields and decisions to review

FieldsChoose only report fields permitted for the current staff user.
FiltersUse Bilty filters and grouping to define the dataset.
ExportsPDF and XLS exports use the current report definition.
EmailPDF email delivery uses the existing Britixo mail stack and is audit-logged.

Record, audit and evidence checks

Reopen the relevant Bilty record or register and confirm its identifier, current status, related parties, timestamps and connected evidence. Check the audit/compliance, payment, public-link, report, API, webhook or WhatsApp evidence that applies to this workflow rather than relying only on a success alert.

How to confirm it worked

Return to Bilty Management → Reports → Email PDF or the resulting register and verify that the stored state matches the intended action. For any downstream automation, confirm the downstream record or queue/log entry as a separate completion check.

Technical basis for this guidance

This guide was checked against controllers/Bilty_management.php; models/Bilty_management_model.php; views/admin/reports.php; libraries/pdf/Bilty_report_pdf.php. It documents only behaviour exposed or enforced by the supplied module; internal secrets, raw signature payloads and unsupported future workflow assumptions are intentionally excluded.

Controls, checks and common mistakes

  • Work only on the intended tenant and Bilty record.
  • Do not bypass a missing permission, validation blocker or protected status by changing unrelated settings.
  • Verify the stored record, downstream integration state and audit evidence after any material action.
Data and workflow safetyConfirm the exact Bilty, authorised audience and final stored status before issuing, publishing a link, recording payment, changing shipment state or sharing a document.
Browse connected topics:reports and exportsbilty management
Build a Bilty reportChoose Bilty report fields, filters and groupingSave and reuse a Bilty report definition