How to add a footer, bank details, and other custom content to Lago invoices

Lago's invoice PDF has a fixed structure, but you can still add your own text three ways: a footer for static text that repeats on every invoice, custom sections for structured blocks like bank details or a PO number, and customer metadata for short reference fields. Which one to reach for depends on the kind of content and how often it changes.

The footer, for static text

Use the footer for payment terms, legal notices, or a standard message. In the dashboard, set it under Settings, then Billing entities, then your entity, then Invoice settings, in the Invoice default footer field. Exact menu labels can differ depending on whether multiple billing entities are enabled, so it is worth a quick confirm against your live instance.

It can also be set via the API, as the invoice_footer field inside billing_configuration on the Update billing entity, Update organization, and Update customer endpoints, up to 600 characters. A footer set on a customer overrides the billing entity's footer for that customer's invoices. The footer renders as plain text at the bottom of the invoice.

Custom sections, for bank details and structured content

Use custom sections for richer content such as your bank account, IBAN, or RIB, a currency conversion note, or a PO number. Create them under Settings, then Invoice settings, then Invoice custom sections, then Add. Each section has a title and a free-form text body, and there is no limit on how many you can create.

Sections can apply at several levels: a billing-entity default, an override per customer, or, through the API, per subscription, per wallet top-up, or per one-off invoice. When more than one applies, the most specific wins, in this order: one-off invoice, then subscription or wallet top-up, then customer, then billing entity. A section renders as a distinct, clearly labeled block at the bottom of the invoice, which reads better than metadata for anything multi-line. For content that belongs to a single customer, a dedicated section applied only to that customer is the supported path, though it does not scale to tens of thousands of customers.

When section content is captured on an invoice

Sections are captured on each invoice at the moment it is generated. A draft invoice picks up your latest changes on refresh, but once an invoice is finalized it keeps a fixed copy of its sections. So if the content has to differ per invoice, for example a PO number or a daily FX rate, set it before that invoice finalizes. The reliable workflow for dynamic content is to configure a grace period on the billing entity so invoices generate in Draft, update the section (or the customer metadata) via the API with the correct value, then finalize.

Customer metadata, for short reference fields

Customer metadata fields, set under Customer, then Edit, then Metadata, appear in the upper-right corner of the invoice. They suit reference numbers, account IDs, or other short identifiers that belong to the customer rather than to the invoice content. Metadata is less prominent and less readable than a custom section for multi-line content, but it needs no separate setup and can be set and updated via the API.

This article reflects guidance drawn from customer case resolutions. It is not officially supported documentation and may not apply to all situations.