Portant Docs
Launch PortantInstall App in Hubspot ↗︎
Portant Docs
Portant Docs
  • 👋Welcome
  • 🟢Product Updates
  • 🌱Getting Started
    • How to Sign up
      • Sign-up without a Google account
    • Quickstart
    • Ask for Help
      • Support Tickets
      • Support Codes
      • Screenshots
      • Developer Console
      • 400 Error
      • Resolve: API developer key is invalid error
      • How to request a transfer of your Portant account
    • Templates
  • 💫Personalise Documents
    • Adding Hyperlinks
    • Adding Images
    • Use custom tag names
    • Tag Formulas
      • Global tags
      • Tag Formulas
      • Tag IF Statements
    • Invalid Tags
    • Portant AI Content
    • Dynamic Google Sheets Charts
    • Tag Checker
    • Add online payment links
    • Add Stripe Payment Links to Your eSign Portal
  • 🌐Sources
    • Google Forms
      • Add formula fields to your Google Form workflow
      • {{tags}} for Google Forms
    • Google Sheets
      • Google Sheets Auto-create
      • How to source data from multiple Sheets
      • Saving Document Links to your Sheet
      • Data Grouping
    • HubSpot
      • How to install the Portant App in HubSpot
        • How to Add Portant App Cards to HubSpot
      • Create a Document in HubSpot
      • How to manage and select HubSpot Properties
        • Full list of available HubSpot Properties
      • Trigger HubSpot Workflows from Portant
      • Add a Portant Action to a HubSpot Workflow
      • How to view created documents in HubSpot
      • Add multiple line items into a single document
      • Add Deal Tags using Portant document statuses
      • Portant eSignatures + HubSpot
      • Review documents using the Review Block in HubSpot
    • Zapier
    • Glide
    • Webhooks
      • Webhook Data Grouping
    • Xero
    • Copper
      • Installing the Copper integration
      • Create your first Copper workflow
      • Generating your first document from Copper
    • Typeform
    • Tally
  • 📄Template Docs
    • Google Docs
    • Google Slides
    • Microsoft Word
    • Microsoft PowerPoint
  • 💡Use Cases
    • eSignatures Requests
    • Incident Report
    • Quarterly Business Reviews
    • Invoices
    • Convert Form Responses to PDFs
  • ✒️eSignatures
    • Getting Started
    • Request Signatures (without a source)
    • Request Multiple Signatures
    • Customise Signature Request Email
    • Create Preview Links for Signature Requests
    • Resend signature requests
    • Cancel Signature
    • Add Audit to eSignatures
    • Request Info On Signing
    • eSigning Laws & Compliance
      • United States: E-SIGN Act and UETA ✅
      • Canada: PIPEDA and Electronic Transactions Act ✅
      • EU: eIDAS Regulation for Electronic Signatures ✅
      • UK: eIDAS Regulation and Electronic Communications Act 2000 ✅
      • Australia: Electronic Transactions Act (ETA) ✅
      • New Zealand: Electronic Transactions Act (ETA) 2002 ✅
      • Israel: Electronic Signature Law 2001
  • ⚡Automation
    • Workflow Filters
    • Re-run an automation
    • Review Block
    • Converting docs to different file types
      • Microsoft Word (.docx)
      • Microsoft Powerpoint
      • Create PDF outputs
      • Save an output as a Microsoft Excel file (.xlsx)
  • ✉️Emails
    • Share a Doc via Email
    • Email Tracking
    • Send from aliases
    • Send Outlook Emails
    • Customize Your Email Content with HTML Editing
  • 📄Outputs
    • Customize Output File names
    • Auto-filing Output Files
    • Changing Output Folder
    • Search and filter your outputs
  • Deleting Outputs in Portant
  • 🎁Portant Add-ons
    • Data Merge
      • How to set-up a Google Sheets source
        • Data Merge Settings for Google Sheets sources
        • Automatically create documents
      • How to set-up a Google Forms source
        • Data Merge Settings for Google Forms
        • Automatically create documents
        • Edit Response and Pre-filled Response Links
      • Inserting Images
      • Advanced Settings
        • Editing tag names
        • Timezone, date and time format settings
        • Editing the Output Folder
        • Conditional logic for emails
        • Conditional Logic for Data Merges
        • Data Grouping in Portant Data Merge
    • Document Merge - Trello Power-up
  • 👥Teams
    • Creating Your Team
    • Sharing Workflows
    • Creating Folders in the Workflows Tab
    • Managing team permissions
    • Whitelabeling eSign Portal
  • ⚙️Settings
    • Change Language Settings
    • How to Set Up Your Account's Global Formatting Settings
  • Delete Multiple Workflows at Once
  • 💳Billing
    • Update Billing
  • Developer
    • Build with Portant
Powered by GitBook
On this page

Was this helpful?

Is Portant compliant: Yes ✅

In the United Kingdom, electronic signatures and transactions are governed by the eIDAS Regulation (Electronic Identification, Authentication and Trust Services) and the Electronic Communications Act 2000. These laws establish the legal validity and enforceability of electronic signatures, ensuring they are equivalent to handwritten signatures in most scenarios. This article provides an overview of the regulations, explains when they apply, and details Portant’s compliance features to help you securely and confidently use electronic signatures in the UK.


Overview of the eIDAS Regulation and Electronic Communications Act 2000

The eIDAS Regulation and Electronic Communications Act 2000 set the standard for electronic signatures and transactions in the UK, supporting their legality and providing a framework for secure electronic identification. Here’s a quick breakdown:

  • eIDAS Regulation (EU Regulation No. 910/2014 on electronic identification and trust services for electronic transactions)

    • Location: UK and European Union (adapted into UK law post-Brexit).

    • Key Point: Establishes three levels of electronic signatures (Simple, Advanced, and Qualified) to ensure legal recognition and security for electronic transactions.

  • Electronic Communications Act 2000

    • Location: United Kingdom

    • Key Point: Recognizes electronic signatures as legally valid, provided there is intent to authenticate, supporting the enforceability of electronic agreements and transactions.


