What is usually required
Company identification on business correspondence
Several European jurisdictions treat business email as business correspondence and require the same details a letterhead carries. The usual list:
- The registered company name, including the legal form.
- The registered office address.
- The company registration number and the register it is held in.
- Where relevant, the VAT or tax identification number.
- For companies in liquidation or administration, a statement of that fact.
The United Kingdom, Germany, Austria, the Netherlands, Poland, Italy and Ireland all have requirements of this shape, with the details differing by country and by company form. A branch or subsidiary usually carries its own details rather than the parent's, which is why a group with several entities needs several versions of the same block.
Regulated sectors
Financial services, insurance and investment firms are typically required to state the authority that regulates them and the registration number they hold. Legal and accountancy practices carry statements about their professional body. Health providers carry confidentiality wording. In each case the requirement comes from the regulator rather than from company law, and it applies to the regulated part of the business, not always to the whole company.
Data protection
Where a message begins a relationship with a person, some companies point to their privacy notice from the footer. This is practice shaped by data protection law rather than a universal requirement to put a paragraph in every email, and a link is usually better than a block of text.
What is habit
The confidentiality paragraph
The long notice telling an unintended recipient to delete the message and notify the sender is almost never required by law. It is a convention of professional practice, its legal weight is debatable, and it is the reason so many company emails end with more disclaimer than message.
That is not an argument for deleting yours. It is an argument for deciding, once, which parts of your footer exist because a rule requires them and which exist because they have always been there. The first group is a compliance rule. The second is a design choice you are allowed to make differently.
Why length matters
A footer longer than the messages it accompanies gets skipped, and on a phone it pushes the reply below several screens of small grey text. Where the requirement is a set of company details, one compact line is usually enough to satisfy it.
Applying it in practice
One rule per country, entity and department
The hard part is not the text, it is making sure the right text reaches the right people and stays there. Asking staff to paste a legal block into their signature guarantees that some of them have it, some have an old version, and nobody can say which.
- Hold the text centrally, with a version history, so the wording in force on a given date is visible.
- Make it a rule rather than a paragraph: by country for company law, by entity for registration details, by department for a regulated function.
- Apply it inside the signature template, above the quoted thread, so it appears once per message rather than stacking down a reply chain.
- Keep a compact variant for replies and mobile.
- Record the rollout: which rule, which group, how many mailboxes, when. That record is what you show when someone asks whether the requirement was met.
Where mail server rules fall short
A transport rule on the mail server applies the same text to everyone in scope, lands below the quoted thread, and is skipped on encrypted messages. For a single company-wide sentence it is workable. For different wording per country and entity, with a record of what applied when, it is not. The comparison is on the Exchange email signature management page, and the rule-based approach is on the email disclaimer software page.