How to Customize Your Invoices in Odoo:
Templates, Fields & Design — 2026 Guide

In 2026, the Invoice Is Both a Brand Asset and a Compliance Object

The 2026 fiscal year has redefined what an invoice is supposed to do. It is no longer a static demand for payment—it is a structured data object consumed by tax authorities, a branded touchpoint your customer sees the moment money is on the line, and a machine-processable record that has to survive audits, e-invoicing networks, and AI-driven reconciliation engines. Odoo 19, with the Odoo 20 reveal scheduled for the OXP events in September 2026, is the version where customization decisions stop being cosmetic and start carrying real financial weight.

The pricing climate makes that point unavoidable. As of April 2026, Enterprise subscriptions still running on versions older than v17 are subject to a 25% legacy version surcharge, layered on top of a 30% North American price increase and a 7% annual indexation. Customizing invoices well now means migrating onto a current, supported version, then building on top of native layouts, Studio extensions, and QWeb inheritance in a way that survives the next two upgrades.

This guide walks through every layer of invoice customization in 2026: the document layout engine, dynamic sections, custom fields, Studio report editing, QWeb & XPath engineering, Peppol e-invoicing, EPC QR codes, AI-assisted automation, and the troubleshooting playbook for the issues that actually break PDFs in production.

The 2026 Migration Landscape: Why Your Invoice Strategy Starts With a Version Decision

Odoo’s 2026 roadmap follows a three-wave migration strategy that puts finance and compliance first. The reason is simple: mandatory e-invoicing across Europe, parts of Latin America, the Gulf, and an expanding list of public-sector buyers in North America requires that financial documents be both human-readable and machine-processable. If you customize an invoice on a legacy version, you are customizing a document that no longer matches the structural data integrity your tax authority expects.

On the developer side, the architectural shift continues. Classic XML-RPC integration endpoints are now scheduled for removal in v22, giving teams a transitional window to migrate external systems pulling invoice data toward the more efficient JSON-2 protocol. Treat that window as part of your invoice strategy, not as a separate project: the way invoices are pulled, signed, and rendered downstream is what makes or breaks a migration.

Native Document Layout: The No-Code Foundation Every Invoice Inherits

Before touching XML or Python, every Odoo invoice should be configured at the Document Layout level. This is the no-code engine that defines the visual identity shared across quotations, sales orders, invoices, and credit notes. Get this right and most of your invoice customization work disappears.

Where to Find It

Navigate to Settings › General Settings › Companies › Document Layout and click Configure Document Layout. The modal exposes four layout frameworks, each tuned to a different industry rhythm:

Step-by-Step: Native Layout Configuration

1. Open the dashboard — log into the v19 environment and open the Accounting or Invoicing module.
2. Settings › Configuration — scroll to the Companies block.
3. Configure Document Layout — pick the framework that matches your brand position.
4. Branding — upload a PNG or SVG logo, set primary & secondary colors via hex picker, choose alignment (left / center / right).
5. Typography & background — pick a corporate font (v19 expanded the rich-text font registry; no custom CSS required for most cases) and select a background style (Blank, Demo logo, Custom upload).
6. Tagline & footer — add the corporate motto, certifications (ISO numbers, B-Corp status, etc.), and the legal footer line.
7. Continue — saves the global settings and applies them to every external document including invoices.

Odoo Studio: Adding Custom Fields and Editing Reports Without Writing a Module

Studio occupies the middle ground between native settings and full code. It’s the right tool when you need a field that doesn’t exist out of the box, a column on the printed PDF, or a conditional block—without the overhead of shipping a custom module.

Step-by-Step: Add a Custom Field via Studio

1. Open an invoice and click the wrench icon (Toggle Studio) in the upper right.
2. Pick the Form view; Studio displays a sidebar with field types.
3. Drag & drop the field type you need (Monetary, Selection, Many2One, Related, etc.) onto the form.
4. Configure properties:
   • Label — e.g. “Environmental Fee”
   • Technical name — Studio prefixes with x_studio_
   • Visibility — required, invisible, or domain-driven
   • For relational fields, set the target model (e.g. res.users for a secondary salesperson)
5. Close Studio — you’re back in the standard interface with the field live.

The Studio Report Editor

The PDF report editor in v19 deviates from the form editor. Instead of dragging fields, you compose templates with slash commands and conditional blocks:

QWeb & XPath: Engineering Invoice Customizations That Survive Upgrades

For anything beyond Studio’s ceiling, the right answer is QWeb inheritance from a custom module. The cardinal rule is the same it’s always been: inherit, don’t override. Direct edits to account.report_invoice_document are wiped on every upgrade. Inherited templates survive because the ORM applies them as a layer on top of the base.

