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 and approve documents in HubSpot
      • Generate Documents from any Custom Object 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
    • Fillable PDF
  • 💡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
    • Review and Approve Documents
    • 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?

  1. eSignatures
  2. eSigning Laws & Compliance

New Zealand: Electronic Transactions Act (ETA) 2002 ✅

Portant's Compliance with New Zealand’s Electronic Transactions Act (ETA) 2002

Is Portant compliant: Yes ✅

In New Zealand, electronic transactions are governed by the Electronic Transactions Act 2002 (ETA), which ensures that electronic signatures and records hold the same legal standing as their paper counterparts. The Act facilitates electronic commerce and communication across New Zealand, enabling businesses and individuals to carry out legally binding transactions online. This article provides an overview of the ETA, explains its requirements, and highlights how Portant’s eSignature solution aligns with the standards set out by the Act.


Overview of the Electronic Transactions Act (ETA) 2002

The Electronic Transactions Act 2002 was enacted to support New Zealand’s growing digital economy by providing a legal framework for electronic signatures and records.

  • Location: New Zealand

  • Purpose: To ensure electronic signatures and records are legally equivalent to handwritten signatures and paper documents, provided they meet certain requirements.

  • Scope: The ETA applies to most types of contracts, agreements, and transactions, including both business and personal exchanges. It applies to electronic records and signatures across all sectors, with certain document types excluded.


When and Where the ETA Applies

The ETA applies in a broad range of digital transactions in New Zealand, subject to the following conditions:

  • Type of Transactions: The ETA covers commercial, personal, and governmental transactions where documents traditionally require a written signature, including contracts, acknowledgments, and approvals.

  • Jurisdictions: Applies to New Zealand-wide transactions, enabling electronic records and signatures to be legally binding across the country.

  • Consent to Use Electronic Signatures: The Act requires that all parties involved consent to conduct the transaction electronically and to use electronic signatures.


Key Compliance Requirements and Portant’s Approach

Portant’s eSignature solution is designed to ensure compliance with the requirements of the ETA, supporting legally binding and secure electronic signatures for transactions in New Zealand. Here are the primary compliance requirements of the ETA and how Portant meets each:

Compliance Requirement
Description
Portant’s Compliance Features

User Consent

All parties must agree to use electronic signatures.

User Consent Mechanisms: Portant requires users to confirm consent before proceeding with electronic signing.

Document Integrity

Signed documents must remain unaltered after signature.

Document Integrity Verification: Portant ensures documents cannot be modified once signed.

Audit Trails

Records of the signing process provide evidence of authenticity.

Audit Trails: Portant maintains detailed logs of each step in the signing process, including timestamps.

Time Stamping

Verifiable date and time of the signature enhance legal authenticity.

Time Stamping: Portant applies a verifiable time and date to each signed document.

Data Protection Compliance

Personal data must be securely managed and stored.

Data Protection: Portant uses industry-standard encryption and secure storage to protect user data.

Role-Based Access Control

Limits document access to authorized individuals.

Role-Based Access: Portant restricts viewing, signing, and management permissions to designated users.


Best Practices for Using eSignatures Under the ETA

Portant’s eSignature solution provides essential features to ensure compliance with the ETA, but there are several considerations for effective and compliant use:

  1. Confirming Consent from All Parties

    • Each party must agree to use electronic signatures for the transaction. Portant’s interface includes clear consent prompts to support this requirement, confirming each user’s intent to sign electronically.

  2. Ensuring Document Security and Integrity

    • Documents must remain unaltered after signing to retain legal validity. Portant’s Document Integrity Verification feature locks signed documents, safeguarding their authenticity and ensuring compliance with ETA requirements.

  3. Keeping Comprehensive Audit Trails

    • Audit logs provide a record of the signing process, supporting legal validity. Portant’s audit trail feature records each stage of the signing process, including timestamps, to maintain an evidentiary record for future reference.

  4. Understanding Document Exceptions

    • While the ETA applies broadly, certain documents, such as wills, property transactions, and powers of attorney, may still require handwritten signatures. Users should verify if their document type falls under any exceptions to electronic signatures in New Zealand.

  5. Maintaining Compliance with Data Protection

    • Personal data associated with electronic signatures must be handled securely. Portant complies with data protection standards, encrypting user data and securely storing signed documents.


Compliance with Different Levels of Assurance

The ETA does not categorize electronic signatures into levels as strictly as other international standards (e.g., the EU’s eIDAS Regulation). However, Portant’s solution provides assurance features similar to basic electronic signatures, with some functionality compatible with higher-assurance requirements if additional verification methods are needed.


Conclusion

Portant’s eSignature solution is designed to comply with New Zealand’s Electronic Transactions Act 2002 by including essential features such as user consent, document integrity, audit trails, and secure data protection. These features ensure that electronic signatures created through Portant are legally enforceable, secure, and reliable for a wide range of business transactions within New Zealand.

If you have further questions about Portant’s compliance with the ETA or need additional guidance on using eSignatures, our support team is here to help.

PreviousAustralia: Electronic Transactions Act (ETA) ✅NextIsrael: Electronic Signature Law 2001

Last updated 6 months ago

Was this helpful?

✒️