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
  • 💙Partners
    • Partner Program
Powered by GitBook
On this page

Was this helpful?

  1. eSignatures
  2. eSigning Laws & Compliance

Australia: Electronic Transactions Act (ETA) ✅

Portant's Compliance with the Electronic Transactions Act (ETA) in Australia

Is Portant compliant: Yes ✅

The Australian Electronic Transactions Act (ETA) governs the use of electronic signatures in Australia, ensuring that electronic documents and signatures are legally equivalent to paper-based ones when specific criteria are met. This article explains when and where the ETA applies, who it affects, and highlights Portant's compliance features, giving you confidence that our eSignature solution meets the ETA requirements.


Overview of the Electronic Transactions Act (ETA)

The ETA was enacted to facilitate electronic commerce across Australia and to make electronic signatures legally binding. The Act applies at both the federal level (Electronic Transactions Act 1999) and state/territory levels, with each state adopting variations based on the federal model.

  • Location: Australia-wide, with federal and state-specific adaptations.

  • Purpose: To ensure electronic records and signatures are legally recognized in the same way as handwritten signatures and paper documents.


When and Where the ETA Applies

The ETA applies to a broad range of transactions, provided all parties consent to use electronic means. Below are key criteria for the ETA’s application:

  • Type of Transactions: It applies to most business, commercial, and personal transactions where documents would traditionally require written signatures, including contracts, agreements, and acknowledgments.

  • Jurisdictions: The federal ETA applies to Commonwealth government agencies, while each state and territory has an ETA governing its electronic transactions.

  • Consent to Use Electronic Signatures: All parties must agree to conduct the transaction electronically, either explicitly or implicitly.


Key Compliance Requirements and Portant’s Approach

To comply with the ETA, Portant’s eSignature solution provides essential features to fulfill the Act’s primary requirements:

Compliance Requirement
Description
Portant’s Compliance Features

User Consent

Parties must agree to the use of electronic means.

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

Document Integrity

Documents must remain unaltered post-signature.

Document Integrity Verification: Portant ensures documents cannot be modified after signing.

Audit Trails

Records of the signing process serve as proof.

Audit Trails: Detailed logs document each stage in the signing process, including timestamps.

Time Stamping

A verifiable time and date should accompany each signature.

Time Stamping: Portant timestamps all signatures with a verifiable date and time.

Data Protection Compliance

Data must be securely stored and handled to protect personal information.

Data Protection: Portant uses encryption and secure storage to ensure data compliance.

Role-Based Access Control

Limits who can access, sign, and manage documents.

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


Practical Considerations for Using eSignatures in Australia

While Portant’s eSignatures are designed to comply with the ETA, there are several considerations to ensure the signatures are legally valid and enforceable:

  1. Obtaining User Consent

    • All parties must agree to sign electronically. Portant’s user interface clearly prompts for consent, ensuring users meet this ETA requirement.

  2. Maintaining Document Security

    • Signed documents should remain unaltered after the signing process. Portant’s Document Integrity Verification feature locks signed documents, protecting them from any post-signature modifications.

  3. Keeping Audit Trails for Record

    • Audit logs provide a record of actions taken during the signing process. Portant’s audit trail feature securely logs each step, creating a verifiable record for future reference.

  4. Understanding State and Territory Variations

    • The ETA is a federal law, but states and territories may have unique requirements. Users may need to review local adaptations of the ETA to ensure compliance, especially for highly regulated transactions.

  5. Determining Applicable Document Types

    • While the ETA generally applies to most types of transactions, certain legal documents (like wills, powers of attorney, and documents requiring a notary) might still require handwritten signatures.


Conclusion

Portant’s eSignature solution fully supports compliance with the Australian ETA through essential features like consent, security, and tracking mechanisms. By meeting ETA requirements, Portant ensures that your electronic signatures are legally enforceable and secure across Australia for a wide range of transactions.

For further assistance on using eSignatures in Portant, or if you have any questions about compliance, please don’t hesitate to contact our support team.

PreviousUK: eIDAS Regulation and Electronic Communications Act 2000 ✅NextNew Zealand: Electronic Transactions Act (ETA) 2002 ✅

Last updated 7 months ago

Was this helpful?

✒️