The first thing that surprises businesses transitioning to e-Invoicing is usually this: documents look identical to one another. There is no logo, the layout is plain, and the corporate identity is lost.
The reason for this is that document data and its appearance are separate. The data is standard; the appearance is generated using a template. When that template is not defined, the default plain design is used.
In this article, we explained what document design does, what can and cannot be changed, and the operational benefits of the design.
Table of Contents
Why are data and appearance separate?
An e-Invoice is essentially a structured data file. It contains recipient information, line items, totals, and taxes in a specific format. This format is standard because the opposing party's system will automatically read this data.
Humans, however, do not read data in its raw form. Therefore, data needs to be converted into a readable page. What performs this conversion is the template.
In practice, this distinction means: changing the appearance does not affect the accuracy of the data. When you update the template, the legal content of the document remains the same, only its presentation changes.
What can be changed?
Logo and corporate identity. The company logo, color scheme, and typography are determined by the template. Having the document sent to the customer carry your brand makes a difference in terms of trust.
Field layout. You can arrange where specific information appears on the page. Having frequently checked fields at the top shortens reading time.
Additional notes. Bank account details, return conditions, or payment instructions can be added to the document. This reduces repetitive questions from customers.
Language. English field labels can be used for international recipients. This is especially useful for export documents; you can check out the e-export invoice article.
Line presentation. How long product descriptions appear, column widths, and page breaks can be customized.
What cannot be changed?
Mandatory fields cannot be removed from the document. Tax information, amounts, document number, and date must be present in every template.
The data itself cannot be altered either. The template is merely a presentation layer; there is no possibility—nor should there be—to display an amount differently.
Document-specific requirements are also preserved. Fields such as carrier information on a dispatch advice or withholding tax display on a receipt must always be included in the template.
Operational benefits of design
Document design might seem like an aesthetic choice, but it produces measurable benefits.
First, it reduces customer inquiries. If payment details and due dates are clearly visible on the document, calls asking "where should I pay?" disappear.
Second is the speed of collection. An easy-to-read document is processed faster by accounting departments. We discussed this aspect of maturity tracking in the term sales and collection risk article.
Third is error detection. The orderly placement of fields enables the reviewer to spot mistakes quickly.
Are multiple templates required?
For most businesses, one template per document type is sufficient. However, some scenarios require differentiation.
In multi-company structures, each company must have its own logo and information. Using a single template creates the risk of sending a document with the wrong logo. This scope distinction is provided by the multi-company model.
It is also common to use separate templates for domestic and international documents. Language and field requirements differ.
Distinguishing between dealers and retail customers is sometimes necessary as well. Documents sent to dealers may contain different additional information; the B2B account groups article addresses this segmentation.
Managing templates
A template is not a file that is created once and forgotten. It needs to be updated whenever an address change, logo update, or a new legal field is required.
Producing a test document before updating is a good habit. A template error propagates to all documents; a single check eliminates this risk.
Who can change templates should also be restricted. Document appearance is part of the corporate identity; authorization ensures you keep this privilege tightly controlled.
Templates are managed under the document designs heading in the e-Document module; even if your integrator changes, the design stays with you.
Characteristics of a good document design
The goal of document design is not to grab attention, but to make reading effortless. The recipient of the invoice usually looks at three things: who sent it, how much, and when it is due.
These three pieces of information should be visible at first glance. A due date tucked away at the bottom of the page is the silent cause of delayed payments.
The line item table must be readable. How long product descriptions wrap, column widths, and font size should all be considered together.
Excessive visual elements should be avoided. An invoice is not a marketing material; simplicity breeds professionalism.
Print compatibility must not be forgotten either. A design that looks great on screen might be unreadable in black and white print; many customers still print and archive.
How does the design process work?
Although document design seems like a one-off task, it needs to be tied to a process. Otherwise, every modification carries risks.
The first step is clarifying the need: which document type, which language, which company? These three questions determine how many templates are required.
The second step is generating a sample document in a test environment. Edge scenarios such as long product names, multi-line invoices, and high amounts should be tested.
The third step is approval. Because the document is part of the corporate identity, the design should not change on a single person's initiative.
The final step is going live and checking the initial documents. It is helpful to add this item to the transition checklist; you can refer to the transition checklist article.
Frequently asked questions
Does a template change affect past documents?
Past documents are stored with the appearance of their respective periods. Changes apply to subsequent documents.
Is software knowledge required for design?
Basic adjustments can be made via ready-made templates. Extensive customizations may require technical support.
Does the design get lost if the integrator changes?
The design is preserved when maintained on the platform side. This is part of the dependency issue we touched upon in the integrator selection article.
Can a QR code or link be added to the document?
It depends on the template structure and provider support. For payment convenience, you can check out the payment link article.
Document design is an opportunity to produce some of the most orderly documents your customers see from you. You cannot change the data, but you completely determine how it is presented.
By consulting with the EQLEM team, you can configure your document designs to match your brand identity.