PDF generation, branding and files

Configure company details used in Letter Manager PDFs and emails

Populate the company settings read by the PDF header, closing signature and email body.

Audience: CRM staffPermission: AdministratorModule v1.0.0

Exact navigationAdmin Area → Setup → Settings → Company Information / Finance invoice company settings

Before you begin

Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.

What this guide covers

Populate the company settings read by the PDF header, closing signature and email body. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Set invoice company name.
Set address, city, state, country and postcode/ZIP.
Set invoice company phone number.
Set main domain, company domain or company website.
Generate and email a test letter and verify all rendered details.

Fields, choices and supported possibilities

Action scopePopulate the company settings read by the PDF header, closing signature and email body.

Module version1.0.0

Exact routeAdmin Area → Setup → Settings → Company Information / Finance invoice company settings

EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.

Code-backed validations and workflow rules

Address helper checks several option-key fallbacks and builds address line 1 plus a city/state/country/postcode line.
United Kingdom, UK or GB is rendered as England by the v8 country helper for this layout.
Website fallback order differs between PDF and email code, so test both outputs.

Expected result and verification

The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
Any warning, missing file or failed send is investigated rather than bypassed.

Security, privacy and operational checks

Apply least privilege and verify recipient identity before sending or exposing public links.
Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
Test configuration and deployment changes with controlled records before production-wide use.
Interpret email opens and e-signatures according to their documented technical limitations.