Daily statement

The link sent to the customer carries a code unique to that report, with an expiration date. Whoever has the link sees that report and nothing else — there is no login, no account, no password. It is the same design as the link-based approval the platform already uses.

The page the customer opens through the link in the email to view the report and acknowledge receipt — without creating an account. Authorization comes from the token in the address, which has an expiration date. — this is the role of the "Acknowledge report (public link)" screen within the platform.

What the customer records there is that they RECEIVED and read the document, with date, time and network address. That answers the question "were they notified?" and does not answer "did they sign?". A signature with legal validity requires an ICP-Brasil certificate or a provider with its own audit trail, and the platform does not do that — saying it does passes on to your customer a problem they discover on the day they need it.

The PDF is built from the answers, so what you see on screen is always the current data. The moment the report is sent to the customer, an exact copy goes to the document archive — because from then on what matters is no longer "the current data", it is what was delivered. That copy is what the company needs if it ever has to prove what it sent.

"I received a report link — what do I do here?" — when this question comes up, this is the screen that answers it.

No. The link in the email carries a token with an expiration date, and that is what authorizes you: you open it, read the whole report embedded in the page itself — acknowledging without being able to read what you receive would be signing a blank check —, enter your name and ID document and confirm. The first acknowledgment is the one that counts: after it, the page shows the record with date and time and no longer offers the button, so reopening the email later does not create a second acknowledgment.

Invalid token and expired token show the SAME message, on purpose: distinguishing the two cases would make the page confirm that "this report exists" to someone who just guessed a code. If your real link stopped working, the most common reason is that the token's validity period has passed — ask whoever sent the report to send it again. And remember the limit printed in the footer: the acknowledgment records receipt of the report; it is not a signature with legal validity.