A company announcement is one of the few documents where a convincing fake causes damage within minutes. A fabricated release about a merger, a recall, or a regulatory finding can reach wire services, trading desks, and newsrooms before the company that supposedly issued it has finished reading it.
The correction always arrives later than the fake. By the time a communications team has confirmed that a release did not come from them, the story has been repeated, the price has moved, and the denial is competing with the original for attention.
The verification gap
When a journalist receives a release, the checks available are surprisingly weak. The email domain can be spoofed. The PDF letterhead can be copied from any previous announcement. The press contact number can be fabricated. Calling the company works, but only during working hours and only if the right person answers, which is precisely the friction a bad actor is counting on.
What is missing is a way for the recipient to answer the question themselves, immediately, without contacting anyone. That is a verification problem, not a communications problem, and it has a technical answer.
Sealing an announcement at publication
Sealing means applying a qualified electronic seal and a qualified timestamp to the release at the moment it is published. Three things become checkable by anyone holding the file.
It came from the company. A qualified electronic seal is issued to a legal entity rather than an individual. It binds the document to the organisation itself, so the seal answers the question of origin directly rather than by inference from a domain name.
It has not been altered. The seal covers a cryptographic hash of the document. Change a figure, a date, or a single word after sealing, and verification fails. This matters for announcements specifically, because the most effective manipulation is often a genuine release with one number quietly changed.
It existed at a specific moment. A qualified timestamp from an accredited authority records when the release existed in that exact form. Under eIDAS Regulation (EU) No 910/2014, a qualified timestamp carries a legal presumption as to the accuracy of the date and time it records.
Why timing carries legal weight here
For listed companies, the moment of publication is not a detail. Disclosure rules across European markets turn on when price sensitive information was released and whether it reached the market in a way that was complete and simultaneous. A record of publication time that rests on a server log is a record controlled by the company itself.
A qualified timestamp is issued by an accredited third party, which changes its evidential character. In Switzerland the framework governing qualified signatures, seals, and timestamps is ZertES (SR 943.03). Within the EU the equivalent framework is eIDAS. In both cases the point is the same: the time record does not depend on the word of the party who benefits from it.
What the newsroom sees
The practical effect is that a recipient can check a release in the time it takes to open a file. The seal confirms the issuing entity, the timestamp confirms the moment of publication, and the integrity check confirms nothing has been edited since. A fabricated release fails all three, and it fails them on the recipient's screen rather than after a phone call.
This works for the parties who most need it and are least likely to call you: a wire service under deadline, a regulator reviewing a disclosure after the fact, a shareholder assembling a record of what was said and when.
Beyond the release itself
The same approach applies to the material around an announcement. Investor presentations, financial statements, product recall notices, and regulatory filings all share the characteristic that their authenticity and timing matter, and that a plausible fake is damaging.
There is a second benefit that surfaces later. When a dispute arises about what a company disclosed and when, a sealed and timestamped archive of announcements is evidence rather than assertion. Communications teams rarely build for that scenario, and legal teams are usually the ones who wish they had.
Any sealed document can be checked using the public validator at swisstrustlayer.com/validate, without an account.