When and Where the eIDAS Regulation and Electronic Communications Act Apply

These regulations apply in a wide range of digital transactions in the UK. Key criteria include:

  • Type of Transactions: The regulations cover most commercial, personal, and governmental transactions that would traditionally require written signatures, including contracts, agreements, and acknowledgments.

  • Jurisdictions: eIDAS was retained in UK law post-Brexit and applies alongside the Electronic Communications Act to uphold electronic signature validity.

  • Consent to Use Electronic Signatures: Both parties must consent to using electronic signatures for the transaction.


Key Compliance Requirements and Portant’s Approach

To meet the requirements of eIDAS and the Electronic Communications Act 2000, Portant’s eSignature solution includes essential features for compliance:


Compliance with eIDAS Signature Levels

Under the eIDAS Regulation, electronic signatures are categorized into three levels: Simple Electronic Signature (SES), Advanced Electronic Signature (AES), and Qualified Electronic Signature (QES). Each level provides varying degrees of security and legal assurance. Portant’s eSignature solution primarily supports SES, which meets the needs of most business transactions, and includes some AES-compatible features. Here is a breakdown of Portant's compliance across these levels:

Note: While Portant fully supports SES for most business transactions, AES or QES levels may be necessary for high-assurance transactions, particularly those requiring unique signer identification. Users needing full AES or QES compliance can consider adding external verification or a qualified trust provider for additional assurance.

By understanding these compliance levels, you can confidently use Portant’s eSignature solution for a range of business transactions in the UK.


Practical Considerations for Using eSignatures in the UK

While Portant’s eSignature solution is designed to meet eIDAS and the Electronic Communications Act standards, there are several considerations to ensure secure and compliant electronic transactions:

  1. Confirming User Consent

    • All parties must agree to the use of electronic signatures. Portant’s user consent prompt ensures compliance by confirming each user’s intention to sign electronically.

  2. Ensuring Document Security

    • Signed documents must be protected against tampering. Portant’s Document Integrity Verification feature locks the document after signing, preventing modifications and preserving authenticity.

  3. Keeping Comprehensive Audit Trails

    • Detailed audit logs are essential for proving a document’s validity. Portant’s audit trail feature securely records each action in the signing process, including timestamps, to create a verifiable record.

  4. Choosing the Right Level of Signature

    • The eIDAS Regulation outlines three levels of signatures:

      • Simple Electronic Signature (SES): Basic level, suitable for most business transactions.

      • Advanced Electronic Signature (AES): Provides a higher level of security, meeting strict identification and control criteria.

      • Qualified Electronic Signature (QES): The highest level, legally equivalent to a handwritten signature in court and requires a qualified certificate from a trust service provider.

    • Portant’s eSignatures generally fall under SES but can support AES, depending on the security needs of the transaction. For high-assurance transactions, users may want to consider QES options.

  5. Understanding Document Exclusions

    • Certain legal documents, like wills, deeds, and property transfers, may still require a handwritten signature. Users should verify if their document types fall under exceptions to electronic signatures.


Conclusion

Portant’s eSignature solution supports compliance with the UK’s eIDAS Regulation and the Electronic Communications Act 2000, providing secure, legally valid electronic signatures for a broad range of transactions. With essential features like user consent, document security, and audit trails, Portant ensures that electronic signatures are enforceable and reliable in the UK.

If you have additional questions about compliance or need further assistance with eSignatures in Portant, our support team is here to help.

Last updated 6 months ago

Was this helpful?

Compliance Requirement
Description
Portant’s Compliance Features
Signature Level
Description
Portant’s Compliance

User Consent

Parties must agree to electronic transactions and signatures.

User Consent Mechanisms: Portant prompts users to confirm consent before signing electronically.

Document Integrity

Documents must remain unaltered after signing.

Document Integrity Verification: Ensures documents cannot be modified post-signature.

Audit Trails

Logs of the signing process serve as proof of authenticity.

Audit Trails: Portant maintains detailed logs of each action during the signing process.

Time Stamping

Verifiable time and date required for legal authenticity.

Time Stamping: Portant provides verifiable timestamps on each signed document.

Data Protection Compliance

Personal data must be protected under UK GDPR standards.

Data Protection: Portant uses encryption and secure storage to protect personal data.

Role-Based Access Control

Controls who can access, sign, and manage documents.

Role-Based Access: Portant restricts document access and management to authorized users only.

Simple Electronic Signature (SES)

Basic level, suitable for most business transactions.

Compliant: Portant provides SES functionality for everyday business transactions, including user consent, document integrity, and audit trails.

Advanced Electronic Signature (AES)

Higher security level, requiring strict identification and control criteria to uniquely identify the signer.

Partial Compliance: Portant supports some AES features (such as audit trails, integrity verification, and timestamping) but does not provide biometric verification or advanced signer identification, which may be required for full AES compliance.

Qualified Electronic Signature (QES)

Highest level, legally equivalent to handwritten signatures in court, requires a qualified certificate from a trust service provider.

Not Compliant: Portant currently does not provide QES, as it requires certificates from a qualified trust service provider under eIDAS.

  1. ✒️eSignatures
  2. eSigning Laws & Compliance

UK: eIDAS Regulation and Electronic Communications Act 2000 ✅

Portant's Compliance with the UK's eIDAS Regulation and Electronic Communications Act 2000

PreviousEU: eIDAS Regulation for Electronic Signatures ✅NextAustralia: Electronic Transactions Act (ETA) ✅