Skip to main content

Why timestamps differ between the signed document and the activity log

Document and log timestamps may differ — all times are stored in UTC for consistency.

Updated over a month ago

You might notice that the timestamp shown in your signed document doesn’t exactly match the timestamp in the activity log.

Don’t worry — this is expected and completely normal.

🔍 Why this happens

The difference is caused by time zones.

Addo Sign stores all timestamps in UTC (Coordinated Universal Time) — the international time standard used across systems and time zones.

However, when timestamps are displayed (for example, in a PDF or in your browser), they’re often converted to your local time zone.

If you’re in Denmark, your local time is usually UTC+1 or UTC+2 (depending on daylight saving time).

🌍 Example

Location

Time zone used

Example

Audit log

UTC (system time)

2025-06-12 12:30 UTC

Signed document

Danish local time (UTC+2)

2025-06-12 14:30 (CEST)

Both timestamps represent the same signing event, just shown in different time zones.

🧠 Why we use UTC

Using UTC ensures:

  • Consistency across users in different countries 🌎

  • Reliable audit trails for legal and compliance purposes 🧾

  • No confusion from daylight saving time changes ⏰

This approach is standard in secure digital signing systems.

✅ Summary

  • Addo Sign stores timestamps in UTC.

  • Danish time is UTC+1 in winter and UTC+2 in summer.

  • A 1–2 hour difference between the document and the log is expected.

  • Both timestamps refer to the same event — only shown in different time zones.

💡Tip: If you ever need to compare times: Local time = UTC time + time zone difference

Example: 12:30 UTC14:30 Danish summer time (UTC+2)

Did this answer your question?