Finish signing
Await signing-session closure and identify the final set; exclude in-progress drafts.
MOBILE-ID · TRUSTED LTANS
eContract & Digital Signature
Preserve contracts, signatures and validation material after the signing workflow closes.
Problem and records to preserve
Years later, certificate paths and status material needed for signature validation may be missing.
SYNTHETIC CASE
Synthetic signed-contract case
SIGN-SYN-001| Element | Illustrative scope |
|---|---|
| Decision makers / users | Legal teams, contract operations and signing-platform owners |
| Source system | eContract / signing platform |
| Revision | Byte changes create another revision; detached signatures must bind the correct document. |
| Record relationship | A post-signing amendment is a new linked object, never altered old bytes. |
Sector-specific record journey
Freeze bytes
Freeze signed bytes, detached signatures and attachments with signing transaction/revision IDs.
Collect material
Collect authorized certificates, status data and existing timestamps; identify missing material.
Preserve
Submit under agreed custody and retain archiveId/jobId/evidence history; no retrospective-proof claim.
Export with authority
Export the authorized contract/revision; subsequent amendments are new linked objects.
Delivered artifacts
| Recipient | Artifact |
|---|---|
| Source system | Intake receipts, source/revision-to-archiveId/jobId mappings and per-item errors. |
| Package recipient | Contract/annex set, revision relationships and authorized validation material. |
| Record owner / operations | Completed/outstanding inventory, applied decisions and report references; no automatic legal conclusion. |
Rights, retention and deployment
Signatory status does not grant every user export rights.
Preservation evidence does not automatically convert signatures to PAdES-LTA or CAdES-LTA; signature-specific processing needs its own scope.
Retention authority and exit
The owner must approve the retention authority and trigger for this record class: Signing workflow ends and documents/validation material are handed over.
Sample dossier and tests
Synthetic text files exercise inventory and hashing; they are not signed contracts, real records or ERS/XMLERS.
Download synthetic dossier| Test | Expected outcome |
|---|---|
| Intact | File inventory, size and SHA-256 match the manifest. |
| Missing / changed bytes | The verifier rejects the package without claiming inventory success. |
| Sector business case | Missing detached signatures or annexes must appear in inventory findings. |
Scope a PoC for this dossier
Test detached signatures, missing attachments and incomplete status material; reports must give reasons instead of blanket validity.
Prepare a sector-specific requestFinalization point and specific acceptance
| Control point | Requirement |
|---|---|
| Source event | Signing workflow ends and documents/validation material are handed over. |
| Revision / decision | Byte changes create another revision; detached signatures must bind the correct document. |
| Test and expected result | A signature from another transaction or changed annex cannot yield successful verification. |
Sample inventory/hashing checks bytes only. Authorization, decision and state cases must run in the provisioned test environment before business acceptance.
Source-system handoff record
| Information | Value / decision |
|---|---|
| Record | SIGN-SYN-001 |
| Source system | eContract / signing platform |
| Revision relationship | A post-signing amendment is a new linked object, never altered old bytes. |
| Recipient and output | Contract/annex set, revision relationships and authorized validation material. |
| Rights and authority | Signatory status does not grant every user export rights. |
| Required rejection test | Missing detached signatures or annexes must appear in inventory findings. |
Sector information is source business metadata, not automatically new REST fields. Agree field mapping and ownership before a PoC.