Anatomy of a Custom Invoice Report

Every report has two pieces: an ir.actions.report record (the metadata) and a QWeb template (the structure). The minimum viable custom invoice report:

For a developer-only deep-dive on QWeb invoice templates—PO numbers, project codes, wire instructions, multi-company layouts, conditional content—see our companion guide Level Up Your Billing: A Step-by-Step Guide to Customizing Odoo Invoices.

<odoo>
  <record id="action_report_custom_invoice"
          model="ir.actions.report">
    <field name="name">Premium Invoice Template</field>
    <field name="model">account.move</field>
    <field name="report_type">qweb-pdf</field>
    <field name="report_name">
      my_module.custom_invoice_template
    </field>
    <field name="binding_model_id"
           ref="account.model_account_move"/>
  </record>

  <template id="custom_invoice_template"
            inherit_id="account.report_invoice_document">
    <xpath expr="//div[@name='reference']"
           position="after">
      <div t-if="o.x_customer_po"
           class="col-auto col-3 mw-100 mb-2">
        <strong>Customer PO:</strong>
        <p class="m-0" t-field="o.x_customer_po"/>
      </div>
    </xpath>
  </template>
</odoo>

XPath Position Cheat Sheet

Rendering Binary Images on the PDF

The single most common technical hurdle in v19 invoice work: product photos render in the web preview but disappear from the PDF. The wkhtmltopdf renderer can’t fetch binary image fields the way the browser does. The fix is to embed them as base64 via the image widget:

<span t-esc="line.product_id.image_128"
      t-options="{
        'widget': 'image',
        'max_width': '64',
        'class': 'rounded'
      }"/>

Peppol, EPC QR Codes, and Total in Words: Customizing for Compliance

The 2026 Wave 1 focus on finance is driven by mandatory e-invoicing. Customizing an invoice without integrating Peppol, EPC QR codes, and locale-specific structures is incomplete work—it’ll fail the moment you ship cross-border or onboard a public-sector customer.

Peppol Activation in Odoo 19

1. Open Accounting › Configuration › Settings › Electronic Invoicing and click Activate Peppol.
2. Provide the Peppol endpoint identifier (VAT number or GLN).
3. For each customer, set the e-invoice format on the contact’s Accounting tab (Factur-X, UBL, CII, etc.).
4. When the invoice is sent, v19 attaches the structured XML alongside the PDF automatically.

EPC / SEPA QR Codes

1. In Accounting › Configuration › Settings, enable QR Codes under Customer Payments.
2. Confirm the bank journal carries both IBAN and BIC.
3. Populate the Recipient Bank field on the invoice Other Info tab.
4. Odoo auto-renders the EPC QR code at the bottom of the printed document; SEPA-area customers can pay via banking-app scan.

Region-specific equivalents are supported through localization modules: Pix (Brazil), FPS (Hong Kong), VietQR (Vietnam), and the various GCC localizations.

Total Amount in Words

In several jurisdictions the literal spelled-out total is a legal requirement to prevent post-print tampering. Enable it under Accounting › Configuration › Settings › Customer Invoices › Display Total in Letters. For per-journal control (uppercase forcing, language overrides for bilingual invoices), several OCA-grade modules expose journal-level configuration without forking the core.

AI Inside Invoicing: OCR, Ask AI, and Vibe Coding

In Odoo 19, AI is the interaction layer of the ERP, not a sidecar. For invoice work, that translates into three concrete capabilities you should design your customizations around:

• OCR + learning preferences — the engine that digitizes incoming vendor bills also feeds tailored templates per supplier. Manual corrections train a per-vendor profile that improves with use.
• Ask AI agent — Ctrl + K or the top-bar button; conversational queries over invoicing data, summarization of dispute history, automatic translation of chatter messages, semantic search (“find the invoice for the sustainability audit last September”).
• Vibe coding & image generation (v19.2) — describe a portal or document layout in natural language, generate product visuals directly inside the ERP. The same product imagery flows automatically into your custom invoice templates.

When designing custom invoice fields, prefer well-named, well-typed fields over free-text Char dumps. The Ask AI agent and the OCR template engine reason about your data through field labels and types—naming a field x_customer_po_number with help text yields dramatically better automation than x_studio_field_4d2a1.

Three Production Pitfalls That Break Invoice Customization

The Odoo Academy (e-)Invoicing Curriculum

The 2026 Academy track on e-invoicing is structured as a 2-hour 2-minute progression that walks teams from the database basics through Peppol, regional localizations (Vietnam Form 01/GTGT, GCC/Saudi, etc.), and accountant transmission. It pairs well with this guide as a hands-on companion — full course on Odoo Academy: (e-)Invoicing.

Open the Odoo Academy (e-)Invoicing course →