11/6/2026Digital Signing

How to Digitally Sign Invoices from Tally, Zoho Books and SAP

Gaurav Singhal

View LinkedIn

Your accounting system does a good job of creating invoices. Signing them is another matter. In many finance teams, invoices come out of Tally, Zoho Books or SAP as PDFs, and then someone signs each one by hand with a USB token before it goes to the customer.

That works for a handful of invoices. At month end, it turns into a queue. This guide looks at why signing is usually a separate step, the common ways teams handle it, and how to sign invoices in batches with your organisation's own certificate.

Key takeaways

  • Tally, Zoho Books and SAP create invoices well, but digital signing is often a separate, manual step done one PDF at a time.
  • The usual bottleneck is the USB token: one person, one machine, one PIN, one document at a time.
  • A document signer certificate (.pfx) held by your organisation can sign many invoices in one batch with a single password entry.
  • Ambill works alongside Tally, Zoho Books and SAP. Invoices generated or synced in Ambill are bulk-signed with your organisation's certificate today.
  • Automatic signing and a developer API are coming soon.

Why signing is usually a separate step

Accounting and ERP systems are built to record transactions and produce invoices. Digital signing needs something different: a signing certificate, the software to apply it to a PDF, and a way to control who can use it.

So most teams end up with a two-step process:

  1. Create the invoice in the accounting system and export or print it to PDF.
  2. Sign the PDF in a separate tool, usually with a USB token plugged into one computer.

The second step is where time goes. Signing tools often need drivers, a specific browser or desktop app, and the token holder at their desk. Each PDF is opened, signed and saved, one at a time.

The common ways teams sign invoices today

Signing each PDF with a USB token

The most common setup. The token holder exports invoices, opens each PDF in a signing tool, enters the PIN and saves the signed copy. It is simple to understand and hard to scale. If the token holder is on leave, invoices wait.

A plugin or connector for one system

Some teams use an add-on that signs from inside a particular accounting product. These can help, but they often still depend on a token on one machine, and they tie your signing process to that one system. Teams running more than one tool, such as Tally in one entity and SAP in another, end up with more than one signing setup.

Buying a signing platform

Larger teams sometimes move to a dedicated digital signature solution. These often come with complex pricing: per-signature or per-envelope fees, annual minimums, setup and integration fees, and sales-led onboarding. For routine invoices, that cost can be hard to justify. We explain why in why digital signature solutions cost so much.

A simpler approach: one certificate, signed in batches

The alternative is to use a document signer certificate: a certificate issued to your organisation, as a .pfx file, through a licensed certifying authority or its partners. Instead of living on a USB token tied to one person, it is held securely by your signing software and used under controls you set.

With an organisation certificate:

  • You upload the certificate once.
  • You select the invoices to sign.
  • You enter the certificate password once for the batch.
  • Every invoice in the batch is signed with your organisation's name.

No token to pass around, no drivers on every machine, and no signing PDFs one at a time. For more on the certificate itself, see what a document signer certificate is, and for the token comparison, see USB DSC token vs cloud signing.

How it works with Ambill today

Ambill is a billing platform, and Ambill Sign is its signing feature. Ambill works alongside Tally, Zoho Books and SAP, so your accounting system stays where it is.

Here is what is live today:

  1. Invoices are generated or synced in Ambill. Your invoices, credit notes and debit notes are in Ambill, alongside the accounting system you already use.
  2. Your certificate is uploaded once. An admin uploads your organisation's document signer certificate (.pfx).
  3. Finance signs in batches. Select the invoices, enter the certificate password once, and the batch is signed with your organisation's certificate.
  4. Signed PDFs go to customers. Each signed invoice carries a standard PDF digital signature that recipients can check in a PDF reader such as Adobe Acrobat Reader.

PumPumPum, Kazam and Workie already use it to sign their invoices in production, with no per-signature fees.

How invoices move between your accounting system and Ambill depends on your setup. We will walk you through what fits when you talk to us.

What is coming soon

Two things are in early access:

Signing any PDF, not only invoices, is coming too.

Example: what batch signing saves

Say your team raises 400 invoices at month end and signing each one with a token takes about a minute, counting opening, signing, PIN entry and saving. That is close to seven hours of one person's time, and it can only happen at the machine with the token.

With batch signing, the same person selects the month's invoices, enters the password once and moves on. These numbers are an example only. Your own volume and timings will differ, but the shape of the saving is the same: signing stops being a queue. For a step-by-step view, see how to digitally sign PDFs in bulk.

Before you start

A few practical points to settle:

  • Get the right certificate. You need a document signer certificate (.pfx) in your organisation's name, issued through a licensed certifying authority or its partners.
  • Decide who can sign. Agree which roles can start a signing batch and who holds the certificate password.
  • Check your documents. Whether a document needs a digital signature depends on your situation. Check with your advisor on what your documents require.
  • Tell your customers. Let their accounts teams know invoices will arrive digitally signed. If they see a "validity unknown" message, point them to how to verify a digitally signed PDF.

Sign your invoices without the token queue

If you raise invoices in Tally, Zoho Books or SAP and want to sign them in batches with your organisation's certificate, we can show you how it fits your setup.

Ambill Sign is part of Ambill, the finance operations platform that also automates accounts receivable, collections and reconciliation. The same invoices you sign can be followed up, collected and matched to payments in one place.

Talk to us about Ambill Sign

Want to sign invoices or other PDFs from your own software? Request API early access

FAQ

Can I digitally sign invoices directly inside Tally?

Signing is usually done as a separate step after the invoice is created, often with a USB token. Ambill works alongside Tally so that invoices generated or synced in Ambill can be signed in batches with your organisation's certificate.

Does this work with Zoho Books and SAP too?

Yes. Ambill works alongside Tally, Zoho Books and SAP. The signing itself happens in Ambill, with your organisation's certificate.

Do I still need a USB token?

No. Ambill Sign uses a document signer certificate (.pfx) uploaded once by your organisation, so there is no token to plug in for each signing session.

Can invoices be signed automatically when they are created?

Automatic signing is coming soon. Today, finance teams select invoices in Ambill and sign them in batches with one password entry.

Is there a per-signature fee?

No. Ambill Sign has simple pricing with no per-signature fees. Talk to us for details that fit your volumes.