Skip to main content

Interactive example · Accounting

Client onboarding for accountants that does the chasing for you

New-client onboarding in most practices is a PDF, three follow-up emails and a phone call to ask whether they're a company or a trust. The client finds it tedious, and so does whoever is doing the chasing. Below, a fictional Bendigo practice does it differently. Try it as the client, then look at what the practice sees.

In short

A client onboarding system for an accounting practice collects a new client's details, entity information, documents and signed engagement letter in one guided flow that adapts to whether they're an individual, sole trader, company, trust or SMSF. It creates the practice's follow-up tasks automatically and shows exactly what's still outstanding.

Interactive demo: Client onboarding for accountants

Live demo · Whitlock & Rowe Accountants, Bendigo is a fictional business with sample data. Nothing you do here is saved or sent.

Whitlock & Rowe Accountants

Bendigo, Victoria

Step 1 of 5 · About you

About you

Tell us who we'll be working for. The rest of this form adjusts to your answer.

I'm setting up as
Progress saves as you goAbout 6 min left

Demo: nothing you type leaves this page.

This demo describes software, not accounting or legal obligations. How you collect tax file numbers, verify identity and word engagement letters depends on your professional standards and your advisers. The demo never asks for a TFN or real ID, and nothing you type leaves the page.

What you just used

Every screen is a decision about how the work runs

  1. Questions that follow the entity

    An individual isn't asked for an ABN. A trust is asked for its deed and trustee. An SMSF gets audit questions. The flow reshapes itself, so clients answer fewer questions and the practice gets complete answers.

  2. Details checked, not just typed

    An ABN lookup fills the entity name, GST status and registration from the public register, which catches the typo before it reaches the ATO. In the demo the lookup is simulated.

  3. A document list built from the answers

    The list is built from the answers: a trust deed for a trust, an investment strategy for an SMSF, bank statements for a sole trader. Clients upload from a phone, and the practice sees what's in and what's missing without opening an inbox.

  4. Engagement letter scoped and signed in the flow

    The scope is written from the services the client picked, and they sign it on the spot. The tax agent authority is part of the same step, so it isn't a separate chase.

  5. Tasks created before anyone opens the file

    Add to the ATO client list, request the prior-year return, connect Xero, schedule BAS reminders. The practice side builds the to-do list from the client's answers and assigns it.

  6. Sensitive data kept out of email

    Tax file numbers and identity documents are collected in a secure portal after sign-up, never by email or an ordinary web form. That's a Privacy (Tax File Number) Rule obligation, and clients notice when it's taken seriously.

Built for you

Your rules, not a template's

Built for your practice, it would follow your process:

  • Your engagement letter wording, fee structures and terms, reviewed by you before launch
  • Your service lines and the questions each needs, including SMSF, payroll and advisory
  • Hand-off into your practice management system where it has an API, such as Karbon, FYI or XPM
  • Reminders that chase missing documents by email and SMS, politely, until they arrive
  • Business clients walked through the ATO's client-to-agent linking step by step
  • Your branding, on your own domain, so clients trust the link they're sent

Connects to what you already use

Where a tool offers an API or a calendar feed, the build talks to it directly. Your data stays in accounts you own.

  • Xero
  • MYOB
  • QuickBooks
  • Karbon
  • FYI
  • Xero Practice Manager
  • DocuSign-style e-signing
  • SMS
  • Microsoft 365

Custom onboarding, a practice platform, or PDFs by email?

Practice platforms such as Ignition, Karbon and FuseSign cover parts of this well, and many practices should start there. Custom work makes sense when the pieces don't join up.

CriteriaPDF forms by emailPractice platform featuresCustom onboarding flow
Adapts to entity typeNo; one form for everyonePartly, with templatesFully, question by question
Document chasingManualAutomated in some toolsAutomated, from the client's own list
Engagement letterPrinted, signed, scannedE-signed, often in a separate toolScoped and signed in the same flow
Practice tasksSet up by handVia integrations, where they existCreated from the answers
Sensitive data handlingTFNs and IDs end up in inboxesSecure, within the platformSecure, designed around your obligations
Best whenYou take on a few new clients a yearYour process fits the platform you already pay forYou onboard steadily and the gaps between tools cost hours

How we'd build yours

Fixed price, agreed before we start

  1. Walk through your current onboarding

    We look at every form, letter and email a new client gets today, and where the practice waits on them. That becomes the flow's first draft.

  2. Fix the scope and the price

    Which entity types, services and integrations are in the first version, written down with one fixed price you approve before we start.

  3. Build it, then run real clients through it

    A few new clients go through it alongside your current process, with you watching what lands on the practice side. Wording gets tightened where clients hesitate.

  4. Switch over and measure the chasing

    Once it's the default, we track time from first contact to a complete file. That's the number it exists to shrink.

What moves the price

Custom work is quoted individually, at a fixed price, once the scope is written down. These are the things that make the biggest difference.

Entity types and services
Each adds its own questions, documents and letter clauses.
Practice management hand-off
An API integration versus a clean export your team imports.
Identity verification
A third-party verification service adds per-check costs and build time.
Reminder automation
Email-only chasing is simpler than email and SMS with escalation.
Australian app build costs, published openly

When you shouldn't build this

If you take on a handful of new clients a year, a well-written PDF and a phone call is fine, and this would be money spent on the wrong thing. If your practice platform already does onboarding and your team actually uses it, improve the templates before you build anything. Custom onboarding pays off for practices that take on new clients every week and still lose hours to chasing between tools.

Want this, with your name on it?

Tell us how the work runs today. We'll reply within one business day with what we'd build first, what we'd leave out, and whether an off-the-shelf tool would serve you better.

Email

jayson@pixelapps.com.au

Location

Macedon Ranges, Victoria

Serving clients across Australia

Only if a quick call would be easier than email.

What are you after?(optional)
Rough budget(optional)

A range is enough. It helps us recommend the right approach, not the biggest one.

We reply within 24 hours. No obligation, and we never share your details.

Common questions

A guided online flow that takes a new client's details, entity information, documents and signed engagement letter in one place, adapting its questions to the client type, and creates the practice's follow-up tasks automatically. It replaces the PDF-and-email back-and-forth most practices still run.

Yes. The letter's scope is generated from the services the client selects, and they sign it within the same flow on a phone or computer. The signed copy is stored against their record, and the tax agent authority can be captured in the same step.

Only in a system built to protect them. TFNs should never travel by email or an ordinary web form. A secure client portal with encryption, access controls and logging is the right place, and handling must meet the Privacy (Tax File Number) Rule.

Where the practice management system offers an API, a new client can be created there automatically with their details and tasks. Where it doesn't, a clean export your team imports in one step is the fallback.

Often you shouldn't. Those tools are good at proposals and signing. A custom flow earns its place when you need entity-specific questions, document lists and task creation to happen in one sequence, and the gaps between your current tools are costing real hours each week.