Tvarka Batch: your first signed folder

These instructions cover the Batch 1.1.1 Windows workflow. Watch the English walkthrough or the Lithuanian walkthrough. The videos show a real run with 60 sample documents; the PIN window is not recorded.

1. Arrange access and delivery

Contact Tvarka with your company name, intended users and signing device. Batch is supplied with assistance: we confirm the order, enable Batch access for the company and provide the installer. The published offer is EUR 249 + VAT per month for unlimited documents, with no per-signature fee.

Your company needs a Tvarka Sign workspace and a workspace API key. A normal Sign key alone does not activate Batch: the company must also have the Batch timestamp entitlement. Ask us to confirm that it is enabled for the workspace that issued your key. Keep the key private; never include it in screenshots, email or support reports.

2. Prepare the computer

1. Install the Batch build supplied for your order. Use its installed Start-menu shortcut. There is no public self-service Batch download in the download catalogue yet.
2. Install Tvarka QES Bridge for Windows, or the Windows Tvarka Sign app that includes the middleware. Batch 1.1.1 requires Bridge 0.2.3 / Sign 0.3.3 or newer. Connect the card reader or USB token and make sure its certificate appears.
3. For Office documents that need conversion to PDF, install Microsoft Office or LibreOffice locally. PDFs, supported images and plain text have their own processing paths. Batch 1.1.1 does not use the separate Sign API cloud-conversion endpoint. If no suitable local converter is available, conversion fails visibly.
4. Open Batch → Settings, paste the entitled workspace key and select Check. A successful check confirms key and Batch access; it does not sign a document. Save the settings. Set company details for ADOC authorship and your optional PDF logo and stamp.

Use a device and certificate agreed during setup. A personal qualified signature identifies the person; a qualified company seal identifies the organisation. The certificate you select determines which is applied.

3. Start with a small folder

1. Choose Document folder and then Output folder. Use a separate output location. Batch keeps the source folder structure and leaves the originals untouched.
2. Choose PDF, ADOC or ASiC-E and review the file list. Existing signed containers and Office files follow the selected format's rules; a format change is not a promise to convert every signed container into a PDF.
3. Select the signing certificate and the PDF stamp options, then press Sign. Review the confirmation before continuing.
4. Complete any PIN prompt in Tvarka Sign middleware. Batch itself neither asks for nor stores a PIN. Prompt frequency follows the device and the middleware's existing PIN mode; changing that mode is separate from installing Batch.
5. Wait for completion and review the result for each file. The progress percentage includes estimates while the middleware is working; a rising percentage is not proof that all files are finished.

4. Read results and retry safely

Click the output path to open the signed files. Select Report to create and open the CSV report for that run. A run with failed documents also saves a report automatically; a successful run keeps results on screen until you request the report.

Read each failure reason, fix the cause, then retry the same folder and output location. Existing output files are skipped rather than overwritten. Saved recovery data can finish unchanged work without another card call when the prepared bytes, settings and certificate still match. Changed inputs are new work. A process loss before the middleware response was saved cannot be recovered this way.

Check a signed sample in the recipient's usual signature validator before processing the full workload. Preserve the signed original. Opening or printing a file is not the same as checking its signature.

When something needs attention

• Key rejected or Batch access disabled: check the selected company, key and Batch entitlement with support. A working general Sign key is not enough.
• No certificate or middleware busy: check the reader/token, Bridge status and any open PIN dialog. Wait for the current device action before retrying.
• Conversion failed: check the local converter and whether the source is password-protected or unsupported. Resolve the file problem and retry.
• Timestamp or completion failed: restore connectivity, keep the source/output and retry. Retain recovery data; do not delete it while work is incomplete.
• Report cannot be saved: check output-folder write access and press Report again while the results remain available.

Contact [email protected] with the Batch/Bridge versions, device model and fixed error message. Use the Log view for status information. Send document contents only if you have agreed a suitable support transfer; do not send keys or PINs.