Hiring

HR onboarding paperwork: the e-signature stack

HR onboarding is paperwork: offer, contract, policy acknowledgment, and bank or ID confirmations. All of it is ordinary private documentation, so under Regulation (EU) No 910/2014, article 25, none of it can be dismissed for being electronic — and it all fits one envelope flow.

The short answer

Yes: the whole onboarding stack can be run as electronic envelopes, with the same evidentiary value as paper versions under article 25(1) and, in Portugal, article 3(5) of Decreto-Lei n.º 12/2021 via article 376 of the Civil Code. The only ceiling is the same as ever — a rule that requires a special form outside the digital envelope.

The stack, document by document

Offer letter — the premise for signing: what the candidate saw, at which version, when. Keep it in the same envelope as the contract so versions match.

Contract + annexes — the three moving parts again: identity binding, content binding, verifiable time. Under RFC 3161, a digest is stamped at the moment of signing, so the contract’s text is a point in time, not a drawer copy.

Policy acknowledgment — what the candidate read, and when: the session-based ceremony log with the drawn signature, the signing trace, the truncated IP address and the device details can show that the acknowledgment happened, not merely that a signature exists somewhere.

Bank or ID groundwork — beyond a document to sign, an actual registry or procedure; these usually sit outside the e-signature scope entirely, so treat them as their own track.

Retention and the envelope flow

Retention: on this platform, originals, per-signature revisions and sealed finals are kept under the customer's retention settings — default maximums of 5 to 20 years by document type — and erased afterwards with cryptographic proof of erasure. Employment records benefit because the retention is kept provable, not just because of the e-signature itself.

Flow HR actually runs: one envelope per hire. The candidate signs on their phone with no account, via a one-time link; HR’s part follows right after; the pack lands completed, with the PAdES level actually reached recorded in the evidence pack, and a CS-verification link is appended for anyone auditing the trail.

What to avoid

Scattershot signatures: signing every document separately, losing the version control an envelope buys. Each document signed digitally twice or three times over becomes a risk.

The ambient assumption that the worker’s signature covers everything from three years of extra work: it doesn’t; the document to be signed is the one you actually send.

Personal data regimes: handling PII inside the envelope is the platform’s job (the ceremony evidence is stored), but how you use it in the employment file can be its own track; check that the envelope respects the data-retention rules your PII regime asks for.

Sources

  • Regulation (EU) No 910/2014, articles 25 and 41 — CELEX 32014R0910.
  • Decreto-Lei n.º 12/2021 (Portugal), article 3.
  • Código Civil português, artigo 376.º.
  • ESIGN Act, 15 U.S.C. §7001.

This is an explanation of the frameworks, not legal advice.

Read next

Signing an employment contract electronically — what the law allows

The contract itself: the deeper legal context behind it.

What a qualified timestamp is: RFC 3161 and eIDAS article 42

Why embedded validation data matters for records that must stay unaltered.