What is in the completion report

When a document completes, a second file comes into being alongside the signed PDF: the completion report. It is a separate PDF describing who signed, when, by what means, and with what proof.

This page lists what it contains — both so you know what it shows to whoever receives it, and so you can answer when someone asks what is recorded about them.

The report is in English

The report’s headings and labels are written in English and do not follow your account language. A document signed entirely in Portuguese still produces a report with sections called Signatures, Timeline and Audit chain (tamper-evidence).

The data inside the fields — names, emails, signature types — comes from the document and appears as it is.

The document

In the Document and Timeline sections:

Field	What it is
Document ID	The document’s public identifier
Name	The file name
Subject	The subject
Pages · Status	The page count and the status
Signature count	The number of certificate-based signatures found in the PDF, if there are any; otherwise the total number of signatures
Document hash (SHA-256)	The file’s fingerprint
Signed with certificate	Yes if the PDF holds at least one signer’s certificate-based signature
Created on · Completed on	When it was created and when it completed
Report generated at	When this report was produced

The Document hash is what later proves the PDF in your hands is the one that was signed: change a single byte and the value changes.

Who sent it

In the Owner section, the report identifies whoever created the document, with Name, Email, Phone and IP address.

Who signed

Each signer gets a section of their own, Signer — {name}:

Field	What it is
Email · Phone	The contacts used for the send
IP address	The address the signature was made from
User-agent	The browser and system used to sign
Signature type	See the table below
Security level	The two-step verification asked of the signer: No, SMS or Password
eIDAS level	SES, AES or QES, followed by the identity assurance
ID document	The type and number of the identity document, where identity confirmation was used
Certificate (extracted from signed PDF)	Where the signature uses a certificate: Common name, Serial number, Issuer, Valid from, Valid to
Professional attributes (SCAP)	Certified with, Certified by, Certified attributes and each body’s NIPC, where the signature carries them
SMS OTP events	Where an SMS code was used: Code (last 4), Phone, Sent, Validated, Status
Signer answers	The answers to the questions the signer fills in: Question and Answer, only when the document had any

Signature type and eIDAS level depend on the method:

Method	Signature type	eIDAS level
Visual signature (with or without an SMS code or identity confirmation)	Without Certificate	SES
Chave Móvel Digital	Mobile Digital Key (CMD)	QES · High
CMD with professional attributes	Mobile Digital Key with Professional Attributes (SCAP)	QES · High
Local Digital Certificate	Advanced Signature	AES · Substantial

A Local Digital Certificate signature also carries the Certificate (extracted from signed PDF) block, with the details of the signer’s own certificate — the Issuer is the authority that issued it to them, not ARTE (formerly AMA).

Why the IP address is there

This is the field that most surprises people opening the report for the first time.

The report exists to identify who signed and to hold that identification up in front of third parties. The IP address, the user-agent and the time are part of that proof: without them the document would say someone signed, but have nothing to stand on if the signature is ever disputed. It is not incidental logging that could be dropped at no cost — it is part of why the file exists.

Whoever receives the completed document receives this too. Worth knowing before forwarding the report outside the organisation: the signed PDF and the report are separate files, and you do not always need to send both.

The report outlives the document

A document you delete stays recoverable for 15 days in Deleted; after that it leaves direct access and, 30 days later, it is removed for good, together with its files. The sealed completion report is not removed with it: it is kept, along with the document’s history, as proof that the signature took place. If you need the report in your own hands, download it before deleting the document.

For what the platform keeps and for how long, see Data retention and privacy.

The audit chain

The Audit chain (tamper-evidence) section says whether the document’s history is still intact. It carries the Chain root hash (SHA-256), the number of verified entries, and one of three verdicts:

Verdict	What it means
VALID — chain reproducible	The chain was recomputed and matches
INVALID — chain broken or tampered	The recomputation does not match
NOT VERIFIABLE — no chained audit entries	There are no chained entries to check

The third is not a fault in the document: an older document may have no chained events to recompute. How the chain is built and verified is in How the history is chained.

The PDF’s own signatures

The report also describes what is applied to the file itself, not only what the platform recorded:

AATL Digital Certificate (Adobe Approved Trust List) — the platform’s certifying seal, with Name, Email, Date and LTV type, which is what allows the signature to be validated in the future.
Certificate (extracted from signed PDF), in each signer’s section — see above.
Unreconciled signatures — signatures found in the PDF that the platform could not match to a registered signer.