Sări la conținut
    Back to blog
    July 26, 2026 5 min read Stefan

    Internal e-stamp: documents signed digitally, no paper involved

    The tenant's e-signature, drawn once in Settings, is applied automatically to NIR, PV, Borderou and Aviz, with a verification code on every PDF.

    #vanagreen
    #reciclare
    #documente
    #semnatura-electronica

    A NIR (Notă de Recepție și Constatare de Diferențe, the Romanian goods-receipt note) or Borderou (payment/handover slip for individuals) generated by VanaGreen ultimately has to look like an official document — with the stamp and signature of the company that issued it. Until now, that meant a manual step: download the PDF, print it, stamp it, sign it, maybe scan it back in if it needs to go out by email. For an operator generating dozens of documents a day, that step repeats just as many times.

    VanaGreen removes the manual step with an internal e-stamp — the company's signature, drawn once, applied automatically to every document generated.

    What this is, technically and legally

    It's worth being clear from the start about what kind of signature this is: an advanced electronic signature, under Romanian Law 214/2024, not a qualified eIDAS signature (the kind that requires a certificate issued by an accredited provider, like certSIGN). The distinction matters legally — but it changes nothing about document validity. NIR, Borderou, and Aviz are already valid supporting documents through the identity of whoever created them and the app's internal audit log (per OMF Order 2634/2015, Annex 1, point 11); the e-stamp doesn't replace that legal basis, it just adds a visual, verifiable proof of authenticity and integrity on top of it.

    The tenant draws or uploads their signature once, in Settings. At that point, the platform automatically generates a cryptographic key pair belonging to that tenant (not an account with an external provider) — the private key is kept encrypted, never directly visible.

    Selective application, off by default twice over

    Activation is deliberately conservative, in two layers. First: finishing the setup (drawing the signature) does not automatically turn on signing — it stays off until the tenant explicitly flips a separate switch. Second: even once turned on, signing only applies to the document types the tenant checks off — NIR/PV, Borderou/payment order, Aviz — not globally, across every document generated.

    If the legal representative changes at some point and the tenant redoes the setup with a new signature, the old key pair is revoked and signing automatically switches back off — an old signature can't stay active under a representative who's no longer valid, without an explicit reconfirmation.

    A verification code, not just an image

    Every signed document gets a visible verification code on the PDF, alongside the signature image. The code isn't decorative — it's the fingerprint of the cryptographic key used to sign. Behind the scenes, the platform computes a hash of the exact content of the generated PDF and cryptographically signs it with the tenant's key; the result is stored separately, so at any point it can be verified whether today's document matches exactly what was originally signed, or whether its bytes have changed since. It's a form of tamper detection, not just a picture of a signature.

    Document generation never depends on signing succeeding — if signing fails for any reason, the document is still generated, just without the e-stamp. An extra step is never allowed to block an essential workflow.

    Why it matters for an operator

    In practice, a document coming out of VanaGreen with the e-stamp turned on skips the print-stamp-sign-scan cycle entirely. It comes out ready, with the company's signature already applied, verifiable through a code anyone can check. For an operator with a high daily volume of documents — especially ones sent straight by email to partners or authorities — that's one manual step less on every single document, with no compromise on traceability or authenticity.

    Want to discuss how this applies to your process?

    Schedule a technical audit

    Related articles