Product

The product is the proof.

Every design decision answers one question: how do we make statutory signing impossible to get wrong, and provable after it's done?

The workflow

Five steps, one queue, no guesswork.

  1. 01

    Drop in the document

    Open any PDF — typed or scanned. Sealixa reads the real page contents, not a pasted template, and tells you what kind of document it sees before you commit.

  2. 02

    Add each signatory once

    A name, a type (person / role), a page range, optional keywords, an optional DSC cert CN to bind to, and a recipient email for confidence delivery. Sealixa resolves every signature block across the range. Save each signatory to the firm's library and recall it for the next client in two clicks.

  3. 03

    Verify where each signature lands

    Every signature box is drawn directly on the rendered page. A red panel lists any overlap between signatories before a single byte is signed. You approve what you see, not what you assume.

  4. 04

    Insert your DSC token

    One Class 3 USB token at a time. Sealixa waits for each signatory's token, signs that signatory's pages, and prompts you to swap in the next. Token identity is tied to the cert, never to insertion order.

  5. 05

    Sign, verify, audit, notify

    Every signature is cryptographically re-verified after signing — checked intact and valid before it's reported as signed. Attach the UDIN you generated on the ICAI/ICSI portal to each signature, and the full session writes to a CSV and JSON audit trail. Send each director a confidence report — automatically, once per completed session, from the firm's own mailbox.

Features

Built for the way statutory signing actually happens.

Template-free anchoring

No Word templates, no layout assumptions. Sealixa finds the real signature line using name context and page position — anchored to the actual document.

Swappable DSC tokens

One token per USB port is a Windows reality, not a bug. Sealixa pauses for each signatory's token, signs their pages, then prompts for the next — no crossing wires.

Full audit trail

Every page, every signature, every second recorded as CSV + JSON. Exportable proof of who signed what and when — never the PIN. Complete and offline.

Scanned-document OCR

Signed-in-ink PDFs become signable again. OCR recovers the text layer on scanned pages so the anchor engine works on the filings typed by hand. It runs only on pages with no text — never on typed documents.

Caveat: OCR quality depends on the scan — low resolution or blurry scans can miss words, and a name already overlaid by wet ink may not read cleanly. Any page where the block cannot be confidently recovered is flagged for your review before signing.

Overlap detection

A signature can't land twice. Sealixa detects when two signatories' blocks collide and flags them before you sign — not after the registrar rejects the filing.

Timers that tell the truth

Per-step and per-signature timing, measured in seconds. Pilot it yourself, benchmark your own workflow, and decide the ROI with your own numbers.

Portfolio workspace

One dashboard across the practice: documents, pages, signatures, verified count, and UDINs per client — the numbers you actually raise an invoice from, rolled up from the audit files.

Director-confidence reports

From the audit trail, a per-person report of every document and page where their DSC was used — with the signed PDFs bundled in, and optionally emailed to them from your own mailbox.

UDIN tracking per signature

Record the UDINs you generate on the ICAI/ICSI portal against each signature, keep them in the audit trail, and roll them up per client for billing. UDINs are optional unless your firm chooses to enforce them — a setting, off by default.

If you choose, it emails

Confidence emails fire from your own firm mail account via your SMTP settings — stored on your machine, never with us. Off by default; the audit trail and packages work fully offline regardless.

Made for practices

Your firm's signatories, saved once, reused forever.

  • Save a signatory once

    Name, type, keywords, page range, DSC cert CN, and recipient email — stored in the firm's local library.

  • Recall on the next client

    Load the preset, click Add Anchor, and Sealixa resolves the same block in the new document.

  • Never drift

    No template files to maintain when annexures reorder — the anchor always re-resolves against the real pages.

  • Bound to the right cert

    A signatory's DSC cert CN travels with their input, so the token that signs their pages is the one bound to them.

Try it on the filing you're dreading to sign today.

The trial is the full product for 14 days — bring your worst document.

Request the trial build