Understanding Signing Certificate Timestamps

When a document is fully signed in GetAccept, a signing certificate is automatically generated. This certificate serves as the legal record of the signing event and contains important details including the exact timestamp of when all required signers completed their signatures. All timestamps on GetAccept signing certificates are displayed in UTC+00:00 (Coordinated Universal Time), regardless of where the signers are located or what timezone their GetAccept account is set to.

Note: All timestamps display in UTC+00:00 regardless of signer location or account timezone settings.

Why GetAccept Uses UTC+00:00 for All Timestamps

GetAccept uses UTC+00:00 as the standard timestamp format for all signing certificates to ensure consistency and prevent confusion across international deals. Since documents are often signed by parties in different time zones across different countries, displaying timestamps in a single universal standard removes ambiguity about when a signature was actually applied.

UTC+00:00 (also called Coordinated Universal Time or "UTC") is the globally recognized reference time. It is not tied to any specific geographic location or daylight saving time rules. This makes it the ideal choice for legal documents that may be signed across borders or reviewed by parties in multiple jurisdictions.

Important: The UTC timestamp on your signing certificate is immutable and cannot be changed. This is intentional , the unchangeable timestamp is part of GetAccept's tamper-proof record and contributes to the legal integrity of the signed document.

How UTC Timestamps Support Legal Compliance

International agreements and contracts often require clear, unambiguous proof of when signatures were applied. Using UTC+00:00 ensures that no matter which country reviews the agreement later, the signing time is interpreted the same way. This is especially important for:

Multi-party international contracts where signers are in different countries
Regulatory compliance in industries with strict timestamp requirements
Legal disputes or audits where the exact signing date and time matter
Qualified Electronic Signature (QES) agreements, which have strict timestamp requirements under EU eIDAS regulations

The UTC timestamp, combined with the full audit log in your certificate, creates a legally defensible record of the signing event.

How to Interpret UTC Timestamps in Your Local Time Zone

If you need to know when a document was signed in your own time zone, you can convert the UTC timestamp shown on the certificate to your local time.

Example: If the certificate shows a signing timestamp of 14:30 UTC+00:00, and you are in Eastern Standard Time (UTC-5), the actual local signing time was 09:30 EST (14:30 − 5 hours = 09:30).

Most online UTC converters are available as a quick search, or you can calculate the offset manually using your local timezone's UTC offset. Your account timezone setting does not affect the certificate timestamp , it only affects how dates appear in your GetAccept dashboard and email communications.

What the Signing Certificate Is and Where to Find It

A signing certificate is a detailed record automatically generated after all required signers have completed their signatures on a document. The certificate includes:

The full names and email addresses of all signers
The date and time each person signed (in UTC+00:00)
The IP address and browser/device information for each signer
A complete chronological audit log of all document activity (opens, views, comments, signatures)
A unique document fingerprint to verify authenticity

After a document is fully signed, the signing certificate is automatically sent via email to all signers and the sender. You can also download the certificate from the signed document in your Contracts tab. The certificate PDF can be stored alongside the signed contract for compliance and record-keeping purposes.

Verifying Document Authenticity Using the Certificate

The signing certificate serves not only as a record but also as proof that the document has not been tampered with. GetAccept assigns each page of a signed document a unique fingerprint, and this fingerprint is recorded in the certificate.

To verify that a document is authentic and has not been modified since signing, you can use GetAccept's document verification tool at https://app.getaccept.com/verifydoc. Upload or paste the signed document, and the verification tool will confirm:

Whether the document was genuinely signed through GetAccept
Whether any pages have been altered since signing
The exact date and time of signing (in UTC+00:00)
The identity and email of all signers

This verification process is available to anyone who has access to the signed document, and no GetAccept login is required.

Key Points to Remember

All signing certificates display timestamps in UTC+00:00 , this cannot be customized
UTC+00:00 is used to ensure consistency across international agreements and prevent timezone confusion
You can convert UTC timestamps to your local time zone using a UTC converter or manual calculation
The certificate timestamp is part of the immutable, legally-binding record of the signature
Signing certificates are generated automatically and sent via email after all required signers complete their signatures
Use the verification tool at https://app.getaccept.com/verifydoc to confirm document authenticity and detect any tampering