Skip to main content

Invoice Template Selection and Priority

Automatically apply invoice templates using client or subsidiary defaults, ensuring consistent PDF layout, branding, and emails.

Updated this week

In Productive, invoices use templates to control their PDF layout, content, and email formatting.

When creating an invoice, Productive automatically determines which template to apply based on a priority system, ensuring consistency while minimizing manual selection.

How Invoice Templates Work

Each template defines how your invoice looks, including:

  • Layout and design (via Document Style)

  • Included fields (e.g., totals, custom notes, tax IDs)

  • Logo and company branding

  • Email subject and body (prefilled when sending the invoice)

πŸ“Œ Templates can be created globally or specifically for a subsidiary.

Automatic Template Selection

When you create an invoice, Productive chooses the template using the following hierarchy:

  1. Client company default invoice template (set in CRM > Companies > Invoice Template)
    ​

  2. Subsidiary default invoice template (set in Settings > Company Info > Subsidiaries > Default Invoice Template)
    ​

  3. First template in alphabetical order if neither client nor subsidiary default is set
    ​

πŸ“Œ This ensures invoices always have a template applied, even if no defaults are configured.

Editing and Using Invoice Templates

  • Navigate to Settings > Document Templates.

  • Select an existing invoice template or click Add Document Template.

  • Customize layout, branding, and email settings in the editor.

After saving, you can assign the template as a default in one or both of the following places:

  1. Client-level default: Go to CRM > Companies, select the client company, and choose the template as the default for that client.

  2. Subsidiary-level default: Go to Settings > Company Info > Subsidiaries, select the subsidiary, and choose the template as the default for that entity.

Once defaults are set, the template will automatically be applied based on the template selection hierarchy described above.

Did this answer your question?