10/16/2026Digital Signing

How to Digitally Sign PDFs in Bulk Without a USB Token

Gaurav Singhal

View LinkedIn

Signing one PDF with a USB token is tedious. Signing a few hundred is a lost afternoon. The documents wait for the one person who has the token and the PIN, the signing software only works on one machine, and every file needs its own clicks.

This guide explains what bulk digital signing is, what you need to set it up, and how to run it without plugging in a dongle.

Key takeaways

  • Bulk signing means applying your organisation's digital signature to many PDFs in one run, instead of one file at a time.
  • The usual setup is a document signer certificate issued as a .pfx file, uploaded once to a signing tool.
  • A digital signature shows who signed a document and that it hasn't been changed since.
  • In Ambill, PumPumPum, Kazam and Workie already use this to sign their invoices in batches. Signing any PDF and a developer API are coming soon.

What bulk digital signing actually means

A digital signature is not a scanned image of a signature pasted onto a page. It is a cryptographic seal added to the PDF using a certificate that belongs to your organisation. Anyone who opens the file in a PDF reader can check two things: which certificate signed it, and whether the content has changed since it was signed.

Bulk signing is the same thing, done for many files at once. You choose the documents, confirm once, and every PDF comes back signed with the same certificate. No one has to open each file, place a signature box and type a PIN again and again.

Why USB tokens make volume signing painful

USB tokens were designed for an individual signing an individual document. That works when someone files a return or signs a single agreement. It struggles as soon as the volume goes up.

  • One device, one person. The token sits in a drawer or in someone's laptop bag. If they are on leave, signing stops.
  • Software on every machine. Tokens need drivers, and signing often needs a desktop app or a browser plugin. Updates break things at awkward times.
  • One file at a time. Most token workflows ask for a PIN and a click per document.
  • No path for your software. If your billing or HR system generates PDFs, there is usually no clean way for it to call a USB token.

Say your team sends 300 documents in a month-end run and each one takes about 30 seconds to open, sign and save. That is two and a half hours of someone's time, every month, spent clicking. The time is only part of it. Documents go out late, and signing depends on one person and one device.

What you need for bulk signing

A document signer certificate (.pfx)

A document signer certificate is issued in the name of your organisation rather than an individual. It is typically delivered as a .pfx file, which holds the certificate and its private key, protected by a password. You get it through a licensed certifying authority or its partners, who will verify your organisation's details before issuing it.

Because it is a file rather than a hardware token, it can be stored securely by a signing service and used without a device being plugged in. That is what makes bulk signing, and signing from software, possible.

A signing tool that accepts the certificate

You need software that can take your .pfx, keep it safe, and apply it to many PDFs in one go. The tool should not require a desktop install on every machine, and it should let you control who on your team can trigger signing.

A clear list of what gets signed

Decide which documents your organisation will sign and who approves the run. Which documents need a signature, and of what kind, depends on your business and the people you send them to. Check with your advisor on what your documents require.

How bulk signing works, step by step

  1. Get the certificate. Apply for a document signer certificate through a licensed certifying authority or one of its partners. You will receive a .pfx file and its password.
  2. Upload it once. Add the .pfx to your signing tool. From then on, the certificate lives in one place instead of on a token that travels between desks.
  3. Select the documents. Pick the PDFs for this run, for example all invoices raised this week.
  4. Confirm with one password entry. Enter the certificate password once for the batch, not once per file.
  5. Send the signed PDFs. Each file now carries your organisation's digital signature, and the recipient can check it in a PDF reader such as Adobe Acrobat Reader.

How Ambill Sign does it today

Ambill Sign is built into Ambill. Finance teams upload their organisation's document signer certificate once, then sign the invoices and credit or debit notes they generate in Ambill in batches, with one password entry per batch. PumPumPum, Kazam and Workie already use it to sign their invoices in production.

There is no token to pass around and nothing to install on each laptop. The person running billing can sign the run themselves, and the signed PDFs are ready to send.

What's coming: any PDF, and an API

Two things are on the way, and both are in early access:

  • Upload and sign any PDF. Not just invoices from Ambill. Contracts, letters, certificates, reports: any PDF your organisation needs to sign with its own certificate.
  • A developer-first signing API. Send a PDF from your own product or workflow, get it back signed with your company's certificate. No token, no desktop app, no per-machine setup. Read more in Digital Signature API: what it takes to sign PDFs from your own software.

We built this because signing at volume should not need complex contracts. Many digital signature providers charge per signature or per envelope, add setup fees and annual minimums, and route you through a sales process. That is hard to justify for routine business documents. We are aiming for simple pricing with no per-signature fees. More on that in why digital signature solutions cost so much.

Tips for running bulk signing smoothly

  • Keep the certificate details current. Note the expiry date and renew before it lapses, so a signing run never stops on the day it is needed.
  • Limit who can sign. Give signing rights to the few people who approve outgoing documents.
  • Sign the final version only. Any change after signing breaks the signature, so finish edits first.
  • Tell recipients what to expect. Some readers show "validity unknown" until the certificate chain is trusted. Our guide on how to verify a digitally signed PDF covers this.
  • Keep your USB token for what it does well. Tokens still suit personal signing. A document signer certificate suits organisational documents at volume. See USB DSC token vs cloud signing for the trade-offs.

Start signing in bulk

If your team signs invoices from Ambill, you can set up bulk signing today. If you want to sign any PDF or sign from your own software, join early access.

Talk to us about Ambill Sign

Request API early access

FAQ

Can I digitally sign multiple PDFs at once?

Yes, if you use a document signer certificate and a tool that supports batch signing. You choose the files, confirm once and every PDF is signed with the same certificate.

Do I need a USB token for bulk signing?

No. Bulk signing usually uses a document signer certificate delivered as a .pfx file, which is uploaded once to the signing tool. No device needs to be plugged in. Learn more in what is a document signer certificate.

Where do I get a document signer certificate?

Through a licensed certifying authority or its partners. They verify your organisation's details and issue the certificate as a .pfx file with a password.

Which documents should we sign digitally?

That depends on your business and your recipients. Check with your advisor on what your documents require.

Can Ambill Sign sign PDFs that were not created in Ambill?

Not yet. Today it signs invoices and credit or debit notes generated in Ambill. Signing any PDF and the developer API are coming soon, and you can request early access.