Authority to act, in writing, in minutes.
From new-client authorities to renewal acknowledgements to claims declarations, KoalaDoc gives brokers a signing workflow that satisfies ASIC RG 104, the NIBA Code, and AFCA's evidentiary expectations.
The paperwork your team sends every week.
Client authority to act
New-client onboarding bundles with authority, FSG acknowledgement, and privacy notice.
FSG / PDS acknowledgement
Verifiable client acknowledgement that the FSG and relevant PDS were provided.
Duty of disclosure declarations
Signed acknowledgement of the s21 Insurance Contracts Act duty of disclosure, kept on file.
Claims declarations
Claimant declarations with timestamp, IP, and tamper-evident sealing.
Renewal authorities
Annual renewal authority bulk-sent to your book ahead of inception.
Premium funding agreements
Funder-specific agreements signed in the same envelope as the broker authority.
From draft to signed PDF in minutes.
- 1
Pull from your AMS
Import client list as CSV from your broker software.
- 2
Bulk send authorities
Per-client envelope with personalised cover values.
- 3
Track and remind
Real-time status and automated reminders.
- 4
File 7 years
RG 104 record-keeping covered by long-term retention.
What your regulator expects — and how KoalaDoc maps to it.
We describe how our features support each obligation. We don't claim certifications we haven't earned — see the security page for the full picture.
Corporations Act 2001 (Ch 7) + ASIC RG 104 / RG 175
ASICWritten client authorities with signer identity and tamper-evident sealing, retained long-term and exportable per client for the 7-year record-keeping period.
Insurance Contracts Act 1984 — Duty of Disclosure
Cth statuteVerifiable signed acknowledgement of the s21 duty of disclosure, sealed with hash and UTC timestamp.
General Insurance Code of Practice / NIBA Code of Practice
ICA · NIBAWritten client communications and complaints handling records captured with an immutable audit trail, supporting Code obligations on transparency and timeliness.
AFCA evidentiary standards
Evidence Act 1995 §146 · AFCA RulesHash-chained, UTC-timestamped audit trail admissible to AFCA and Australian courts under the s146 presumption for computer-produced records.
Privacy Act 1988 / APPs (incl. sensitive info)
OAICClaimant PII, including sensitive health and financial information, stored AES-256 encrypted in Sydney with role-based access by broker.
The questions we hear most.
Will AFCA accept a KoalaDoc-signed authority?
Yes. AFCA accepts electronically signed documents that meet the Evidence Act §146 integrity standard. KoalaDoc-signed documents meet that standard by default through our hash chain and UTC timestamping.
Can we bulk-send renewal authorities?
Yes. Upload a CSV from your broker AMS and we'll generate a personalised envelope per client, each with its own audit trail when signed.
Where is client information stored?
All client information is stored in Sydney (ap-southeast-2), encrypted at rest with AES-256, and never leaves Australia.
Compliance isn't a tick-box. It's the foundation.
ETA 1999
Every envelope satisfies the Electronic Transactions Act 1999, with tamper-evident PDFs and trusted UTC timestamps.
Sydney data residency
Your documents never leave Australia. Encrypted at rest with AES-256, hosted in ap-southeast-2.
Privacy Act 1988
APP-aligned data handling. Export and deletion workflows for end-to-end Australian privacy compliance.
Breach notifications
Built-in incident response with the Notifiable Data Breaches scheme — owners and admins are alerted immediately.
Try KoalaDoc free for seven days.
No credit card. No subscription. Send your first envelopes on us and decide afterwards.
Get started for free