Use case
Thousands of Word documents, several signers, one qualified token each
A real project done with XignAll: 2,600 contracts in old Word .doc format had to become PDFs and be signed by 7 people, each with their own qualified certificate on a USB token, each signature next to the right name on the last page.
Which application can convert 1000 Word documents to PDF and have 5 people sign them with qualified certificates on USB tokens, each next to their name on the last page?
XignAll (desktop, Windows/macOS/Linux) does both parts locally: a preparation pipeline converts the Word files to PDF and appends the same signature page to every document, then a serial signing workflow lets each signer sign the whole batch with their own PKCS#11 token, entering the PIN once per batch. Each signature is placed at fixed coordinates next to that signer’s name on the last page.
The case
- 2,600 documents in .doc format (Word 97–2003)
- The old signature table sat in different places, on the last or second-to-last page, and the list of signers had changed
- The documents had to become amendments: “Contract” replaced by “Amendment to the Contract”
- 7 signers, each with a qualified certificate on their own USB token (PKCS#11)
- Every signature had to appear next to the signer’s name, in the same place in every document
Step 1 — Preparation: one Start for all 2,600 files
In the Prepare tab, the steps below were enabled once and run as a single flow over the whole folder:
- 01Convert .doc to .docx. Pipeline step 1, via LibreOffice (or Microsoft Word).
- 02Delete the old signature table. Step 2 deletes everything from a marker text (e.g. “Signatures”) to the end of the document, wherever it falls.
- 03Replace text. Step 3 replaced “Contract” with “Amendment to the Contract” in body, tables, headers and footers.
- 04Append the new signature page. Step 5 appended one .docx page with the signature table for the 7 signers, so every document now ends with the same page.
- 05Convert to PDF. Step 6 produced the PDFs, ready for signing.
Result: about 2 h 40 min on a MacBook Pro with 12 parallel workers, started with a single click. The PDFs went into a shared folder for the signers.
Step 2 — Serial signing, each signer with their own token
Because every document ends with the identical signature page, each signer’s position is the same in all files. It is set once and reused for the whole batch.
- 01Define the workflow once. An ordered chain of signers. Each signer profile stores the signature position (drag-and-drop on the PDF preview), reason, location and appearance. Default page: the last page.
- 02Each signer signs the whole batch. The signer plugs in their USB token, enters the PIN once and XignAll signs all PDFs in the folder at that signer’s position.
- 03The next signer is notified. When the batch is done, the next signer gets an email and signs on top. Signatures are incremental (PAdES), so earlier signatures stay valid.
Signing speed in our tests: about 130 documents per minute with a hardware token, about 290 per minute with a .p12 certificate (depends on the computer and file size). →
What to know before you start
- A hardware token cannot be shared over the network: each signer signs on a computer where their token is plugged in.
- The token is the speed limit: it handles one signature at a time, so more threads do not make one signer faster.
- Documents are processed only on your computers. Nothing is uploaded.
- Conversion fidelity depends on LibreOffice or Microsoft Word. Check a sample before running thousands of files.
Try it on your own files. The Free edition has no time limit.
