How to Fix BER Decoding Errors When Verifying PDF Signatures
Question details
Users encounter a Basic Encoding Rules (BER) decoding error when attempting to verify or apply a digital signature to a PDF document using an A3 hardware certificate.

- Product
- Adobe Acrobat
- Device & OS
- not provided
- Scenario
- Verifying or applying a secure digital signature to a PDF using a smart-card or A3 hardware certificate.
- Observed behavior
- The PDF reader displays an 'Error while verifying signature. BER decoding error' message and fails to validate the signature, even though the certificate functions normally in other desktop applications.
Ensure your physical A3 certificate smart-card or USB token is securely connected to your computer and recognized by your operating system. It is also recommended to temporarily disable any aggressive antivirus software that might block the certificate middleware from communicating with your PDF reader.
Update Your PDF Reader and Certificate Middleware
Outdated software or smart-card drivers are the most common cause of certificate encoding incompatibility.
Certificate authorities frequently update their security standards. If your PDF reader or your hardware token's middleware is outdated, it may fail to properly parse the Basic Encoding Rules (BER) of the signature.
Open your PDF application, navigate to the 'Help' menu in the top toolbar, and select 'Check for Updates' to install the latest version.
Disconnect your A3 certificate token, visit your Certificate Authority's official website, and download the latest middleware and driver installation package for your operating system.
Install the downloaded drivers, restart your computer, plug the token back in, and attempt to verify the PDF signature again.

Adjust Signature Verification Settings
Modifying how the application handles certificate validation checks can bypass certain network or encoding timeouts.
Recreate the PDF to Remove Corrupted Fields
If the error occurs on a specific file only, the PDF's internal signature field structure may be corrupted.
Use WPS Office for Seamless PDF Digital Signatures
If you continue to experience BER decoding errors and compatibility issues in your current PDF software, try signing and verifying your documents with WPS Office. The built-in WPS PDF tool is highly compatible with standard digital certificates, providing a stable, lightweight environment for securing your important files without complex middleware setups.
- 1. Open the PDF in WPS: Download and install WPS Office, then open your PDF document using the WPS PDF editor.
- 2. Access security tools: Navigate to the 'Protect' tab located in the top ribbon menu.
- 3. Initiate signing: Click on 'Sign Document' and select 'Digital Signature' from the drop-down options.
- 4. Apply your certificate: Choose your A3 certificate from the system list, place the signature box on the page, and click 'Sign' to securely save the file.

Frequently Asked Questions
What does a BER decoding error mean in a PDF?
A BER (Basic Encoding Rules) decoding error means that the PDF software cannot correctly interpret the data structure of the digital signature or the hardware certificate. This is usually caused by outdated smart-card drivers, incompatible middleware, or an improperly formatted signature field within the document.
Why does my A3 certificate work on government websites but fail in my PDF software?
Web browsers and dedicated PDF applications use different verification engines and certificate repositories. PDF software often requires highly specific smart-card middleware configurations and strict adherence to PDF signature standards to successfully read A3 hardware certificates.
Can a corrupted PDF file cause a signature decoding error?
Yes. If the PDF was previously saved with a malformed signature field, missing fonts, or corrupted metadata, any subsequent attempt to verify the signature or append a new one can trigger encoding errors. Recreating the document often resolves this issue.
How do I ensure my certificate chain is properly recognized?
You need to open your operating system's certificate manager (such as certmgr.msc on Windows) and verify that the root and intermediate certificates provided by your Certificate Authority are correctly installed under the 'Trusted Root Certification Authorities' and 'Intermediate Certification Authorities' folders.




