Electronic signing of PDF documents in Montenegro is increasingly replacing paper contracts, statements, eGovernment applications and communication with institutions. Under the Law on Electronic Identification and Electronic Signature, a qualified electronic signature has the same legal force as a handwritten one — but only if it is technically created correctly. The biggest problem in practice is not the click on "Sign" in Adobe Reader, but everything that precedes it.
⚠ Common problems when signing
When trying to sign a PDF document — or when opening an already signed one — users run into a series of typical messages that stop the process or call the signature's validity into question:
- •The certificate does not appear in the signing list in Adobe
- •"Signature validity is unknown" when opening a signed document
- •"At least one signature is invalid" — the recipient sees the signature as invalid
- •Embedded timestamp not valid — the timestamp is incorrect or missing
- •Adobe Reader freezes or crashes the moment the token asks for the PIN
What must be in place for a legally valid signature
For your signature on a PDF to have the same force as a handwritten one, the system requires a strictly defined environment. Each of these conditions must be met — if any is missing, the signature technically exists but will not be legally accepted:
- 1 A valid, in-date qualified certificate, issued by a recognized CA in Montenegro (Pošta CG, MUP, Core IT, Crnogorski Telekom).
- 2 Adobe Reader configured correctly — with Windows Certificate Store integration enabled, otherwise it can't see the certificates on the token or card.
- 3 The issuer's root certificate in the Windows Trusted Root — without this trust, every recipient of the document (court, bank, portal) sees the signature as untrusted.
⚡ Legal and administrative traps
Technical correctness of the signature is not the only condition — there are situations where everything formally "works", but legally or administratively the signature does not serve its purpose:
- •The signature is invalidated by any change to the document after signing — even the smallest correction means loss of legal value
- •Different document recipients (institutions, banks, courts) may interpret the same signature differently depending on the Adobe version and their configuration
- •A firewall or DNS that blocks OCSP/TSA traffic results in an invalid timestamp
- •The certificate on the token may expire without it being visible in Adobe — the signature goes through, but is not legally valid
Discovering an invalid signature at a later stage (when the recipient rejects it) can be a matter of both deadlines and reputation.
Why the legal certainty of your signature is our responsibility
The legal validity of your signature must not be a matter of luck or improvisation. We configure Adobe Reader, validate certificates and root authorities, and verify that the signature passes validation at the intended recipient — whether it is a portal, a bank or a court. The goal is not "just to sign" — the goal is for the signature to stand before anyone who opens it.
Remotely via AnyDesk, usually in 15–30 minutes. Diagnosis is free; you pay only when we confirm the problem is solvable. So instead of uncertainty, you get the assurance that your signature carries full legal weight.